Tim Sievers
Dabbler
- Joined
- Jul 30, 2015
- Messages
- 14
All,
I have been dealing with random reboots (usually happens between 3 and 14 days) on two Dell 2950 servers. I setup syslog and enabled the debug kernel, but that has only added to the oddity. I cannot find any kernel panics in the logs (but I do get a samba panic on the one server), but there are no logs after some event triggers a reboot, except for the logs of the reboot. The only thing I can find from reviewing the logs is that they seem to end right before the server would run "/usr/libexec/atrun" via crontab. The last time this happened, the syslog reported that the server responded to SNMP after missing the atrun, so syslog and snmp were still operational right before it rebooted. I have disabled the cron job and I have been monitoring the atrun job queue, but I have not been seeing anything. On top of any suggestions you may have, could you also answer the following questions:
1. What does FreeNAS schedule with "at", and are the jobs supposed to stay in the folder?
2. If it is a bad USB, would using another USB in a mirror setup prevent this lockup?
I have already updated from 9.3-Stable-201506292332 to 9.3-Stable-201508250051 and it seems to be running fine for almost a week, but the issue is not predictable.
I have been dealing with random reboots (usually happens between 3 and 14 days) on two Dell 2950 servers. I setup syslog and enabled the debug kernel, but that has only added to the oddity. I cannot find any kernel panics in the logs (but I do get a samba panic on the one server), but there are no logs after some event triggers a reboot, except for the logs of the reboot. The only thing I can find from reviewing the logs is that they seem to end right before the server would run "/usr/libexec/atrun" via crontab. The last time this happened, the syslog reported that the server responded to SNMP after missing the atrun, so syslog and snmp were still operational right before it rebooted. I have disabled the cron job and I have been monitoring the atrun job queue, but I have not been seeing anything. On top of any suggestions you may have, could you also answer the following questions:
1. What does FreeNAS schedule with "at", and are the jobs supposed to stay in the folder?
2. If it is a bad USB, would using another USB in a mirror setup prevent this lockup?
I have already updated from 9.3-Stable-201506292332 to 9.3-Stable-201508250051 and it seems to be running fine for almost a week, but the issue is not predictable.