search

meganz / MEGAcmd

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

How to identify missing file(s) in mega-put? #889

Open rsbrux opened 1 year ago

rsbrux commented 1 year ago

I have megacmd running on a Synology NAS to regularly copy the contents of a NAS folder to MEGA: mega-put -c -vvv <NAS directory> <MEGA directory> DSM is running megacmd v4.0. Since I upgraded Synology DSM from 6.2 to 7.1.1 I am getting: Current status: 13 (Interrupted) Despite -vvv, the log doesn't give any useful information. It just shows a few lines like this: [API:err: 03:07:01] Failed to upload: Incomplete Under DSM I can't provide debug flags to megacmd on startup, it is either running or it isn't. How can I find out what is "incomplete" in this transfer?

rsbrux commented 1 year ago

This is happening every day. Can't anyone give me a hint?

ZhmerenkaSolution commented 11 months ago

I do not recommend to use put https://github.com/meganz/MEGAcmd/issues/909#issuecomment-1786713377 If you can read output of console window, you may launch first MEGAcmdServer and then execute mega-put, server usually contains transfer or read files/folders errors.

rsbrux commented 11 months ago

I have to use put because I need one-way transfers. I am saving rotating backup versions (a la rsync). Running the server interactively just to see an error message is quite unwieldy. What are the chances of mega-put getting some useful logging, at least of errors?

ZhmerenkaSolution commented 11 months ago

@rsbrux I suppose server running in background even if you simply execute mega-put.

What are the chances of mega-put getting some useful logging, at least of errors

MEGAServer have to output transfer errors.

rsbrux commented 10 months ago

where can I find the megaserver error log?

rsbrux commented 10 months ago

Running the command: mega-put -c -vvv /volume1/Backup/IMCZ /IMCZ/backups/WildApricot/Monday interactively doesn't yield any more useful information, despite the -vvv option:

[API:debug: 13:35:33] Starting upload: /volume1/Backup/IMCZ to : WildApricot/Monday
[API:err: 13:41:44] Failed to upload: Incomplete#################################################||(1/1 KB: 100.00 %)
[verbose: 13:41:44] Inform State Listener: Output to write in socket 651: <<progress:-2:4324634370>>
[API:verbose: 13:41:44]  Procesed put --client-width=118 --clientID=278 -c -vvv /volume1/Backup/IMCZ /IMCZ/backups/WildApricot/Monday in thread: 140474933298944 socket output: 659
[verbose: 13:41:44] Output to write in socket 659
TRANSFERRING ||############################################################################||(4124/4124 MB: 100.00 %)
rsbrux commented 10 months ago

As a workaround, I downloaded an entire backup and conducted a file-by-file comparison, which revealed many failures. This cannot be the way to go, however. How can I get a log of the upload errors?