Shine

日志文件占用空间太大，报错。 日志 4月28日14:47:50 Tower nginx：2024/04/28 14:47:50 [crit] 28013#28013：ngx_slab_alloc()失败：没有内存4月28日14:47:50 Tower nginx：2024/04/28 14 :47:50 [错误] 28013#28013: shpool alloc failed Apr 28 14:47:50 Tower nginx: 2024/04/28 14:47:50 [错误] 28013#28013: nchan: 分配消息时共享内存不足大小为 16798。增加 nchan_max_reserved_memory。 4月28日14:47:50 Tower nginx：2024/04/28 14:47:50 [错误] 28013#28013：*2758286 nchan：发布消息时出错（HTTP状态代码500），客户端：unix：，服务器：，请求：“POST /pub/disks?buffer_length=1 HTTP/1.1”，主机：“localhost”4月28日14:47:50 Tower nginx：2024/04/28 14:47:50 [错误] 28013#28013：MEMSTORE： 00：无法为通道/磁盘创建共享消息 4 月 28 日 14:47:53 Tower nginx：2024/04/28 14:47:53 [crit] 28013#28013：ngx_slab_alloc() 失败：没有内存 4 月 28 日 14： 47:53 塔 nginx：2024/04/28 14:47:53 [错误] 28013#28013：shpool 分配失败 4 月 28 日 14:47:53 塔 nginx：2024/04/28 14:47:53 [错误] 28013 #28013: nchan: 分配大小为 16798 的消息时共享内存不足。增加 nchan_max_reserved_memory。 4月28日14:47:53 Tower nginx：2024/04/28 14:47:53 [错误] 28013#28013：*2758299 nchan：发布消息时出错（HTTP状态代码500），客户端：unix：，服务器：，请求：“POST /pub/disks?buffer_length=1 HTTP/1.1”，主机：“localhost”4月28日14:47:53 Tower nginx：2024/04/28 14:47:53 [错误] 28013#28013：MEMSTORE： 00：无法为通道 /disks 创建共享消息 4 月 28 日 14:47:54 Tower nginx：2024/04/28 14:47:54 [crit] 28013#28013：ngx_slab_alloc() 失败：没有内存 4 月 28 日 14： 47:54 塔 nginx：2024/04/28 14:47:54 [错误] 28013#28013：shpool 分配失败 4 月 28 日 14:47:54 塔 nginx：2024/04/28 14:47:54 [错误] 28013 #28013: nchan: 分配大小为 16798 的消息时共享内存不足。增加 nchan_max_reserved_memory。 4月28日14:47:54 Tower nginx：2024/04/28 14:47:54 [错误] 28013#28013：*2758304 nchan：发布消息时出错（HTTP状态代码500），客户端：unix：，服务器：，请求：“POST /pub/disks?buffer_length=1 HTTP/1.1”，主机：“localhost”4月28日14:47:54 Tower nginx：2024/04/28 14:47:54 [错误] 28013#28013：MEMSTORE： 00：无法为通道/磁盘创建共享消息 syslog.txt

好的，我试一下，感谢回复

system configuration

STOP

死机前后日志 Sep 30 04:16:40 Tower kernel: e1000e 0000:00:1f.6 eth0: Reset adapter unexpectedly Sep 30 04:16:40 Tower kernel: bond0: (slave eth0): link status definitely down, disabling slave Sep 30 04:16:40 Tower kernel: device eth0 left promiscuous mode Sep 30 04:16:40 Tower kernel: bond0: now running without any active interface! Sep 30 04:16:40 Tower kernel: br0: port 1(bond0) entered disabled state Sep 30 04:16:43 Tower kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Sep 30 04:16:43 Tower kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Sep 30 04:16:43 Tower kernel: bond0: (slave eth0): making interface the new active one Sep 30 04:16:43 Tower kernel: device eth0 entered promiscuous mode Sep 30 04:16:43 Tower kernel: bond0: active interface up! Sep 30 04:16:43 Tower kernel: br0: port 1(bond0) entered blocking state Sep 30 04:16:43 Tower kernel: br0: port 1(bond0) entered forwarding state Sep 30 04:50:03 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="8890" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Sep 30 07:10:48 Tower kernel: e1000e 0000:00:1f.6 eth0: Detected Hardware Unit Hang:

unraid 6.12.4无故丢失网卡，无法获取ip地址，重启后正常。下面是诊断记录。还有断网时插入显示器显示的图片

After upgrading to version 6.12.3 of unRAID, I encountered an issue where Docker is unable to obtain an IPv6 address. When selecting the br0 option on the new page, only the internal IPv4 address is available, and there is no IPv6 address. I attempted to modify the Docker settings on the Docker configuration page using both ipvlan and macvlan options, but neither of them was effective. Here is the diagnostic information: tower-diagnostics-20230807-1040.zip

Explanation of the situation： The web user interface being inaccessible and the abnormal termination of the NGINX service are likely indicative of a system bug. This assumption is reinforced by the fact that two other friends who upgraded with me have also encountered the same issue. As a temporary solution, I have observed that forcefully terminating the NGINX process and manually restarting it restores the web user interface temporarily. However, after a period of time, the error resurfaces. This is the error information from my nginx. 2023/06/28 16:22:37 [info] 2466#2466: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:161 2023/06/28 16:22:52 [info] 3615#3615: Using 116KiB of shared memory for nchan in /etc/nginx/nginx.conf:161 2023/06/28 16:22:52 [info] 3615#3615: 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/06/28 16:22:52 [alert] 8504#8504: worker process 3618 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3618 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/06/28 16:22:52 [alert] 8504#8504: worker process 3628 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3628 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/06/28 16:22:52 [alert] 8504#8504: worker process 3629 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3629 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/06/28 16:22:52 [alert] 8504#8504: worker process 3631 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3631 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/06/28 16:22:52 [alert] 8504#8504: worker process 3632 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3632 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. Proposed solution： Execute via SSH pkill -9 nginx /etc/rc.d/rc.nginx start

This is the error information from my nginx. 2023/06/28 16:22:37 [info] 2466#2466: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:161 2023/06/28 16:22:52 [info] 3615#3615: Using 116KiB of shared memory for nchan in /etc/nginx/nginx.conf:161 2023/06/28 16:22:52 [info] 3615#3615: 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/06/28 16:22:52 [alert] 8504#8504: worker process 3618 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3618 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/06/28 16:22:52 [alert] 8504#8504: worker process 3628 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3628 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/06/28 16:22:52 [alert] 8504#8504: worker process 3629 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3629 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/06/28 16:22:52 [alert] 8504#8504: worker process 3631 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3631 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/06/28 16:22:52 [alert] 8504#8504: worker process 3632 exited on signal 6 2023/06/28 16:22:52 [alert] 8504#8504: shared memory zone "memstore" was locked by 3632 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.

Yes, I have also encountered this issue where only the web UI cannot be accessed and the logs indicate abnormal termination of the nginx service. I believe this is a system bug, as two other friends who upgraded with me have also encountered this problem. When I forcefully terminate the nginx process and manually restart it, the web UI resumes its services. However, after some time, the error reappears.

好的 谢谢大佬

大佬好，更新6.12.1后，只要启动虚拟机就会报下面这个错误，导致虚拟机没办法自动启动。6.11.5正常运行 VM Autostart disabled: 27-06-2023 22:06 vfio-pci-errors VM Autostart disabled due to vfio-bind error