meganz / MEGAcmd

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

MEGAcmd sync Pending not changing #191

Open vikramthapa opened 5 years ago

vikramthapa commented 5 years ago

As per my understanding,

$> sync [local path] [remote path]

tell me if I misunderstood.

Command issued: $ sync /home/online /online

Where, /home/online is a local directory in by Ubuntu Linux and /online is a directory in MEGA remote directory. But, the SyncState is always Pending. Why is that?

ID LOCALPATH REMOTEPATH ActState SyncState SIZE FILES DIRS 0 /home/.../online /online Active Pending 0.00 B 0 1

Why is that? I am confused.

polmr commented 5 years ago

Your command was issued correctly. It should eventually change to state Synced. Remember you need to have permissions to access local folder. If the problem persist, debugging might be required (https://github.com/meganz/MEGAcmd/blob/master/contrib/docs/DEBUG.md). If you can't find the reason and you can reproduce it, you might want to procure us a log of the server while that happens. In order to do so: Please, close all megacmd instances and execute the server in a separate console: Open a console and type

killall -2 mega-cmd-server mega-cmd-server --debug-full | tee megacmd.log Then, open another console and then try to reproduce the issue. Finally quit the server (Ctrl+C in the console that run it should do). Then please send us that megacmd.log file. The log might contain some sensitive data. Feel free to remove anything you don't want to share with us. If you do not want to post it here (you'd rather not), send it to support@mega.nz and refer this issue in your email so that it can reach development team.

graphitegh commented 4 years ago

Could you guys get to the bottom of this? I did what the guy above did all 8.9GB is Pending not syncing. Thanks

ID LOCALPATH REMOTEPATH ActState SyncState SIZE FILES DIRS
0 /home/user/localfoldermega / Active Pending 8.93 GB 25001 5532

alexxxz1977 commented 2 years ago

Check the logs and be sure that you have "write" access to a local folder