Date: Sun, 14 Sep 2008 13:50:48 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: server is crashing constantly Message-ID: <gaits2$kh3$2@ger.gmane.org> In-Reply-To: <152402.4340.qm@web45308.mail.sp1.yahoo.com> References: <152402.4340.qm@web45308.mail.sp1.yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Jonathan Horne wrote:
> I have a new web server for a moderately high traffic website that i have recently deployed for a friend. it has apache22, php5, and mysql50 on it (latest from ports). this server is crashing 2-3 times a day, and thus far i have no idea where to start troubleshooting this.
>
> That is what im getting in the /var/log/messages.
>
> Sep 13 20:09:25 rps savecore: reboot after panic: page fault
> Sep 13 20:09:25 rps savecore: writing core to vmcore.0
>
>
> Here is the uname:
> FreeBSD rps.rangerpowersports.com 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #0: Fri Sep 5 01:58:09 CDT 2008 root@rangerpowersports:/usr/obj/usr/src/sys/RPS i386
>
> Any ideas or recommendations about where to start looking to track this down would really be appreciated.
Enable dumpdev and dumpdir in rc.conf, here's the manual excerpt:
dumpdev (str) Indicates the device (usually a swap partition) to
which a crash dump should be written in the event of a
system
crash. If the value of this variable is ``AUTO'', the
first
suitable swap device listed in /etc/fstab will be used as
dump device. Otherwise, the value of this variable is
passed
as the argument to dumpon(8). To disable crash dumps, set
this variable to ``NO''.
dumpdir (str) When the system reboots after a crash and a crash
dump
is found on the device specified by the dumpdev variable,
savecore(8) will save that crash dump and a copy of the
ker-
nel to the directory specified by the dumpdir variable.
The
default value is /var/crash. Set to ``NO'' to not run
savecore(8) at boot time when dumpdir is set.
Then, when it crashes, inspect the dump. See here:
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
If you suspect it's a FreeBSD problem and not a hardware problem, you'll
need to send debugging data similar to that in the example in handbook.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjM+pgACgkQldnAQVacBchpwwCeMz9Dx0b8H2G8yo4sDpFFPie+
Gd4AoObQWu29qJIge8y2hWQZUKkB4Jvb
=r/MD
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gaits2$kh3$2>