May 23, 201115 yr I saw something for the first time tonight in my syslog. May 23 03:54:48 Tower logger: ./Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 03:54:48 Tower logger: .d..t...... Movies/ May 23 03:54:48 Tower logger: cd+++++++++ Movies/Planet Terror (2007)/ (Errors) May 23 03:54:48 Tower logger: >f+++++++++ Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 04:08:02 Tower logger: ./Movies/Planet Terror (2007) (Errors) May 23 04:08:02 Tower logger: .d..t...... Movies/Planet Terror (2007)/ (Errors) Mover moved about a dozen files for me, and this one was the only one with these error messages. All were moved to the same drive, which has 1TB of free space (so no issue with available space). Any reason why it would throw an error? What should I assume about the file? Is it corrupted? Did it not move to the protected array?
May 23, 201115 yr Author Mover has completed. The file is in my protected array. I played it some and skipped around to different parts and playback appears to be okay. I wonder what triggered the error?
May 23, 201115 yr Did anything have Planet Terror (2007).mkv open when mover ran? Mover tries to delete the /mnt/cache source after copying which could then fail for the file and the non-empty parent directory.
May 23, 201115 yr Any chance you had the \\tower\cache... directory open on a windows box? A telnet session open somewhere in the directory path? I honestly don't know. I think the "Errors" output is from find's -exec but any non-zero exit could cause that. - You know the file made it to the new destination, at least mostly complete. - Check to make sure the \\tower\cache copy is gone. If it's still there then the error could have been something preventing the delete, or a result from the copy that told the system not to trust the copy so don't delete the original. If the cache file is there use a CRC (or at least the cmp command) to verify files are the same before deleting the original. I'd be watching for more of these until I better understood the origin. I could be completely wrong; it's possible this error path is a normal part of mover's logic/process. Joe? Anyone?
May 24, 201115 yr Author No cache director open. No telnet. It was running a preclear on another drive at the time, but that wouldn't explain why 8 files moved with no errors, and just this one showed error status. It was moved to the protected array and it was deleted from the cache drive. I basically just don't know what the error was. Syslog really doesn't seem to say, and the file appears to have been moved intact.
May 24, 201115 yr I saw something for the first time tonight in my syslog. May 23 03:54:48 Tower logger: ./Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 03:54:48 Tower logger: .d..t...... Movies/ May 23 03:54:48 Tower logger: cd+++++++++ Movies/Planet Terror (2007)/ (Errors) May 23 03:54:48 Tower logger: >f+++++++++ Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 04:08:02 Tower logger: ./Movies/Planet Terror (2007) (Errors) May 23 04:08:02 Tower logger: .d..t...... Movies/Planet Terror (2007)/ (Errors) Mover moved about a dozen files for me, and this one was the only one with these error messages. All were moved to the same drive, which has 1TB of free space (so no issue with available space). Any reason why it would throw an error? What should I assume about the file? Is it corrupted? Did it not move to the protected array? It is NOT an error. It is YOU mistakenly assuming that unMENU's log file browser is able to tell the difference between a line in the log file with the word: error and one with the word Terror
May 24, 201115 yr Author I saw something for the first time tonight in my syslog. May 23 03:54:48 Tower logger: ./Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 03:54:48 Tower logger: .d..t...... Movies/ May 23 03:54:48 Tower logger: cd+++++++++ Movies/Planet Terror (2007)/ (Errors) May 23 03:54:48 Tower logger: >f+++++++++ Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 04:08:02 Tower logger: ./Movies/Planet Terror (2007) (Errors) May 23 04:08:02 Tower logger: .d..t...... Movies/Planet Terror (2007)/ (Errors) Mover moved about a dozen files for me, and this one was the only one with these error messages. All were moved to the same drive, which has 1TB of free space (so no issue with available space). Any reason why it would throw an error? What should I assume about the file? Is it corrupted? Did it not move to the protected array? It is NOT an error. It is YOU mistakenly assuming that unMENU's log file browser is able to tell the difference between a line in the log file with the word: error and one with the word Terror Well, I guess I thought unRAID was smarter than that. I have seen syslog errors that didn't contain the character string "error" in them and the syslog was able to identify them as an error. I assumed it did more than simply parse the character string of each log entry looking for a string matching "error". I guess their aren't alot of words contain the string "error" so the likely hood of false errors being reported is minimal. But Lime may want to warn users against changing the default Tower name to something like "Terror" or "Unholy Terror". Their syslog might freak out!
May 24, 201115 yr It is NOT an error. It is YOU mistakenly assuming that unMENU's log file browser is able to tell the difference between a line in the log file with the word: error and one with the word Terror Oh, that is excellent. I was trying to remember if anything extraneous like that might be produced from a failing find. unMENU hadn't even crossed my mind.
May 24, 201115 yr I saw something for the first time tonight in my syslog. May 23 03:54:48 Tower logger: ./Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 03:54:48 Tower logger: .d..t...... Movies/ May 23 03:54:48 Tower logger: cd+++++++++ Movies/Planet Terror (2007)/ (Errors) May 23 03:54:48 Tower logger: >f+++++++++ Movies/Planet Terror (2007)/Planet Terror (2007).mkv (Errors) May 23 04:08:02 Tower logger: ./Movies/Planet Terror (2007) (Errors) May 23 04:08:02 Tower logger: .d..t...... Movies/Planet Terror (2007)/ (Errors) Mover moved about a dozen files for me, and this one was the only one with these error messages. All were moved to the same drive, which has 1TB of free space (so no issue with available space). Any reason why it would throw an error? What should I assume about the file? Is it corrupted? Did it not move to the protected array? It is NOT an error. It is YOU mistakenly assuming that unMENU's log file browser is able to tell the difference between a line in the log file with the word: error and one with the word Terror Well, I guess I thought unRAID was smarter than that. I have seen syslog errors that didn't contain the character string "error" in them and the syslog was able to identify them as an error. I assumed it did more than simply parse the character string of each log entry looking for a string matching "error". I guess their aren't alot of words contain the string "error" so the likely hood of false errors being reported is minimal. But Lime may want to warn users against changing the default Tower name to something like "Terror" or "Unholy Terror". Their syslog might freak out! First, the unMENU syslog viewer and coloring scheme has absolutely nothing to do with lime-technology. It is mostly the work of unRAID users like yourself who looked at the messages in the syslog and defined a set of patterns to use to color code them. The pattern matching is not the most complete, and it was mostly defined years ago when first written, but it has been fairly decent. The pattern/colors to be matched are in /boot/unmenu/syslog_match.conf You can define additional locally defined rules in /boot/unmenu/syslog_match_local.conf if you desire. The lines in "red" (errors) are those that match the following patterns: any_case ||"error"||red match_case||"Emask "||red match_case||"arity incorrect"||red match_case||"Fsck?"||red match_case||"invalid opcode: "||red match_case||"nobody cared"||red match_case||"Unknown boot option"||red match_case||" ata[0-9\. ]+: disabled"||red match_case||" DMA disabled"||red match_case||"kernel BUG "||red match_case||"Write Protect is on"||red any_case||"Call trace"||red any_case||"tainted"||red any_case||"kernel: \["||red any_case||"out[ _]of[ _]memory"||red any_case||"killed"||red match_case||"HPA detected: current [0-9]*055,"||red That first line will match the character string "error" anywhere on a syslog line and write it in "red" Since it uses regular expressions I'm sure it could be improved to ignore "Terror", but still match "error" The first rule matched sets the color. Therefore you can define a new rule any_case||"Terror"||black put it at the top of the syslog_match.conf file, and it will force the Terror line to be shown as "black" and ignored. Joe L.
Archived
This topic is now archived and is closed to further replies.