May 13, 20242 yr 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.
May 15, 20242 yr 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.
May 16, 20242 yr Author 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
May 16, 20242 yr Author 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.
May 16, 20242 yr 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.
May 18, 20242 yr Author 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.
May 18, 20242 yr 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.
May 22, 20242 yr Author 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.
June 18, 20242 yr Author On 5/22/2024 at 3:30 AM, JorgeB said: Post the complete persistent syslog. I finally caught the error as it was happening and was about to get the logs leading up to the repeating line. Jun 18 15:54:15 cloud kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd Jun 18 15:54:15 cloud kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd Jun 18 15:54:15 cloud kernel: cp210x 1-4:1.0: cp210x converter detected Jun 18 15:54:15 cloud kernel: usb 1-4: cp210x converter now attached to ttyUSB0 Jun 18 15:54:15 cloud kernel: cp210x 1-4:1.1: cp210x converter detected Jun 18 15:54:15 cloud kernel: cp210x 1-4:1.1: Failed to attach ACPI GPIO chip Jun 18 15:54:15 cloud kernel: usb 1-4: cp210x converter now attached to ttyUSB1 Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager tty_add Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager tty_add Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 Jun 18 15:54:15 cloud kernel: usb 1-2.3: reset high-speed USB device number 7 using xhci_hcd Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager Processing tty attach Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager Processing tty attach Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 port Jun 18 15:54:15 cloud usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 port Jun 18 15:54:17 cloud kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 Jun 18 15:54:17 cloud kernel: cp210x 1-4:1.0: device disconnected Jun 18 15:54:17 cloud kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1 Jun 18 15:54:17 cloud kernel: cp210x 1-4:1.1: Failed to retrieve ACPI GPIO chip Jun 18 15:54:17 cloud kernel: cp210x 1-4:1.1: device disconnected Jun 18 15:54:18 cloud kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd Jun 18 15:54:19 cloud kernel: usb 1-4: reset full-speed USB device number 4 using xhci_hcd Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.0: cp210x converter detected Jun 18 15:54:19 cloud kernel: usb 1-4: cp210x converter now attached to ttyUSB0 Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.1: cp210x converter detected Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.1: Failed to attach ACPI GPIO chip Jun 18 15:54:19 cloud kernel: usb 1-4: cp210x converter now attached to ttyUSB1 Jun 18 15:54:19 cloud kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.0: device disconnected Jun 18 15:54:19 cloud kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1 Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.1: Failed to retrieve ACPI GPIO chip Jun 18 15:54:19 cloud kernel: cp210x 1-4:1.1: device disconnected Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager tty_add Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager tty_add Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 Jun 18 15:54:19 cloud kernel: usb 1-2.3: reset high-speed USB device number 7 using xhci_hcd Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager Processing tty attach Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB1 port Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager Processing tty attach Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 Jun 18 15:54:19 cloud usb_manager: Info: rc.usb_manager Autoconnect No Mapping found Silicon_Labs_HubZ_Smart_Home_Controller_6160034E /dev/ttyUSB0 port Jun 18 15:56:21 cloud kernel: usb 1-4: usbfs: process 20431 (qemu-system-x86) did not claim interface 1 before use And then the last line repeats until the log fills and system crashes
June 19, 20242 yr Looks like a problem with a USB device, see if you can identify and leave it temporarily disconnected to re-test
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.