Since I upgraded to version 6.12 i have random crashes, difficult to replicate causing the server to be completely unresponsive remotely and physically there (the screen won't even turn on or keyboard respond) forcing me to reboot.

 

Things I have tried;

 

- Ensured Docker is set to IPVLAN

- Upgraded from 6.12.6 to 6.12.9

- Enabled the syslog server

 

I have another crashed on April 9th, what seems to be at around 3:32 am, the logs don't seem to provide anything of help.

I have attached my diagnostics and the syslog, any help or input would be appreciated.

 

Previous to yesterdays crash, the 2 times before that, I do know what the last thing i did was before it crashed: I have a windows VM running Blueiris and i logged into it to check the cameras. Yesterdays though, i did not perform that action.

kenny-diagnostics-20240409-0554.zip syslog-192.168.1.110.log

I noticed on the bootup log the following line 

 

Apr  9 05:42:02 kenny kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

 

Is that a concern? What does it mean?

 

 

Edited April 10, 20242 yr by flixxx

Anyone can offer any suggestions?

On 4/10/2024 at 1:09 AM, flixxx said:

Is that a concern?

Possibly not, I've seen those in various diags of users with no apparent issues, post another syslog after the next crash to see if there's anything else there.

It just happened again, May 2nd 7:22 am. This is the start of the errors. i attached the full log

 

May  2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: shpool alloc failed
May  2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: nchan: Out of shared memory while allocating message of size 8717. Increase nchan_max_reserved_memory.
May  2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: *6796183 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
May  2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: MEMSTORE:00: can't create shared message for channel /disks
May  2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [crit] 9348#9348: ngx_slab_alloc() failed: no memory
May  2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: shpool alloc failed
May  2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: nchan: Out of shared memory while allocating message of size 8717. Increase nchan_max_reserved_memory.
May  2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: *6796189 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
May  2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: MEMSTORE:00: can't create shared message for channel /disks

 

syslog-192.168.1.110.log syslog-192.168.1.110.log

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

4 minutes ago, JorgeB said:

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

Hi, are you recommending that this is how I should treat unraid going forward?

 

This will not be possible, if 6.13 is so fragile that leaving a tab open will cause the entire OS collapse, then this should be investigated and fixed at the source.

 

In all my years running unraid and prior to upgrading to 6.13 this was NEVER an issue.

If safe mode helps it could be a plugin, if it's the browser not sure what you could do, I don't have a problem with leaving the browser open, but it does appear to help some users.