You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the server, for whatever reason, does not have rsync installed, backintime will simply state that there has been no changes since the last snapshot and will not record an error, no give any indication that something is wrong other than the time to decide nothing has changed is ludicrously short (almost instant).
In my case, the server containing the snapshot was rebuilt and I forgot to reinstall rsync. The error given when manually running the rsync command found in the information log on the shell is:
bash: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: remote command not found (code 127) at io.c(226) [sender=3.1.1]
The text was updated successfully, but these errors were encountered:
BiT does check the remote server if it is able to create snapshots when you press OK in Settings. But these tests are to heavy to run every time a new snapshot is executed.
I'm working on analyzing rsync return code. Currently the return code is not used.
If the server, for whatever reason, does not have rsync installed, backintime will simply state that there has been no changes since the last snapshot and will not record an error, no give any indication that something is wrong other than the time to decide nothing has changed is ludicrously short (almost instant).
In my case, the server containing the snapshot was rebuilt and I forgot to reinstall rsync. The error given when manually running the rsync command found in the information log on the shell is:
The text was updated successfully, but these errors were encountered: