repeated reloads lead to unresponsive server

[Thomas Ward]

Do you actually use NCHAN for anything?  If you are not actively using
nchan, you should consider simply removing `libnginx-mod-nchan`

Note also this is a third party module, so it's not necessarily
'endorsed' by NGINX Upstream per se.  Also, Debian is *ancient* with its
nginx version and modules, I'd suggest you switch to a more recent
Debian version with newer nginx, or use the nginx.org repositories (no
third party plugins there though...)


Thomas

On 8/31/20 11:03 AM, james.anderson wrote:
> we observe that after several days in service, where the server is reloaded
> several hundred times a day, it eventually stops responding.
>
> a reload completes, but still all connections time out.
> a restart corrects the issue.
>
> is there a limit to the number of times a server permits a reload before it
> is necessary to restart it.
> when the problem starts, entries like the following appear in the nginx
> error log
>
> ter process /usr/sbin/nginx -g daemon on; master_process on;:
> /build/nginx-5J5hor/nginx-1.18.0/debian/modules/nchan/src/store/memory/memst\
> ore.c:701: nchan_store_init_worker: Assertion `procslot_found == 1' failed.
> 2020/08/31 12:07:18 [alert] 1451759#1451759: worker process 1500846 exited
> on signal 6 (core dumped)
> 2020/08/31 12:07:18 [alert] 1451759#1451759: shared memory zone "memstore"
> was locked by 1500846
>
> i see no mention of this issue here. but i did note
>
>     https://github.com/slact/nchan/issues/446
>
> versions:
> root at nl12:~# uname -a
> Linux nl12.dydra.com 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC
> 2020 x86_64 x86_64 x86_64 GNU/Linux
> root at nl12:~# which nginx
> /usr/sbin/nginx
> root at nl12:~# /usr/sbin/nginx -v
> nginx version: nginx/1.18.0 (Ubuntu)
>
> Posted at Nginx Forum: https://forum.nginx.org/read.php?2,289247,289247#msg-289247
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20200831/6c99d209/attachment.htm>