On Thu, Sep 1, 2016 at 4:26 PM, Todd Russell <[email protected]> wrote: > 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 >
That sounds like it could be something but you would have to see if there is something running in the background peaking a cpu or something like that. You could also check what happens on a login... _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
