search

meganz / MEGAcmd

Command Line Interactive and Scriptable Application to access MEGA
Other
1.89k stars 406 forks source link

Problem to access Mega Cmd: server irresponsive + failed to create socket for registering for state changes #944

Open nummu4 opened 4 months ago

nummu4 commented 4 months ago

I've set a synchronization with my NAS and it worked very slow but fine. Today I had to shut down my mac and when I try to restart mega-cmd it doesn't work anymore. In the first time it says "Server seems irresponsive" and after some try now I've this message: Unable to connect to service: error=111 Please ensure mega-cmd-server is running Failed to create socket for registering for state changes Server seems irresponsive

This message goes on loop even if I don't do anything on the terminal. I'm not an expert, so I don't know what to look for in order to solve this problem. Maybe I can stop the server and start it again? But how?

My Megacmd version is 1.6.3

dhanton commented 4 months ago

Hi, can you verify if the server process is running when this happens? Using top or a similar command. If so, you can force-quit it with killall -2 mega-cmd-server.

Afterwards you could try running mega-cmd-server manually in a different console. Even if it still doesn't work, the output (with --debug-full) might still be useful.

Another thing you could try is removing the ~/.megaCmd folder and restarting.

nummu4 commented 4 months ago

Hi, I've removed the ~/.megaCmd folder and now it seems to work. My sync is now in the "processing" staus, I think it will restart syncing as soon as all file are scanned. Is it right? The syncronization was very slow (2,9 TB in about a month), so I think it will take a while.

dhanton commented 4 months ago

Okay cool :slightly_smiling_face: Feel free to reopen this issue if the problem persists.

nummu4 commented 4 months ago

Is it normal that from this morning the status is still stuck on "processing" and doesn't change in "syncing"?

dhanton commented 4 months ago

I think it should've moved to "syncing" already. I would suggest disabling & enabling the sync or restarting.

nummu4 commented 4 months ago

Hi, I've tried to restart, but now I've again the message server irresponsive. I've already tried to delete the .megaCmd folder and also to stop and restart the app on the NAS, but it doesn't work and I cant' do anything. I can only digit a letter, and than it stops Schermata 2024-02-26 alle 13 59 05

nummu4 commented 4 months ago

And the .megaCmd folder doesn't appear anymore on my NAS

dhanton commented 4 months ago

Sorry I'm a bit confused on what your setup is. You're running megacmd on both NAS and MacOS, correct? Could you explain a bit more how you're using each machine? Which one is affected by this issue?

In any case, could you kill any mega-cmd-* processes (in the affected machine) and run mega-cmd-server manually on the console? The output of the server might help figure out what the issue is :slightly_smiling_face:

nummu4 commented 4 months ago

Mega-cmd is installed on my NAS Qnap, but I access it with shell on my mac, where I see this message How can I run mega-cmd-server manually on the console? I'll try to do it tomorrow morning because now I can't

dhanton commented 4 months ago

Thanks for the explanation, that makes sense :slightly_smiling_face:

The server should be installed alongside the rest of the megacmd utilities, so you should be able to run it by doing mega-cmd-server on the console. You can then run mega-cmd on a different shell while the server is running to access megacmd normally.