Date: Tue, 18 Apr 2017 13:16:38 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: 10.3-stable random server reboots - finding the reason Message-ID: <a91d4083-929d-295e-4daa-cc223ec5dbe4@freebsd.org> In-Reply-To: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net> References: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VDMkrWlIhlaqUk0wonncUMKKcwgooPNNO Content-Type: multipart/mixed; boundary="oQ4DSJfBI8LrqdwLd5hX5MT2AX70VV4o0"; protected-headers="v1" From: Matthew Seaman <matthew@freebsd.org> To: freebsd-questions@freebsd.org Message-ID: <a91d4083-929d-295e-4daa-cc223ec5dbe4@freebsd.org> Subject: Re: 10.3-stable random server reboots - finding the reason References: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net> In-Reply-To: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net> --oQ4DSJfBI8LrqdwLd5hX5MT2AX70VV4o0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 04/18/17 12:59, tech-lists wrote: > I have an up-to-date 10.3 server that is randomly rebooting, after bein= g > up for days. Previously it had been up for many months. The problem is,= > nothing seems to be left in the logs to indicate why it's doing this. I= > have all.log and console.log enabled. >=20 > So, what I'm asking is, how can I capture its last gasp? >=20 Well, probably the most effective way to do that is to hook up a serial cable and make a continuous log of the system console onto another machine. That's not guaranteed to get you good diagnostics though. A server that spontaneously becomes unstable is often suffering from hardware problems. It could be all sorts of things -- one of the fans died so it's overheating; the power supply is flaking out; capacitors on the motherboard are giving up; memory has gone bad. Many of these sort of problems will result in an instant system crash with nothing in any log files or on the console. Start by trying out some hardware diagnostics, like running memtest86 for 24h or so. Cheers, Matthew --oQ4DSJfBI8LrqdwLd5hX5MT2AX70VV4o0-- --VDMkrWlIhlaqUk0wonncUMKKcwgooPNNO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlj2A60ACgkQAFE/EOCp 5OetihAAsig8BO2dQPZ1VpvXPYcocySZESnGIqPofGSTLi9DG/XpV+UbsuPBRMiY ZYHPejRZRWPCs3bX82ljrbB9KympVueXCTdbVO6yGDul54kYUanfrvbvTUKNsybq AuUS8x/mopjQ3PBP3z7tPg41ULBOtKXEbP52vfqfRXr1qYlshFkYdyQNScmGLOBX swN8THrr1x8Nc4YjHSr/9njpWL+29PKOWABVkw6OH6ZTm9QA890vqz/BhZHU8inj YVWOlq14uQPU6VVPs3tjHAfT3ufjpQGSlYNNkxhawKy8/iBTjshfEjzMNgO9+Rmf KQ9YTzfZqCwKU1QMTnc6tpSrYVU69xeaFXcs2JothH8cKagLCh1t3nf3uJ0FWD00 FcgL6LcTXZWoKs/YJJeOC4wmCysQDQU43BLgJUihSUEpTWA3uUWnHKR6pbIQ44H2 BhyrkTjkiK6wbP4VhiOPCXhj/vLBdhIjfTSTQ2omBSNwRDnwl5oTHgcTV9AZ4vVI 0rCROQusC8IthcwhMzOPC7OXr/GWGDv9NCWYacpS4sfZ+Qfm1kJOQcKA5fSKvOL1 Bykmm8NtXB5jEFm5yLqqgS/mQ0Meuz9H6EeDN4cv9kebABl89oE6EO9SYB95NcUr 4xueeF95kYJsTJx9kw7a3pll8m/1+MBs3zHjuT/7Z07MeFwddUE= =qUYX -----END PGP SIGNATURE----- --VDMkrWlIhlaqUk0wonncUMKKcwgooPNNO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a91d4083-929d-295e-4daa-cc223ec5dbe4>