Timer too close error, log files wrapping???
I have gotten intermittent (as in maybe every week at most) "Timer too close" errors that hose a print. While looking at the latest klippy.log I noticed that it happened right after midnight for the raspberry pi OS localtime. While looking at the log files I noticed that my crowsnest log file was huge (2GB). I am now suspicious that the "timer too close" error is caused by the log file wrapping that happens at midnight. Not sure if the log file wrapping does a file "move" or a file "copy". One would think a file move would not cause significant IO or cpu usage. But a file copy would cause a lot of IO. Now, I know I do not want a 2GB crowsnest log file, so I did edit the crowsnest config file to change the log level to "quiet". Hopefully that will fix that problem. And wondering if others have noticed a timer too close error at midnight. Or maybe it is just a coincidence. Unfortunately I have no other older logs with this error so I cannot check if they happened at midnight or not.
0 Replies