1.5.1 binary release for Synology DSM7

[jimmyherron]

Hi

After going through reddit, the github issues, etc I feel like that not providing a downloadable version of the synology packages for manually installation is really killing usability.

Currently, sync does not work at all properly on the 1.4 version from package manager, there is no way to upgrade without building the package ourselves.

[jx-mega]

Hello, thanks for your feedback. We do have a 1.5.1 version pending approval from NAS with several improvements (including a total renewal of the communication between server and clients). Hopefully, it will be released in the near future.

[voldemarz]

mega-cmd is barely working in Synology DSM 7.1-42661. Have two syncs set and they work, but having issues configuring, quarying.

Here's the list of things that does not work:

• Can't quary existing syncs (don't see any documented way, "sync --show-handles" suggested email support doesn't work).
• Can't delete existing sync with "-d" flag as suggested here https://github.com/meganz/MEGAcmd/issues/257
• mega-cmd sometimes reports that server is down when it isn't, process visible in explorer and files are being synced
• Sometimes when in mega-cmd interactive shell, after a "sync" command, on first key press, a server log message gets appended to the text being typed.

Won't create a new issues for these in GitHub and will wait for updated package. Just pointing out some of current issues.

[abtracy91]

+1. If you've been waiting for approval from Synology for this long, proving the binary package would be quite nice. That way people who are having problems with known issues could do a manual install, bypassing the Synology store.

[donblas]

+1 As first fixed release has been submitted to Synology in Feb 22 - and still nothing has been published - I really think it's worth to release a package on your own, as many vendors do. Currently Megacmd is almost unusable for DSM7 users since one year, despite a fixed code. Time to stop this.

[Gerdal]

As you can see Synology doesn't give a damn about mega.nz users. Official (Synology approved) packages are released, at least so far, every 2 years. I agree that mega.nz should release its own packages for manual installation in DSM. This would be the easiest way to have an always up-to-date client. The other option I have found is to install mega.nz from Entware (opkg). It's a bit breakneck, definitely unofficial and unsupported solution, but it works. I've provided a link to the instructions for those interested:

https://github.com/Entware/Entware/wiki/Install-on-Synology-NAS

At last I have a properly working client with working sync command, etc.

And I was disappointed with Synology Team. DSM is great, NAS and router too, but the frequency of application updates.... especially the 3rd party ones.... definitely leaves a lot to be desired....

[donblas]

The other option I have found is to install mega.nz from Entware (opkg).

Thanks, I will try it. I have build 1.5.1 for DS918+ (DSM 7.1) using this guide but, even if apparently package is created with success, I still have constant seg faults, error codes and a non-working service.

And I was disappointed with Synology Team. DSM is great, NAS and router too, but the frequency of application updates.... especially the 3rd party ones.... definitely leaves a lot to be desired....

Agree. But I don't think this can't be changed, as it's not related to MEGAcmd package only. What 3rd party app vendors can do (and mainly do) is releasing their own packages. Hope that MEGAcmd team will align to this.

[Gerdal]

Thanks, I will try it. I have build 1.5.1 for DS918+ (DSM 7.1) using this guide but, even if apparently package is created with success, I still have constant seg faults, error codes and a non-working service.

I had the same issues with myself built package for DS220+. I don't know where is the difference but package from entware works perfectly fine. Today is third day and mega-cmd-server is still working without any issues, crashes, segfaults etc.

Agree. But I don't think this can't be changed, as it's not related to MEGAcmd package only. What 3rd party app vendors can do (and mainly do) is releasing their own packages. Hope that MEGAcmd team will align to this.

I agree and I hope that the day will come when MEGAcmd team will start build release packages also for Synology users :)

[romanr]

Any news on this? Is it in approval or was abandoned?

[JnHkstr]

Any news on this? Is it in approval or was abandoned?

would like to know as well. I asked Synology but they just report that they don't support 3rd party packages. Also Asked Mega but got no response

[romanr]

The package 1.6.1 was done two weeks ago. Synology support wrote In response to my ticket:

We have now released version 1.6.1 of MEGAcmd and we have sent it to Synology. It depends on Synology to update the website with the packages

So if @JnHkstr says Synology don't support 3rd party packages, what is going on?
And here https://github.com/meganz/MEGAcmd/tags are 1.6.1 releases for all platforms except Synology. Why is excluded from releases on Github?

[romanr]

I got 1.6.1, installed on DSM 7.1.1 and it crashes on start. #799

I guess this is the bottom, in a year all they produced is a failing update. There's nothing to wait for from Mega.

[JnHkstr]

i got this follow up response:

The fact the package is in the package center means Synology will check the package before release it, but not update it directly. If there must be an update, they should provide it to Synology. I assume this is a discussion between our devs and the MegaCMD devs, but we do not have any information at our level, I am sorry. If not version has been pushed by developpers, then we can not publish any update.

[polmr]

Newer releases of MEGAcmd for NAS (Synology/QNAP) featuring several improvements and fixes, can now be downloaded from here: https://mega.io/nas. Note: Non English version website may still show old links to QNAP/Synology stores. If that is your case, please, temporarily switch to English (upper world icon with your locale initials).

[Gerdal]

I still see 1.4.0 there...

[polmr]

@Gerdal , thanks for pointing that out. You are seeing an outdated cached version of the page. Can you try again in a different browser or a new incognito window?

Also, switching to a different language should work too.

[Gerdal]

I've changed language from polish to English and it works. Thanks for the 1.6.1 version :D

[romanr]

Interesting, the package downloaded from same place two weeks ago didn't work megacmdpkg-x86_64-1.6.1-0001.spk file size 169.6 MB downloaded on Mar 22 crashed with exception (#799). megacmdpkg-x86_64-1.6.1-0001.spk file size 174 MB is working!

[zerweck]

Interesting, the package downloaded from same place two weeks ago didn't work megacmdpkg-x86_64-1.6.1-0001.spk file size 169.6 MB downloaded on Mar 22 crashed with exception (#799). megacmdpkg-x86_64-1.6.1-0001.spk file size 174 MB is working!

Thank you very much, after hours of googling this thread and your comment showed me the way. I can confirm the file you mentioned from https://mega.io/nas works for me on DSM 7.1.1-42962 Update 5. I had to remove my older MegaCmd Installation first via package manager. It keeps the login, settings and syncs though.

[romanr]

Interesting, the package downloaded from same place two weeks ago didn't work megacmdpkg-x86_64-1.6.1-0001.spk file size 169.6 MB downloaded on Mar 22 crashed with exception (#799). megacmdpkg-x86_64-1.6.1-0001.spk file size 174 MB is working!

Thank you very much, after hours of googling this thread and your comment showed me the way. I can confirm the file you mentioned from https://mega.io/nas works for me on DSM 7.1.1-42962 Update 5. I had to remove my older MegaCmd Installation first via package manager. It keeps the login, settings and syncs though.

MEGA outdone themselves! How badly project has to be organised if they release different build a month later under the exact same version number. The only way of user to know if it's new is to look at file size. They should publish the checksum as normal distributions do. The version in release is for a reason so, you know, we can see it's a new version of package and not the same. Maybe "-0001" suffixes supposed to mean the build number for cases like this. If they had testing or some product manager it wouldn't happen.

[plamendev]

none of the suitable packages work on my DS220+, keep getting the same errors as before, see screenshot.

Anyone got a working solution on how to sync Mega to Synology?

[romanr]

none of the suitable packages work on my DS220+, keep getting the same errors as before, see screenshot.

Anyone got a working solution on how to sync Mega to Synology?

1. When pasting from command line, copy and paste text as code block. Not image. this is not Reddit.
2. Possibly mega process left a "lock" and terminated. and now it thinks another server instance is running. check "hidden" folder .megaCmd.: cd .megaCmd; ls -al
3. check if mega process is actually running: ps aux |grep mega
4. if not's not running, you can try running how it suggests mega-cmd --skip…