FS#38727 - {mirror} symlink has no referent (rsync error)

Attached to Project: Arch Linux
Opened by rrze-ftp-admins (rrze-ftp-admins) - Thursday, 30 January 2014, 15:14 GMT
Last edited by Florian Pritz (bluewind) - Thursday, 05 June 2014, 20:33 GMT
Task Type Bug Report
Category Mirrors
Status Closed
Assigned To Florian Pritz (bluewind)
Jakob Wadsager (fleet)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

According to rsync, syncs from ftp5.gwdg.de fail. The problem seems to lay with a bad symlink:

$ VERBOSE=1 ~/bin/rsync-wrapper-ftp.sh archlinux
Doing work now, calling rsync: rsync -v --progress -rtlHq --delete-after --delay-updates --copy-links --safe-links --max-delete=5000 --delete-excluded --exclude=.* rsync://ftp5.gwdg.de/pub/linux/archlinux/ '/data/ftp///archlinux//'...
symlink has no referent: "/linux/archlinux/community/os/i686/python-xlib-0.15rc1-6-any.pkg.tar.xz.sig" (in pub)
symlink has no referent: "/linux/archlinux/community/os/x86_64/python-xlib-0.15rc1-6-any.pkg.tar.xz.sig" (in pub)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1536) [generator=3.0.9]
$

This task depends upon

Closed by  Florian Pritz (bluewind)
Thursday, 05 June 2014, 20:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Confirmed fixed via email.
Comment by rrze-ftp-admins (rrze-ftp-admins) - Tuesday, 18 February 2014, 07:32 GMT
Ping.

The problem still exists and causes rsync to exit with exitcode 2. This means that for every mirror, that automatically tracks the sync processes (like ftp.fau.de does, which can be seen at http://ftp.fau.de/cgi-bin/show-mirror-status.cgi), archlinux pops up as failed.
Comment by rrze-ftp-admins (rrze-ftp-admins) - Wednesday, 26 February 2014, 20:24 GMT
When ever somebody fixes this, please inform us. Until then, monitoring will just be ignored and we won't notice if anything significant goes wrong with our two mirrors.
Comment by Florian Pritz (bluewind) - Thursday, 29 May 2014, 21:39 GMT
Thanks for reporting, should be all good now. Please test.
Comment by Oleg Lyashko (ovl) - Thursday, 29 May 2014, 22:38 GMT
Tested on several repo - the problem resolved.

Loading...