can't figure out what is causing this error, any help is appreciated

 

tower-diagnostics-20230628-0449.zip

rebooting solve the problem temporarily but it happens again 

I'm having the same issue. Any help would be appreciated.

meshifyunraid-diagnostics-20230630-0834.zip

Both try updating to v6.12.2 to see if it helps.

14 hours ago, JorgeB said:

Both try updating to v6.12.2 to see if it helps.

did that yesterday and it ddin't seem to help. my logs seems to be filled with the same errors over and over 

Spoiler

Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [crit] 9470#9470: ngx_slab_alloc() failed: no memory
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: shpool alloc failed
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: nchan: Out of shared memory while allocating message of size 10307. Increase nchan_max_reserved_memory.
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: *506134 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: MEMSTORE:00: can't create shared message for channel /devices
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [crit] 9470#9470: ngx_slab_alloc() failed: no memory
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: shpool alloc failed
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: nchan: Out of shared memory while allocating message of size 2179. Increase nchan_max_reserved_memory.
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: *506137 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/dockerload?buffer_length=0 HTTP/1.1", host: "localhost"
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: MEMSTORE:00: can't create unbuffered message for channel /dockerload
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [crit] 9470#9470: ngx_slab_alloc() failed: no memory
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: shpool alloc failed
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: nchan: Out of shared memory while allocating message of size 2572. Increase nchan_max_reserved_memory.
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: *506139 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/notify?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  1 03:35:39 Tower nginx: 2023/07/01 03:35:39 [error] 9470#9470: MEMSTORE:00: can't create shared message for channel /notify
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [crit] 9470#9470: ngx_slab_alloc() failed: no memory
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: shpool alloc failed
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: nchan: Out of shared memory while allocating message of size 15806. Increase nchan_max_reserved_memory.
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: *506141 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: MEMSTORE:00: can't create shared message for channel /disks
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [crit] 9470#9470: ngx_slab_alloc() failed: no memory
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: shpool alloc failed
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: nchan: Out of shared memory while allocating message of size 5720. Increase nchan_max_reserved_memory.
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: *506142 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/shares?buffer_length=1 HTTP/1.1", host: "localhost"
Jul  1 03:35:40 Tower nginx: 2023/07/01 03:35:40 [error] 9470#9470: MEMSTORE:00: can't create shared message for channel /shares

 

 

tower-diagnostics-20230701-0616.zip

Try booting in safe mode and leave docker service disabled, if no errors, start enabling containers one by one and re-testing.

 

3 hours ago, JorgeB said:

Try booting in safe mode and leave docker service disabled, if no errors, start enabling containers one by one and re-testing.

just to be sure, by safe mode you mean Maintenace mode? 

if so, i booted into Maintenace mode and when checking the log there was no errors other than these three. 

Jul  1 14:32:49 Tower kernel: I/O error, dev sdf, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2
Jul  1 14:32:49 Tower kernel: I/O error, dev sdf, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
Jul  1 14:32:49 Tower kernel: I/O error, dev sdf, sector 88 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2

 

when enabling docker service I get this error: docker service failed to start Couldn't create socket: [2] No such file or directory.

4 minutes ago, sohailoo said:

by safe mode you mean Maintenace mode? 

No, I mean safe mode, it's a boot option in the Unraid boot menu, or in the GUI before rebooting:

 

6 minutes ago, JorgeB said:

No, I mean safe mode, it's a boot option in the Unraid boot menu, or in the GUI before rebooting:

 

oh, sorry just noticed the option. I'll give it a shit and get back to you. thanks btw

2 hours ago, JorgeB said:

No, I mean safe mode, it's a boot option in the Unraid boot menu, or in the GUI before rebooting:

 

2.5 hours in safe mode with all containers running and no errors.

should I leave it running in safe mode for the rest of the day? 

after 3.5 hours it started spitting the same error over and over.

tower-diagnostics-20230701-1835.zip

Edited July 1, 20233 yr by sohailoo

Close all browser tabs / windows on all devices that may be open to the WebUI (especially Android devices) and then try again.

12 hours ago, Squid said:

Close all browser tabs / windows on all devices that may be open to the WebUI (especially Android devices) and then try again.

apparently, this fixed it. thanks there's no way I would've figured this out myself!