zhangxiao Posted July 23, 2022 Share Posted July 23, 2022 The docker is crashed suddenly. My docker image is stored on cache pool (raid 0). Attached is my system log saved on another log server. unraid.zip Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 attach diagnostics to your NEXT post in this thread. 1 hour ago, zhangxiao said: Attached is my system log saved on another log server. see if you can convert those logs into a single zipped plain text file Quote Link to comment
zhangxiao Posted July 23, 2022 Author Share Posted July 23, 2022 Thank you for the reply. Attached is the diagnostics file and exported system log in 1 single file. mediaserver-diagnostics-20220723-2208.zip All_2022-7-23-22_9_41.html Quote Link to comment
Squid Posted July 23, 2022 Share Posted July 23, 2022 Switch your network driver (Settings Docker - Probably need to stop the service from running in order to do this) from macvlan to instead be ipvlan The other file with the dump shows that the docker.img is possibly trashed and would also contribute. https://forums.unraid.net/topic/57181-docker-faq/#comment-564309 Quote Link to comment
zhangxiao Posted July 23, 2022 Author Share Posted July 23, 2022 Just now, the server is crashed again. The system log record a stall on CPU. Today, the server crashed for 3 time. I am tired of it.🥶 syslog-192.168.40.3.log Quote Link to comment
trurl Posted July 23, 2022 Share Posted July 23, 2022 Did you do this? 5 hours ago, Squid said: Switch your network driver (Settings Docker - Probably need to stop the service from running in order to do this) from macvlan to instead be ipvlan Quote Link to comment
zhangxiao Posted July 24, 2022 Author Share Posted July 24, 2022 I just changed to the IPVLAN for docker. I will check whether it will crash again. Quote Link to comment
zhangxiao Posted July 24, 2022 Author Share Posted July 24, 2022 Moreover, in the syslog, there are a lot of server disconneted records. I am using X550 for eth0. While I cannot connect eth0 (X550), I can connect to eth1 (i210). I have not observed the link lost on i210. But on X550, it is quite offen. Jul 24 05:21:58 MediaServer upsmon[6403]: Poll UPS [[email protected]] failed - Server disconnected Jul 24 05:21:58 MediaServer upsmon[6403]: Communications with UPS [email protected] lost Jul 24 05:22:03 MediaServer upsmon[6403]: Login on UPS [[email protected]] failed - got [ERR ACCESS-DENIED] Jul 24 05:22:08 MediaServer upsmon[6403]: Communications with UPS [email protected] established Jul 24 09:34:20 MediaServer upsmon[6403]: Poll UPS [[email protected]] failed - Server disconnected Jul 24 09:34:20 MediaServer upsmon[6403]: Communications with UPS [email protected] lost Jul 24 09:34:25 MediaServer upsmon[6403]: Login on UPS [[email protected]] failed - got [ERR ACCESS-DENIED] Jul 24 09:34:30 MediaServer upsmon[6403]: Communications with UPS [email protected] established Jul 24 09:39:00 MediaServer webGUI: Successful login user root from 192.168.40.76 Jul 24 09:40:13 MediaServer webGUI: Successful login user root from 192.168.40.76 Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered blocking state Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered disabled state Jul 24 09:40:20 MediaServer kernel: device veth8406a9a entered promiscuous mode Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered blocking state Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered forwarding state Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered disabled state Jul 24 09:40:20 MediaServer kernel: eth0: renamed from veth6d2fbb8 Jul 24 09:40:20 MediaServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8406a9a: link becomes ready Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered blocking state Jul 24 09:40:20 MediaServer kernel: docker0: port 3(veth8406a9a) entered forwarding state Jul 24 09:40:21 MediaServer avahi-daemon[19002]: Joining mDNS multicast group on interface veth8406a9a.IPv6 with address fe80::e4b4:1eff:fe92:af7c. Jul 24 09:40:21 MediaServer avahi-daemon[19002]: New relevant interface veth8406a9a.IPv6 for mDNS. Jul 24 09:40:21 MediaServer avahi-daemon[19002]: Registering new address record for fe80::e4b4:1eff:fe92:af7c on veth8406a9a.*. 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.