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

BackInTime snapshots fail with path errors #1262

Closed
casanovg opened this issue Jun 28, 2022 · 6 comments
Closed

BackInTime snapshots fail with path errors #1262

casanovg opened this issue Jun 28, 2022 · 6 comments

Comments

@casanovg
Copy link

Backintime stopped working on Fedora 36 as of June 5th, it worked smoothly before. The backup storage I am using is remote, mounting sshfs folders.

The error it returns when launching a snapshot is from rsync (see below). However, I've tried copying directories by hand to remote sshfs folders with several different rsync options and it works fine.

This initially rules out login and connection problems with the backup server. It would give the impression that backintime is "building" the routes wrong before launching the rsync command:

WARNING: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/netbackup/.ssh/id_rsa -p 22 /tmp/tmpawvpdq4q/ netbackup@10.6.17.70:"/mnt/hta-nasvol01/hta-backup/backintime/hta-fileserver.htarg.lan/netbackup/10/20220628-091035-792"" returns 3 | rsync: change_dir#3 "/mnt/hta-nasvol01/home/netbackup//"/mnt/hta-nasvol01/hta-backup/backintime/hta-fileserver.htarg.lan/netbackup/10" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(703) [Receiver=3.1.3]

Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 1165, in
startApp()
File "/usr/share/backintime/common/backintime.py", line 517, in startApp
args.func(args)
File "/usr/share/backintime/common/backintime.py", line 739, in backup
ret = takeSnapshot(cfg, force)
File "/usr/share/backintime/common/backintime.py", line 94, in takeSnapshot
ret = snapshots.Snapshots(cfg).backup(force)
File "/usr/share/backintime/common/snapshots.py", line 701, in backup
self.remove(sid)
File "/usr/share/backintime/common/snapshots.py", line 583, in remove
shutil.rmtree(sid.path())
File "/usr/lib64/python3.10/shutil.py", line 714, in rmtree
onerror(os.lstat, path, sys.exc_info())
File "/usr/lib64/python3.10/shutil.py", line 712, in rmtree
orig_st = os.lstat(path)

FileNotFoundError: [Errno 2] No such file or directory: '/home/netbackup/.local/share/backintime/mnt/8_15082/backintime/hta-fileserver.htarg.lan/netbackup/10/20220628-091035-792'

@casanovg casanovg changed the title Backintime-qt snapshots fail with path errors BackInTime snapshots fail with path errors Jun 28, 2022
@gsker
Copy link

gsker commented Jun 28, 2022

Could you include your version of backintime and the version of rsync?

@casanovg
Copy link
Author

Sure ...
[netbackup@hta-fileserver ~]$ backintime --version
backintime 1.3.2
[netbackup@hta-fileserver ~]$ rsync --version
rsync version 3.2.4 protocol version 31

@gsker
Copy link

gsker commented Jun 28, 2022

Is this a duplicate of #1247 ?

@emtiu
Copy link
Member

emtiu commented Jun 28, 2022

Is this a duplicate of #1247 ?

Looks like it. @casanovg, could you test if the workarounds described there help you out for the moment?

@casanovg
Copy link
Author

Apparently yes, it's the same. Adding "--old-args" as suggested in that thread works again, Thanks!
Sorry to open a new issue, I didn't link it by title because I normally use the BackInTime version packed by Fedora "out-of-the-box". I never update its components (rsync, QT, etc.) individually.

@emtiu
Copy link
Member

emtiu commented Jun 28, 2022

Apparently yes, it's the same. Adding "--old-args" as suggested in that thread works again, Thanks! Sorry to open a new issue, I didn't link it by title because I normally use the BackInTime version packed by Fedora "out-of-the-box". I never update its components (rsync, QT, etc.) individually.

No problem, we're a new, small team trying to sort things out with issues etc. before touching the code and hopefully getting backintime back in shape :) Thanks for reporting!

@emtiu emtiu closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants