search

meganz / MEGAcmd

Command Line Interactive and Scriptable Application to access MEGA
Other
1.94k stars 407 forks source link

Server seems irresponsive #839

Open Tzuramishav opened 1 year ago

Tzuramishav commented 1 year ago

mega-cmd-server seems to hang a lot on my Ubuntu server. When I run mega-cmd I get "Server seems irresponsive". When I kill the mega-cmd-server process, remove the ~/.megacmd dir and log in again, it sometimes helps, sometimes not. When I run mega-sync I get "Failed to fetch nodes: Internal error"

Any suggestions on how to fix this?

polmr commented 1 year ago

Would you mind assisting us in debugging the reason for that?

1 - install debug symbols 

sudo apt update && sudo apt install megacmd-dbg

2 - run mega-cmd-server in a debugger (you might need to install gdb)

gdb mega-cmd-server

It should say something like:

Reading symbols from mega-cmd-server...Reading symbols from /usr/lib/debug/.build-id/10/3dc7527ee44c6531970f4ab228264c223bc4c6.debug...done.
done.
(gdb)

3 - Then run the program (type 'r' + Enter) Let it run until it crashes.

4 - once so, then type in the gdb console: 

set pagination off
thread apply all bt

5 - then please, scroll back and send us the entire output of that command.

Also, increasing log level with before login in mega-log DEBUG, may give us some extra hints. The logs will be located at $HOME/.megaCmd/megacmdserver.log as stated above

ViperCode7 commented 11 months ago

I too am in need of a fix for this. I can replicate it simply by loging in and executing a find pattern. While it lists, I hit CTRL+C to terminate the client and then the server appears to suffer from this hanging issue, displaying endlessly ERROR on connecting to namedPipe ###. Would it no be better for the server to have a limited number of attempts? And then break the current operation from that client? As it would stand to reason the client might have suffered a crash, or like in my case, was terminated by the user.