If you have remote console via IPMI it might be an idea to leave an
active top session so you can see the last point at which the machine
stopped. It may provided a pointer to bad process e.g. eating all the
machine RAM.
Regards
Steve
On 14/09/2017 11:30, wishmaster wrote:
Hi!
My 11.0-STABLE system had been working stable for a three last years, but
became unstable a week ago. The system just freezes about once/2 days (at
night) and no responsive via network, nothing in the console.
Before the first freezing I had made updates of applications in the base system
and jails.
Options VIMAGE and Linux compat. are enabled.
The first thought was bad sectors on the HDD, but dd if=/dev/ada0 of=/dev/null
bs=128k rejected this one.
How can I debug this situation?
Thank,
Vit
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
