Thank you for the report!

I can reproduce it with the mirror that you mentioned in IRC:


 # mb scan muug
Tue Dec  1 18:52:12 2009 www.muug.mb.ca: starting
Tue Dec  1 18:52:17 2009 www.muug.mb.ca: total files before scan: 0
www.muug.mb.ca: Moved to ftp location, assuming success if followedwww.muug.mb.ca: Moved to 
ftp location, assuming success if followedwww.muug.mb.ca: Moved to ftp location, assuming 
success if followedwww.muug.mb.ca: Moved to ftp location, assuming success if 
followedwww.muug.mb.ca: Moved to ftp location, assuming success if followed__DIE__: 
(/usr/bin/scanner 1026 main::sread => /usr/bin/scanner 989 (eval) => /usr/bin/scanner 989 
main::__ANON__)
__DIE__: (/usr/bin/scanner 968 main::rsync_get_filelist => /usr/bin/scanner 1134 
main::muxread => /usr/bin/scanner 1026 main::sread)
rsync timeout...
Completed in 10.8 minutes


This is related to issue 11.

I agree with the suggestion, that it might be useful if the mirror is disabled when scanning 
problems occur, especially if they persist. A good notification about the problem could be a 
good replacement for automatic action, fully agreed.

On the other hand, it is also important to find out wether the scanner crashes for some 
reason, because it would also be good if it continues its work. In the above case, the scan 
via rsync ran into a timeout. There's not much to do though, and it wouldn't be useful if the 
scan cannot be takes days either.

scanner should handle mirrors, which cant be scanned better

options:
1. like disable the mirror.
2. inform the admin more directly. the scanner output mail is a bit noisy.