Jump to content
Sign in to follow this  
clowrym

Duplicate Device / Powerclamp errors when Updating Docker Container

1 post in this topic Last Reply

Recommended Posts

I have been having an issue for the last couple months anytime My Plex Docker updates I get the following Errors in my syslog. On occasion doing an update to the plex container will kill all Network access to my server, Or will shut my server down completely. I have tried adjusting my folder mappings & posted in Linuxservers Plex docker support thread who suggested this isnt likely an issue with the container. Its only an issue when updating my plex container, none of the other seems to have the problem.

Jul 11 04:00:05 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished
Jul 11 04:00:15 Tower Docker Auto Update: Stopping plex
Jul 11 04:00:18 Tower Docker Auto Update: Stopping radarr
Jul 11 04:00:23 Tower kernel: veth650c3aa: renamed from eth0
Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state
Jul 11 04:00:23 Tower avahi-daemon[10153]: Interface vethcacec4b.IPv6 no longer relevant for mDNS.
Jul 11 04:00:23 Tower avahi-daemon[10153]: Leaving mDNS multicast group on interface vethcacec4b.IPv6 with address fe80::bc75:9ff:feac:7216.
Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state
Jul 11 04:00:23 Tower kernel: device vethcacec4b left promiscuous mode
Jul 11 04:00:23 Tower kernel: docker0: port 2(vethcacec4b) entered disabled state
Jul 11 04:00:23 Tower avahi-daemon[10153]: Withdrawing address record for fe80::bc75:9ff:feac:7216 on vethcacec4b.
Jul 11 04:00:23 Tower Docker Auto Update: Installing Updates for plex radarr
Jul 11 04:00:46 Tower Docker Auto Update: Restarting plex
Jul 11 04:00:47 Tower Docker Auto Update: Restarting radarr
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered disabled state
Jul 11 04:00:47 Tower kernel: device veth5b9bbf5 entered promiscuous mode
Jul 11 04:00:47 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth5b9bbf5: link is not ready
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered forwarding state
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered disabled state
Jul 11 04:00:47 Tower kernel: eth0: renamed from vethbf235a3
Jul 11 04:00:47 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5b9bbf5: link becomes ready
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered blocking state
Jul 11 04:00:47 Tower kernel: docker0: port 2(veth5b9bbf5) entered forwarding state
Jul 11 04:00:48 Tower Docker Auto Update: Community Applications Docker Autoupdate finished
Jul 11 04:00:49 Tower avahi-daemon[10153]: Joining mDNS multicast group on interface veth5b9bbf5.IPv6 with address fe80::d40f:23ff:fe6f:dcdc.
Jul 11 04:00:49 Tower avahi-daemon[10153]: New relevant interface veth5b9bbf5.IPv6 for mDNS.
Jul 11 04:00:49 Tower avahi-daemon[10153]: Registering new address record for fe80::d40f:23ff:fe6f:dcdc on veth5b9bbf5.*.
Jul 11 04:00:58 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdc1
Jul 11 04:00:58 Tower kernel: BTRFS warning (device md6): duplicate device fsid:devid for e5144b2d-b213-4aae-8b7a-07a4556cae15:1 old:/dev/md6 new:/dev/sde1
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: intel_powerclamp: No package C-state available
Jul 11 04:00:58 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdn1
Jul 11 04:00:59 Tower kernel: BTRFS warning (device md5): duplicate device fsid:devid for fe9954eb-fe72-400e-9e51-a93a620db2b6:1 old:/dev/md5 new:/dev/sdp1
Jul 11 04:01:03 Tower kernel: BTRFS warning (device md8): duplicate device fsid:devid for fe834164-5e8e-4dad-8ad1-3186ed9ca15d:1 old:/dev/md8 new:/dev/sdl1
Jul 11 04:01:03 Tower kernel: BTRFS warning (device md4): duplicate device fsid:devid for 16d6aaf7-f0d9-419d-ac06-d0351d960bdb:1 old:/dev/md4 new:/dev/sdt1
Jul 11 04:01:05 Tower kernel: BTRFS warning (device md1): duplicate device fsid:devid for 1b8fa8ee-850f-48f2-8614-af47d6577726:1 old:/dev/md1 new:/dev/sdh1
Jul 11 04:01:07 Tower kernel: BTRFS warning (device md3): duplicate device fsid:devid for ef88f475-319d-426d-b02d-89353e6cc2be:1 old:/dev/md3 new:/dev/sdf1
Jul 11 04:40:02 Tower kernel: mdcmd (516): spindown 18
Jul 11 04:51:34 Tower kernel: mdcmd (517): spindown 19

 

 

tower-diagnostics-20190711-1711.zip

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this