Date: Tue, 10 Apr 2007 18:14:57 -0300 From: "Marc G. Fournier" <scrappy@hub.org> To: Derek Ragona <derek@computinginnovations.com>, freebsd-questions@freebsd.org Subject: Re: KVM over IP (Was: Re: adding keyboard after reboot with no keyboard) ... Message-ID: <382F7DBCA05C7674D542FCFC@ganymede.hub.org> In-Reply-To: <6.0.0.22.2.20070410150409.02531170@mail.computinginnovations.com> References: <DB1C681FBA350242795277B4@ganymede.hub.org> <6.0.0.22.2.20070410100710.025273c8@mail.computinginnovations.com> <0FC87C0D2B43ABA3F0CECCAD@ganymede.hub.org> <6.0.0.22.2.20070410150409.02531170@mail.computinginnovations.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Tuesday, April 10, 2007 15:09:24 -0500 Derek Ragona <derek@computinginnovations.com> wrote: > At 02:11 PM 4/10/2007, Marc G. Fournier wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> Does anyone know of a reasonably priced one? Our newer servers, we've been >> using HP servers, so that we have this built in, but I have 6 older servers >> that I'd love to be able to deal with remotely without headaches ... I only >> need to be able to access one at a time ... >> >> I've tried the 'serial console' route, but if the server crashes, logging >> in to >> the serial console doesn't show you anything, whereas, with the HP 'remote >> console' feature, its the same as a KVM, where running it does a screen >> refresh, so that I can see what is on the screen at the time of the crash ... > > The simplest thing you can do is to make sure you are logging the console > messages. I set all remote servers to log the actual console output to a > separate log file in /etc/syslog.conf adding the line: > console.info /var/log/console.log > > and adding a line to /etc/newsyslog.conf to rotate the logs: > /var/log/console.log 600 5 100 * J I'm looking at 'post-crash' kind of error messages ... after the point that the hard drives are no longer being written to ... as well as the ability to login remotely during a reboot when it gets to teh point that it says 'hit RETURN for /bin/sh' because it had a problem with fsck'ng a drive, that sort of thing ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGG/5R4QvfyHIvDvMRAnfyAJ9Bxl0M0EjuG4RJSItZQLwYC2j8hgCfWm5O XE2W/bqgRK3DyXDGf1no/4Y= =er1i -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?382F7DBCA05C7674D542FCFC>