mega-cmd unresponsive on Synology NAS

[BKFCAW]

I am a Pro II subscriber, with 2 Linux boxes, 2 Max Minis and 1 Synology NAS (213j). For a while, all machines were synchronizing with MEGA properly, but as of yesterday, the NAS would not sync, and mega-cmd has become unresponsive. I finally uninstalled/reinstalled the MEGA app on the NAS. Now when I try to start mega-cmd, there is the greeting banner, then nothing, by that I mean that apparently mega-cmd-server and mega-cmd are running, but there is no mega-cmd prompt. I note from a 'top' command that mega-cmd-server is taking close to 60% of memory, but almost no CPU cycles.

[BKFCAW]

I've tried again, and this time I get

Fetching nodes ||######################################||(195/195 MB: 100.00 %)

...at which point it hangs.

At this point I cannot access the Synology MEGA server to change, add or delete any sync information between the Synology and MEGA. The next step is to try to mount the Synology drive on a Mac, where communication with MEGA seems to work. Failing that, I will switch to iDrive or another service.

[polmr]

Hello @BKFCAW
Are you using latest MEGAcmd version from https://mega.io/nas ?

If so, a log may indicate what is halting the execution of MEGAcmd Server.

Instructions to retrieve it:

1. Ensure MEGAcmd server is not running.
   On a terminal:

pgrep mega-cmd-server >/dev/null && echo still running

If so, execute

mega-quit

Ensure again it's not running

pgrep mega-cmd-server >/dev/null && echo still running

If the above does not work, you can try to kill it in with more ungentle manners:

killall -2 mega-cmd-server && sleep 1 && killall -9 mega-cmd-server

2. Execute the server with debug level enabled:

mega-cmd-server --debug-full 2>&1 > ~/megacmd.log

The above will save a log file in your HOME folder.

3. Let it run for > 2 minutes. You can try to open another console and open mega-cmd (shell), to ensure it's not working.

4. Close the server: Ctrl + C in the terminal where you execute the server, or mega-quit from another one.

5. Have log sent to supporrt@mega.nz, since it may contain sensitive data. It will only be used for the purpose of analyzing your issue. Link this issue in your email.

[BKFCAW]

Thank you for your input. I had already tried various actions, and generally the server was running; it was just not responding, sometimes losing a connection in the middle of a sync. At this point I am planning to go with AWS S3 using their Glacier Deep Archive storage class, which is far cheaper than any other option I know of. I have backup discs at home, so this is essentially fire insurance, with retrieval only in a dire emergency. More to the point, S3 response is instant, no dropped connection or servers that fall silent.

…

On Mar 18, 2024, at 6:09 AM, polmr ***@***.***> wrote: Hello @BKFCAW <https://github.com/BKFCAW> Are you using latest MEGAcmd version from https://mega.io/nas ? If so, a log may indicate what is halting the execution of MEGAcmd Server. Instructions to retrieve it: Ensure MEGAcmd server is not running. On a terminal: pgrep mega-cmd-server >/dev/null && echo still running If so, execute mega-quit Ensure again it's not running pgrep mega-cmd-server >/dev/null && echo still running If the above does not work, you can try to kill it in with more ungentle manners: killall -2 mega-cmd-server && sleep 1 && killall -9 mega-cmd-server Execute the server with debug level enabled: mega-cmd-server --debug-full 2>&1 > ~/megacmd.log The above will save a log file in your HOME folder. Let it run for > 2 minutes. You can try to open another console and open mega-cmd (shell), to ensure it's not working. Close the server: Ctrl + C in the terminal where you execute the server, or mega-quit from another one. Have log sent to ***@***.*** ***@***.***>, since it may contain sensitive data. It will only be used for the purpose of analyzing your issue. Link this issue in your email. — Reply to this email directly, view it on GitHub <#950 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYOQFIY6Q4B7DPVBUA6JKZTYY24L3AVCNFSM6AAAAABEWQB6M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBTGQ2DCMJWHA>. You are receiving this because you were mentioned.