Portsnap causes system to reboot
Whenever I run portsnap fetch update (edit: it also happens for a simple portsnap fetch), my system reboots unexpectedly. Here's the output: # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap2.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Sep 24 00:04:04 EEST 2008 to Thu Oct 9 10:28:42 EEST 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... done. Fetching 602 patches.102030405060708090100110120130140150160170180190200210220230240250260270280290300310320330340350360370380390400410420430440450460470480490500510520530540550560570580590600. done. Applying patches... Read from remote host X: Connection reset by peer Connection to X closed. And then I can log-in again a few minutes later, and the uptime has gone down to a few seconds, so I know it rebooted. Any ideas why this is happening? Some background info: $ uname -mrs FreeBSD 7.0-RELEASE-p5 i386 And: $ cat /etc/make.conf # added by use.perl 2008-07-16 15:32:01 PERL_VER=5.8.8 PERL_VERSION=5.8.8 CFLAGS=-O2 -pipe COPTFLAGS=-O2 -pipe CPUTYPE=athlon-xp NO_PROFILE=true Since this started happening, I have still successfully updated ports by csup'ing the ports tree. I can also still rebuild the world and kernel without issue. This is a remote box, and I don't use X with it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portsnap causes system to reboot
On Thu, Oct 09, 2008 at 07:38:09PM +0300, Walter Venable wrote: Whenever I run portsnap fetch update (edit: it also happens for a simple portsnap fetch), my system reboots unexpectedly. Here's the output: # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap2.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Sep 24 00:04:04 EEST 2008 to Thu Oct 9 10:28:42 EEST 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... done. Fetching 602 patches.102030405060708090100110120130140150160170180190200210220230240250260270280290300310320330340350360370380390400410420430440450460470480490500510520530540550560570580590600. done. Applying patches... Read from remote host X: Connection reset by peer Connection to X closed. And then I can log-in again a few minutes later, and the uptime has gone down to a few seconds, so I know it rebooted. Any ideas why this is happening? Nope, not without kernel panic information. Does this machine have serial console? Are kernel panic dumps being put into /var/crash? Is the machine even configured for it (see dumpdev, dumpdir, and savecore in rc.conf). Some background info: $ uname -mrs FreeBSD 7.0-RELEASE-p5 i386 It would be useful if you could provide uname -a please, if you're concerned about the hostname, just XXX it out. Seeing the kernel build date is useful. CFLAGS=-O2 -pipe COPTFLAGS=-O2 -pipe CPUTYPE=athlon-xp Please don't do this. Use ?= for this, not =. If you think I'm trolling, please read /usr/share/examples/etc/make.conf. Since this started happening, I have still successfully updated ports by csup'ing the ports tree. I can also still rebuild the world and kernel without issue. This is a remote box, and I don't use X with it. It almost sounds like a filesystem problem. You might consider booting into single-user and running fsck -y. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portsnap causes system to reboot
I found this: $ cat /var/crash/ ..minfreboundsçinfo.0ç vmcore.0zinfo.vmcore.1zinfo.vmcore.2zinfo.vmcore.3zinfo.vmcore.4zinfo.vmcore.5zinfo.vmcore.6zinfo.7vmcore.7zÀ Any idea what that means? Yes, I'm tired, and I did cat on a directory. I found this in vmcore.7: 118Checking for core dump on /dev/ad4s1b... 118savecore: reboot after panic: ffs_clusteralloc: map mismatch 118Oct 9 11:16:26 freebsd savecore: reboot after panic: ffs_clusteralloc: map mismatch 118savecore: writing core to vmcore.6 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portsnap causes system to reboot
Jeremy Chadwick wrote: On Thu, Oct 09, 2008 at 07:38:09PM +0300, Walter Venable wrote: Whenever I run portsnap fetch update (edit: it also happens for a simple portsnap fetch), my system reboots unexpectedly. Here's the output: # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap2.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Sep 24 00:04:04 EEST 2008 to Thu Oct 9 10:28:42 EEST 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... done. Fetching 602 patches.102030405060708090100110120130140150160170180190200210220230240250260270280290300310320330340350360370380390400410420430440450460470480490500510520530540550560570580590600. done. Applying patches... Read from remote host X: Connection reset by peer Connection to X closed. And then I can log-in again a few minutes later, and the uptime has gone down to a few seconds, so I know it rebooted. Any ideas why this is happening? Nope, not without kernel panic information. Does this machine have serial console? Are kernel panic dumps being put into /var/crash? Is the machine even configured for it (see dumpdev, dumpdir, and savecore in rc.conf). I found this: $ cat /var/crash/ ..minfreboundsçinfo.0ç vmcore.0zinfo.vmcore.1zinfo.vmcore.2zinfo.vmcore.3zinfo.vmcore.4zinfo.vmcore.5zinfo.vmcore.6zinfo.7vmcore.7zÀ Any idea what that means? Some background info: $ uname -mrs FreeBSD 7.0-RELEASE-p5 i386 It would be useful if you could provide uname -a please, if you're concerned about the hostname, just XXX it out. Seeing the kernel build date is useful. $ uname -a FreeBSD freebsd 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Thu Oct 9 02:30:36 EEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ECORAZENI i386 CFLAGS=-O2 -pipe COPTFLAGS=-O2 -pipe CPUTYPE=athlon-xp Please don't do this. Use ?= for this, not =. If you think I'm trolling, please read /usr/share/examples/etc/make.conf. It's recompiling with an empty make.conf now. Since this started happening, I have still successfully updated ports by csup'ing the ports tree. I can also still rebuild the world and kernel without issue. This is a remote box, and I don't use X with it. It almost sounds like a filesystem problem. You might consider booting into single-user and running fsck -y. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portsnap causes system to reboot
On Fri, Oct 10, 2008 at 12:54:38AM +0300, Walter Venable wrote: I found this: $ cat /var/crash/ ..minfreboundsçinfo.0ç vmcore.0zinfo.vmcore.1zinfo.vmcore.2zinfo.vmcore.3zinfo.vmcore.4zinfo.vmcore.5zinfo.vmcore.6zinfo.7vmcore.7zÀ Any idea what that means? Yes, I'm tired, and I did cat on a directory. I found this in vmcore.7: 118Checking for core dump on /dev/ad4s1b... 118savecore: reboot after panic: ffs_clusteralloc: map mismatch 118Oct 9 11:16:26 freebsd savecore: reboot after panic: ffs_clusteralloc: map mismatch 118savecore: writing core to vmcore.6 Please reboot your machine into single-user mode, and run fsck -y. I'm betting there's some filesystem corruption. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
