Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39614 - [rsnapthost] will not work with cp
Attached to Project:
Community Packages
Opened by Mikey D (ProfessorKaos64) - Monday, 24 March 2014, 21:00 GMT
Last edited by Florian Pritz (bluewind) - Wednesday, 26 March 2014, 21:23 GMT
Opened by Mikey D (ProfessorKaos64) - Monday, 24 March 2014, 21:00 GMT
Last edited by Florian Pritz (bluewind) - Wednesday, 26 March 2014, 21:23 GMT
|
DetailsDescription: I cannot run rsnapshot as a normal user, only as root. This stopped functioning only after I started getting suspicious about my logfiles. If I comment out the locate to cp at /usr/bin/cp, the backup runs just fine. The paths in the error are fully accessible
Error Produced: [code] [24/Mar/2014:02:00:01] /usr/bin/rsnapshot daily: started [24/Mar/2014:02:00:01] echo 32621 > /mnt/backup_drive/rsnapshot.pid [24/Mar/2014:02:00:01] mv /mnt/backup_drive/daily.5/ /mnt/backup_drive/daily.6/ [24/Mar/2014:02:00:01] mv /mnt/backup_drive/daily.4/ /mnt/backup_drive/daily.5/ [24/Mar/2014:02:00:01] mv /mnt/backup_drive/daily.3/ /mnt/backup_drive/daily.4/ [24/Mar/2014:02:00:01] mv /mnt/backup_drive/daily.2/ /mnt/backup_drive/daily.3/ [24/Mar/2014:02:00:01] mv /mnt/backup_drive/daily.1/ /mnt/backup_drive/daily.2/ [24/Mar/2014:02:00:01] /usr/bin/cp -al /mnt/backup_drive/daily.0 /mnt/backup_drive/daily.1 [24/Mar/2014:02:31:27] /usr/bin/rsnapshot daily: ERROR: /usr/bin/cp -al /mnt/backup_drive/daily.0 /mnt/backup_drive/daily.1 failed (result 256, exit status 1). Perhaps your cp does not support -al options? [24/Mar/2014:02:31:27] /usr/bin/rsnapshot daily: ERROR: Error! cp_al("/mnt/backup_drive/daily.0/", "/mnt/backup_drive/daily.1/") [24/Mar/2014:02:31:27] /usr/bin/logger -i -p user.err -t rsnapshot /usr/bin/rsnapshot daily: ERROR: Error! cp_al("/mnt/backup_drive/daily.0/", "/mnt/backup_drive/daily.1/") [24/Mar/2014:02:31:27] rm -f /mnt/backup_drive/rsnapshot.pid [/code] Additional info: * package version(s) rsnapshot 1.3.1-5 coreutils 8.22-3 (base) * config and/or log files etc. rsnapshot config: slexy.org/view/s25ckxjOGM Steps to reproduce: [code] # uncomment this to use the rm program instead of the built-in perl routine. # cmd_rm /usr/bin/rm Leave "cmd_rm" uncommented. [/code] |
This task depends upon
Closed by Florian Pritz (bluewind)
Wednesday, 26 March 2014, 21:23 GMT
Reason for closing: Works for me
Wednesday, 26 March 2014, 21:23 GMT
Reason for closing: Works for me
Also why do you mention cmd_rm at the end of the report?
cp -al /mnt/backup_drive/daily.0/ /mnt/backup_drive/daily.1/
I apologize, then end of the report should be :
# LINUX USERS: Be sure to uncomment "cmd_cp". This gives you extra features.
# EVERYONE ELSE: Leave "cmd_cp" commented out for compatibility.
#
# See the README file or the man page for more details.
#
cmd_cp /usr/bin/cp