March 3, 201610 yr Hey All! I had my server up and running for days with no problem until wanted to add a fan to my case. I had to shut down, which I did properly (stopped array and ran the command) but now my docker will not start. I receive the following in the log Mar 2 21:01:17 Tower avahi-daemon[11538]: Service group file /services/afp.service changed, reloading. Mar 2 21:01:17 Tower emhttp: Starting Docker... Mar 2 21:01:17 Tower kernel: BTRFS: device fsid ddb0abf9-ea09-4004-a6b8-20cd7a7fd46c devid 1 transid 30367 /dev/loop0 Mar 2 21:01:17 Tower kernel: BTRFS info (device loop0): disk space caching is enabled Mar 2 21:01:17 Tower kernel: BTRFS: has skinny extents Mar 2 21:01:17 Tower logger: Resize '/var/lib/docker' of 'max' Mar 2 21:01:17 Tower logger: starting docker ... Mar 2 21:01:17 Tower kernel: BTRFS: new size for /dev/loop0 is 10737418240 Mar 2 21:01:18 Tower avahi-daemon[11538]: Service "Tower" (/services/smb.service) successfully established. Mar 2 21:01:18 Tower avahi-daemon[11538]: Service "Tower-AFP" (/services/afp.service) successfully established. Mar 2 21:01:18 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Mar 2 21:01:18 Tower avahi-daemon[11538]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1. Mar 2 21:01:18 Tower avahi-daemon[11538]: New relevant interface docker0.IPv4 for mDNS. Mar 2 21:01:18 Tower avahi-daemon[11538]: Registering new address record for 172.17.42.1 on docker0.IPv4. Mar 2 21:01:19 Tower kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) Mar 2 21:01:19 Tower emhttp: Starting libvirt... Mar 2 21:01:19 Tower logger: Starting libvirtd... Mar 2 21:01:19 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Mar 2 21:01:19 Tower kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]> Mar 2 21:01:19 Tower kernel: Ebtables v2.0 registered Mar 2 21:01:19 Tower kernel: device virbr0-nic entered promiscuous mode Mar 2 21:01:19 Tower avahi-daemon[11538]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Mar 2 21:01:19 Tower avahi-daemon[11538]: New relevant interface virbr0.IPv4 for mDNS. Mar 2 21:01:19 Tower avahi-daemon[11538]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Mar 2 21:01:19 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Mar 2 21:01:19 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Mar 2 21:01:19 Tower dnsmasq[12492]: started, version 2.72 cachesize 150 Mar 2 21:01:19 Tower dnsmasq[12492]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect Mar 2 21:01:19 Tower dnsmasq-dhcp[12492]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Mar 2 21:01:19 Tower dnsmasq-dhcp[12492]: DHCP, sockets bound exclusively to interface virbr0 Mar 2 21:01:19 Tower dnsmasq[12492]: reading /etc/resolv.conf Mar 2 21:01:19 Tower dnsmasq[12492]: using nameserver 172.16.64.1#53 Mar 2 21:01:19 Tower dnsmasq[12492]: read /etc/hosts - 1 addresses Mar 2 21:01:19 Tower dnsmasq[12492]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 2 21:01:19 Tower dnsmasq-dhcp[12492]: read /var/lib/libvirt/dnsmasq/default.hostsfile Mar 2 21:01:19 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Mar 2 21:01:20 Tower ntpd[1522]: Listen normally on 3 docker0 172.17.42.1:123 Mar 2 21:01:20 Tower ntpd[1522]: new interface(s) found: waking up resolver Which leads me to think it has started but I cannot tell. Am I missing something?? Thanks in advance! T EDIT: Read this https://lime-technology.com/forum/index.php?topic=47071.0 and unfortunately had to restart my docker
Archived
This topic is now archived and is closed to further replies.