Albert Wu Posted May 1, 2023 Share Posted May 1, 2023 (edited) Network down, ifconfig in phyisical terminal shows no ipv4 address. and syslog.zipsyslog.zipipv6 address is also not reach able. try to restart network service with: /etc/rc.d/rc.inetd restart - wont fix. the mirrored chaos log mirrored-syslog.zipis attached, and also diagnostics log aio-diagnostics-20230501-1203.zipfor reference. Note:docker network br1 is set to macvlan with a dedicated port system log showing repeating message like follow, system is still reachable around May 1 01:00:00 Apr 30 00:00:13 AIO kernel: device vetha859cec entered promiscuous mode Apr 30 00:00:13 AIO kernel: eth0: renamed from vethda7234f Apr 30 00:00:14 AIO kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Apr 30 00:00:14 AIO kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha859cec: link becomes ready Apr 30 00:00:14 AIO kernel: docker0: port 7(vetha859cec) entered blocking state Apr 30 00:00:14 AIO kernel: docker0: port 7(vetha859cec) entered forwarding state Apr 30 00:00:14 AIO kernel: docker0: port 7(vetha859cec) entered disabled state Apr 30 00:00:14 AIO kernel: vethda7234f: renamed from eth0 Apr 30 00:00:14 AIO kernel: docker0: port 7(vetha859cec) entered disabled state Apr 30 00:00:14 AIO kernel: device vetha859cec left promiscuous mode May 1 01:54:52 AIO nginx: 2023/05/01 01:54:52 [alert] 8838#8838: worker process 25225 exited on signal 6 May 1 01:54:52 AIO nginx: 2023/05/01 01:54:52 [alert] 8838#8838: shared memory zone "memstore" was locked by 25225 May 1 02:33:54 AIO rsyslogd: file '/var/log/syslog'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 1 02:33:54 AIO rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 1 02:33:54 AIO rsyslogd: file '/var/log/syslog'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] May 1 02:33:54 AIO rsyslogd: action 'action-0-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Edited May 1, 2023 by Albert Wu Quote Link to comment
JorgeB Posted May 1, 2023 Share Posted May 1, 2023 5 hours ago, Albert Wu said: ifconfig in phyisical terminal shows no ipv4 address There's is one for the bridge, which is normal for this config: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.168.10.103 netmask 255.255.255.0 broadcast 172.168.10.255 Is that IP not accessible? Quote Link to comment
Albert Wu Posted May 1, 2023 Author Share Posted May 1, 2023 47 minutes ago, JorgeB said: There's is one for the bridge, which is normal for this config: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.168.10.103 netmask 255.255.255.0 broadcast 172.168.10.255 Is that IP not accessible? no, that address is correct, it is the main ip of unraid server, but since this issue happen, it can not be reach through webui or PING from local network. (tried unplug and replug ethernet port, restart network service, none of these fix this) Quote Link to comment
JorgeB Posted May 1, 2023 Share Posted May 1, 2023 You can delete/rename /boot/config/network.cfg and network-rules.cfg then reboot to return to defaults. Quote Link to comment
Albert Wu Posted May 1, 2023 Author Share Posted May 1, 2023 (edited) 13 minutes ago, JorgeB said: You can delete/rename /boot/config/network.cfg and network-rules.cfg then reboot to return to defaults. The configuration should be OK, it's just return to normal after reboot Just wondering what's causing this kind of issue, so to make sure it wont happen again. Can you help to recognize what's this log mean? May 1 01:54:52 AIO nginx: 2023/05/01 01:54:52 [alert] 8838#8838: worker process 25225 exited on signal 6 May 1 01:54:52 AIO nginx: 2023/05/01 01:54:52 [alert] 8838#8838: shared memory zone "memstore" was locked by 25225 Edited May 1, 2023 by Albert Wu Quote Link to comment
JorgeB Posted May 1, 2023 Share Posted May 1, 2023 15 minutes ago, Albert Wu said: Can you help to recognize what's this log mean? Sorry, don't know what that means. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.