Date: Fri, 25 Feb 2011 14:00:44 -0600 From: "Mark Felder" <feld@feld.me> To: "Greg Larkin" <glarkin@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: Help: Looking to contact someone running FreeBSD on ESX Message-ID: <op.vrg5vibd34t2sn@tech304> In-Reply-To: <4D67FFD1.6090905@FreeBSD.org> References: <op.vrgzxrj034t2sn@tech304> <4D67FFD1.6090905@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Feb 2011 13:15:29 -0600, Greg Larkin <glarkin@freebsd.org> wrote: > I haven't used watchdogd(8) (http://bit.ly/eKHUEN) before, but I wonder > if it would help you by firing some data logging command (-e option) so > you have some information to go on. That actually looks like a great solution, but I currently cannot recompile the kernel to enable SW_WATCHDOG and take those servers down. We have identical hardware in a test environment that I can do that on and hopefully see if we can get a clone of the problematic VMs to fail there with the watchdogd enabled. Thanks, Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.vrg5vibd34t2sn>