Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer gets killed after running for some time #123

Open
canedmonkey opened this issue Jun 27, 2023 · 3 comments
Open

Transfer gets killed after running for some time #123

canedmonkey opened this issue Jun 27, 2023 · 3 comments
Labels
needinfo Further information is needed

Comments

@canedmonkey
Copy link

Hi

I have successfully managed to start a file transfer but if the file transfer takes longer than the timeout value, the tasks exits at timeout. Transfer is stopped.

Similarly, task will continue to run even when file transfer has stopped and will only stop at timeout.

I could see that my file transfer was no completing so I used --log-file= to capture the output. The file transfer just seems to stop mid transfer, no error or exit. Tasker just keeps running until timeout is reached and then exits with timeout error

@ribbons
Copy link
Owner

ribbons commented Jun 28, 2023

This sounds to me like two different issues?

You're correct that if the Tasker timeout is configured to be less than the time taken for a transfer it will stop but the transfer continues running. It isn't currently possible for Rsync for Tasker to get the timeout configured on the Tasker side, but I requested this to be added to the plugin library and the good news is that João kindly implemented this, so should be in the next release of the library (whenever that is): joaomgcd/TaskerPluginSample#21. After that happens I can then implement more intuitive behaviour of killing rsync when the timeout is about to be reached.

I've not been able to reproduce your second issue but it sounds like something might be stopping the plugin after it has been running for a while, have you tried disabling battery optimisation for Rsync for Tasker? If you have it would be good if you can share more info (device, Android version, length of time before stopping, size of transfer, etc).

@ribbons ribbons added the needinfo Further information is needed label Jun 28, 2023
@canedmonkey
Copy link
Author

I tried to disable battery optimisation for rsync and tasker but no joy. The transfer just seems to stop with no indication why. Very frustrating but I seem to have got it to work anyway

I'm trying to make a backucup copy of my home folder, so it's fairly large at 3.3Gb. I found that if I run rsync in archive -a mode then the transfer picks up where it left off and after three or four attempts, I did end up with a complete copy of /sdcard/ on my NAS.

Subsequent backups now complete with no problem as they are obviously much smaller. Transferring single directories completes without a problem. I backed up my DCIM folder which is about 800mb, and the transfer was lightning fast.

I can use this along with the wakeonlan plugin to backup my home folder to my NAS every night at 4am. Tested it last night and the photos I took yesterday are now on my NAS... Nice

@ribbons
Copy link
Owner

ribbons commented Jul 2, 2023

Ah, great - glad you were able to get the full transfer done in several attempts. Sounds like something might be killing off the process after a certain length of time, so I'll leave this issue open for others to add their findings to so we can try and figure out the cause.

@ribbons ribbons changed the title Task only stops at Timeout Transfer gets killed after running for some time Jul 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needinfo Further information is needed
Projects
None yet
Development

No branches or pull requests

2 participants