I Like FreeNAS
Cadet
- Joined
- Feb 26, 2016
- Messages
- 2
I recently setup a cron job to shut down my system at 12:45am each night and that works fine. Odd thing is at 2:00am the system starts itself up again. The motherboard BIOS is set to startup at 8:30am and I don't have any CRON jobs starting up the system. I'm fairly new to FreeNAS and Linux in general but the only other schedule that I know of is the scrub and that runs at 10:00am every 35 days. What schedule am I missing?
Log messages below. The system restarted itself at 2:00am and the messages below show that last few seconds of startup.
Log messages below. The system restarted itself at 2:00am and the messages below show that last few seconds of startup.
Code:
Feb 26 02:05:22 nas kernel: epair0a: link state changed to UP Feb 26 02:05:22 nas kernel: epair0a: link state changed to UP Feb 26 02:05:22 nas kernel: epair0b: link state changed to UP Feb 26 02:05:22 nas kernel: epair0b: link state changed to UP Feb 26 02:05:22 nas kernel: epair0a: promiscuous mode enabled Feb 26 02:05:22 nas kernel: re0: link state changed to DOWN Feb 26 02:05:22 nas kernel: re0: link state changed to DOWN Feb 26 02:05:22 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Feb 26 02:05:22 nas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b Feb 26 02:05:26 nas kernel: re0: link state changed to UP Feb 26 02:05:26 nas kernel: re0: link state changed to UP Feb 26 02:37:02 nas smbd[6201]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 192.168.0.105 != (NULL)