Hi guys,
I sporadically have the issue that my FreeNAS gets stuck when rebooting over the webUI.
I have logfiles from the moment the shutdown command was sent.
I then switched it off manually by holding down the power button and started it up again at 09:59:20 where it booted up normally again.
It seem to somehow has something to do with DHCP oder DNS, can't really figure it out by myself...
Any help highly appreciated!
I sporadically have the issue that my FreeNAS gets stuck when rebooting over the webUI.
I have logfiles from the moment the shutdown command was sent.
Dec 14 09:36:03 ce0nas notifier: shutdown: [pid 73077]
Dec 14 09:36:03 ce0nas notifier: Shutdown NOW!
Dec 14 09:36:04 ce0nas syslog-ng[73574]: syslog-ng starting up; version='3.6.4'
Dec 14 09:36:04 ce0nas GEOM_ELI: Device ada1p1.eli destroyed.
Dec 14 09:36:04 ce0nas GEOM_ELI: Detached ada1p1.eli on last close.
Dec 14 09:36:04 ce0nas kernel: pid 1468 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Dec 14 09:36:04 ce0nas GEOM_ELI: Device ada2p1.eli destroyed.
Dec 14 09:36:04 ce0nas GEOM_ELI: Detached ada2p1.eli on last close.
Dec 14 09:36:04 ce0nas GEOM_ELI: Device ada3p1.eli destroyed.
Dec 14 09:36:04 ce0nas GEOM_ELI: Detached ada3p1.eli on last close.
Dec 14 09:36:04 ce0nas GEOM_ELI: Device ada4p1.eli destroyed.
Dec 14 09:36:04 ce0nas GEOM_ELI: Detached ada4p1.eli on last close.
Dec 14 09:36:04 ce0nas kernel: epair0a: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: epair0a: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: epair0b: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: epair0b: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: em0: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: em0: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: em0: promiscuous mode disabled
Dec 14 09:36:04 ce0nas kernel: bridge0: link state changed to DOWN
Dec 14 09:36:04 ce0nas kernel: bridge0: link state changed to DOWN
Dec 14 09:36:08 ce0nas smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Dec 14 09:36:08 ce0nas kernel: em0: link state changed to UP
Dec 14 09:36:08 ce0nas kernel: em0: link state changed to UP
Dec 14 09:36:08 ce0nas ntpd[1949]: ntpd exiting on signal 15 (Terminated)
Dec 14 09:36:09 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Dec 14 09:36:10 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Dec 14 09:36:11 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Dec 14 09:36:12 ce0nas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:4 Err:-1 Errno:61 Conne
ction refused
Dec 14 09:36:13 ce0nas dhclient: New IP Address (em0): 192.168.10.22
Dec 14 09:36:13 ce0nas dhclient: New Subnet Mask (em0): 255.255.255.0
Dec 14 09:36:13 ce0nas dhclient: New Broadcast Address (em0): 192.168.10.255
Dec 14 09:36:13 ce0nas dhclient: New Routers (em0): 192.168.10.254
Dec 14 09:36:14 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Dec 14 09:36:15 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Dec 14 09:36:16 ce0nas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Dec 14 09:36:17 ce0nas syslog-ng[73574]: syslog-ng shutting down; version='3.6.4'
Dec 14 09:59:20 ce0nas syslog-ng[1468]: syslog-ng starting up; version='3.6.4'
I then switched it off manually by holding down the power button and started it up again at 09:59:20 where it booted up normally again.
It seem to somehow has something to do with DHCP oder DNS, can't really figure it out by myself...
Any help highly appreciated!