meridian Posted August 26, 2022 Share Posted August 26, 2022 (edited) Hi, I have issues with my setup (6.10.3) and my logs are filling up rapidly and I have to manually reboot several times a week. I can se two types of errors and it only happens when a Windows 11 VM is turned on. The VM itself runs fine as far as I can tell. Can anyone provide me with some ideas on how to fix it? Quote Aug 25 14:26:14 unraid01 nginx: 2022/08/25 14:26:14 [error] 6201#6201: nchan: Out of shared memory while allocating message of size 5862. Increase nchan_max_reserved_memory. Aug 25 14:26:14 unraid01 nginx: 2022/08/25 14:26:14 [error] 6201#6201: *5562084 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Aug 25 14:26:14 unraid01 nginx: 2022/08/25 14:26:14 [error] 6201#6201: MEMSTORE:00: can't create shared message for channel /disks Aug 25 14:26:15 unraid01 nginx: 2022/08/25 14:26:15 [crit] 6201#6201: ngx_slab_alloc() failed: no memory Aug 25 14:26:15 unraid01 nginx: 2022/08/25 14:26:15 [error] 6201#6201: shpool alloc failed Quote Aug 25 22:06:30 unraid01 kernel: CPU: 15 PID: 16617 Comm: CPU 9/KVM Tainted: G W 5.15.46-Unraid #1 Aug 25 22:06:30 unraid01 kernel: Call Trace: Aug 25 22:08:04 unraid01 kernel: CPU: 12 PID: 16611 Comm: CPU 3/KVM Tainted: G W 5.15.46-Unraid #1 Aug 25 22:08:04 unraid01 kernel: Call Trace: Aug 26 01:03:04 unraid01 kernel: CPU: 7 PID: 16616 Comm: CPU 8/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:03:04 unraid01 kernel: Call Trace: Aug 26 01:03:38 unraid01 kernel: CPU: 15 PID: 16617 Comm: CPU 9/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:03:38 unraid01 kernel: Call Trace: Aug 26 01:03:52 unraid01 kernel: CPU: 6 PID: 16614 Comm: CPU 6/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:03:52 unraid01 kernel: Call Trace: Aug 26 01:05:58 unraid01 kernel: CPU: 14 PID: 16615 Comm: CPU 7/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:05:58 unraid01 kernel: Call Trace: Aug 26 01:06:09 unraid01 kernel: CPU: 5 PID: 16612 Comm: CPU 4/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:06:09 unraid01 kernel: Call Trace: Aug 26 01:06:21 unraid01 kernel: CPU: 14 PID: 16615 Comm: CPU 7/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:06:21 unraid01 kernel: Call Trace: Aug 26 01:06:48 unraid01 kernel: CPU: 13 PID: 16613 Comm: CPU 5/KVM Tainted: G W 5.15.46-Unraid #1 Aug 26 01:06:48 unraid01 kernel: Call Trace: unraid01-diagnostics-20220826-1053.zip unraid01-syslog-20220826-0906.zip Edited August 30, 2022 by meridian Solved Quote Link to comment
Solution JorgeB Posted August 26, 2022 Solution Share Posted August 26, 2022 Try updating to v6.11.0-rc4, if that doesn't help and IIRC a user with a similar error KVM error fixed it by creating as new identical VM, i.e., it was something in that specif VM. Quote Link to comment
meridian Posted August 29, 2022 Author Share Posted August 29, 2022 Thanks, I´ll give it a try. 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.