Bugzilla – Bug 17466
scanner doesn't say which file it's croaking on
Last modified: 2011-08-21 04:57:43 UTC
This is SBS r33110. But it's actually 7.6.1, and the OSX version is 10.8. You guys need a new sysadmin. I have no idea where the Mac version of SBS is finding all these files from. I just installed it to test something. Could the scanner list the filename? I guess that this is the redirected stderr, and it's the C libraries which are being unhelpful. hawkwind% tail scanner.log [11-08-18 23:37:14.5016] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.5281] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.5438] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.5671] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.5963] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.6166] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.6401] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.6672] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.6814] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). [11-08-18 23:37:14.7005] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file (only read 4). hawkwind%
I see this also in 7.6.1 r33073 on Windows 7: [11-08-14 08:13:48.1134] Audio::Scan::scan (64) Warning: Error: Unable to read at least 10 bytes from file. [11-08-14 08:14:15.5047] Audio::Scan::scan (64) Warning: Error: Unable to read at least 16 bytes from file. The default logging levels show no indication of which files are problematic. 7.5.x logging levels did show each file name as it was scanned which made identification easier but that is gone in 7.6.x. Although it is possible to increase the log level to do this, it would be good to name the file with this error to remove the need to do this. Full story at: http://forums.slimdevices.com/showthread.php?p=649773#post649773 The details of the problematic files are in bug 17475.
Of course if the scanner barfs at a file kindly piont the user to it . In my ideal parallell universe, sbs would have a button to automagically upload a problem file for analyzis and the result would be mailed to you afterwards ;)
*** This bug has been confirmed by popular vote. ***