Pfsense 2.0 randomly rebooting



  • I'm having a problem with my pfsense box randomly rebooting. There doesn't seem to be any pattern except that it occurs approximately once a week. Sometimes it'll only go six days, sometimes it will go for 10, but never more than that. There haven't been any problems or errors. It just reboots.



  • Without having anything else to go on I'd suspect hardware. You can set up a syslog server and redirect the logs there to save any logs that might get sent right before the reboot but usually with strange random behavior it's hardware. Can you swap out the install to another machine?



  • Hi,

    In my opinion you should change firstly RAM. ;)

    Regards,
    SGTR


  • Netgate Administrator

    I see you have, for a time at least, been running squid on a CF card. It is possible that the card has run out of write cycles on some blocks. Have you seen any warnings in the logs that might point to this?
    What hardware are you running now?

    Steve



  • seems you aren't getting a kernel panic (it would prompt you to submit a crash report upon logging in), so it's definitely hardware of some sort. Could be anything, RAM (though usually that would cause a panic because of memory corruption), power supply, motherboard, CPU, overheating, lots of possibilities.



  • @stephenw10:

    I see you have, for a time at least, been running squid on a CF card. It is possible that the card has run out of write cycles on some blocks. Have you seen any warnings in the logs that might point to this?
    What hardware are you running now?

    Steve

    That's possible. I haven't noticed any warnings, but I haven't been monitoring the logs too closely. Though I did check them once right after a reboot, and didn't see anything. What would such a warning look like?

    I have a hard time believing it's hardware, but everyone else seems to think that, so maybe I'm wrong.  ;)



  • if it were the CF you'd be seeing at least some errors in the logs, and usually a ton of them. Write errors, timeouts, something on adX or daX depending on what your CF device is.



  • It must not be the CF card then. It started doing this not very long after I built the system, so it's probably not write cycles anyway. I suppose it could be that some hardware was bad out of the box, but it was working fine at first, so I don't know.

    @cmb:

    if it were the CF you'd be seeing at least some errors in the logs, and usually a ton of them. Write errors, timeouts, something on adX or daX depending on what your CF device is.


Log in to reply