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
Title scanner should handle mirrors, which cant be scanned better
Priority wish Status chatting
Make an option to ignore timeouts during darix,
Superseder scans. Nosy List poeml
View: 107
Assigned To Keywords scanner
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.
History
Date User Action Args
2012-04-16 04:51:59 poeml set superseder: + Make an option to ignore
timeouts during scans.
status: unread -> chatting
2009-12-01 21:53:42 poeml set nosy: + poeml
messages: + msg79
2009-12-01 20:54:43 poeml set keyword: + scanner
2009-12-01 18:13:28 darix create
(end of migrated issue)
The text was updated successfully, but these errors were encountered:
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue28
msg73 (view) Author: darix Date: 2009-12-01.18:13:28
scanner should handle mirrors, which cant be scanned better
options:
msg79 (view) Author: poeml Date: 2009-12-01.21:53:41
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.
(end of migrated issue)
The text was updated successfully, but these errors were encountered: