-
Posts
397 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by xthursdayx
-
-
Okay, I'll run it again now, in the meantime here is the rest of that snippet:
Apr 16 05:25:56 vulfTower kernel: mdcmd (67): spindown 6 Apr 16 05:37:52 vulfTower kernel: mdcmd (68): spindown 5 Apr 16 05:40:38 vulfTower kernel: mdcmd (69): spindown 2 Apr 16 05:40:55 vulfTower kernel: mdcmd (70): spindown 3 Apr 16 06:00:49 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Down Apr 16 06:00:49 vulfTower kernel: bond0: link status definitely down for interface eth0, disabling it Apr 16 06:00:49 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Down Apr 16 06:00:50 vulfTower kernel: bond0: link status definitely down for interface eth1, disabling it Apr 16 06:00:50 vulfTower kernel: device eth1 left promiscuous mode Apr 16 06:00:50 vulfTower kernel: bond0: now running without any active interface! Apr 16 06:00:50 vulfTower kernel: br0: port 1(bond0) entered disabled state Apr 16 06:00:52 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Apr 16 06:00:52 vulfTower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Apr 16 06:00:52 vulfTower kernel: bond0: making interface eth0 the new active one Apr 16 06:00:52 vulfTower kernel: device eth0 entered promiscuous mode Apr 16 06:00:52 vulfTower kernel: bond0: first active interface up! Apr 16 06:00:52 vulfTower kernel: br0: port 1(bond0) entered blocking state Apr 16 06:00:52 vulfTower kernel: br0: port 1(bond0) entered forwarding state Apr 16 06:02:35 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Down Apr 16 06:02:35 vulfTower kernel: bond0: link status definitely down for interface eth0, disabling it Apr 16 06:02:35 vulfTower kernel: device eth0 left promiscuous mode Apr 16 06:02:35 vulfTower kernel: bond0: now running without any active interface! Apr 16 06:02:36 vulfTower kernel: br0: port 1(bond0) entered disabled state Apr 16 06:02:37 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Apr 16 06:02:38 vulfTower kernel: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex Apr 16 06:02:38 vulfTower kernel: bond0: making interface eth1 the new active one Apr 16 06:02:38 vulfTower kernel: device eth1 entered promiscuous mode Apr 16 06:02:38 vulfTower kernel: bond0: first active interface up! Apr 16 06:02:38 vulfTower kernel: br0: port 1(bond0) entered blocking state Apr 16 06:02:38 vulfTower kernel: br0: port 1(bond0) entered forwarding state Apr 16 06:02:38 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Apr 16 06:02:38 vulfTower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Apr 16 06:02:58 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Down Apr 16 06:02:58 vulfTower kernel: bond0: link status definitely down for interface eth0, disabling it Apr 16 06:02:59 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Down Apr 16 06:02:59 vulfTower kernel: bond0: link status definitely down for interface eth1, disabling it Apr 16 06:02:59 vulfTower kernel: device eth1 left promiscuous mode Apr 16 06:02:59 vulfTower kernel: bond0: now running without any active interface! Apr 16 06:02:59 vulfTower kernel: br0: port 1(bond0) entered disabled state Apr 16 06:03:02 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Apr 16 06:03:02 vulfTower kernel: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex Apr 16 06:03:02 vulfTower kernel: bond0: making interface eth1 the new active one Apr 16 06:03:02 vulfTower kernel: device eth1 entered promiscuous mode Apr 16 06:03:02 vulfTower kernel: bond0: first active interface up! Apr 16 06:03:02 vulfTower kernel: br0: port 1(bond0) entered blocking state Apr 16 06:03:02 vulfTower kernel: br0: port 1(bond0) entered forwarding state Apr 16 06:03:10 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Apr 16 06:03:10 vulfTower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Apr 16 06:03:11 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Down Apr 16 06:03:11 vulfTower kernel: bond0: link status definitely down for interface eth1, disabling it Apr 16 06:03:11 vulfTower kernel: bond0: making interface eth0 the new active one Apr 16 06:03:11 vulfTower kernel: device eth1 left promiscuous mode Apr 16 06:03:11 vulfTower kernel: device eth0 entered promiscuous mode Apr 16 06:03:14 vulfTower kernel: igb 0000:08:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Apr 16 06:03:14 vulfTower kernel: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex Apr 16 06:03:38 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Down Apr 16 06:03:38 vulfTower kernel: bond0: link status definitely down for interface eth0, disabling it Apr 16 06:03:38 vulfTower kernel: bond0: making interface eth1 the new active one Apr 16 06:03:38 vulfTower kernel: device eth0 left promiscuous mode Apr 16 06:03:38 vulfTower kernel: device eth1 entered promiscuous mode Apr 16 06:03:40 vulfTower kernel: igb 0000:07:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Apr 16 06:03:41 vulfTower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Apr 16 06:50:30 vulfTower kernel: mdcmd (71): spindown 1 Apr 16 09:02:45 vulfTower kernel: mdcmd (72): spindown 6 Apr 16 09:22:47 vulfTower CA Backup/Restore: Backup Complete Apr 16 09:22:47 vulfTower CA Backup/Restore: Verifying backup Apr 16 09:22:47 vulfTower CA Backup/Restore: Using command: cd '/mnt/cache/appdata/' && /usr/bin/tar --diff -C '/mnt/cache/appdata/' -af '/mnt/user/Backup/Community_Applications_Backup/[email protected]/CA_backup.tar' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress -
Hi all, I'm not sure what the deal is, but while I was out of town last week a bunch of my docker containers disappeared from my server and the ones that remained were off (when they're set to automatically start). I thought this might have been an issue with the container auto-update feature, so I just reinstalled them all. However I found that the y connection to my Unraid server kept failing and the update (or reinstall) process would fail or stall, creating an orphaned container image that I would have to delete before trying again. I've gotten everything installed again, but just woke up this morning to find all of my containers shut off when they were all on when I went to bed. Looking at my system log the only things I can see happening are an automatic container update and scheduled appdata backup. However this is what the log of my Community Apps Backup looks like. I am unsure if the authentication error towards the end is the problem. Any ideas what the problem might be, or advice about running diagnostics?
Apr 16 04:05:07 vulfTower CA Backup/Restore: ####################################### Apr 16 04:05:07 vulfTower CA Backup/Restore: Community Applications appData Backup Apr 16 04:05:07 vulfTower CA Backup/Restore: Applications will be unavailable during Apr 16 04:05:07 vulfTower CA Backup/Restore: this process. They will automatically Apr 16 04:05:07 vulfTower CA Backup/Restore: be restarted upon completion. Apr 16 04:05:07 vulfTower CA Backup/Restore: ####################################### Apr 16 04:05:07 vulfTower CA Backup/Restore: Stopping airsonic Apr 16 04:05:41 vulfTower kernel: vethfe3893a: renamed from eth0 Apr 16 04:05:41 vulfTower kernel: docker0: port 4(vethf23d514) entered disabled state Apr 16 04:05:43 vulfTower avahi-daemon[4721]: Interface vethf23d514.IPv6 no longer relevant for mDNS. Apr 16 04:05:43 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethf23d514.IPv6 with address fe80::dce7:fdff:feb1:7c07. Apr 16 04:05:43 vulfTower kernel: docker0: port 4(vethf23d514) entered disabled state Apr 16 04:05:43 vulfTower kernel: device vethf23d514 left promiscuous mode Apr 16 04:05:43 vulfTower kernel: docker0: port 4(vethf23d514) entered disabled state Apr 16 04:05:43 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::dce7:fdff:feb1:7c07 on vethf23d514. Apr 16 04:05:58 vulfTower CA Backup/Restore: docker stop -t 60 airsonic Apr 16 04:05:58 vulfTower CA Backup/Restore: Stopping binhex-delugevpn Apr 16 04:06:17 vulfTower kernel: vethf519ad7: renamed from eth0 Apr 16 04:06:17 vulfTower kernel: docker0: port 16(vethca35827) entered disabled state Apr 16 04:06:19 vulfTower avahi-daemon[4721]: Interface vethca35827.IPv6 no longer relevant for mDNS. Apr 16 04:06:19 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethca35827.IPv6 with address fe80::e43b:3dff:fe4b:fb53. Apr 16 04:06:19 vulfTower kernel: docker0: port 16(vethca35827) entered disabled state Apr 16 04:06:19 vulfTower kernel: device vethca35827 left promiscuous mode Apr 16 04:06:19 vulfTower kernel: docker0: port 16(vethca35827) entered disabled state Apr 16 04:06:19 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::e43b:3dff:fe4b:fb53 on vethca35827. Apr 16 04:06:25 vulfTower CA Backup/Restore: docker stop -t 60 binhex-delugevpn Apr 16 04:06:25 vulfTower CA Backup/Restore: Stopping binhex-emby Apr 16 04:06:28 vulfTower kernel: veth248d48b: renamed from eth0 Apr 16 04:06:29 vulfTower kernel: docker0: port 15(vethb3891a2) entered disabled state Apr 16 04:06:30 vulfTower avahi-daemon[4721]: Interface vethb3891a2.IPv6 no longer relevant for mDNS. Apr 16 04:06:30 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethb3891a2.IPv6 with address fe80::ac32:cff:fe75:d6d8. Apr 16 04:06:30 vulfTower kernel: docker0: port 15(vethb3891a2) entered disabled state Apr 16 04:06:30 vulfTower kernel: device vethb3891a2 left promiscuous mode Apr 16 04:06:30 vulfTower kernel: docker0: port 15(vethb3891a2) entered disabled state Apr 16 04:06:30 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::ac32:cff:fe75:d6d8 on vethb3891a2. Apr 16 04:06:34 vulfTower CA Backup/Restore: docker stop -t 60 binhex-emby Apr 16 04:06:34 vulfTower CA Backup/Restore: Stopping calibre-web Apr 16 04:06:46 vulfTower kernel: veth98e9317: renamed from eth0 Apr 16 04:06:46 vulfTower kernel: docker0: port 13(veth376ecf7) entered disabled state Apr 16 04:06:48 vulfTower avahi-daemon[4721]: Interface veth376ecf7.IPv6 no longer relevant for mDNS. Apr 16 04:06:48 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth376ecf7.IPv6 with address fe80::fc1a:2eff:fe5a:68a6. Apr 16 04:06:48 vulfTower kernel: docker0: port 13(veth376ecf7) entered disabled state Apr 16 04:06:48 vulfTower kernel: device veth376ecf7 left promiscuous mode Apr 16 04:06:48 vulfTower kernel: docker0: port 13(veth376ecf7) entered disabled state Apr 16 04:06:48 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::fc1a:2eff:fe5a:68a6 on veth376ecf7. Apr 16 04:06:52 vulfTower CA Backup/Restore: docker stop -t 60 calibre-web Apr 16 04:06:52 vulfTower CA Backup/Restore: Stopping couchpotato Apr 16 04:07:08 vulfTower kernel: vethf28f246: renamed from eth0 Apr 16 04:07:08 vulfTower kernel: docker0: port 10(vethbe598b8) entered disabled state Apr 16 04:07:10 vulfTower kernel: docker0: port 10(vethbe598b8) entered disabled state Apr 16 04:07:10 vulfTower avahi-daemon[4721]: Interface vethbe598b8.IPv6 no longer relevant for mDNS. Apr 16 04:07:10 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethbe598b8.IPv6 with address fe80::4410:dcff:fedf:7190. Apr 16 04:07:10 vulfTower kernel: device vethbe598b8 left promiscuous mode Apr 16 04:07:10 vulfTower kernel: docker0: port 10(vethbe598b8) entered disabled state Apr 16 04:07:10 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::4410:dcff:fedf:7190 on vethbe598b8. Apr 16 04:07:14 vulfTower CA Backup/Restore: docker stop -t 60 couchpotato Apr 16 04:07:14 vulfTower CA Backup/Restore: Stopping duplicati Apr 16 04:07:37 vulfTower kernel: veth3598a0e: renamed from eth0 Apr 16 04:07:37 vulfTower kernel: docker0: port 11(vethcffc2b3) entered disabled state Apr 16 04:07:38 vulfTower avahi-daemon[4721]: Interface vethcffc2b3.IPv6 no longer relevant for mDNS. Apr 16 04:07:38 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethcffc2b3.IPv6 with address fe80::10bc:3ff:fe66:3bed. Apr 16 04:07:38 vulfTower kernel: docker0: port 11(vethcffc2b3) entered disabled state Apr 16 04:07:38 vulfTower kernel: device vethcffc2b3 left promiscuous mode Apr 16 04:07:38 vulfTower kernel: docker0: port 11(vethcffc2b3) entered disabled state Apr 16 04:07:38 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::10bc:3ff:fe66:3bed on vethcffc2b3. Apr 16 04:07:42 vulfTower CA Backup/Restore: docker stop -t 60 duplicati Apr 16 04:07:42 vulfTower CA Backup/Restore: Stopping headphones Apr 16 04:08:02 vulfTower kernel: vethdcee554: renamed from eth0 Apr 16 04:08:02 vulfTower kernel: docker0: port 9(vethc7e99e4) entered disabled state Apr 16 04:08:04 vulfTower avahi-daemon[4721]: Interface vethc7e99e4.IPv6 no longer relevant for mDNS. Apr 16 04:08:04 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethc7e99e4.IPv6 with address fe80::487e:98ff:fe3c:47fa. Apr 16 04:08:04 vulfTower kernel: docker0: port 9(vethc7e99e4) entered disabled state Apr 16 04:08:04 vulfTower kernel: device vethc7e99e4 left promiscuous mode Apr 16 04:08:04 vulfTower kernel: docker0: port 9(vethc7e99e4) entered disabled state Apr 16 04:08:04 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::487e:98ff:fe3c:47fa on vethc7e99e4. Apr 16 04:08:08 vulfTower CA Backup/Restore: docker stop -t 60 headphones Apr 16 04:08:08 vulfTower CA Backup/Restore: Stopping Hydra Apr 16 04:08:26 vulfTower kernel: veth475610a: renamed from eth0 Apr 16 04:08:26 vulfTower kernel: docker0: port 19(veth010bbeb) entered disabled state Apr 16 04:08:28 vulfTower avahi-daemon[4721]: Interface veth010bbeb.IPv6 no longer relevant for mDNS. Apr 16 04:08:28 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth010bbeb.IPv6 with address fe80::f090:8eff:fefd:499a. Apr 16 04:08:28 vulfTower kernel: docker0: port 19(veth010bbeb) entered disabled state Apr 16 04:08:28 vulfTower kernel: device veth010bbeb left promiscuous mode Apr 16 04:08:28 vulfTower kernel: docker0: port 19(veth010bbeb) entered disabled state Apr 16 04:08:28 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::f090:8eff:fefd:499a on veth010bbeb. Apr 16 04:08:31 vulfTower CA Backup/Restore: docker stop -t 60 Hydra Apr 16 04:08:31 vulfTower CA Backup/Restore: Stopping jackett Apr 16 04:08:47 vulfTower kernel: veth2d848d1: renamed from eth0 Apr 16 04:08:47 vulfTower kernel: docker0: port 6(veth9e8acbe) entered disabled state Apr 16 04:08:49 vulfTower kernel: docker0: port 6(veth9e8acbe) entered disabled state Apr 16 04:08:49 vulfTower avahi-daemon[4721]: Interface veth9e8acbe.IPv6 no longer relevant for mDNS. Apr 16 04:08:49 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth9e8acbe.IPv6 with address fe80::b030:e9ff:fe92:7813. Apr 16 04:08:49 vulfTower kernel: device veth9e8acbe left promiscuous mode Apr 16 04:08:49 vulfTower kernel: docker0: port 6(veth9e8acbe) entered disabled state Apr 16 04:08:49 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::b030:e9ff:fe92:7813 on veth9e8acbe. Apr 16 04:08:53 vulfTower CA Backup/Restore: docker stop -t 60 jackett Apr 16 04:08:53 vulfTower CA Backup/Restore: Stopping Krusader Apr 16 04:09:51 vulfTower kernel: vethac9ed2d: renamed from eth0 Apr 16 04:09:51 vulfTower kernel: docker0: port 21(vetha14d86e) entered disabled state Apr 16 04:09:52 vulfTower kernel: docker0: port 21(vetha14d86e) entered disabled state Apr 16 04:09:52 vulfTower avahi-daemon[4721]: Interface vetha14d86e.IPv6 no longer relevant for mDNS. Apr 16 04:09:52 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vetha14d86e.IPv6 with address fe80::14ee:19ff:fecc:96d8. Apr 16 04:09:52 vulfTower kernel: device vetha14d86e left promiscuous mode Apr 16 04:09:52 vulfTower kernel: docker0: port 21(vetha14d86e) entered disabled state Apr 16 04:09:52 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::14ee:19ff:fecc:96d8 on vetha14d86e. Apr 16 04:09:55 vulfTower CA Backup/Restore: docker stop -t 60 Krusader Apr 16 04:09:55 vulfTower CA Backup/Restore: Stopping lazylibrarian Apr 16 04:10:06 vulfTower kernel: vethc29e755: renamed from eth0 Apr 16 04:10:06 vulfTower kernel: docker0: port 5(vethf4b5a96) entered disabled state Apr 16 04:10:07 vulfTower avahi-daemon[4721]: Interface vethf4b5a96.IPv6 no longer relevant for mDNS. Apr 16 04:10:07 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethf4b5a96.IPv6 with address fe80::b:2cff:fe21:9a75. Apr 16 04:10:07 vulfTower kernel: docker0: port 5(vethf4b5a96) entered disabled state Apr 16 04:10:07 vulfTower kernel: device vethf4b5a96 left promiscuous mode Apr 16 04:10:07 vulfTower kernel: docker0: port 5(vethf4b5a96) entered disabled state Apr 16 04:10:07 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::b:2cff:fe21:9a75 on vethf4b5a96. Apr 16 04:10:11 vulfTower CA Backup/Restore: docker stop -t 60 lazylibrarian Apr 16 04:10:11 vulfTower CA Backup/Restore: Stopping letsencrypt Apr 16 04:10:41 vulfTower kernel: veth281da32: renamed from eth0 Apr 16 04:10:41 vulfTower kernel: docker0: port 2(vetha7b2c22) entered disabled state Apr 16 04:10:42 vulfTower kernel: docker0: port 2(vetha7b2c22) entered disabled state Apr 16 04:10:42 vulfTower avahi-daemon[4721]: Interface vetha7b2c22.IPv6 no longer relevant for mDNS. Apr 16 04:10:42 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vetha7b2c22.IPv6 with address fe80::64c1:5cff:fe10:b031. Apr 16 04:10:42 vulfTower kernel: device vetha7b2c22 left promiscuous mode Apr 16 04:10:42 vulfTower kernel: docker0: port 2(vetha7b2c22) entered disabled state Apr 16 04:10:42 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::64c1:5cff:fe10:b031 on vetha7b2c22. Apr 16 04:10:46 vulfTower CA Backup/Restore: docker stop -t 60 letsencrypt Apr 16 04:10:46 vulfTower CA Backup/Restore: Stopping musicbrainz Apr 16 04:11:22 vulfTower kernel: docker0: port 14(veth94effb2) entered disabled state Apr 16 04:11:22 vulfTower kernel: veth222edf7: renamed from eth0 Apr 16 04:11:23 vulfTower avahi-daemon[4721]: Interface veth94effb2.IPv6 no longer relevant for mDNS. Apr 16 04:11:23 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth94effb2.IPv6 with address fe80::786b:87ff:fed4:ca14. Apr 16 04:11:23 vulfTower kernel: docker0: port 14(veth94effb2) entered disabled state Apr 16 04:11:23 vulfTower kernel: device veth94effb2 left promiscuous mode Apr 16 04:11:23 vulfTower kernel: docker0: port 14(veth94effb2) entered disabled state Apr 16 04:11:23 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::786b:87ff:fed4:ca14 on veth94effb2. Apr 16 04:11:25 vulfTower CA Backup/Restore: docker stop -t 60 musicbrainz Apr 16 04:11:25 vulfTower CA Backup/Restore: Stopping Mylar_Dev Apr 16 04:11:30 vulfTower CA Backup/Restore: docker stop -t 60 Mylar_Dev Apr 16 04:11:30 vulfTower CA Backup/Restore: Stopping NZBGet Apr 16 04:11:37 vulfTower kernel: veth962681a: renamed from eth0 Apr 16 04:11:37 vulfTower kernel: docker0: port 17(veth3a83f21) entered disabled state Apr 16 04:11:38 vulfTower avahi-daemon[4721]: Interface veth3a83f21.IPv6 no longer relevant for mDNS. Apr 16 04:11:38 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth3a83f21.IPv6 with address fe80::e848:e9ff:feb1:54ef. Apr 16 04:11:38 vulfTower kernel: docker0: port 17(veth3a83f21) entered disabled state Apr 16 04:11:38 vulfTower kernel: device veth3a83f21 left promiscuous mode Apr 16 04:11:38 vulfTower kernel: docker0: port 17(veth3a83f21) entered disabled state Apr 16 04:11:38 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::e848:e9ff:feb1:54ef on veth3a83f21. Apr 16 04:11:40 vulfTower CA Backup/Restore: docker stop -t 60 NZBGet Apr 16 04:11:40 vulfTower CA Backup/Restore: Stopping ombi Apr 16 04:11:48 vulfTower kernel: vethfa27fa6: renamed from eth0 Apr 16 04:11:48 vulfTower kernel: docker0: port 1(veth7233cd5) entered disabled state Apr 16 04:11:49 vulfTower kernel: docker0: port 1(veth7233cd5) entered disabled state Apr 16 04:11:49 vulfTower avahi-daemon[4721]: Interface veth7233cd5.IPv6 no longer relevant for mDNS. Apr 16 04:11:49 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth7233cd5.IPv6 with address fe80::3c77:99ff:fe13:f5f1. Apr 16 04:11:49 vulfTower kernel: device veth7233cd5 left promiscuous mode Apr 16 04:11:49 vulfTower kernel: docker0: port 1(veth7233cd5) entered disabled state Apr 16 04:11:49 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::3c77:99ff:fe13:f5f1 on veth7233cd5. Apr 16 04:11:51 vulfTower CA Backup/Restore: docker stop -t 60 ombi Apr 16 04:11:51 vulfTower CA Backup/Restore: Stopping plex Apr 16 04:12:02 vulfTower CA Backup/Restore: docker stop -t 60 plex Apr 16 04:12:02 vulfTower CA Backup/Restore: Stopping plexpy Apr 16 04:12:09 vulfTower kernel: vethcfab548: renamed from eth0 Apr 16 04:12:09 vulfTower kernel: docker0: port 8(vethf1002cd) entered disabled state Apr 16 04:12:10 vulfTower kernel: docker0: port 8(vethf1002cd) entered disabled state Apr 16 04:12:10 vulfTower avahi-daemon[4721]: Interface vethf1002cd.IPv6 no longer relevant for mDNS. Apr 16 04:12:10 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethf1002cd.IPv6 with address fe80::a4f1:7cff:fe85:e4b. Apr 16 04:12:10 vulfTower kernel: device vethf1002cd left promiscuous mode Apr 16 04:12:10 vulfTower kernel: docker0: port 8(vethf1002cd) entered disabled state Apr 16 04:12:10 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::a4f1:7cff:fe85:e4b on vethf1002cd. Apr 16 04:12:12 vulfTower CA Backup/Restore: docker stop -t 60 plexpy Apr 16 04:12:12 vulfTower CA Backup/Restore: Stopping sabnzbd Apr 16 04:12:18 vulfTower kernel: veth8cc7200: renamed from eth0 Apr 16 04:12:18 vulfTower kernel: docker0: port 3(veth4bfc678) entered disabled state Apr 16 04:12:19 vulfTower kernel: docker0: port 3(veth4bfc678) entered disabled state Apr 16 04:12:19 vulfTower avahi-daemon[4721]: Interface veth4bfc678.IPv6 no longer relevant for mDNS. Apr 16 04:12:19 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth4bfc678.IPv6 with address fe80::10fa:ffff:fec3:2d3d. Apr 16 04:12:19 vulfTower kernel: device veth4bfc678 left promiscuous mode Apr 16 04:12:19 vulfTower kernel: docker0: port 3(veth4bfc678) entered disabled state Apr 16 04:12:19 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::10fa:ffff:fec3:2d3d on veth4bfc678. Apr 16 04:12:20 vulfTower CA Backup/Restore: docker stop -t 60 sabnzbd Apr 16 04:12:20 vulfTower CA Backup/Restore: Stopping Sonarr Apr 16 04:12:26 vulfTower kernel: vetha6aad89: renamed from eth0 Apr 16 04:12:26 vulfTower kernel: docker0: port 12(vethfeb974b) entered disabled state Apr 16 04:12:26 vulfTower avahi-daemon[4721]: Interface vethfeb974b.IPv6 no longer relevant for mDNS. Apr 16 04:12:26 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethfeb974b.IPv6 with address fe80::588b:3ff:fe63:99d2. Apr 16 04:12:26 vulfTower kernel: docker0: port 12(vethfeb974b) entered disabled state Apr 16 04:12:26 vulfTower kernel: device vethfeb974b left promiscuous mode Apr 16 04:12:26 vulfTower kernel: docker0: port 12(vethfeb974b) entered disabled state Apr 16 04:12:26 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::588b:3ff:fe63:99d2 on vethfeb974b. Apr 16 04:12:28 vulfTower CA Backup/Restore: docker stop -t 60 Sonarr Apr 16 04:12:28 vulfTower CA Backup/Restore: Stopping transmission Apr 16 04:12:33 vulfTower kernel: veth0ee9d90: renamed from eth0 Apr 16 04:12:33 vulfTower kernel: docker0: port 20(veth54bc497) entered disabled state Apr 16 04:12:34 vulfTower avahi-daemon[4721]: Interface veth54bc497.IPv6 no longer relevant for mDNS. Apr 16 04:12:34 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth54bc497.IPv6 with address fe80::7488:d6ff:fe7d:c639. Apr 16 04:12:34 vulfTower kernel: docker0: port 20(veth54bc497) entered disabled state Apr 16 04:12:34 vulfTower kernel: device veth54bc497 left promiscuous mode Apr 16 04:12:34 vulfTower kernel: docker0: port 20(veth54bc497) entered disabled state Apr 16 04:12:34 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::7488:d6ff:fe7d:c639 on veth54bc497. Apr 16 04:12:35 vulfTower CA Backup/Restore: docker stop -t 60 transmission Apr 16 04:12:35 vulfTower CA Backup/Restore: Stopping yacreaderlibrary-server-docker Apr 16 04:13:36 vulfTower kernel: veth53841f1: renamed from eth0 Apr 16 04:13:36 vulfTower kernel: docker0: port 7(veth22c1ef4) entered disabled state Apr 16 04:13:37 vulfTower avahi-daemon[4721]: Interface veth22c1ef4.IPv6 no longer relevant for mDNS. Apr 16 04:13:37 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth22c1ef4.IPv6 with address fe80::a87d:2cff:fe3f:a830. Apr 16 04:13:37 vulfTower kernel: docker0: port 7(veth22c1ef4) entered disabled state Apr 16 04:13:37 vulfTower kernel: device veth22c1ef4 left promiscuous mode Apr 16 04:13:37 vulfTower kernel: docker0: port 7(veth22c1ef4) entered disabled state Apr 16 04:13:37 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::a87d:2cff:fe3f:a830 on veth22c1ef4. Apr 16 04:13:38 vulfTower CA Backup/Restore: docker stop -t 60 yacreaderlibrary-server-docker Apr 16 04:13:38 vulfTower CA Backup/Restore: Backing up USB Flash drive config folder to Apr 16 04:13:38 vulfTower CA Backup/Restore: Using command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log" /boot/ "/mnt/cache/appdata/Community_Applications_USB_Backup" > /dev/null 2>&1 Apr 16 04:13:58 vulfTower CA Backup/Restore: Backing Up appData from /mnt/cache/appdata/ to /mnt/user/Backup/Community_Applications_Backup/[email protected] Apr 16 04:13:58 vulfTower CA Backup/Restore: Using command: cd '/mnt/cache/appdata/' && /usr/bin/tar -cvaf '/mnt/user/Backup/Community_Applications_Backup/[email protected]/CA_backup.tar' --exclude "Community_Applications_USB_Backup" --exclude "Community_Applications_VM_XML_Backup" --exclude 'docker.img' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Apr 16 05:00:01 vulfTower Docker Auto Update: Community Applications Docker Autoupdate running Apr 16 05:00:01 vulfTower Docker Auto Update: Checking for available updates Apr 16 05:00:41 vulfTower Docker Auto Update: Installing Updates for plex Apr 16 05:02:08 vulfTower sSMTP[14927]: Creating SSL connection to host Apr 16 05:02:08 vulfTower sSMTP[14927]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384 Apr 16 05:02:08 vulfTower sSMTP[14927]: Authorization failed (535 5.7.1 Authentication failed) Apr 16 05:02:08 vulfTower Docker Auto Update: Community Applications Docker Autoupdate finished -
1 minute ago, johnnie.black said:
Don't see nothing out of the ordinary, how much data in TB is missing? The disk are all pretty full:
Filesystem Size Used Avail Use% Mounted on /dev/md1 3.7T 3.3T 377G 90% /mnt/disk1 /dev/md2 2.8T 2.5T 324G 89% /mnt/disk2 /dev/md3 3.7T 3.2T 466G 88% /mnt/disk3 /dev/md4 3.7T 3.2T 466G 88% /mnt/disk4 /dev/md5 3.7T 3.2T 463G 88% /mnt/disk5 /dev/md6 3.7T 3.1T 603G 84% /mnt/disk6
I spoke mistakenly in my first message, it's 200Gb that are missing. But, you're right, the disks are pretty full, which makes me wonder if the files have just moved somewhere. I've tried looking manually (with Krusader) and from command line using this command: find /mnt/user -name '*.cbr, but haven't found them yet. Hopefully I will, but I'm still wondering how they got moved to begin with!
-
Cool, I'll check it out. I think I've been fairly consid
1 minute ago, Frank1940 said:I had a look at your diagnostics file and there appears to be some error condition issues in it. I am hoping that one of the true Gurus like @johnnie.black will come across this thread and have a look at it for you.
In the mean time, you can open a open up a terminal program and log onto your server.
At the Command line run these two commands:
cd /mnt/user ls -alLook and see if you have any shares that have names Media and media ---- Two shares with identical names EXCEPT for capitalization will give SMB fits. If the directories with missing files in deep into the file structure, you can just move down the change with a command that looks like this:
cd MediaSee if you can find any files in places where they should not be...
Thanks, I'll check it out. I think I've been fairly consistent with my file structure naming scheme, but who knows.
-
Hi, yeah, I'm fairly/somewhat familiar with Linux in that I've been tinkering with unRAID for 3 years now, but always learning. My diagnostics are attached below.
-
So, I woke up to a nightmare this morning, and I'm wondering if anyone here can help me or at least help me know what went wrong. For some reason between 11:30pm and 5am last night all of my multiple terabyte comic collection disappeared from my server. The directories are all in place, but they're now empty.
I run Mylar and YCAReader docker containers and have never had a problem over the last few years. Last week I added the Ubiquity container to try out its interface for serving my comic collection on my home network, but those are the only docker containers that have access to my Comics folder.
I have no idea if I might be able to find this data (or repair it?), or how I can find out what happened (if there is a log or anything that would show this).
Any ideas?
-
On 2/16/2018 at 8:53 AM, coppit said:
Did you set USE_UI to true in the config file?
Yes, it still doesn't appear to be working.... neither via browser or RDP. Any ideas?
Should the network type be Bridge or br0?
-
4 hours ago, sparklyballs said:
nothing to worry about
"errors" from syncing that are safe to ignore
Cool, thanks a lot. Do I need to do anything to allow the database to regularly update or will it do so automatically during the hourly checks?
-
Hi, I just installed this container and while the GUI works I'm getting some errors in the log (below). Any idea what the issue is?
------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-brainzcode: executing... [cont-init.d] 20-brainzcode: exited 0. [cont-init.d] 30-initialise-database: executing... [cont-init.d] 30-initialise-database: exited 0. [cont-init.d] 35-generate_css: executing... fatal: Not a git repository (or any of the parent directories): .git fatal: Not a git repository (or any of the parent directories): .git [02:00:05] Using gulpfile /app/musicbrainz/gulpfile.js [02:00:05] Starting 'default'... [02:01:41] Finished 'default' after 1.58 min [cont-init.d] 35-generate_css: exited 0. [cont-init.d] 40-config: executing... [cont-init.d] 40-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. LOG: database system shutdown was interrupted; last known up at 2018-02-15 20:59:38 EST LOG: database system was not properly shut down; automatic recovery in progress LOG: redo starts at 3/2C4F1820 LOG: invalid record length at 3/2DECA3B8: wanted 24, got 0 LOG: redo done at 3/2DECA348 LOG: last completed transaction was at log time 2018-02-15 20:59:35.395681-05 LOG: MultiXact member wraparound protections are now enabled LOG: database system is ready to accept connections LOG: autovacuum launcher started WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks ERROR: constraint "dbmirror_pendingdata_SeqId" of relation "dbmirror_pendingdata" does not exist STATEMENT: ALTER TABLE dbmirror_pendingdata DROP CONSTRAINT "dbmirror_pendingdata_SeqId" CASCADE WARNING: SET TRANSACTION can only be used in transaction blocks WARNING: SET CONSTRAINTS can only be used in transaction blocks -
Hi, i just installed this, but for some reason am unable to access the UI via HostIP:8282 (remapped from 8080) or HostIP:3389, nor am I able to access it via RDP, at HostIP, HostIP:8282 or HostIP:3389. I also tried setting my network for the container to br0 and assigning a static IP (192.168.1.112), and attempted to connect via 192.168.1.112:8080 and 192.168.1.112:3389 (in the browser) and 192.168.1.112, 192.168.1.112:8282 and 192.168.1.112:3389 via RDP - none of these worked either. Finally, I tried setting my container network to host, but this too failed. Any ideas what is wrong? The FileBot container's logs look fine.
-
Yeah, I just realized that UnRaid now uses https and now feel like an idiot
Thanks though!
-
I just upgraded to 6.4.0_rc18f and immediately noticed that my letsencrypt server redirect page was no longer working. I checked my docker and found that letsencrypt was not running and could not be started. So, I moved the letsencrypt image and tried to reinstall through Community Apps, however every time I try to reinstall I get an error which tells me that port 443 is already in use. This has never been the case in the past, and no other docker is using port 443. Anyone have any idea how I can fix this? Thanks! See below for the install error:
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (ba8eb657425e3c10dc7c7e2db6706d13c4d829918522bb0dd4bbbcc009a3ae24): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use. The command failed. -
Same here too...
-
On 7/9/2017 at 3:44 AM, CHBMB said:
I'm away from home for a week on a family holiday, I'll try and VPN home at some point and take a look, thanks for taking the time and effort to post the steps, helps enormously.
Sent from my LG-H815 using Tapatalk
Thank you for taking the time to read through it all! I patiently await any insights you might have. Just in case this helps at all, I will share some additional observations re; https
I have OpenVPN-as set to allow access and management to my Unraid server when I'm outside my home network. Whenever I try to access the OpenVPN-as admin/connect UI (from inside my home network) I'm only able to access it via http, as https always fails to connect. I always thought that this was just a quirk of that particular container, but now that I'm also unable to access the nextcloud setup UI via https, and nextcloud.mydomain.com also fails (either because it times out and says 502 Bad Gateway - with https://nextcloud.mydomain.com, or because it says that I'm trying to access an https port with http - with http://nextcloud.mydomain.com). I'm now starting to wonder if the root of my problem setting up Nextcloud, or at least accessing it once it is set up, has to do with security certificates and being unable to access containers on my server via https.... This is way outside my knowledge base, so I'm not sure how to fix this or even further diagnose if this is the case, but this is what I've been observing at least.
-
Okay here goes the new install from scratch... Again, everything works as expected until the final step of actually accessing my Nextcloud container via https://nextcloud.mydomain.com. I have a sense that this might be because of a problem accessing my server via https (I noticed this with OpenVPN-as also, but thought it was just something to do with that container), but I'm not sure. I've detailed every step of my process below (basically repeating the LinuxServer guide). Any help would be very much appreciated. I'm at a total roadblock with this.
1. I first installed mace's DDclient container, and used it to point my namecheap domain at my unraid server via an a name dynamic DNS record.
2. I then installed LetsEncrypt from community apps with these settings:
And forwarded ports 80 > 81 and 443 > 443 in my router.
3. I then installed the LS MariaDB container from community apps using these settings:
I removed the # from line 124 of my mariadb custom.conf file, so that it read "bind-address=0.0.0.0" and restarted mariadb.
I then created my Nextcloud database using these commands:
docker exec -it mariadb-nextcloud bash mysql -uroot -p CREATE USER 'admin' IDENTIFIED by 'password'; CREATE DATABASE IF NOT EXISTS nextcloud; GRANT ALL PRIVILEGES ON nextcloud.* TO 'admin' IDENTIFIED BY 'password';4. I then added Nextcloud from community apps using these settings:
At this point, after the container installs, when I try to access the Nextcloud webui at https://192.168.1.107:444/ I receive a privacy error (NET::ERR_CERT_AUTHORITY_INVALID) and have to allow the webui to load "not secure" (non-https) in order to access it.
I continue and set up nextcloud via the webui by:
Adding an admin username and an admin password.
Adding the information for my MariaDB user, password, and nextcloud database name (nextcloud), and replacing localhost with my Unraid ip address and MariaDB port (192.168.1.107:3306).
After finalizing the setup I am able to access the Nextcloud webui, though the connection is still 'not secure' (meaning, I assume, http rather than https).
5. I then setup my letsencrypt reverse proxy to allow access to nextcloud via https://nextcloud.mydomain.com by first going to mnt/cache/appdata/letsencrypt/nginx/site-confs and creating a file called nextcloud with the code:
server { listen 443 ssl; server_name nextcloud.mydomain.com; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.0.1:444/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } }I then edited the file mnt/cache/appdata/nextcloud/www/nextcloud/config/config.php to say:
<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.0.1:444', 1 => 'nextcloud.mydomain.com', ), 'overwrite.cli.url' => 'https://nextcloud.mydomain.com', 'overwritehost' => 'nextcloud.mydomain.com', 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '11.0.1.2', 'dbname' => 'nextcloud', 'dbhost' => '192.168.0.1:3305', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'admin', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxx', 'logtimezone' => 'UTC', 'installed' => true, );
6. Finally, I restarted both the letsencrypt and nextcloud containers and try to access Nextcloud via https://nextcloud.mydomain.com. The page tried to load for a long time before eventually displaying the message "502 Bad Gateway", and the same thing happens if I try to select "webui' from my Unraid dashboard. If I try to access Nexcloud via 192.168.1.107:444 I get the message "400 Bad Request - The plain HTTP request was sent to HTTPS port", and if I try https://192.168.1.107:444 I get the same 502 Bad Gateway timeout.
-
This container has been working great for me with PIA for downloading, but for some reason once downloading is complete and I try to seed I get an error that says "cannot assign requested address". Any ideas how I can fix this? I'm mostly downloading from private trackers.
-
16 hours ago, CHBMB said:
Only thing I got is you missed a step in the guide or didn't get something quite right. Beyond that it's impossible to say.
Okay, I tried installing three times following all of the steps, but I may have messed something up. I will try again this weekend when I have more time and document each step along the way and share my process to see if I'm missing anything.
-
On 7/1/2017 at 4:46 PM, zandrsn said:
Also, after I setsetup my nextcloud via http and set up a letsencrypt reverse proxy (following the LS guide), when I try to access my nextcloud Webui I just get the default index page instead of the nextcloud Webui:
Welcome to our server The website is currently being setup under this address. For help and support, please contact: [email protected]or, if I get rid of my default letsencrypt ngix site-conf and just leave the nextcloud conf, when I try to open my nextcloud WebUI (via my Unraid dashboard), I get a https version of my nextcloud.server.com page that times out ERR_TIMED_OUT.
Do I need to change anything in my default site-conf file to be able to access my nextcloud ui or is this a problem with https access on my server perhaps?Just bumping this to see if anyone has an idea. Thanks.
-
41 minutes ago, zandrsn said:
So, I've followed the linuxsever install guide, and have letsencrypt working, as well as my mariadb nextcloud db. However when I install the nextcloud container and open the ui for the first time I'm unable to access via https and can only get to the login page by normal http. Any idea why this is?
Also, after I setsetup my nextcloud via http and set up a letsencrypt reverse proxy (following the LS guide), when I try to access my nextcloud Webui I just get the default index page instead of the nextcloud Webui:
Welcome to our server The website is currently being setup under this address. For help and support, please contact: [email protected]or, if I get rid of my default letsencrypt ngix site-conf and just leave the nextcloud conf, when I try to open my nextcloud WebUI (via my Unraid dashboard), I get a https version of my nextcloud.server.com page that times out ERR_TIMED_OUT.
Do I need to change anything in my default site-conf file to be able to access my nextcloud ui or is this a problem with https access on my server perhaps? -
So, I've followed the linuxsever install guide, and have letsencrypt working, as well as my mariadb nextcloud db. However when I install the nextcloud container and open the ui for the first time I'm unable to access via https and can only get to the login page by normal http. Any idea why this is?
-
12 hours ago, CHBMB said:
The prerequisite to getting nextcloud working is you should be able to hit nextcloud.server.com from WAN, so you will need a c-name record.
Sent from my LG-H815 using Tapatalk
Thanks for the help; got this bit sorted, with my subdomain routing to my unraid server. Still having issues with nextcloud however, so I scrapped my installs of letsencrypt and nextcloud to start again with fresh configs. I have some questions about the nextcloud install, but I'll ask in that thread instead.
-
On 2/21/2017 at 3:15 PM, ChaOConnor said:
docker exec -it letsencrypt htpasswd -c /config/nginx/.htpasswd <username>add: auth_basic_user_file /config/nginx/.htpasswd; to the default file under each service I wanted to protect.
after doing the above, you also need to add
auth_basic "Administrator Login";
auth_basic_user_file /config/nginx/.htpasswd;
in the server config per http://www.tecmint.com/password-protect-web-directories-in-nginx/
Sorry if this is a dumb question, does anyone know why I'm getting a 403 Forbidden after adding .htpasswd access (using these instructions) while I wasn't before? I get the login box and my username/pw is recognized but then I get a 403 Forbidden page.
-
9 hours ago, CHBMB said:
You've half followed two different guides. I'd personally choose one and stick to it. You need to add nextcloud to your nameprovider so the DNS queries point to your server.
Okay, thanks, I'll try to do that.
The only reason I followed the cyanlabs guide is because the LinuxSever guide assumed that the reader already had a Letsencrypt container installed (and a DuckDNS container pointing a domain to their server), and so didn't provide any instructions for installing it. I didn't have Letsencrypt installed yet, so needed instructions for installing it as a prerequisite for installing nextcloud. I followed every part of the LS guide after installing Letsencrypt though, and both the configs I used were from the LS guide.
When you say 'add nextcloud to your nameprovider', do you mean as a cname or url redirect? I'm using namecheap and have tried to figure out what I need to do to point DNS queries to my server, but this step wasn't in either guide I followed, and I'm not sure exactly what to do. As I mentioned, Letsencrypt works with other services such as sonarr, radarr and deluge, but not with nextcloud.
-
hi guys, thanks for the great containers.
I've followed the cyanlabs guide and was able to get sonarr and radarr working through my domain name and letsencrypt.
I had previously followed your tutorial on installing nextcloud on unraid with letsencrypt proxy up until the point that says "Setting Up A Letsencrypt Reverse Proxy". At this point I was able to access nextcloud from my serverip:444 and was able to configure nextcloud with my mariadb info.
I then followed cyanlabs' guide to set up letsencrypt. However after following this guide, while everything else I set up (sonarr, radarr, deluge) works through my domain/location (ex: http://domain/sonarr), nextcloud is inaccessible through /nextcloud. This wasn't a big concern for me because at this point I planned to continue following your tutorial which would cause me to access next cloud at nextcloud.domain.com instead of /nextcloud anyway, however I found that I was also unable to access nextcloud on my local network through serverip:444...
I tried following the rest of your tutorial anyway, and I still get ERR_CONNECTION_CLOSED when I try to connect to serverip:444 and my log file shows
nginx: [emerg] open() "/config/nginx/proxy.conf" failed (2: No such file or directory) in /config/nginx/site-confs/nextcloud:31There is no proxy.conf file in my site-confs directory, and I didn't see a step in either tutorial to create this file (or where I should edit my default.config to reflect nextcloud.conf rather than a generic proxy.conf)
My nextcloud site-conf is:
server { listen 443 ssl; server_name nextcloud.vulf.stream; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.1.107:444/; proxy_max_temp_file_size 4096m; include /config/nginx/proxy.conf; } }
And my /config/www/nextcloud/config/config.php looks like this:
<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxxxxxxx', 'passwordsalt' => 'xxxxxxxxxxxxxxxxxxxxxxxx', 'secret' => 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'trusted_domains' => array ( 0 => '192.168.1.107:444', 1 => 'nextcloud.vulf.stream', ), 'overwrite.cli.url' => 'https://nextcloud.vulf.stream', 'overwritehost' => 'nextcloud.vulf.stream' 'overwriteprotocol' => 'https', 'dbtype' => 'mysql', 'version' => '12.0.0.29', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.107:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'zandrsn', 'dbpassword' => 'xxxxxxxxxxxxxxxxxxxxx', 'installed' => true, );
Any ideas?
I was also just wanted to make sure that I don't need to add the nextcloud subdomain on my domain nameprovider's web console right? I'm assuming that this will redirect automatically on the server end.
Docker Containers Stopping Unexpectedly and Having Problems Updating
in Docker Engine
Posted
Okay, this is my whole log from my last Community Apps Appdata backup. The containers turned back on afterward and none disappeared, which is great, but I'm still a little concerned about the fact that some did disappear before and that my ability to update and edit containers kept failing before...
Apr 16 12:28:42 vulfTower CA Backup/Restore: ####################################### Apr 16 12:28:42 vulfTower CA Backup/Restore: Community Applications appData Backup Apr 16 12:28:42 vulfTower CA Backup/Restore: Applications will be unavailable during Apr 16 12:28:42 vulfTower CA Backup/Restore: this process. They will automatically Apr 16 12:28:42 vulfTower CA Backup/Restore: be restarted upon completion. Apr 16 12:28:42 vulfTower CA Backup/Restore: ####################################### Apr 16 12:28:42 vulfTower CA Backup/Restore: Stopping airsonic Apr 16 12:29:22 vulfTower kernel: vethbe74d52: renamed from eth0 Apr 16 12:29:22 vulfTower kernel: docker0: port 12(veth77b2933) entered disabled state Apr 16 12:29:25 vulfTower avahi-daemon[4721]: Interface veth77b2933.IPv6 no longer relevant for mDNS. Apr 16 12:29:25 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth77b2933.IPv6 with address fe80::487a:d8ff:fea1:a8ce. Apr 16 12:29:25 vulfTower kernel: docker0: port 12(veth77b2933) entered disabled state Apr 16 12:29:25 vulfTower kernel: device veth77b2933 left promiscuous mode Apr 16 12:29:25 vulfTower kernel: docker0: port 12(veth77b2933) entered disabled state Apr 16 12:29:25 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::487a:d8ff:fea1:a8ce on veth77b2933. Apr 16 12:29:31 vulfTower CA Backup/Restore: docker stop -t 60 airsonic Apr 16 12:29:31 vulfTower CA Backup/Restore: Stopping binhex-delugevpn Apr 16 12:29:39 vulfTower kernel: veth3db9f32: renamed from eth0 Apr 16 12:29:39 vulfTower kernel: docker0: port 7(veth28ee5a8) entered disabled state Apr 16 12:29:44 vulfTower avahi-daemon[4721]: Interface veth28ee5a8.IPv6 no longer relevant for mDNS. Apr 16 12:29:44 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth28ee5a8.IPv6 with address fe80::bcab:73ff:fea8:6271. Apr 16 12:29:44 vulfTower kernel: docker0: port 7(veth28ee5a8) entered disabled state Apr 16 12:29:44 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::bcab:73ff:fea8:6271 on veth28ee5a8. Apr 16 12:29:44 vulfTower kernel: device veth28ee5a8 left promiscuous mode Apr 16 12:29:44 vulfTower kernel: docker0: port 7(veth28ee5a8) entered disabled state Apr 16 12:29:51 vulfTower CA Backup/Restore: docker stop -t 60 binhex-delugevpn Apr 16 12:29:51 vulfTower CA Backup/Restore: Stopping binhex-emby Apr 16 12:29:53 vulfTower kernel: veth68ed636: renamed from eth0 Apr 16 12:29:53 vulfTower kernel: docker0: port 13(veth539323d) entered disabled state Apr 16 12:29:56 vulfTower avahi-daemon[4721]: Interface veth539323d.IPv6 no longer relevant for mDNS. Apr 16 12:29:56 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth539323d.IPv6 with address fe80::c4fa:b7ff:fe18:72d8. Apr 16 12:29:56 vulfTower kernel: docker0: port 13(veth539323d) entered disabled state Apr 16 12:29:56 vulfTower kernel: device veth539323d left promiscuous mode Apr 16 12:29:56 vulfTower kernel: docker0: port 13(veth539323d) entered disabled state Apr 16 12:29:56 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::c4fa:b7ff:fe18:72d8 on veth539323d. Apr 16 12:30:01 vulfTower CA Backup/Restore: docker stop -t 60 binhex-emby Apr 16 12:30:01 vulfTower CA Backup/Restore: Stopping calibre-web Apr 16 12:30:15 vulfTower kernel: veth72172c6: renamed from eth0 Apr 16 12:30:15 vulfTower kernel: docker0: port 14(vethd4dd778) entered disabled state Apr 16 12:30:19 vulfTower kernel: docker0: port 14(vethd4dd778) entered disabled state Apr 16 12:30:19 vulfTower avahi-daemon[4721]: Interface vethd4dd778.IPv6 no longer relevant for mDNS. Apr 16 12:30:19 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethd4dd778.IPv6 with address fe80::60af:f7ff:fe7f:edd. Apr 16 12:30:19 vulfTower kernel: device vethd4dd778 left promiscuous mode Apr 16 12:30:19 vulfTower kernel: docker0: port 14(vethd4dd778) entered disabled state Apr 16 12:30:19 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::60af:f7ff:fe7f:edd on vethd4dd778. Apr 16 12:30:28 vulfTower CA Backup/Restore: docker stop -t 60 calibre-web Apr 16 12:30:28 vulfTower CA Backup/Restore: Stopping couchpotato Apr 16 12:30:50 vulfTower kernel: vethcba6ad2: renamed from eth0 Apr 16 12:30:50 vulfTower kernel: docker0: port 6(veth193ffd4) entered disabled state Apr 16 12:30:52 vulfTower avahi-daemon[4721]: Interface veth193ffd4.IPv6 no longer relevant for mDNS. Apr 16 12:30:52 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth193ffd4.IPv6 with address fe80::9467:afff:fec1:95d. Apr 16 12:30:52 vulfTower kernel: docker0: port 6(veth193ffd4) entered disabled state Apr 16 12:30:52 vulfTower kernel: device veth193ffd4 left promiscuous mode Apr 16 12:30:52 vulfTower kernel: docker0: port 6(veth193ffd4) entered disabled state Apr 16 12:30:52 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::9467:afff:fec1:95d on veth193ffd4. Apr 16 12:30:57 vulfTower CA Backup/Restore: docker stop -t 60 couchpotato Apr 16 12:30:57 vulfTower CA Backup/Restore: Stopping duplicati Apr 16 12:31:13 vulfTower kernel: veth219b2de: renamed from eth0 Apr 16 12:31:13 vulfTower kernel: docker0: port 15(vethfcccf83) entered disabled state Apr 16 12:31:16 vulfTower kernel: docker0: port 15(vethfcccf83) entered disabled state Apr 16 12:31:16 vulfTower avahi-daemon[4721]: Interface vethfcccf83.IPv6 no longer relevant for mDNS. Apr 16 12:31:16 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethfcccf83.IPv6 with address fe80::7cdf:58ff:fe27:2217. Apr 16 12:31:16 vulfTower kernel: device vethfcccf83 left promiscuous mode Apr 16 12:31:16 vulfTower kernel: docker0: port 15(vethfcccf83) entered disabled state Apr 16 12:31:16 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::7cdf:58ff:fe27:2217 on vethfcccf83. Apr 16 12:31:23 vulfTower CA Backup/Restore: docker stop -t 60 duplicati Apr 16 12:31:23 vulfTower CA Backup/Restore: Stopping headphones Apr 16 12:31:39 vulfTower kernel: vethd0c889b: renamed from eth0 Apr 16 12:31:39 vulfTower kernel: docker0: port 5(veth9b7e15a) entered disabled state Apr 16 12:31:41 vulfTower avahi-daemon[4721]: Interface veth9b7e15a.IPv6 no longer relevant for mDNS. Apr 16 12:31:41 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth9b7e15a.IPv6 with address fe80::cc5c:6dff:fe2e:bd26. Apr 16 12:31:41 vulfTower kernel: docker0: port 5(veth9b7e15a) entered disabled state Apr 16 12:31:41 vulfTower kernel: device veth9b7e15a left promiscuous mode Apr 16 12:31:41 vulfTower kernel: docker0: port 5(veth9b7e15a) entered disabled state Apr 16 12:31:41 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::cc5c:6dff:fe2e:bd26 on veth9b7e15a. Apr 16 12:31:47 vulfTower CA Backup/Restore: docker stop -t 60 headphones Apr 16 12:31:47 vulfTower CA Backup/Restore: Stopping Hydra Apr 16 12:32:02 vulfTower kernel: vethdd018a3: renamed from eth0 Apr 16 12:32:02 vulfTower kernel: docker0: port 16(veth704bbc2) entered disabled state Apr 16 12:32:04 vulfTower avahi-daemon[4721]: Interface veth704bbc2.IPv6 no longer relevant for mDNS. Apr 16 12:32:04 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth704bbc2.IPv6 with address fe80::80c6:8bff:fe1b:873c. Apr 16 12:32:04 vulfTower kernel: docker0: port 16(veth704bbc2) entered disabled state Apr 16 12:32:04 vulfTower kernel: device veth704bbc2 left promiscuous mode Apr 16 12:32:04 vulfTower kernel: docker0: port 16(veth704bbc2) entered disabled state Apr 16 12:32:04 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::80c6:8bff:fe1b:873c on veth704bbc2. Apr 16 12:32:10 vulfTower CA Backup/Restore: docker stop -t 60 Hydra Apr 16 12:32:10 vulfTower CA Backup/Restore: Stopping jackett Apr 16 12:32:25 vulfTower kernel: vetha1850da: renamed from eth0 Apr 16 12:32:25 vulfTower kernel: docker0: port 11(vethf6264df) entered disabled state Apr 16 12:32:27 vulfTower avahi-daemon[4721]: Interface vethf6264df.IPv6 no longer relevant for mDNS. Apr 16 12:32:27 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethf6264df.IPv6 with address fe80::9402:d2ff:fe95:ef9d. Apr 16 12:32:27 vulfTower kernel: docker0: port 11(vethf6264df) entered disabled state Apr 16 12:32:27 vulfTower kernel: device vethf6264df left promiscuous mode Apr 16 12:32:27 vulfTower kernel: docker0: port 11(vethf6264df) entered disabled state Apr 16 12:32:27 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::9402:d2ff:fe95:ef9d on vethf6264df. Apr 16 12:32:32 vulfTower CA Backup/Restore: docker stop -t 60 jackett Apr 16 12:32:32 vulfTower CA Backup/Restore: Stopping Krusader Apr 16 12:33:32 vulfTower kernel: vethf1aa2ab: renamed from eth0 Apr 16 12:33:32 vulfTower kernel: docker0: port 18(veth25e4ac3) entered disabled state Apr 16 12:33:35 vulfTower avahi-daemon[4721]: Interface veth25e4ac3.IPv6 no longer relevant for mDNS. Apr 16 12:33:35 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth25e4ac3.IPv6 with address fe80::30da:58ff:fe67:b964. Apr 16 12:33:35 vulfTower kernel: docker0: port 18(veth25e4ac3) entered disabled state Apr 16 12:33:35 vulfTower kernel: device veth25e4ac3 left promiscuous mode Apr 16 12:33:35 vulfTower kernel: docker0: port 18(veth25e4ac3) entered disabled state Apr 16 12:33:35 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::30da:58ff:fe67:b964 on veth25e4ac3. Apr 16 12:33:40 vulfTower CA Backup/Restore: docker stop -t 60 Krusader Apr 16 12:33:40 vulfTower CA Backup/Restore: Stopping lazylibrarian Apr 16 12:33:52 vulfTower kernel: veth897d0d2: renamed from eth0 Apr 16 12:33:52 vulfTower kernel: docker0: port 9(vethef7fa57) entered disabled state Apr 16 12:33:54 vulfTower kernel: docker0: port 9(vethef7fa57) entered disabled state Apr 16 12:33:54 vulfTower avahi-daemon[4721]: Interface vethef7fa57.IPv6 no longer relevant for mDNS. Apr 16 12:33:54 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethef7fa57.IPv6 with address fe80::6809:24ff:fe11:8a66. Apr 16 12:33:54 vulfTower kernel: device vethef7fa57 left promiscuous mode Apr 16 12:33:54 vulfTower kernel: docker0: port 9(vethef7fa57) entered disabled state Apr 16 12:33:54 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::6809:24ff:fe11:8a66 on vethef7fa57. Apr 16 12:33:58 vulfTower CA Backup/Restore: docker stop -t 60 lazylibrarian Apr 16 12:33:58 vulfTower CA Backup/Restore: Stopping letsencrypt Apr 16 12:34:29 vulfTower kernel: vethc2b8d01: renamed from eth0 Apr 16 12:34:29 vulfTower kernel: docker0: port 8(veth418813e) entered disabled state Apr 16 12:34:31 vulfTower avahi-daemon[4721]: Interface veth418813e.IPv6 no longer relevant for mDNS. Apr 16 12:34:31 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth418813e.IPv6 with address fe80::28d3:5cff:fe81:2c8f. Apr 16 12:34:31 vulfTower kernel: docker0: port 8(veth418813e) entered disabled state Apr 16 12:34:31 vulfTower kernel: device veth418813e left promiscuous mode Apr 16 12:34:31 vulfTower kernel: docker0: port 8(veth418813e) entered disabled state Apr 16 12:34:31 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::28d3:5cff:fe81:2c8f on veth418813e. Apr 16 12:34:37 vulfTower CA Backup/Restore: docker stop -t 60 letsencrypt Apr 16 12:34:37 vulfTower CA Backup/Restore: Stopping musicbrainz Apr 16 12:35:04 vulfTower kernel: veth18d6512: renamed from eth0 Apr 16 12:35:04 vulfTower kernel: docker0: port 19(vethcfc55e7) entered disabled state Apr 16 12:35:06 vulfTower avahi-daemon[4721]: Interface vethcfc55e7.IPv6 no longer relevant for mDNS. Apr 16 12:35:06 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethcfc55e7.IPv6 with address fe80::d054:8eff:fe11:ced1. Apr 16 12:35:06 vulfTower kernel: docker0: port 19(vethcfc55e7) entered disabled state Apr 16 12:35:06 vulfTower kernel: device vethcfc55e7 left promiscuous mode Apr 16 12:35:06 vulfTower kernel: docker0: port 19(vethcfc55e7) entered disabled state Apr 16 12:35:06 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::d054:8eff:fe11:ced1 on vethcfc55e7. Apr 16 12:35:09 vulfTower CA Backup/Restore: docker stop -t 60 musicbrainz Apr 16 12:35:09 vulfTower CA Backup/Restore: Stopping Mylar_Dev Apr 16 12:35:25 vulfTower CA Backup/Restore: docker stop -t 60 Mylar_Dev Apr 16 12:35:25 vulfTower CA Backup/Restore: Stopping NZBGet Apr 16 12:35:33 vulfTower kernel: veth96d0e2b: renamed from eth0 Apr 16 12:35:33 vulfTower kernel: docker0: port 10(veth3b1e322) entered disabled state Apr 16 12:35:34 vulfTower avahi-daemon[4721]: Interface veth3b1e322.IPv6 no longer relevant for mDNS. Apr 16 12:35:34 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth3b1e322.IPv6 with address fe80::48e8:8bff:fe68:ee7d. Apr 16 12:35:34 vulfTower kernel: docker0: port 10(veth3b1e322) entered disabled state Apr 16 12:35:34 vulfTower kernel: device veth3b1e322 left promiscuous mode Apr 16 12:35:34 vulfTower kernel: docker0: port 10(veth3b1e322) entered disabled state Apr 16 12:35:34 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::48e8:8bff:fe68:ee7d on veth3b1e322. Apr 16 12:35:37 vulfTower CA Backup/Restore: docker stop -t 60 NZBGet Apr 16 12:35:37 vulfTower CA Backup/Restore: Stopping ombi Apr 16 12:35:49 vulfTower kernel: veth06cede5: renamed from eth0 Apr 16 12:35:49 vulfTower kernel: docker0: port 20(veth0da3e12) entered disabled state Apr 16 12:35:50 vulfTower avahi-daemon[4721]: Interface veth0da3e12.IPv6 no longer relevant for mDNS. Apr 16 12:35:50 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth0da3e12.IPv6 with address fe80::ecbf:4fff:fecd:72c5. Apr 16 12:35:50 vulfTower kernel: docker0: port 20(veth0da3e12) entered disabled state Apr 16 12:35:50 vulfTower kernel: device veth0da3e12 left promiscuous mode Apr 16 12:35:50 vulfTower kernel: docker0: port 20(veth0da3e12) entered disabled state Apr 16 12:35:50 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::ecbf:4fff:fecd:72c5 on veth0da3e12. Apr 16 12:35:53 vulfTower CA Backup/Restore: docker stop -t 60 ombi Apr 16 12:35:53 vulfTower CA Backup/Restore: Stopping plex Apr 16 12:36:14 vulfTower CA Backup/Restore: docker stop -t 60 plex Apr 16 12:36:14 vulfTower CA Backup/Restore: Stopping plexpy Apr 16 12:36:24 vulfTower kernel: veth186b9f8: renamed from eth0 Apr 16 12:36:24 vulfTower kernel: docker0: port 17(veth14e9d5b) entered disabled state Apr 16 12:36:25 vulfTower avahi-daemon[4721]: Interface veth14e9d5b.IPv6 no longer relevant for mDNS. Apr 16 12:36:25 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth14e9d5b.IPv6 with address fe80::945b:8bff:fed5:4ff2. Apr 16 12:36:25 vulfTower kernel: docker0: port 17(veth14e9d5b) entered disabled state Apr 16 12:36:25 vulfTower kernel: device veth14e9d5b left promiscuous mode Apr 16 12:36:25 vulfTower kernel: docker0: port 17(veth14e9d5b) entered disabled state Apr 16 12:36:25 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::945b:8bff:fed5:4ff2 on veth14e9d5b. Apr 16 12:36:28 vulfTower CA Backup/Restore: docker stop -t 60 plexpy Apr 16 12:36:28 vulfTower CA Backup/Restore: Stopping sabnzbd Apr 16 12:36:39 vulfTower kernel: docker0: port 4(vethdeed3c2) entered disabled state Apr 16 12:36:39 vulfTower kernel: vetha200199: renamed from eth0 Apr 16 12:36:40 vulfTower avahi-daemon[4721]: Interface vethdeed3c2.IPv6 no longer relevant for mDNS. Apr 16 12:36:40 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vethdeed3c2.IPv6 with address fe80::a095:8aff:fe63:ad33. Apr 16 12:36:40 vulfTower kernel: docker0: port 4(vethdeed3c2) entered disabled state Apr 16 12:36:40 vulfTower kernel: device vethdeed3c2 left promiscuous mode Apr 16 12:36:40 vulfTower kernel: docker0: port 4(vethdeed3c2) entered disabled state Apr 16 12:36:40 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::a095:8aff:fe63:ad33 on vethdeed3c2. Apr 16 12:36:43 vulfTower CA Backup/Restore: docker stop -t 60 sabnzbd Apr 16 12:36:43 vulfTower CA Backup/Restore: Stopping Sonarr Apr 16 12:36:49 vulfTower kernel: docker0: port 2(veth0d6369f) entered disabled state Apr 16 12:36:49 vulfTower kernel: vethb9a3d16: renamed from eth0 Apr 16 12:36:50 vulfTower avahi-daemon[4721]: Interface veth0d6369f.IPv6 no longer relevant for mDNS. Apr 16 12:36:50 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth0d6369f.IPv6 with address fe80::c8c9:f0ff:fe97:65d7. Apr 16 12:36:50 vulfTower kernel: docker0: port 2(veth0d6369f) entered disabled state Apr 16 12:36:50 vulfTower kernel: device veth0d6369f left promiscuous mode Apr 16 12:36:50 vulfTower kernel: docker0: port 2(veth0d6369f) entered disabled state Apr 16 12:36:50 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::c8c9:f0ff:fe97:65d7 on veth0d6369f. Apr 16 12:36:53 vulfTower CA Backup/Restore: docker stop -t 60 Sonarr Apr 16 12:36:53 vulfTower CA Backup/Restore: Stopping transmission Apr 16 12:36:55 vulfTower kernel: transmission-da[14001]: segfault at 18 ip 000055dfa137c0a5 sp 0000145ef80977b0 error 6 in transmission-daemon[55dfa1354000+72000] Apr 16 12:37:00 vulfTower kernel: vethf0dfc1e: renamed from eth0 Apr 16 12:37:00 vulfTower kernel: docker0: port 3(vetha764468) entered disabled state Apr 16 12:37:01 vulfTower kernel: docker0: port 3(vetha764468) entered disabled state Apr 16 12:37:01 vulfTower avahi-daemon[4721]: Interface vetha764468.IPv6 no longer relevant for mDNS. Apr 16 12:37:01 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vetha764468.IPv6 with address fe80::eca5:ebff:fe9a:ca03. Apr 16 12:37:01 vulfTower kernel: device vetha764468 left promiscuous mode Apr 16 12:37:01 vulfTower kernel: docker0: port 3(vetha764468) entered disabled state Apr 16 12:37:01 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::eca5:ebff:fe9a:ca03 on vetha764468. Apr 16 12:37:04 vulfTower CA Backup/Restore: docker stop -t 60 transmission Apr 16 12:37:04 vulfTower CA Backup/Restore: Stopping yacreaderlibrary-server-docker Apr 16 12:38:05 vulfTower kernel: vethe2a0caf: renamed from eth0 Apr 16 12:38:05 vulfTower kernel: docker0: port 1(veth6ebf678) entered disabled state Apr 16 12:38:06 vulfTower avahi-daemon[4721]: Interface veth6ebf678.IPv6 no longer relevant for mDNS. Apr 16 12:38:06 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface veth6ebf678.IPv6 with address fe80::90de:2eff:fe02:6e7. Apr 16 12:38:06 vulfTower kernel: docker0: port 1(veth6ebf678) entered disabled state Apr 16 12:38:06 vulfTower kernel: device veth6ebf678 left promiscuous mode Apr 16 12:38:06 vulfTower kernel: docker0: port 1(veth6ebf678) entered disabled state Apr 16 12:38:06 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::90de:2eff:fe02:6e7 on veth6ebf678. Apr 16 12:38:09 vulfTower CA Backup/Restore: docker stop -t 60 yacreaderlibrary-server-docker Apr 16 12:38:09 vulfTower CA Backup/Restore: Backing up USB Flash drive config folder to Apr 16 12:38:09 vulfTower CA Backup/Restore: Using command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log" /boot/ "/mnt/cache/appdata/Community_Applications_USB_Backup" > /dev/null 2>&1 Apr 16 12:38:11 vulfTower CA Backup/Restore: Backing Up appData from /mnt/cache/appdata/ to /mnt/user/Backup/Community_Applications_Backup/[email protected] Apr 16 12:38:11 vulfTower CA Backup/Restore: Using command: cd '/mnt/cache/appdata/' && /usr/bin/tar -cvaf '/mnt/user/Backup/Community_Applications_Backup/[email protected]/CA_backup.tar' --exclude "Community_Applications_USB_Backup" --exclude "Community_Applications_VM_XML_Backup" --exclude 'docker.img' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Apr 16 14:23:22 vulfTower kernel: mdcmd (74): spindown 3 Apr 16 14:27:41 vulfTower kernel: mdcmd (75): spindown 2 Apr 16 14:30:31 vulfTower kernel: mdcmd (76): spindown 5 Apr 16 14:34:32 vulfTower kernel: mdcmd (77): spindown 6 Apr 16 15:34:37 vulfTower CA Backup/Restore: Backup Complete Apr 16 15:34:37 vulfTower CA Backup/Restore: Verifying backup Apr 16 15:34:37 vulfTower CA Backup/Restore: Using command: cd '/mnt/cache/appdata/' && /usr/bin/tar --diff -C '/mnt/cache/appdata/' -af '/mnt/user/Backup/Community_Applications_Backup/[email protected]/CA_backup.tar' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress Apr 16 15:57:22 vulfTower emhttpd: req (14): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 15:57:22 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:03:54 vulfTower emhttpd: req (15): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:03:54 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:19:55 vulfTower emhttpd: req (16): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:19:55 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:29:05 vulfTower emhttpd: req (17): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:29:05 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:37:29 vulfTower emhttpd: req (18): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:37:29 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:39:08 vulfTower avahi-daemon[4721]: Interface vnet0.IPv6 no longer relevant for mDNS. Apr 16 16:39:08 vulfTower avahi-daemon[4721]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fead:c8f7. Apr 16 16:39:08 vulfTower kernel: br0: port 2(vnet0) entered disabled state Apr 16 16:39:08 vulfTower kernel: device vnet0 left promiscuous mode Apr 16 16:39:08 vulfTower kernel: br0: port 2(vnet0) entered disabled state Apr 16 16:39:08 vulfTower avahi-daemon[4721]: Withdrawing address record for fe80::fc54:ff:fead:c8f7 on vnet0. Apr 16 16:46:04 vulfTower emhttpd: req (19): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:46:04 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 16:52:59 vulfTower emhttpd: req (20): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 16:52:59 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Apr 16 17:10:48 vulfTower kernel: mdcmd (78): spindown 5 Apr 16 17:28:54 vulfTower kernel: mdcmd (79): spindown 3 Apr 16 17:31:41 vulfTower kernel: mdcmd (80): spindown 2 Apr 16 17:34:13 vulfTower CA Backup/Restore: Restarting airsonic Apr 16 17:34:13 vulfTower kernel: docker0: port 1(vetha34a4ab) entered blocking state Apr 16 17:34:13 vulfTower kernel: docker0: port 1(vetha34a4ab) entered disabled state Apr 16 17:34:13 vulfTower kernel: device vetha34a4ab entered promiscuous mode Apr 16 17:34:13 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vetha34a4ab: link is not ready Apr 16 17:34:13 vulfTower kernel: docker0: port 1(vetha34a4ab) entered blocking state Apr 16 17:34:13 vulfTower kernel: docker0: port 1(vetha34a4ab) entered forwarding state Apr 16 17:34:13 vulfTower kernel: docker0: port 1(vetha34a4ab) entered disabled state Apr 16 17:34:15 vulfTower kernel: eth0: renamed from veth789244f Apr 16 17:34:15 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha34a4ab: link becomes ready Apr 16 17:34:15 vulfTower kernel: docker0: port 1(vetha34a4ab) entered blocking state Apr 16 17:34:15 vulfTower kernel: docker0: port 1(vetha34a4ab) entered forwarding state Apr 16 17:34:15 vulfTower CA Backup/Restore: Restarting binhex-delugevpn Apr 16 17:34:16 vulfTower kernel: docker0: port 2(veth83d5358) entered blocking state Apr 16 17:34:16 vulfTower kernel: docker0: port 2(veth83d5358) entered disabled state Apr 16 17:34:16 vulfTower kernel: device veth83d5358 entered promiscuous mode Apr 16 17:34:16 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth83d5358: link is not ready Apr 16 17:34:16 vulfTower kernel: docker0: port 2(veth83d5358) entered blocking state Apr 16 17:34:16 vulfTower kernel: docker0: port 2(veth83d5358) entered forwarding state Apr 16 17:34:16 vulfTower kernel: docker0: port 2(veth83d5358) entered disabled state Apr 16 17:34:17 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vetha34a4ab.IPv6 with address fe80::54a8:1fff:fe0d:2e8f. Apr 16 17:34:17 vulfTower avahi-daemon[4721]: New relevant interface vetha34a4ab.IPv6 for mDNS. Apr 16 17:34:17 vulfTower avahi-daemon[4721]: Registering new address record for fe80::54a8:1fff:fe0d:2e8f on vetha34a4ab.*. Apr 16 17:34:18 vulfTower kernel: eth0: renamed from veth6eaf70a Apr 16 17:34:18 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth83d5358: link becomes ready Apr 16 17:34:18 vulfTower kernel: docker0: port 2(veth83d5358) entered blocking state Apr 16 17:34:18 vulfTower kernel: docker0: port 2(veth83d5358) entered forwarding state Apr 16 17:34:19 vulfTower CA Backup/Restore: Restarting binhex-emby Apr 16 17:34:19 vulfTower kernel: docker0: port 3(veth200606b) entered blocking state Apr 16 17:34:19 vulfTower kernel: docker0: port 3(veth200606b) entered disabled state Apr 16 17:34:19 vulfTower kernel: device veth200606b entered promiscuous mode Apr 16 17:34:19 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth200606b: link is not ready Apr 16 17:34:19 vulfTower kernel: docker0: port 3(veth200606b) entered blocking state Apr 16 17:34:19 vulfTower kernel: docker0: port 3(veth200606b) entered forwarding state Apr 16 17:34:19 vulfTower kernel: docker0: port 3(veth200606b) entered disabled state Apr 16 17:34:19 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth83d5358.IPv6 with address fe80::6cac:42ff:fe6e:d195. Apr 16 17:34:19 vulfTower avahi-daemon[4721]: New relevant interface veth83d5358.IPv6 for mDNS. Apr 16 17:34:19 vulfTower avahi-daemon[4721]: Registering new address record for fe80::6cac:42ff:fe6e:d195 on veth83d5358.*. Apr 16 17:34:22 vulfTower kernel: eth0: renamed from veth6297c5a Apr 16 17:34:22 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth200606b: link becomes ready Apr 16 17:34:22 vulfTower kernel: docker0: port 3(veth200606b) entered blocking state Apr 16 17:34:22 vulfTower kernel: docker0: port 3(veth200606b) entered forwarding state Apr 16 17:34:23 vulfTower CA Backup/Restore: Restarting calibre-web Apr 16 17:34:23 vulfTower kernel: docker0: port 4(vethb8f9cab) entered blocking state Apr 16 17:34:23 vulfTower kernel: docker0: port 4(vethb8f9cab) entered disabled state Apr 16 17:34:23 vulfTower kernel: device vethb8f9cab entered promiscuous mode Apr 16 17:34:23 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethb8f9cab: link is not ready Apr 16 17:34:23 vulfTower kernel: docker0: port 4(vethb8f9cab) entered blocking state Apr 16 17:34:23 vulfTower kernel: docker0: port 4(vethb8f9cab) entered forwarding state Apr 16 17:34:23 vulfTower kernel: docker0: port 4(vethb8f9cab) entered disabled state Apr 16 17:34:24 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth200606b.IPv6 with address fe80::f835:18ff:feec:218c. Apr 16 17:34:24 vulfTower avahi-daemon[4721]: New relevant interface veth200606b.IPv6 for mDNS. Apr 16 17:34:24 vulfTower avahi-daemon[4721]: Registering new address record for fe80::f835:18ff:feec:218c on veth200606b.*. Apr 16 17:34:26 vulfTower kernel: eth0: renamed from veth6e05d34 Apr 16 17:34:26 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb8f9cab: link becomes ready Apr 16 17:34:26 vulfTower kernel: docker0: port 4(vethb8f9cab) entered blocking state Apr 16 17:34:26 vulfTower kernel: docker0: port 4(vethb8f9cab) entered forwarding state Apr 16 17:34:27 vulfTower CA Backup/Restore: Restarting couchpotato Apr 16 17:34:27 vulfTower kernel: docker0: port 5(veth679d508) entered blocking state Apr 16 17:34:27 vulfTower kernel: docker0: port 5(veth679d508) entered disabled state Apr 16 17:34:27 vulfTower kernel: device veth679d508 entered promiscuous mode Apr 16 17:34:27 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth679d508: link is not ready Apr 16 17:34:27 vulfTower kernel: docker0: port 5(veth679d508) entered blocking state Apr 16 17:34:27 vulfTower kernel: docker0: port 5(veth679d508) entered forwarding state Apr 16 17:34:27 vulfTower kernel: docker0: port 5(veth679d508) entered disabled state Apr 16 17:34:28 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethb8f9cab.IPv6 with address fe80::5860:5fff:feec:97b9. Apr 16 17:34:28 vulfTower avahi-daemon[4721]: New relevant interface vethb8f9cab.IPv6 for mDNS. Apr 16 17:34:28 vulfTower avahi-daemon[4721]: Registering new address record for fe80::5860:5fff:feec:97b9 on vethb8f9cab.*. Apr 16 17:34:31 vulfTower kernel: eth0: renamed from vethb764126 Apr 16 17:34:31 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth679d508: link becomes ready Apr 16 17:34:31 vulfTower kernel: docker0: port 5(veth679d508) entered blocking state Apr 16 17:34:31 vulfTower kernel: docker0: port 5(veth679d508) entered forwarding state Apr 16 17:34:32 vulfTower CA Backup/Restore: Restarting duplicati Apr 16 17:34:32 vulfTower kernel: docker0: port 6(vetha233cae) entered blocking state Apr 16 17:34:32 vulfTower kernel: docker0: port 6(vetha233cae) entered disabled state Apr 16 17:34:32 vulfTower kernel: device vetha233cae entered promiscuous mode Apr 16 17:34:32 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vetha233cae: link is not ready Apr 16 17:34:32 vulfTower kernel: docker0: port 6(vetha233cae) entered blocking state Apr 16 17:34:32 vulfTower kernel: docker0: port 6(vetha233cae) entered forwarding state Apr 16 17:34:32 vulfTower kernel: docker0: port 6(vetha233cae) entered disabled state Apr 16 17:34:32 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth679d508.IPv6 with address fe80::ac4f:daff:fe59:bf0. Apr 16 17:34:32 vulfTower avahi-daemon[4721]: New relevant interface veth679d508.IPv6 for mDNS. Apr 16 17:34:32 vulfTower avahi-daemon[4721]: Registering new address record for fe80::ac4f:daff:fe59:bf0 on veth679d508.*. Apr 16 17:34:41 vulfTower kernel: eth0: renamed from veth89cb846 Apr 16 17:34:41 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha233cae: link becomes ready Apr 16 17:34:41 vulfTower kernel: docker0: port 6(vetha233cae) entered blocking state Apr 16 17:34:41 vulfTower kernel: docker0: port 6(vetha233cae) entered forwarding state Apr 16 17:34:42 vulfTower CA Backup/Restore: Restarting headphones Apr 16 17:34:42 vulfTower kernel: docker0: port 7(veth863b304) entered blocking state Apr 16 17:34:42 vulfTower kernel: docker0: port 7(veth863b304) entered disabled state Apr 16 17:34:42 vulfTower kernel: device veth863b304 entered promiscuous mode Apr 16 17:34:42 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth863b304: link is not ready Apr 16 17:34:42 vulfTower kernel: docker0: port 7(veth863b304) entered blocking state Apr 16 17:34:42 vulfTower kernel: docker0: port 7(veth863b304) entered forwarding state Apr 16 17:34:42 vulfTower kernel: docker0: port 7(veth863b304) entered disabled state Apr 16 17:34:43 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vetha233cae.IPv6 with address fe80::c098:21ff:fe7f:2f48. Apr 16 17:34:43 vulfTower avahi-daemon[4721]: New relevant interface vetha233cae.IPv6 for mDNS. Apr 16 17:34:43 vulfTower avahi-daemon[4721]: Registering new address record for fe80::c098:21ff:fe7f:2f48 on vetha233cae.*. Apr 16 17:34:50 vulfTower kernel: eth0: renamed from veth82a4e32 Apr 16 17:34:50 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth863b304: link becomes ready Apr 16 17:34:50 vulfTower kernel: docker0: port 7(veth863b304) entered blocking state Apr 16 17:34:50 vulfTower kernel: docker0: port 7(veth863b304) entered forwarding state Apr 16 17:34:51 vulfTower CA Backup/Restore: Restarting Hydra Apr 16 17:34:51 vulfTower kernel: docker0: port 8(vethd82df26) entered blocking state Apr 16 17:34:51 vulfTower kernel: docker0: port 8(vethd82df26) entered disabled state Apr 16 17:34:51 vulfTower kernel: device vethd82df26 entered promiscuous mode Apr 16 17:34:51 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethd82df26: link is not ready Apr 16 17:34:51 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth863b304.IPv6 with address fe80::60cf:42ff:fe33:3d9a. Apr 16 17:34:51 vulfTower avahi-daemon[4721]: New relevant interface veth863b304.IPv6 for mDNS. Apr 16 17:34:51 vulfTower avahi-daemon[4721]: Registering new address record for fe80::60cf:42ff:fe33:3d9a on veth863b304.*. Apr 16 17:35:00 vulfTower kernel: eth0: renamed from veth440b560 Apr 16 17:35:00 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd82df26: link becomes ready Apr 16 17:35:00 vulfTower kernel: docker0: port 8(vethd82df26) entered blocking state Apr 16 17:35:00 vulfTower kernel: docker0: port 8(vethd82df26) entered forwarding state Apr 16 17:35:02 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethd82df26.IPv6 with address fe80::7064:39ff:fed2:7a39. Apr 16 17:35:02 vulfTower avahi-daemon[4721]: New relevant interface vethd82df26.IPv6 for mDNS. Apr 16 17:35:02 vulfTower avahi-daemon[4721]: Registering new address record for fe80::7064:39ff:fed2:7a39 on vethd82df26.*. Apr 16 17:35:02 vulfTower CA Backup/Restore: Restarting jackett Apr 16 17:35:02 vulfTower kernel: docker0: port 9(vethd9276ba) entered blocking state Apr 16 17:35:02 vulfTower kernel: docker0: port 9(vethd9276ba) entered disabled state Apr 16 17:35:02 vulfTower kernel: device vethd9276ba entered promiscuous mode Apr 16 17:35:02 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethd9276ba: link is not ready Apr 16 17:35:14 vulfTower kernel: eth0: renamed from veth7d403e3 Apr 16 17:35:14 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd9276ba: link becomes ready Apr 16 17:35:14 vulfTower kernel: docker0: port 9(vethd9276ba) entered blocking state Apr 16 17:35:14 vulfTower kernel: docker0: port 9(vethd9276ba) entered forwarding state Apr 16 17:35:16 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethd9276ba.IPv6 with address fe80::c47c:69ff:fea6:f06d. Apr 16 17:35:16 vulfTower avahi-daemon[4721]: New relevant interface vethd9276ba.IPv6 for mDNS. Apr 16 17:35:16 vulfTower avahi-daemon[4721]: Registering new address record for fe80::c47c:69ff:fea6:f06d on vethd9276ba.*. Apr 16 17:35:16 vulfTower CA Backup/Restore: Restarting Krusader Apr 16 17:35:16 vulfTower kernel: docker0: port 10(veth81e1f9f) entered blocking state Apr 16 17:35:16 vulfTower kernel: docker0: port 10(veth81e1f9f) entered disabled state Apr 16 17:35:16 vulfTower kernel: device veth81e1f9f entered promiscuous mode Apr 16 17:35:16 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth81e1f9f: link is not ready Apr 16 17:35:16 vulfTower kernel: docker0: port 10(veth81e1f9f) entered blocking state Apr 16 17:35:16 vulfTower kernel: docker0: port 10(veth81e1f9f) entered forwarding state Apr 16 17:35:16 vulfTower kernel: docker0: port 10(veth81e1f9f) entered disabled state Apr 16 17:35:21 vulfTower kernel: eth0: renamed from vethc70c0d1 Apr 16 17:35:21 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth81e1f9f: link becomes ready Apr 16 17:35:21 vulfTower kernel: docker0: port 10(veth81e1f9f) entered blocking state Apr 16 17:35:21 vulfTower kernel: docker0: port 10(veth81e1f9f) entered forwarding state Apr 16 17:35:22 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth81e1f9f.IPv6 with address fe80::6c2f:63ff:fe21:df03. Apr 16 17:35:22 vulfTower avahi-daemon[4721]: New relevant interface veth81e1f9f.IPv6 for mDNS. Apr 16 17:35:22 vulfTower avahi-daemon[4721]: Registering new address record for fe80::6c2f:63ff:fe21:df03 on veth81e1f9f.*. Apr 16 17:35:25 vulfTower CA Backup/Restore: Restarting lazylibrarian Apr 16 17:35:25 vulfTower kernel: docker0: port 11(veth8e5d71a) entered blocking state Apr 16 17:35:25 vulfTower kernel: docker0: port 11(veth8e5d71a) entered disabled state Apr 16 17:35:25 vulfTower kernel: device veth8e5d71a entered promiscuous mode Apr 16 17:35:25 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth8e5d71a: link is not ready Apr 16 17:35:25 vulfTower kernel: docker0: port 11(veth8e5d71a) entered blocking state Apr 16 17:35:25 vulfTower kernel: docker0: port 11(veth8e5d71a) entered forwarding state Apr 16 17:35:25 vulfTower kernel: docker0: port 11(veth8e5d71a) entered disabled state Apr 16 17:35:39 vulfTower kernel: eth0: renamed from veth4152fb1 Apr 16 17:35:39 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8e5d71a: link becomes ready Apr 16 17:35:39 vulfTower kernel: docker0: port 11(veth8e5d71a) entered blocking state Apr 16 17:35:39 vulfTower kernel: docker0: port 11(veth8e5d71a) entered forwarding state Apr 16 17:35:40 vulfTower CA Backup/Restore: Restarting letsencrypt Apr 16 17:35:40 vulfTower kernel: docker0: port 12(veth0ae8371) entered blocking state Apr 16 17:35:40 vulfTower kernel: docker0: port 12(veth0ae8371) entered disabled state Apr 16 17:35:40 vulfTower kernel: device veth0ae8371 entered promiscuous mode Apr 16 17:35:40 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth0ae8371: link is not ready Apr 16 17:35:40 vulfTower kernel: docker0: port 12(veth0ae8371) entered blocking state Apr 16 17:35:40 vulfTower kernel: docker0: port 12(veth0ae8371) entered forwarding state Apr 16 17:35:40 vulfTower kernel: docker0: port 12(veth0ae8371) entered disabled state Apr 16 17:35:41 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth8e5d71a.IPv6 with address fe80::1cfe:82ff:fe12:c5c7. Apr 16 17:35:41 vulfTower avahi-daemon[4721]: New relevant interface veth8e5d71a.IPv6 for mDNS. Apr 16 17:35:41 vulfTower avahi-daemon[4721]: Registering new address record for fe80::1cfe:82ff:fe12:c5c7 on veth8e5d71a.*. Apr 16 17:35:47 vulfTower kernel: eth0: renamed from vethadff4dd Apr 16 17:35:47 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0ae8371: link becomes ready Apr 16 17:35:47 vulfTower kernel: docker0: port 12(veth0ae8371) entered blocking state Apr 16 17:35:47 vulfTower kernel: docker0: port 12(veth0ae8371) entered forwarding state Apr 16 17:35:48 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth0ae8371.IPv6 with address fe80::48ad:b6ff:fe81:dd5. Apr 16 17:35:48 vulfTower avahi-daemon[4721]: New relevant interface veth0ae8371.IPv6 for mDNS. Apr 16 17:35:48 vulfTower avahi-daemon[4721]: Registering new address record for fe80::48ad:b6ff:fe81:dd5 on veth0ae8371.*. Apr 16 17:35:58 vulfTower CA Backup/Restore: Restarting musicbrainz Apr 16 17:35:58 vulfTower kernel: docker0: port 13(vethadd5962) entered blocking state Apr 16 17:35:58 vulfTower kernel: docker0: port 13(vethadd5962) entered disabled state Apr 16 17:35:58 vulfTower kernel: device vethadd5962 entered promiscuous mode Apr 16 17:35:58 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethadd5962: link is not ready Apr 16 17:35:58 vulfTower kernel: docker0: port 13(vethadd5962) entered blocking state Apr 16 17:35:58 vulfTower kernel: docker0: port 13(vethadd5962) entered forwarding state Apr 16 17:35:58 vulfTower kernel: docker0: port 13(vethadd5962) entered disabled state Apr 16 17:36:15 vulfTower kernel: eth0: renamed from veth97de12c Apr 16 17:36:15 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethadd5962: link becomes ready Apr 16 17:36:15 vulfTower kernel: docker0: port 13(vethadd5962) entered blocking state Apr 16 17:36:15 vulfTower kernel: docker0: port 13(vethadd5962) entered forwarding state Apr 16 17:36:16 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethadd5962.IPv6 with address fe80::3c3b:5dff:feef:8895. Apr 16 17:36:16 vulfTower avahi-daemon[4721]: New relevant interface vethadd5962.IPv6 for mDNS. Apr 16 17:36:16 vulfTower avahi-daemon[4721]: Registering new address record for fe80::3c3b:5dff:feef:8895 on vethadd5962.*. Apr 16 17:36:17 vulfTower CA Backup/Restore: Restarting Mylar_Dev Apr 16 17:36:30 vulfTower CA Backup/Restore: Restarting NZBGet Apr 16 17:36:31 vulfTower kernel: docker0: port 14(veth96ae976) entered blocking state Apr 16 17:36:31 vulfTower kernel: docker0: port 14(veth96ae976) entered disabled state Apr 16 17:36:31 vulfTower kernel: device veth96ae976 entered promiscuous mode Apr 16 17:36:31 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth96ae976: link is not ready Apr 16 17:36:39 vulfTower kernel: eth0: renamed from veth503b30e Apr 16 17:36:39 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth96ae976: link becomes ready Apr 16 17:36:39 vulfTower kernel: docker0: port 14(veth96ae976) entered blocking state Apr 16 17:36:39 vulfTower kernel: docker0: port 14(veth96ae976) entered forwarding state Apr 16 17:36:41 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth96ae976.IPv6 with address fe80::434:4cff:febf:52a6. Apr 16 17:36:41 vulfTower avahi-daemon[4721]: New relevant interface veth96ae976.IPv6 for mDNS. Apr 16 17:36:41 vulfTower avahi-daemon[4721]: Registering new address record for fe80::434:4cff:febf:52a6 on veth96ae976.*. Apr 16 17:36:43 vulfTower CA Backup/Restore: Restarting ombi Apr 16 17:36:43 vulfTower kernel: docker0: port 15(vetha9e07ff) entered blocking state Apr 16 17:36:43 vulfTower kernel: docker0: port 15(vetha9e07ff) entered disabled state Apr 16 17:36:43 vulfTower kernel: device vetha9e07ff entered promiscuous mode Apr 16 17:36:43 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vetha9e07ff: link is not ready Apr 16 17:36:43 vulfTower kernel: docker0: port 15(vetha9e07ff) entered blocking state Apr 16 17:36:43 vulfTower kernel: docker0: port 15(vetha9e07ff) entered forwarding state Apr 16 17:36:43 vulfTower kernel: docker0: port 15(vetha9e07ff) entered disabled state Apr 16 17:37:19 vulfTower kernel: eth0: renamed from veth3ad4c5b Apr 16 17:37:19 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha9e07ff: link becomes ready Apr 16 17:37:19 vulfTower kernel: docker0: port 15(vetha9e07ff) entered blocking state Apr 16 17:37:19 vulfTower kernel: docker0: port 15(vetha9e07ff) entered forwarding state Apr 16 17:37:20 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vetha9e07ff.IPv6 with address fe80::a001:1cff:fe9d:8a7b. Apr 16 17:37:20 vulfTower avahi-daemon[4721]: New relevant interface vetha9e07ff.IPv6 for mDNS. Apr 16 17:37:20 vulfTower avahi-daemon[4721]: Registering new address record for fe80::a001:1cff:fe9d:8a7b on vetha9e07ff.*. Apr 16 17:37:22 vulfTower CA Backup/Restore: Restarting plex Apr 16 17:37:37 vulfTower CA Backup/Restore: Restarting plexpy Apr 16 17:37:37 vulfTower kernel: docker0: port 16(vethd2b9a58) entered blocking state Apr 16 17:37:37 vulfTower kernel: docker0: port 16(vethd2b9a58) entered disabled state Apr 16 17:37:37 vulfTower kernel: device vethd2b9a58 entered promiscuous mode Apr 16 17:37:37 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethd2b9a58: link is not ready Apr 16 17:37:44 vulfTower kernel: eth0: renamed from vethbb16f29 Apr 16 17:37:44 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd2b9a58: link becomes ready Apr 16 17:37:44 vulfTower kernel: docker0: port 16(vethd2b9a58) entered blocking state Apr 16 17:37:44 vulfTower kernel: docker0: port 16(vethd2b9a58) entered forwarding state Apr 16 17:37:46 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethd2b9a58.IPv6 with address fe80::10dd:cbff:fe14:78cd. Apr 16 17:37:46 vulfTower avahi-daemon[4721]: New relevant interface vethd2b9a58.IPv6 for mDNS. Apr 16 17:37:46 vulfTower avahi-daemon[4721]: Registering new address record for fe80::10dd:cbff:fe14:78cd on vethd2b9a58.*. Apr 16 17:37:47 vulfTower CA Backup/Restore: Restarting sabnzbd Apr 16 17:37:47 vulfTower kernel: docker0: port 17(vetha7f7043) entered blocking state Apr 16 17:37:47 vulfTower kernel: docker0: port 17(vetha7f7043) entered disabled state Apr 16 17:37:47 vulfTower kernel: device vetha7f7043 entered promiscuous mode Apr 16 17:37:47 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vetha7f7043: link is not ready Apr 16 17:37:47 vulfTower kernel: docker0: port 17(vetha7f7043) entered blocking state Apr 16 17:37:47 vulfTower kernel: docker0: port 17(vetha7f7043) entered forwarding state Apr 16 17:37:47 vulfTower kernel: docker0: port 17(vetha7f7043) entered disabled state Apr 16 17:37:55 vulfTower kernel: eth0: renamed from vethc62bc34 Apr 16 17:37:55 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha7f7043: link becomes ready Apr 16 17:37:55 vulfTower kernel: docker0: port 17(vetha7f7043) entered blocking state Apr 16 17:37:55 vulfTower kernel: docker0: port 17(vetha7f7043) entered forwarding state Apr 16 17:37:57 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vetha7f7043.IPv6 with address fe80::2874:4aff:fe04:941a. Apr 16 17:37:57 vulfTower avahi-daemon[4721]: New relevant interface vetha7f7043.IPv6 for mDNS. Apr 16 17:37:57 vulfTower avahi-daemon[4721]: Registering new address record for fe80::2874:4aff:fe04:941a on vetha7f7043.*. Apr 16 17:37:58 vulfTower CA Backup/Restore: Restarting Sonarr Apr 16 17:37:58 vulfTower kernel: docker0: port 18(veth407c6a9) entered blocking state Apr 16 17:37:58 vulfTower kernel: docker0: port 18(veth407c6a9) entered disabled state Apr 16 17:37:58 vulfTower kernel: device veth407c6a9 entered promiscuous mode Apr 16 17:37:58 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth407c6a9: link is not ready Apr 16 17:38:04 vulfTower kernel: eth0: renamed from vethc9d45a4 Apr 16 17:38:04 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth407c6a9: link becomes ready Apr 16 17:38:04 vulfTower kernel: docker0: port 18(veth407c6a9) entered blocking state Apr 16 17:38:04 vulfTower kernel: docker0: port 18(veth407c6a9) entered forwarding state Apr 16 17:38:05 vulfTower CA Backup/Restore: Restarting transmission Apr 16 17:38:05 vulfTower kernel: docker0: port 19(vethe56a759) entered blocking state Apr 16 17:38:05 vulfTower kernel: docker0: port 19(vethe56a759) entered disabled state Apr 16 17:38:05 vulfTower kernel: device vethe56a759 entered promiscuous mode Apr 16 17:38:05 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): vethe56a759: link is not ready Apr 16 17:38:05 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth407c6a9.IPv6 with address fe80::648a:bbff:feb4:7269. Apr 16 17:38:05 vulfTower avahi-daemon[4721]: New relevant interface veth407c6a9.IPv6 for mDNS. Apr 16 17:38:05 vulfTower avahi-daemon[4721]: Registering new address record for fe80::648a:bbff:feb4:7269 on veth407c6a9.*. Apr 16 17:38:15 vulfTower kernel: eth0: renamed from veth5ab7d49 Apr 16 17:38:15 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe56a759: link becomes ready Apr 16 17:38:15 vulfTower kernel: docker0: port 19(vethe56a759) entered blocking state Apr 16 17:38:15 vulfTower kernel: docker0: port 19(vethe56a759) entered forwarding state Apr 16 17:38:17 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface vethe56a759.IPv6 with address fe80::789c:1dff:fe3f:93f8. Apr 16 17:38:17 vulfTower avahi-daemon[4721]: New relevant interface vethe56a759.IPv6 for mDNS. Apr 16 17:38:17 vulfTower avahi-daemon[4721]: Registering new address record for fe80::789c:1dff:fe3f:93f8 on vethe56a759.*. Apr 16 17:38:17 vulfTower CA Backup/Restore: Restarting yacreaderlibrary-server-docker Apr 16 17:38:17 vulfTower kernel: docker0: port 20(veth0b425bb) entered blocking state Apr 16 17:38:17 vulfTower kernel: docker0: port 20(veth0b425bb) entered disabled state Apr 16 17:38:17 vulfTower kernel: device veth0b425bb entered promiscuous mode Apr 16 17:38:17 vulfTower kernel: IPv6: ADDRCONF(NETDEV_UP): veth0b425bb: link is not ready Apr 16 17:38:43 vulfTower kernel: eth0: renamed from veth262a583 Apr 16 17:38:43 vulfTower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0b425bb: link becomes ready Apr 16 17:38:43 vulfTower kernel: docker0: port 20(veth0b425bb) entered blocking state Apr 16 17:38:43 vulfTower kernel: docker0: port 20(veth0b425bb) entered forwarding state Apr 16 17:38:44 vulfTower avahi-daemon[4721]: Joining mDNS multicast group on interface veth0b425bb.IPv6 with address fe80::e43d:15ff:feb8:d623. Apr 16 17:38:44 vulfTower avahi-daemon[4721]: New relevant interface veth0b425bb.IPv6 for mDNS. Apr 16 17:38:44 vulfTower avahi-daemon[4721]: Registering new address record for fe80::e43d:15ff:feb8:d623 on veth0b425bb.*. Apr 16 17:38:55 vulfTower CA Backup/Restore: ####################### Apr 16 17:38:55 vulfTower CA Backup/Restore: appData Backup complete Apr 16 17:38:55 vulfTower CA Backup/Restore: ####################### Apr 16 17:38:55 vulfTower CA Backup/Restore: Backup / Restore Completed Apr 16 19:36:12 vulfTower emhttpd: req (21): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Apr 16 19:36:12 vulfTower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog