Einzigstes Posted March 23, 2019 Share Posted March 23, 2019 Hi, I updated to version 6.6.7 two days ago and first I noticed, that my plex-server was not accessable. I had to restart the whole system, as the docker wouldn't restart (Execution Error) All my shares are not displayed either in that case. It works fine for some amount of time, but if every day now, when I come home in the evening without using my server for most of the day I get these problemes. Could it have something to do with the disk spin-down? Server-Log: ErrorWarningSystemArrayLogin Mar 22 16:11:46 Server1 kernel: docker0: port 3(veth289a205) entered forwarding state Mar 22 16:11:46 Server1 kernel: docker0: port 3(veth289a205) entered disabled state Mar 22 16:11:49 Server1 kernel: eth0: renamed from veth7002418 Mar 22 16:11:49 Server1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc50d4db: link becomes ready Mar 22 16:11:49 Server1 kernel: docker0: port 1(vethc50d4db) entered blocking state Mar 22 16:11:49 Server1 kernel: docker0: port 1(vethc50d4db) entered forwarding state Mar 22 16:11:49 Server1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Mar 22 16:11:50 Server1 avahi-daemon[4367]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:21ff:fea5:821d. Mar 22 16:11:50 Server1 avahi-daemon[4367]: New relevant interface docker0.IPv6 for mDNS. Mar 22 16:11:50 Server1 avahi-daemon[4367]: Registering new address record for fe80::42:21ff:fea5:821d on docker0.*. Mar 22 16:11:51 Server1 avahi-daemon[4367]: Joining mDNS multicast group on interface vethc50d4db.IPv6 with address fe80::248e:9dff:fe70:24cc. Mar 22 16:11:51 Server1 avahi-daemon[4367]: New relevant interface vethc50d4db.IPv6 for mDNS. Mar 22 16:11:51 Server1 avahi-daemon[4367]: Registering new address record for fe80::248e:9dff:fe70:24cc on vethc50d4db.*. Mar 22 16:11:55 Server1 kernel: eth0: renamed from veth771ba9d Mar 22 16:11:55 Server1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2bf32cd: link becomes ready Mar 22 16:11:55 Server1 kernel: docker0: port 2(veth2bf32cd) entered blocking state Mar 22 16:11:55 Server1 kernel: docker0: port 2(veth2bf32cd) entered forwarding state Mar 22 16:11:57 Server1 avahi-daemon[4367]: Joining mDNS multicast group on interface veth2bf32cd.IPv6 with address fe80::5c51:90ff:fe66:5d25. Mar 22 16:11:57 Server1 avahi-daemon[4367]: New relevant interface veth2bf32cd.IPv6 for mDNS. Mar 22 16:11:57 Server1 avahi-daemon[4367]: Registering new address record for fe80::5c51:90ff:fe66:5d25 on veth2bf32cd.*. Mar 22 16:11:57 Server1 kernel: eth0: renamed from veth89675b0 Mar 22 16:11:57 Server1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth289a205: link becomes ready Mar 22 16:11:57 Server1 kernel: docker0: port 3(veth289a205) entered blocking state Mar 22 16:11:57 Server1 kernel: docker0: port 3(veth289a205) entered forwarding state Mar 22 16:11:58 Server1 avahi-daemon[4367]: Joining mDNS multicast group on interface veth289a205.IPv6 with address fe80::5863:afff:fe93:1e1. Mar 22 16:11:58 Server1 avahi-daemon[4367]: New relevant interface veth289a205.IPv6 for mDNS. Mar 22 16:11:58 Server1 avahi-daemon[4367]: Registering new address record for fe80::5863:afff:fe93:1e1 on veth289a205.*. Mar 22 16:15:00 Server1 root: Fix Common Problems Version 2019.03.14b Mar 22 21:16:57 Server1 kernel: mdcmd (40): spindown 3 Mar 23 02:17:24 Server1 kernel: Plex Media Scan[23171]: segfault at 300000010 ip 00001511fbd0d097 sp 00001511ed9ca0a0 error 4 in libcrypto.so.1.0.0[1511fbbfc000+204000] Mar 23 02:17:24 Server1 kernel: Code: 8b 4f 1c 31 d2 4c 89 e0 48 f7 f1 49 8b 07 48 63 ca 4c 8b 2c c8 4d 85 ed 74 37 49 8b 6f 08 48 8d 1c c8 90 49 ff 87 a0 00 00 00 <4d> 39 65 10 75 11 49 ff 47 68 49 8b 7d 00 4c 89 f6 ff d5 85 c0 74 Mar 23 03:00:01 Server1 kernel: shfs[28049]: segfault at 0 ip 0000000000402722 sp 00001501612ab8f0 error 4 in shfs[400000+f000] Mar 23 03:00:01 Server1 kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8 Mar 23 03:00:01 Server1 emhttpd: error: get_filesystem_status, 6453: Transport endpoint is not connected (107): scandir Mar 23 03:00:12 Server1 crond[1714]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Mar 23 04:05:22 Server1 kernel: mdcmd (41): spindown 1 Mar 23 10:00:01 Server1 root: /etc/libvirt: 921 MiB (965713920 bytes) trimmed Mar 23 10:00:01 Server1 root: /var/lib/docker: 15.2 GiB (16292868096 bytes) trimmed com.plexapp.system.log Quote Link to comment
Squid Posted March 23, 2019 Share Posted March 23, 2019 13 minutes ago, Einzigstes said: Could it have something to do with the disk spin-down? Very Unlikely 14 minutes ago, Einzigstes said: All my shares are not displayed either in that case. 13 minutes ago, Einzigstes said: Mar 23 03:00:01 Server1 emhttpd: error: get_filesystem_status, 6453: Transport endpoint is not connected (107): scandir Because of this can you post your Tools - Diagnostics Quote Link to comment
Einzigstes Posted March 23, 2019 Author Share Posted March 23, 2019 9 minutes ago, Squid said: Very Unlikely Because of this can you post your Tools - Diagnostics My diagnostics: server1-diagnostics-20190323-1852.zip Quote Link to comment
Squid Posted March 23, 2019 Share Posted March 23, 2019 It's after you've rebooted. Wait until it happens again then post them again. Quote Link to comment
Einzigstes Posted March 24, 2019 Author Share Posted March 24, 2019 (edited) 22 hours ago, Squid said: It's after you've rebooted. Wait until it happens again then post them again. ok, here's the diagnostics without a reboot server1-diagnostics-20190324-1724.zip Edited March 24, 2019 by Einzigstes 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.