meganz / MEGAcmd

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

ERROR reading output code: 104 #551

Open ghost opened 3 years ago

ghost commented 3 years ago

Hello. Sometimes (2-3 times per week) I get error: "ERROR reading output code: 104.........................................................................................................................................................................||(22/681 MB: 3.28 %) ERROR reading output socket"

I am using script which send files to mega...But when I got this error, script failed.

tobiasfiechter commented 3 years ago

I get a similar error, when starting the mega-cmd-server on my raspberry pi 4:

[Initiating server in background. Log: /home/pi/.megaCmd/megacmdserver.log] Resuming session ... terminate called after throwing an instance of 'char const*' ERROR reading output code: 104

polmr commented 3 years ago

Such errors happens probably when the server dies. If you can reproduce that, running the server in a dedicated gdb process might tell us where:

1 - install debug symbols (asuming a linux distro with apt) 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:

done.
(gdb) 

3 - Then run the program (type 'r' + Enter) Let it run until it crashes. Try to reproduce the issue using MEGAcmd shell, or non-interactive mode ...

4 - once so, then type in the gdb console: 'thread apply all bt' Press "Enter" until the output is complete, and

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

tobiasfiechter commented 3 years ago

Hi, thanks this is the output:

[info: 10:52:10] Loaded sync: ...
[info: 10:52:23] Loaded sync: ...
[info: 10:53:31] Loaded sync: ...
[info: 10:53:31] Loaded sync: ...
terminate called after throwing an instance of 'char const*'

Thread 2 "mega-cmd-server" received signal SIGABRT, Aborted.
[Switching to Thread 0xf5fe1220 (LWP 25997)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
polmr commented 3 years ago

I am afraid you missed: thread apply all bt that should list the traces of all threads (including the Thread 2) ... :thinking:

tobiasfiechter commented 3 years ago

Hi @polmr, ok I could reproduce the error. Here is the output:

terminate called after throwing an instance of 'char const*'

Thread 2 "mega-cmd-server" received signal SIGABRT, Aborted.
[Switching to Thread 0xf5fe1220 (LWP 30348)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) thread apply all bt

Thread 77 (Thread 0xc63f0b40 (LWP 32075)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xc63f04f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xc63f04f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xc63f04f0, abstime@entry=0xc63f04e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xc63f0b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 76 (Thread 0xc63f7b40 (LWP 32074)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xc63f74f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xc63f74f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xc63f74f0, abstime@entry=0xc63f74e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xc63f7b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 75 (Thread 0xc63feb40 (LWP 32073)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xc63fe4f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xc63fe4f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xc63fe4f0, abstime@entry=0xc63fe4e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xc63feb40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 74 (Thread 0xeef08b40 (LWP 32072)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef084f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef084f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef084f0, abstime@entry=0xeef084e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef08b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 73 (Thread 0xeef0fb40 (LWP 32071)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef0f4f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef0f4f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef0f4f0, abstime@entry=0xeef0f4e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef0fb40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
--Type <RET> for more, q to quit, c to continue without paging--
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 70 (Thread 0xeef24b40 (LWP 32068)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef244f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef244f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef244f0, abstime@entry=0xeef244e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef24b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 69 (Thread 0xeef32b40 (LWP 32067)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef324f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef324f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef324f0, abstime@entry=0xeef324e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef32b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 68 (Thread 0xeef39b40 (LWP 32066)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef394f0, expected=0, futex_word=0xf73361cc <__aio_new_request_notification+44>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef394f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef394f0, abstime@entry=0xeef394e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef39b40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 67 (Thread 0xeef2bb40 (LWP 32065)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef2b4f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef2b4f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef2b4f0, abstime@entry=0xeef2b4e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef2bb40) at pthread_create.c:486
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 66 (Thread 0xeef16b40 (LWP 32064)):
#0  futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0xeef164f0, expected=0, futex_word=0xf73361c8 <__aio_new_request_notification+40>)
    at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  __pthread_cond_wait_common (abstime=0xeef164f0, mutex=0x0, cond=0xf73361a0 <__aio_new_request_notification>) at pthread_cond_wait.c:539
#2  __pthread_cond_timedwait (cond=0xf73361a0 <__aio_new_request_notification>, mutex=0x0, abstime=0xeef164f0, abstime@entry=0xeef164e8) at pthread_cond_wait.c:667
#3  0xf7322354 in handle_fildes_io (arg=<optimized out>) at ../sysdeps/pthread/aio_misc.c:629
#4  0xf7665494 in start_thread (arg=0xeef16b40) at pthread_create.c:486
--Type <RET> for more, q to quit, c to continue without paging--
#5  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 17 (Thread 0xc59ff220 (LWP 30514)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:38
#1  0x0030028c in uv__epoll_wait (epfd=70, events=0xc59fa9d8, nevents=1024, timeout=-1) at src/unix/linux-syscalls.c:321
#2  0x002fc4f8 in uv__io_poll (loop=0xdbfb0ad8, timeout=-1) at src/unix/linux-core.c:243
#3  0x002eb964 in uv_run (loop=0xdbfb0ad8, mode=UV_RUN_DEFAULT) at src/unix/core.c:351
#4  0x002049b0 in mega::MegaTCPServer::run (this=this@entry=0xdbfb0ad0) at src/megaapi_impl.cpp:25328
#5  0x00204c48 in mega::MegaTCPServer::threadEntryPoint (param=0xdbfb0ad0) at src/megaapi_impl.cpp:25588
#6  0xf7665494 in start_thread (arg=0xc59ff220) at pthread_create.c:486
#7  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 16 (Thread 0xc633b220 (LWP 30513)):
#0  syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:38
#1  0x0030028c in uv__epoll_wait (epfd=63, events=0xc63369d8, nevents=1024, timeout=-1) at src/unix/linux-syscalls.c:321
#2  0x002fc4f8 in uv__io_poll (loop=0xdbfb05b8, timeout=-1) at src/unix/linux-core.c:243
#3  0x002eb964 in uv_run (loop=0xdbfb05b8, mode=UV_RUN_DEFAULT) at src/unix/core.c:351
#4  0x002049b0 in mega::MegaTCPServer::run (this=this@entry=0xdbfb05b0) at src/megaapi_impl.cpp:25328
#5  0x00204c48 in mega::MegaTCPServer::threadEntryPoint (param=0xdbfb05b0) at src/megaapi_impl.cpp:25588
#6  0xf7665494 in start_thread (arg=0xc633b220) at pthread_create.c:486
#7  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 15 (Thread 0xef7d4220 (LWP 30361)):
#0  __GI___nanosleep (remaining=0x0, requested_time=0xef7d39cc) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
#1  __GI___nanosleep (requested_time=0xef7d39cc, requested_time@entry=0xef7d39c4, remaining=remaining@entry=0x0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2  0xf7080fc0 in usleep (useconds=useconds@entry=300000) at ../sysdeps/posix/usleep.c:32
#3  0x00063f24 in megacmd::sleepMilliSeconds (milliseconds=milliseconds@entry=300) at src/megacmdcommonutils.cpp:945
#4  0x0003e464 in megacmd::retryConnections (pointer=<optimized out>) at src/megacmd.cpp:3688
#5  0xf7665494 in start_thread (arg=0xef7d4220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 13 (Thread 0xf07d6220 (LWP 30359)):
#0  __GI___select (timeout=0xfffeefca, exceptfds=0xe17bd4, writefds=0xe17b54, readfds=0xe17ad4, nfds=32) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=32, readfds=readfds@entry=0xe17ad4, writefds=writefds@entry=0xe17b54, exceptfds=exceptfds@entry=0xe17bd4, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=0xe17ac8) at src/posix/waiter.cpp:113
#3  0x002668e0 in mega::MegaApiImpl::loop (this=this@entry=0xdd88f0) at src/megaapi_impl.cpp:6230
#4  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xdd88f0) at src/megaapi_impl.cpp:5017
#5  0xf7665494 in start_thread (arg=0xf07d6220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 12 (Thread 0xf0fd7220 (LWP 30358)):
#0  __GI___select (timeout=0x0, exceptfds=0xe25274, writefds=0xe251f4, readfds=0xe25174, nfds=33) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=33, readfds=readfds@entry=0xe25174, writefds=writefds@entry=0xe251f4, exceptfds=exceptfds@entry=0xe25274, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=this@entry=0xe25168) at src/posix/waiter.cpp:113
--Type <RET> for more, q to quit, c to continue without paging--
#3  0x001bac0c in mega::GfxProc::loop (this=0xe25160) at src/gfx.cpp:106
#4  0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#5  0xf7665494 in start_thread (arg=0xf0fd7220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 11 (Thread 0xf17d8220 (LWP 30357)):
#0  __GI___select (timeout=0xfffeefca, exceptfds=0xdc478c, writefds=0xdc470c, readfds=0xdc468c, nfds=27) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=27, readfds=readfds@entry=0xdc468c, writefds=writefds@entry=0xdc470c, exceptfds=exceptfds@entry=0xdc478c, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=0xdc4680) at src/posix/waiter.cpp:113
#3  0x002668e0 in mega::MegaApiImpl::loop (this=this@entry=0xd854a8) at src/megaapi_impl.cpp:6230
#4  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xd854a8) at src/megaapi_impl.cpp:5017
#5  0xf7665494 in start_thread (arg=0xf17d8220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 10 (Thread 0xf1fd9220 (LWP 30356)):
#0  __GI___select (timeout=0x0, exceptfds=0xdd1e2c, writefds=0xdd1dac, readfds=0xdd1d2c, nfds=28) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=28, readfds=readfds@entry=0xdd1d2c, writefds=writefds@entry=0xdd1dac, exceptfds=exceptfds@entry=0xdd1e2c, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=this@entry=0xdd1d20) at src/posix/waiter.cpp:113
#3  0x001bac0c in mega::GfxProc::loop (this=0xdd1d18) at src/gfx.cpp:106
#4  0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#5  0xf7665494 in start_thread (arg=0xf1fd9220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 9 (Thread 0xf27da220 (LWP 30355)):
#0  __GI___select (timeout=0xfffeefca, exceptfds=0xd71344, writefds=0xd712c4, readfds=0xd71244, nfds=22) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=22, readfds=readfds@entry=0xd71244, writefds=writefds@entry=0xd712c4, exceptfds=exceptfds@entry=0xd71344, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=0xd71238) at src/posix/waiter.cpp:113
#3  0x002668e0 in mega::MegaApiImpl::loop (this=this@entry=0xd32060) at src/megaapi_impl.cpp:6230
#4  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xd32060) at src/megaapi_impl.cpp:5017
#5  0xf7665494 in start_thread (arg=0xf27da220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 8 (Thread 0xf2fdb220 (LWP 30354)):
#0  __GI___select (timeout=0x0, exceptfds=0xd7e9e4, writefds=0xd7e964, readfds=0xd7e8e4, nfds=23) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=23, readfds=readfds@entry=0xd7e8e4, writefds=writefds@entry=0xd7e964, exceptfds=exceptfds@entry=0xd7e9e4, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=this@entry=0xd7e8d8) at src/posix/waiter.cpp:113
#3  0x001bac0c in mega::GfxProc::loop (this=0xd7e8d0) at src/gfx.cpp:106
#4  0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#5  0xf7665494 in start_thread (arg=0xf2fdb220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 7 (Thread 0xf37dc220 (LWP 30353)):
#0  __GI___select (timeout=0xfffeefca, exceptfds=0xd2b0f4, writefds=0xd2b074, readfds=0xd2aff4, nfds=17) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=17, readfds=readfds@entry=0xd2aff4, writefds=writefds@entry=0xd2b074, exceptfds=exceptfds@entry=0xd2b0f4, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=0xd2afe8) at src/posix/waiter.cpp:113
#3  0x002668e0 in mega::MegaApiImpl::loop (this=this@entry=0xcded50) at src/megaapi_impl.cpp:6230
#4  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xcded50) at src/megaapi_impl.cpp:5017
#5  0xf7665494 in start_thread (arg=0xf37dc220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0xf3fdd220 (LWP 30352)):
#0  __GI___select (timeout=0x0, exceptfds=0xd2bdf4, writefds=0xd2bd74, readfds=0xd2bcf4, nfds=18) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=18, readfds=readfds@entry=0xd2bcf4, writefds=writefds@entry=0xd2bd74, exceptfds=exceptfds@entry=0xd2bdf4, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=this@entry=0xd2bce8) at src/posix/waiter.cpp:113
#3  0x001bac0c in mega::GfxProc::loop (this=0xd2bce0) at src/gfx.cpp:106
#4  0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#5  0xf7665494 in start_thread (arg=0xf3fdd220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0xf47de220 (LWP 30351)):
#0  __GI___select (timeout=0xfffeefca, exceptfds=0xcd7eb4, writefds=0xcd7e34, readfds=0xcd7db4, nfds=12) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=12, readfds=readfds@entry=0xcd7db4, writefds=writefds@entry=0xcd7e34, exceptfds=exceptfds@entry=0xcd7eb4, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=0xcd7da8) at src/posix/waiter.cpp:113
#3  0x002668e0 in mega::MegaApiImpl::loop (this=this@entry=0xc8bc78) at src/megaapi_impl.cpp:6230
--Type <RET> for more, q to quit, c to continue without paging--
#4  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xc8bc78) at src/megaapi_impl.cpp:5017
#5  0xf7665494 in start_thread (arg=0xf47de220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0xf4fdf220 (LWP 30350)):
#0  __GI___select (timeout=0x0, exceptfds=0xcd816c, writefds=0xcd80ec, readfds=0xcd806c, nfds=13) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=13, readfds=readfds@entry=0xcd806c, writefds=writefds@entry=0xcd80ec, exceptfds=exceptfds@entry=0xcd816c, timeout=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x00150fd8 in mega::PosixWaiter::wait (this=this@entry=0xcd8060) at src/posix/waiter.cpp:113
#3  0x001bac0c in mega::GfxProc::loop (this=0xcd8058) at src/gfx.cpp:106
#4  0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#5  0xf7665494 in start_thread (arg=0xf4fdf220) at pthread_create.c:486
#6  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xf57e0220 (LWP 30349)):
#0  0x001543e0 in mega::MegaClient::<lambda(mega::Transfer*)>::operator() (__closure=0xf57df7a0, __closure=0xf57df7a0, t=0xdfa98700) at /usr/include/c++/8/array:185
#1  std::_Function_handler<bool(mega::Transfer*), mega::MegaClient::dispatchTransfers()::<lambda(mega::Transfer*)> >::_M_invoke(const std::_Any_data &, mega::Transfer *&&) (__functor=...,
    __args#0=<optimized out>) at /usr/include/c++/8/bits/std_function.h:282
#2  0x001d2e38 in std::function<bool (mega::Transfer*)>::operator()(mega::Transfer*) const (__args#0=<optimized out>, this=0xf57df7a0) at /usr/include/c++/8/bits/std_function.h:682
#3  mega::TransferList::nexttransfers(std::function<bool (mega::Transfer*)>&) (this=this@entry=0xc52ca8, continuefunction=...) at src/transfer.cpp:1972
#4  0x001616d0 in mega::MegaClient::dispatchTransfers (this=0x2857200, this@entry=0xc52678) at src/megaclient.cpp:3318
#5  0x00183cc4 in mega::MegaClient::exec (this=<optimized out>) at src/megaclient.cpp:2187
#6  0x00266978 in mega::MegaApiImpl::loop (this=this@entry=0xbf9b58) at src/megaapi_impl.cpp:6255
#7  0x002669f0 in mega::MegaApiImpl::threadEntryPoint (param=0xbf9b58) at src/megaapi_impl.cpp:5017
#8  0xf7665494 in start_thread (arg=0xf57e0220) at pthread_create.c:486
#9  0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xf5fe1220 (LWP 30348)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0xf6fc7230 in __GI_abort () at abort.c:79
#2  0xf72218d8 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#3  0xf721f5b0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#4  0xf721f624 in std::terminate() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#5  0xf721f990 in __cxa_throw () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#6  0x003f5fc0 in _ReadProc(png_struct_def*, unsigned char*, unsigned int) ()
#7  0x0047ce18 in png_read_data ()
#8  0x00489378 in png_read_chunk_header ()
#9  0x00475b1c in png_read_info ()
#10 0x003f70dc in Load ()
#11 0x003c8f44 in FreeImage_LoadFromHandle ()
#12 0x003c8fd4 in FreeImage_Load ()
#13 0x002711f0 in mega::GfxProcFreeImage::readbitmap (this=this@entry=0xc514c8, fa=fa@entry=0x0, localname=localname@entry=0xbc108030, size=size@entry=1000) at src/gfx/freeimage.cpp:460
#14 0x001bac8c in mega::GfxProc::loop (this=0xc514c8) at src/gfx.cpp:119
#15 0x001bb274 in mega::GfxProc::threadEntryPoint (param=<optimized out>) at src/gfx.cpp:96
#16 0xf7665494 in start_thread (arg=0xf5fe1220) at pthread_create.c:486
#17 0xf7087578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xf645e010 (LWP 30345)):
#0  __GI___select (timeout=0xfffeefbc, exceptfds=0x0, writefds=0x0, readfds=0xe2bff0, nfds=1024) at ../sysdeps/unix/sysv/linux/select.c:41
#1  __GI___select (nfds=nfds@entry=1024, readfds=0xe2bff0, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0, timeout=timeout@entry=0x0) at ../sysdeps/unix/sysv/linux/select.c:37
#2  0x000e06b4 in megacmd::ComunicationsManagerFileSockets::waitForPetition (this=<optimized out>) at src/comunicationsmanagerfilesockets.cpp:214
#3  0x00042cfc in megacmd::megacmd () at src/megacmd.cpp:3836
#4  0x000320c8 in main (argc=<optimized out>, argv=<optimized out>) at src/megacmd.cpp:4834
tobiasfiechter commented 3 years ago

The issue still persists. I tried deleting and readding all my syncs, but no success.

jkrasinger commented 3 years ago

Got this error "ERROR reading output code: 104" on Synology NAS DSM 7.0 when using "mega-sync" command without parameters for displaying the active syncs. The mega-sync-server dies with

[267945.585612] mega-cmd-server[10157]: segfault at 0 ip (null) sp 00007fd5b67fad58 error 14 in mega-cmd-server[400000+130c000] coredump[10158]: Process mega-cmd-server4768 dumped core on signal [11]. Core file [/volume1/@mega-cmd-server.core.gz]. Cmdline [mega-cmd-server ]

I can add and delete syncs with this command, but not display the state. When restarting the mega-sync-server then the log shows the activated syncs .... and they are working!!

tobiasfiechter commented 3 years ago

So I tried to remove all syncs and made a systemctl service with mega-get and mega-put commands. Even with mega-get I get the 104 error.

The service output is like this:

Aug 17 20:15:31 raspi4 bash[2659]: [Initiating server in background. Log: /home/pi/.megaCmd/megacmdserver.log] Aug 17 20:15:34 raspi4 bash[2659]: Resuming session ... Aug 17 20:16:06 raspi4 bash[2659]: [API:err: 18:16:06] terminate called after throwing an instance of 'char const': No such file or directory Aug 17 20:16:06 raspi4 bash[2659]: terminate called after throwing an instance of 'char const' Aug 17 20:16:06 raspi4 bash[2659]: ERROR reading output code: Aug 17 20:16:06 raspi4 bash[2659]: [Server is probably down. Type to respawn or reconnect to it] Aug 17 20:16:06 raspi4 bash[2659]: 104

aabellagm commented 3 years ago

Hi @tobiasfiechter

Thanks a lot for the stack trace. The problems seems to be an image (I think a png one) that make FreeImage crash while creating the thumbnails. I see you are using a Raspberry: Could you please specify the OS version and MEGAcmd version you are using? Has the package been downloaded from our web or is it custom build? The output of these commands will be very helpful:

lsb_release -a
cat /etc/os-release
cat /etc/issue
uname -a
tobiasfiechter commented 3 years ago

Hi Alfonso

Thank you for your answer! I executed the following commands:

@.:~ $ lsb_release -a -bash: lsb_release: command not found @.:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" @.***:~ $ cat /etc/issue Raspbian GNU/Linux 10 \n \l

@.:~ $ uname -a Linux raspi4 5.10.52-v8+ #1440 SMP PREEMPT Tue Jul 27 09:56:40 BST 2021 aarch64 GNU/Linux @.:~ $ mega-version [Initiating server in background. Log: /home/pi/.megaCmd/megacmdserver.log] Resuming session ... MEGAcmd version: 1.2.0.6: code 1020006 @.**:~ $ terminate called after throwing an instance of 'char const'

Greetings

Alfonso Abella @.***> schrieb am Fr., 27. Aug. 2021, 14:21:

Hi @tobiasfiechter https://github.com/tobiasfiechter

Thanks a lot for the stack trace. The problems seems to be an image (I think a png one) that make FreeImage crash while creating the thumbnails. I see you are using a Raspberry: Could you please specify the OS version and MEGAcmd version you are using? Has the package been downloaded from our web or is it custom build? The output of these commands will be very helpful:

lsb_release -a cat /etc/os-release cat /etc/issue uname -a

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/meganz/MEGAcmd/issues/551#issuecomment-907162014, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQOVNYYMCG3QYBF3KRIC7TT657M5ANCNFSM5BKGINYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

aabellagm commented 3 years ago

Hi @tobiasfiechter, We have prepared a pre-release package for the next 1.5.0 which may fix your problems: https://mega.nz/folder/E5JCTZpC#WFgWY9IEMAjVegEPi6gzWw

Install it on top of the one you currently have if any:

sudo apt install /path/to/downloaded/megacmd_1.5.0-8.1_armhf.deb

If you experience any crash, follow the instructions Pablo gave you above, but installing the megacmd-dbg_1.5.0-8.1_amd64.deb package in this link. Again, you can install it on top of the one you have.

If you install any of them, once the official 1.5.0 release is ready in our repositories, the package will be updated as any other package in your distro. No major problems are expected with this version, but if you find any, please report! =)

tobiasfiechter commented 3 years ago

Hi @aabellagm, Thank you for the response. I installed the pre-release and so far no errors appeared.

geustace commented 3 years ago

I have just tried to get mega-sync working on a new Synology DS920+ was and am getting the same Error 104 as mentioned above. As fas as I can see the server is dead and NOT working. If I try to run the server on its own, it Seg Faults

[API:err: 05:37:19] scsn not known, not updating database [info: 05:37:20] Loaded sync: /volume1/xxxxx to /xxxxx [info: 05:37:21] Loaded sync: /volume1/yyyyy to /yyyyy Segmentation fault (core dumped)

dwmega commented 3 years ago

Hey @geustace,

What version of MegaCMD are you running on your Synology device?

geustace commented 3 years ago

I don't think I can build a package for the Synology (or can I?), if I can I am quite happy to assist with finding a resolution/debugging. Been in IT for 40+ years.

geustace commented 3 years ago

Have a debian system I have been using for developing an integration for Home Assistant, and I think that the 920+ is Intel based.

mattw-mega commented 3 years ago

Hi @geustace , you can try building it yourself for Synology by following the instructions at https://github.com/meganz/MEGAcmd/blob/master/build/SynologyNAS/README.md .

We would be interested if you can diagnose the problem that way. thanks

geustace commented 3 years ago

More than happy to give it a go. I am guessing that the build in their packages repo is for 6.x, I am running 7.0, anyway something to have a play with over the next few days.

geustace commented 2 years ago

@aabellagm, Any chance of getting the source for 1.5, I have finally managed to get a Synology build environment working and the resulting 1.4 core dumps at the same place as the offical package. Before diving too deep into debugging, I would like to see if 1.5 has already fixed the issue.

geustace commented 2 years ago

When looking at the core with gdb on the system I did the build on, I get the following warning warning: Unexpected size of section `.reg-xstate/14374' in core file, which may or may not be obscuring information

warning: Unexpected size of section .reg-xstate/14399' in core file. Core was generated bymega-cmd-server'. Program terminated with signal SIGSEGV, Segmentation fault.

warning: Unexpected size of section `.reg-xstate/14399' in core file.

0 0x0000000000000000 in ?? ()

[Current thread is 1 (LWP 14399)] (gdb) bt

0 0x0000000000000000 in ?? ()

1 0x0000000000577eb3 in gthread_mutex_timedlock (abs_timeout=0x7fb8267fada0,

__mutex=0x2b62398)
at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/x86_64-pc-linux-gnu/bits/gthr-default.h:781

2 gthread_recursive_mutex_timedlock (__abs_timeout=0x7fb8267fada0, mutex=0x2b62398)

at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/x86_64-pc-linux-gnu/bits/gthr-default.h:837

3 std::recursive_timed_mutex::_M_timedlock (__ts=..., this=0x2b62398)

at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/mutex:292

4 std::timed_mutex_impl::_M_try_lock_until<std::chrono::duration<long, std::ratio<1l, 1000000000l> > > (atime=..., this=0x2b62398)

at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/mutex:164

5 std::timed_mutex_impl::_M_try_lock_until<std::chrono::_V2::steady_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > > (atime=..., this=0x2b62398)

at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/mutex:172

6 std::timed_mutex_impl::_M_try_lock_for<long, std::ratio<1l, 1000l> > (rtime=..., this=0x2b62398)

at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/mutex:148

7 std::recursive_timed_mutex::try_lock_for<long, std::ratio<1l, 1000l> > (__rtime=...,

this=0x2b62398)
at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/mutex:269

8 std::unique_lock::try_lock_for<long, std::ratio<1l, 1000l> > (

__rtime=..., this=0x7fb8267fad70)
at /usr/local/x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/include/c++/7.5.0/bits/std_mutex.h:311

9 mega::MegaApiImpl::syncPathState (this=0x2b61e80, path=path@entry=0x7fb8267fae60)

at src/megaapi_impl.cpp:8322

10 0x00000000005df5c9 in mega::MegaApi::syncPathState (this=,

path=path@entry=0x7fb8267fae60) at src/megaapi.cpp:3151

11 0x0000000000481e85 in megacmd::MegaCmdExecuter::printSync (this=this@entry=0x2b61890,

i=i@entry=0, key=..., nodepath=nodepath@entry=0x7fb820002140 "/AGREE",
thesync=thesync@entry=0x7fb820001600, n=n@entry=0x7fb8200021a0, nfiles=3615, nfolders=339,
PATHSIZE=26, cd=0x7fb8267fb2d0) at src/megacmdexecuter.cpp:4360
geustace commented 2 years ago

So far on my journey I have found that Openssl 1.1.1d now needs an extra argument on the Configure of no-asm if it detects the platform as linux-generic64. This is when building on Ubuntu 16.04

If one can get the sync loaded, then mega-cmd-server seems to be able to process them without crashing. It would appear that the crash is related to displaying the status. i.e. using just the 'sync' command on its own.

jkrasinger commented 2 years ago

Yes, this is exactly the same i mentioned on Aug 11th.

cgagnaire commented 2 years ago

Hi, Same issue here on a Synology DSM 7.

onestix commented 2 years ago

Hi, any progress on this? I am having the same problem on Synology DSM 7 (DS918+). Everything else seems to be working for me, except the "mega-sync" command. I downloaded the latest spkg 1.4.0-1000 available through Package center.

geustace commented 2 years ago

On my part, no.  C++ is not a language I have used much so I was struggling to follow the code.  I did manage to get it to compile but my binary exhibited the same issues as the one I installed.

I'd really like someone that knows the code to fix this for us.

On 24/03/22 5:08 am, onestix wrote:

Hi, any progress on this? I am having the same problem on Synology DSM 7 (DS918+). Everything else seems to be working for me, except the "mega-sync" command.

— Reply to this email directly, view it on GitHub https://github.com/meganz/MEGAcmd/issues/551#issuecomment-1076518845, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVDXWMS4GSY7DK35FQD5BKLVBM6YTANCNFSM5BKGINYA. You are receiving this because you were mentioned.Message ID: @.***>

-- Netflix: "The Social Dilemma", this is a MUST see. And when you have watched that one "The Great Hack"

onestix commented 2 years ago

I have currently resorted to using the command "mega-transfers" to check whether I have any pending jobs.

TonieStark commented 2 years ago

I am on DSM 7 as well, with MEGAcmd 1.4.0 from Package center. I just started to experiment with MEGAcmd on my NAS and was able to setup a sync just to try it out. Now I am neither able to delete the test sync nor stop/pause it 🙁

@mattw-mega @dwmega Any progress on getting a new version out for the Package center, or at least a .spk one can sideload?

Thanks!

onestix commented 2 years ago

I am on DSM 7 as well, with MEGAcmd 1.4.0 from Package center. I just started to experiment with MEGAcmd on my NAS and was able to setup a sync just to try it out. Now I am neither able to delete the test sync nor stop/pause it 🙁

@mattw-mega @dwmega Any progress on getting a new version out for the Package center, or at least a .spk one can sideload?

Thanks!

Yea same here. Did not manage to remove the Sync.. I read in the docs that by logging out, you are in theory disabling the syncs so this is what I did.

jkrasinger commented 2 years ago

I think you can manage your syncs on DSM 7 even if the mega-sync commands are failing with the "104" error:

1) run the Command "mega-ls", this will restart the backgroung MEGA Server (if it is not running, if it runs then only the file listing is shown) 2) run your needed "mega-sync" command (remove, add, ....). Even if it fails with the "104" error it is done, but the background MEGA-server is cancelled. 3) Now execute the "mega-ls" again. It is restarting the background server and giving the actual log file name to the console. Take a look into this file, it show you the actual state of the "mega-sync". BTW. If for any reason the background Server stops, the "mega-ls" is restarting it and also restarts the mega-sync if there is any syncing active.

I hope this helps

geustace commented 2 years ago
  1. run the Command "mega-ls", this will restart the backgroung MEGA Server (if it is not running, if it runs then only the file listing is shown)

I have put mega-ls in a scheduled task as the server seems to fall over quite regularly and then my syncs all stop.  This was a useful tip to kick off the server again if it isnt running.

Netflix: "The Social Dilemma", this is a MUST see. And when you have watched that one "The Great Hack"

dyuste commented 2 years ago

I apologize for the delay in publishing the new MEGAcmd 1.5.0 package. It has already been submitted to Synology and it is currently under test and review. We will keep you tell you as soon as it is approved by Synology and available for download.

sentience commented 2 years ago

Anything we can do on our end to progress this? Perhaps we should contact Synology support and request the package update be made available?

TonieStark commented 2 years ago

@dyuste Could you please check with Synology why this is taking so long?

sentience commented 2 years ago

I have submitted a support ticket to Synology to see if we can get an update from the customer side.

sentience commented 2 years ago

I got this reply from Synology support:

Hello,

Thanks for contacting Synology.

For the MEGAcmd 1.5.0 version, actually it is planned to be published at the beginning of next month, we will implement the update as soon as we can.

Please feel free to let us know if you need any further information.

Best regards,

Synology Inc.

TonieStark commented 1 year ago

Where are we with this one?

polmr commented 1 year ago

MEGA will soon provide MEGAcmd packages for Synology. Thanks for your patience.

JnHkstr commented 1 year ago

I have same error and I wonder when would v1.5 become available?

polmr commented 1 year ago

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).

coreice commented 1 year ago

Maybe good to know: today I updated from version 1.4.0 (from the Synology store) to version 1.6.1 via the package mentioned above. I had some troubles to get version 1.6.1 to work, removing the old .megaCmd folder in the (current) user home directory solved the issue for me (be aware you have to login again after removing).

cgagnaire commented 1 year ago

Sync is working as intended! Thanks for the work and the follow up!

AdmiralHawkins commented 1 year ago

Maybe good to know: today I updated from version 1.4.0 (from the Synology store) to version 1.6.1 via the package mentioned above. I had some troubles to get version 1.6.1 to work, removing the old .megaCmd folder in the (current) user home directory solved the issue for me (be aware you have to login again after removing).

Hello, Synology DS416 here with DSM 7.1.1-42962 Update 5, with MEGAcmd 1.4.0, got same "ERROR reading output socket" message and I solved doing this:

endremborza commented 1 year ago

Hello.

Synology still lists the 1.4 as the latest version on their site, and their package manager only offers that one as well. It is a bit troubling that they seem to have claimed that it would be released in a month over a year ago. Is there a way I can bug them with this or did something happen?

Thanks

endremborza commented 1 year ago

also, this:

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).

even expanded with this bit: https://github.com/meganz/MEGAcmd/blob/master/README.md#nas-systems is not quite clear to me.

my NAS runs with a INTEL Celeron J4025 DSM 7.2, among the files in https://mega.nz/folder/ogBQnbKa#CoRlU5uarTf4XpY3TbPELQ/folder/Z8pQlQSC (megacmdpkg-alpine4k-1.6.3-0001.spk, megacmdpkg-alpine-1.6.3-0001.spk, megacmdpkg-armada37xx-1.6.3-0001.spk, megacmdpkg-armada38x-1.6.3-0001.spk, megacmdpkg-kvmx64-1.6.3-0001.spk, megacmdpkg-monaco-1.6.3-0001.spk, megacmdpkg-rtd1296-1.6.3-0001.spk, megacmdpkg-rtd1619b-1.6.3-0001.spk) I have no idea which to use and I suspect none are designed to fit.

I promise I am not one to whine in the issues of an open-source product, but I actually pay for mega and would really appreciate this feature to work.

Thanks

polmr commented 1 year ago

@endremborza , here are some rebuilds of Synology packages in case you want to give them a try: https://mega.nz/folder/tIYE0CKY#IAlCrQ7AgcMMcWsyn70KYA

Your system would have a x86_64 architecture. Those would need the kvmx64 package.