WuZiMu Posted February 16, 2021 Share Posted February 16, 2021 (edited) Could use help determining root cause of these two issues. Particularly, the latter which causes the shares to go missing causing the Docker containers to go ham and my CPU usage to spike to 90-100%. This started happening repeatedly in the past few weeks. Before I'd have weeks of uptime. I'd appreciate any troubleshooting tips. The first set of error messages. Feb 15 04:29:24 Vendetta nginx: 2021/02/15 04:29:24 [error] 9532#9532: shpool alloc failed Feb 15 04:29:24 Vendetta nginx: 2021/02/15 04:29:24 [error] 9532#9532: nchan: Out of shared memory while allocating message of size 10057. Increase nchan_max_reserved_memory. Feb 15 04:29:24 Vendetta nginx: 2021/02/15 04:29:24 [error] 9532#9532: *94514 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Second set of error messages, see csum failed root. Google search indicates it might be a cache drive issue. But why is it reporting BTRFS when all drives are formatted as XFS? Restarting the machine seems to fix the issue temporarily but it comes back after a day or two of uptime. Quote Feb 16 04:40:17 Vendetta kernel: BTRFS warning (device loop3): csum failed root 1127 ino 15735 off 36864 csum 0x63e4a1df expected csum 0x16c777d4 mirror 1 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Feb 16 04:40:18 Vendetta sSMTP[13757]: Sent mail for [email protected] (221 2.0.0 closing connection d22sm12973631qtp.34 - gsmtp) uid=0 username=xxx outbytes=529 Feb 16 04:40:19 Vendetta kernel: BTRFS warning (device loop3): csum failed root 1127 ino 15735 off 36864 csum 0x63e4a1df expected csum 0x16c777d4 mirror 1 ### [PREVIOUS LINE REPEATED 560 TIMES] ### Feb 16 04:49:40 Vendetta usbhid-ups[8061]: nut_libusb_get_string: Pipe error. Feb 16 04:49:40 Vendetta kernel: BTRFS warning (device loop3): csum failed root 1127 ino 15735 off 36864 csum 0x63e4a1df expected csum 0x16c777d4 mirror 1 ### [PREVIOUS LINE REPEATED 1075 TIMES] ### vendetta-diagnostics-20210216-0630.zip Edited February 16, 2021 by WuZiMu Quote Link to comment
JorgeB Posted February 16, 2021 Share Posted February 16, 2021 Delete and recreate the docker image, but if it keeps getting corrupt out of the blue you likely have a hardware problem, like bad RAM. 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.