jpfeifer14 Posted May 13 Share Posted May 13 Unraid is intermittently crashing because the log fills up with this error: May 13 12:00:00 cloud kernel: usb 1-4: usbfs: process 14474 (qemu-system-x86) did not claim interface 1 before use [4:50 PM] usb 1-4 is a zwave/zigbee controller attached to HA vm. Most of the time there is no issue, but occasionally it starts throwing back that error and the whole server crashes as a result of the Log filling up. Quote Link to comment
jpfeifer14 Posted May 15 Author Share Posted May 15 cloud-diagnostics-20240514-2206.zip Quote Link to comment
JorgeB Posted May 15 Share Posted May 15 I'm not seeing that error on the diags, I do see constant OOM errors apparently caused by frigate, you may want to limit its RAM usage. Quote Link to comment
jpfeifer14 Posted May 16 Author Share Posted May 16 That was a past issue I had, I thought I had limited its ram usage. But the other day, and one other time this month, the error from my original post was filling the logs Quote Link to comment
jpfeifer14 Posted May 16 Author Share Posted May 16 Is there a way to at least maybe stop a crash from the log filling up? Can it be set to only retain a certain number of log entries? When the server crashes and Im out of town its a bit of a problem. Quote Link to comment
JorgeB Posted May 16 Share Posted May 16 It could be helpful seeing the start of that error, you can enable the syslog server to see if it can catch it. Regarding the log, you could for example use a user script to make it rotate sooner. Quote Link to comment
jpfeifer14 Posted Saturday at 02:37 AM Author Share Posted Saturday at 02:37 AM Unfortunately the backup syslog provided no extra context, just that same error repeating. The log history ended before it showed the start of the error. Quote Link to comment
JorgeB Posted Saturday at 07:16 AM Share Posted Saturday at 07:16 AM 4 hours ago, jpfeifer14 said: The log history ended before it showed the start of the error. Nut sure I follow, log should have everything from when it was enabled until now, post that log. Quote Link to comment
jpfeifer14 Posted yesterday at 05:06 AM Author Share Posted yesterday at 05:06 AM On 5/18/2024 at 2:16 AM, JorgeB said: Nut sure I follow, log should have everything from when it was enabled until now, post that log. It crashed the server, so I had to reboot. I looked for the historical log entries in the local log server, but the entire log was populated with the same error. Quote Link to comment
JorgeB Posted yesterday at 08:30 AM Share Posted yesterday at 08:30 AM Post the complete persistent syslog. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.