Prev: GSoC: Libpkg, package tools
Next: Xorg does not start after upgrade from 7.4 to 7.5 (Undefined symbol"xf86LoaderReqSymLists" in intel_drv.so)
From: "Hans F. Nordhaug" on 1 May 2010 18:18 Hi! I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a lot of "(httpd), uid 80: exited on signal 11" in my logs. I have similar problems with amavisd - see http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 I'm have updated and recompiled all ports. The logs /var/log/messages and the httpd error log both just report "exited on signal 11" or "Segmentation fault (11)" Any hints? Regards, Hans PS! I have run fsck and ut fixed som problems, but I still get "exited on signal 11". _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Helmut Schneider" on 2 May 2010 07:50 Hans F. Nordhaug wrote: > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a lot > of "(httpd), uid 80: exited on signal 11" in my logs. I have similar > problems with amavisd - see > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > I'm have updated and recompiled all ports. The logs /var/log/messages > and the httpd error log both just report > "exited on signal 11" or "Segmentation fault (11)" > > Any hints? Find the .core file, start gdb with the core file, type "bt", post the output. Helmut -- No Swen today, my love has gone away My mailbox stands for lorn, a symbol of the dawn _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Hans F. Nordhaug" on 2 May 2010 11:02 * Helmut Schneider <jumper99(a)gmx.de> [2010-05-02]: > Hans F. Nordhaug wrote: > > > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a lot > > of "(httpd), uid 80: exited on signal 11" in my logs. I have similar > > problems with amavisd - see > > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > > I'm have updated and recompiled all ports. The logs /var/log/messages > > and the httpd error log both just report > > "exited on signal 11" or "Segmentation fault (11)" > > > > Any hints? > > Find the .core file, start gdb with the core file, type "bt", post the > output. Sorry, I should have mentioned that I can't find any core files. "find / -name '*.core'" returns nothing. Hans _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: "Helmut Schneider" on 3 May 2010 06:49 Hans F. Nordhaug wrote: > * Helmut Schneider <jumper99(a)gmx.de> [2010-05-02]: > > Hans F. Nordhaug wrote: > > > > > I recently upgrade to FreeBSD 8.0 (from 7.2) and suddenly I get a > > > lot of "(httpd), uid 80: exited on signal 11" in my logs. I have > > > similar problems with amavisd - see > > > > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-April/thread.html#215757 > > > I'm have updated and recompiled all ports. The logs > > > /var/log/messages and the httpd error log both just report > > > "exited on signal 11" or "Segmentation fault (11)" > > > > > > Any hints? > > > > Find the .core file, start gdb with the core file, type "bt", post > > the output. > > Sorry, I should have mentioned that I can't find any core files. > "find / -name '*.core'" returns nothing. I guess one can assume that - you already checked RAM with memtest or so. - you already check your hard drive (you mentiened you fsck'ed your hard drive and found errors that wer corrected) - you are running one or more perl apps within apache? _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Matthew Seaman on 3 May 2010 08:34
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/05/2010 11:49:35, Helmut Schneider wrote: > I guess one can assume that > > - you already checked RAM with memtest or so. > - you already check your hard drive (you mentiened you fsck'ed your > hard drive and found errors that wer corrected) > - you are running one or more perl apps within apache? - - You've checked the order of the loadable PHP modules in /usr/local/etc/php/extensions.ini ? That's been the number one cause of apache crashes mentioned on this list in the last several years. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvewtkACgkQ8Mjk52CukIxP+wCfefnotupBUQKWVgW9rHdQifKF UI4AnjygGeoTDFd6sNVHTEqP7WMAsK7d =xhvu -----END PGP SIGNATURE----- _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |