Hi,

 

my Unraid 6.12.3 stopped accepting HTTP requests this early morning. Some basic tests and I discovered, that my nginx error log is full of this:

 

2023/09/03 05:07:01 [alert] 2261#2261: worker process 5493 exited on signal 6
2023/09/03 05:07:01 [alert] 2261#2261: shared memory zone "memstore" was locked by 5493
ter process /usr/sbin/nginx -c /etc/nginx/nginx.conf: ./nchan-1.3.6/src/store/memory/memstore.c:705: nchan_store_init_worker: Assertion `procslot_found == 1' failed.

 

 

here some lines just before this happened:

 

2023/09/03 04:52:21 [info] 19603#19603: Using 116KiB of shared memory for nchan in /etc/nginx/nginx.conf:161
2023/09/03 04:52:21 [info] 19603#19603: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:161
2023/09/03 04:57:55 [info] 28501#28501: Using 116KiB of shared memory for nchan in /etc/nginx/nginx.conf:161
2023/09/03 04:57:55 [info] 28501#28501: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:161
ter process /usr/sbin/nginx -c /etc/nginx/nginx.conf: ./nchan-1.3.6/src/store/memory/memstore.c:705: nchan_store_init_worker: Assertion `procslot_found == 1' failed.
2023/09/03 04:57:55 [alert] 2261#2261: worker process 28504 exited on signal 6
2023/09/03 04:57:55 [alert] 2261#2261: shared memory zone "memstore" was locked by 28504

 

 

Some nchan issues? Server uptime:

10:12:30 up 13 days, 20:10,  2 users,  load average: 0.04, 0.08, 0.03

 

Never had this issue before.

 

Memory:

 

free -h
               total        used        free      shared  buff/cache   available
Mem:            15Gi       5.5Gi       8.0Gi       129Mi       2.1Gi       9.6Gi
Swap:             0B          0B          0B

 

The syslog has no further entries. If I should provide diags anyway, let me know. I left the server in its state for further diagnostics, if needed.

 

EDIT: It seems, that this issue happens to some users here. Googling revelaed, that the nchan author should have fixed this already? Whoch version of nchan is Unraid using?

 

=> https://github.com/slact/nchan/issues/446#issuecomment-400874440

 

EDIT2: Ahh, I just see, Unraid uses latest (1.3.6) of nchan.

EDIT3: Some other author comment on this: https://github.com/slact/nchan/issues/446#issuecomment-686848568

 

Maybe a nchan expert here could tell us more, how nchan is built?

Edited September 3, 20232 yr by KluthR

Since this issue is known, I leave my findings here. Seems nchan can be a bit diffcult sometimes. I killed (kill -9) the main process and restarted it, using rc.nginx which worked.