1 possible clue I didn't mention. Early in the week, I enabled ssh for the first time and it started generating ssh keys... but it never finished. Hours later I still couldn't ssh in and shrugged my shoulders and forgot about it. After the first hard lock reboot, the next time I logged into the web console, there were two alerts saying it had started generating ssh keys and that it had finished... those were both generated after the reboot. The third hard lock happened today while I was working on getting ssh in using the key for a user. It happened right at the time when the successful ssh should have occurred. Perhaps this suggests something with drive access or maybe memory?
Peace, Todd Russell Director of IT and Webmaster Saint Joseph Abbey and Seminary College 985-867-2266 985-789-4319 Please consider helping Saint Joseph Abbey and Seminary College recover from the devastating flood waters that overtook our campus on March 11, 2016. http://helptheabbey.com --------------------------------------------------------------- http://saintjosephabbey.com For IT Requests, please submit a ticket at: https://docs.google.com/forms/d/1e3PCRvnEVNU5-rVFolf9zivA9-m41Nj07eDjjCtFwpI/viewform?usp=send_form#start=invite On Thu, Sep 1, 2016 at 4:53 PM, Todd Russell <[email protected]> wrote: > Everything had been fine for ages. Had a hard lock Tuesday before lunch... > couldn't ping it, no response at physical kb, had to hard reboot it. > > Came back late that night to apply 2.3.2 update. Had another hard lock > today a little after noon. Was looking into it and getting set up to ssh in > from home so I could plan to reboot every night until after Labor Day trip > when I would look further into it. Then got another hard lock while trying > to ssh in around 3:30. > > Coming back tonight to do memtest, SpinRite on the SSD, etc..., but I was > wondering if anyone has any ideas of anything that might cause hard locks > aside from hardware problems? If this was linux, I would blame it on > systemd, but I don't know if FreeBSD would ever hard lock outside of > hardware issues. > > The hardware is a SuperMicro Atom board I bought from iXSystems installed > to a Samsung 850 Pro with 8GB ECC RAM. > > I know this isn't much to go on, and I am not expecting help with > troubleshooting, but there was nothing in system logs or dmesg that looked > out of place after the first 2. Mostly I am curious if others have ever > seen hard locks happen in FreeBSD and what caused them in their experience. > Thanks in advance for any help. > > Peace, > Todd Russell > Director of IT and Webmaster > Saint Joseph Abbey and Seminary College > 985-867-2266 > 985-789-4319 > > Please consider helping Saint Joseph Abbey and Seminary College recover > from the devastating flood waters that overtook our campus on March 11, > 2016. > http://helptheabbey.com > > --------------------------------------------------------------- > > http://saintjosephabbey.com > > For IT Requests, please submit a ticket at: > https://docs.google.com/forms/d/1e3PCRvnEVNU5-rVFolf9zivA9- > m41Nj07eDjjCtFwpI/viewform?usp=send_form#start=invite > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
