Cron Shutdown -> Restart

Status
Not open for further replies.

Jacopx

Patron
Joined
Feb 19, 2016
Messages
367
hi everyones, I have setup since 3 months, a cron jobs for shutting my system down every work day at 1:35.
In the last 2 days something goes wrong and my cron doesn't work, it start the shutdown procedure but I restart (without LED power off) immediately! I have recieved this mail:

Code:
FreeNAS.local daily security run output
FreeNAS

##########@gmail.com
to me
4 hours agoDetails

FreeNAS.local changes in mounted filesystems:
28a29
> WDVolume_A/jails/.warden-template-VirtualBox-4.3.12 /mnt/WDVolume_A/jails/.warden-template-VirtualBox-4.3.12 zfs      rw,nfsv4acls    0 0
29a31,32
> WDVolume_A/jails/.warden-template-standard /mnt/WDVolume_A/jails/.warden-template-standard zfs        rw,nfsv4acls    0 0
> WDVolume_A/jails/grafana_1 /mnt/WDVolume_A/jails/grafana_1 zfs        rw,nfsv4acls    0 0
33a37
> WDVolume_A/jails/vm_1 /mnt/WDVolume_A/jails/vm_1 zfs  rw,nfsv4acls    0 0
37a42,44
> WDVolume_A/virtualm   /mnt/WDVolume_A/virtualm zfs    rw,nfsv4acls    0 0
> WDVolume_A/virtualm/data /mnt/WDVolume_A/virtualm/data zfs    rw,nfsv4acls    0 0
> WDVolume_A/virtualm/image /mnt/WDVolume_A/virtualm/image zfs  rw,nfsv4acls    0 0
48c55
< devfs                 /mnt/WDVolume_A/jails/owncloud_1/dev devfs      rw,multilabel   0 0
---
> devfs                 /mnt/WDVolume_A/jails/grafana_1/dev devfs       rw,multilabel   0 0
50d56
< devfs                 /mnt/WDVolume_A/jails/sickrage_1/dev devfs      rw,multilabel   0 0
56c62
< procfs                        /mnt/WDVolume_A/jails/owncloud_1/proc procfs    rw              0 0
---
> procfs                        /mnt/WDVolume_A/jails/grafana_1/proc procfs     rw              0 0
58d63
< procfs                        /mnt/WDVolume_A/jails/sickrage_1/proc procfs    rw              0 0

FreeNAS.local kernel log messages:
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #12 Launched!
> SMP: AP CPU #15 Launched!
> SMP: AP CPU #11 Launched!
> SMP: AP CPU #8 Launched!
> SMP: AP CPU #13 Launched!
> SMP: AP CPU #10 Launched!
> Timecounter "TSC-low" frequency 1300029286 Hz quality 1000
> vboxdrv: fAsync=0 offMin=0x3a1 offMax=0x4207
> epair0a: promiscuous mode enabled
> lagg0: link state changed to UP
> em0: link state changed to UP
> epair2a: Ethernet address: 02:ff:20:00:08:0a
> epair2b: Ethernet address: 02:ff:70:00:09:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (410 items).  Lost 41 pages of memory.
> Freed UMA keg (udpcb) was not empty (3674 items).  Lost 22 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (240 items).  Lost 24 pages of memory.
> Freed UMA keg (tcpcb) was not empty (72 items).  Lost 24 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair2a: Ethernet address: 02:ff:20:00:08:0a
> epair2b: Ethernet address: 02:ff:70:00:09:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> pid 36268 (VBoxHeadless), uid 1001: exited on signal 11
> tun0: link state changed to DOWN
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (470 items).  Lost 47 pages of memory.
> Freed UMA keg (udpcb) was not empty (4175 items).  Lost 25 pages of memory.
> Freed UMA keg (tcptw) was not empty (3510 items).  Lost 78 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (2610 items).  Lost 261 pages of memory.
> Freed UMA keg (tcpcb) was not empty (216 items).  Lost 72 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.1.50 moved from 02:ff:20:00:07:0a to 0c:c4:7a:c4:0b:e2 on epair1b
> epair2a: Ethernet address: 02:ff:20:00:08:0a
> epair2b: Ethernet address: 02:ff:70:00:09:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (270 items).  Lost 27 pages of memory.
> Freed UMA keg (udpcb) was not empty (2338 items).  Lost 14 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair2a: Ethernet address: 02:ff:20:00:08:0a
> epair2b: Ethernet address: 02:ff:70:00:09:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (320 items).  Lost 32 pages of memory.
> Freed UMA keg (udpcb) was not empty (2839 items).  Lost 17 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (320 items).  Lost 32 pages of memory.
> Freed UMA keg (tcpcb) was not empty (108 items).  Lost 36 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> pid 17557 (VBoxHeadless), uid 1001: exited on signal 11
> pid 19295 (VBoxHeadless), uid 1001: exited on signal 11
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (350 items).  Lost 35 pages of memory.
> Freed UMA keg (udpcb) was not empty (3173 items).  Lost 19 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (180 items).  Lost 18 pages of memory.
> Freed UMA keg (tcpcb) was not empty (54 items).  Lost 18 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair3a: link state changed to DOWN
> epair3b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (470 items).  Lost 47 pages of memory.
> Freed UMA keg (udpcb) was not empty (4175 items).  Lost 25 pages of memory.
> Freed UMA keg (tcptw) was not empty (2520 items).  Lost 56 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (1770 items).  Lost 177 pages of memory.
> Freed UMA keg (tcpcb) was not empty (405 items).  Lost 135 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> em1: promiscuous mode disabled
> ifa_del_loopback_route: deletion failed: 48
> Freed UMA keg (udp_inpcb) was not empty (440 items).  Lost 44 pages of memory.
> Freed UMA keg (udpcb) was not empty (3841 items).  Lost 23 pages of memory.
> Freed UMA keg (tcptw) was not empty (1755 items).  Lost 39 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (440 items).  Lost 44 pages of memory.
> Freed UMA keg (sackhole) was not empty (3625 items).  Lost 29 pages of memory.
> Freed UMA keg (tcpcb) was not empty (162 items).  Lost 54 pages of memory.
> Freed UMA keg (ripcb) was not empty (180 items).  Lost 18 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz (2600.06-MHz K8-class CPU)
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #15 Launched!
> SMP: AP CPU #8 Launched!
> SMP: AP CPU #6 Launched!
> SMP: AP CPU #14 Launched!
> SMP: AP CPU #11 Launched!
> Timecounter "TSC-low" frequency 1300029834 Hz quality 1000
> vboxdrv: fAsync=0 offMin=0x24b offMax=0x1071
> bridge0: link state changed to UP

-- End of security output --
Reply
Forward


How can I solve it? :)
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
Stop shutting down your FN box at night. Okay, you might save a bit of your electricity bill, but long term you're likely going to have issues. Most maintenance jobs, such as scrubs, security checks, etc. usually happen overnight. By shutting down you're not letting these tasks run.

By letting FN do it thing, you'll find these security emails wont look as scary in the future.
 

styno

Patron
Joined
Apr 11, 2016
Messages
466

Jacopx

Patron
Joined
Feb 19, 2016
Messages
367

Jacopx

Patron
Joined
Feb 19, 2016
Messages
367
Stop shutting down your FN box at night. Okay, you might save a bit of your electricity bill, but long term you're likely going to have issues. Most maintenance jobs, such as scrubs, security checks, etc. usually happen overnight. By shutting down you're not letting these tasks run.

By letting FN do it thing, you'll find these security emails wont look as scary in the future.

Yes, in fact I have set scrubs and other stuff during the morning when I'm not using it (it's an home server).
If I shutdown it every night I can save around 30/40€ per year [emoji53]
 

nojohnny101

Wizard
Joined
Dec 3, 2015
Messages
1,478
If I shutdown it every night I can save around 30/40€ per year
emoji53.png

well you might just shorten the life of your drives enough to make that up and break even!
 
Status
Not open for further replies.
Top