Apache 22 - FreeBSD 8.0 - (httpd), uid 80: exited on signal 11
in [Ports]
|
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: "Helmut Schneider" on 3 May 2010 08:45 Matthew Seaman wrote: > 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. I guess the problem is with perl and not with php - otherwise you're right. _______________________________________________ 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: Christer Solskogen on 3 May 2010 08:54 On Sun, May 2, 2010 at 12:18 AM, Hans F. Nordhaug <Hans.F.Nordhaug(a)himolde.no> wrote: > Any hints? > I had the same thing, and my problem was gallery2 which used mysqli to contact my mysql-server. change $storeConfig['type'] = 'mysqli'; to $storeConfig['type'] = 'mysql'; I also had problems with png and gallery2. So if you use gallery2, browse thru your pictures while you follow /var/log/messages. -- chs, _______________________________________________ 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 9 May 2010 12:23 * Helmut Schneider <jumper99(a)gmx.de> [2010-05-03]: > 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? Thx to you and everybody else who have answered so far: - I have (now) checked RAM with memtest for several days. No issues. - Yes, I have already checked my hard drive using fsck, and the few problems that were reported was fixed a week ago. - My websites are using PHP, not Perl. I have checked/fixed the extension loading order using fixphpextorder.sh as posted on http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround It didn't help. I don't have that many extensions - the order is: root(a)myserver[~](18:18:19)718:>cat /usr/local/etc/php/extensions.ini extension=pgsql.so extension=iconv.so extension=hash.so extension=dom.so extension=gd.so extension=pdo.so extension=zlib.so extension=mbstring.so extension=pdo_mysql.so extension=openssl.so extension=session.so extension=simplexml.so extension=gettext.so extension=sqlite.so extension=mysql.so extension=xml.so Any more hints? Regards, Hans PS! There are still no core files generated. I have ":coredumpsize=unlimited" in /etc/login.conf, but maybe something else is surpressing the core file generation.) PS! The Perl exit problem is still present, but that was related to amavisd. _______________________________________________ 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 16 May 2010 21:30 * Hans F. Nordhaug <Hans.F.Nordhaug(a)hiMolde.no> [2010-05-09]: > * Helmut Schneider <jumper99(a)gmx.de> [2010-05-03]: > > 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? > > Thx to you and everybody else who have answered so far: > > - I have (now) checked RAM with memtest for several days. No issues. > - Yes, I have already checked my hard drive using fsck, and the few > problems that were reported was fixed a week ago. > - My websites are using PHP, not Perl. I have checked/fixed the > extension loading order using fixphpextorder.sh as posted on > http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround > It didn't help. I don't have that many extensions - the order is: [cut] OK, this problem is just not going away. Doing a reload of a page, the segmentation fault will appear from 20-50% of the time. It's getting more and more clear that this is a PHP bug in some way. I have compiled PHP and Apache with debugging, disabled the Suhosin patch and only suing two extensions: php5-xml and php5-session. All ports are up-to-date. This is still on FreeBSD 8 with PHP 5.3.2. The backtrace is: gdb /usr/local/sbin/httpd (gdb) run -X Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 28501140 (LWP 100131)] 0x28ad2030 in zend_mm_check_ptr (heap=0x28e4f900, ptr=0x29994d0c, silent=1, __zend_filename=0x28c53d6b "Zend/zend_language_scanner.l", __zend_lineno=685, __zend_orig_filename=0x0, __zend_orig_lineno=0) at /usr/ports/lang/php5/work/php-5.3.2/Zend/zend_alloc.c:1347 1347 if (p->info._size != ZEND_MM_NEXT_BLOCK(p)->info._prev) { (gdb) bt #0 0x28ad2030 in zend_mm_check_ptr (heap=0x28e4f900, ptr=0x29994d0c, silent=1, __zend_filename=0x28c53d6b "Zend/zend_language_scanner.l", __zend_lineno=685, __zend_orig_filename=0x0, __zend_orig_lineno=0) at /usr/ports/lang/php5/work/php-5.3.2/Zend/zend_alloc.c:1347 #1 0x28ad366c in _zend_mm_free_int (heap=0x28e4f900, p=0x29994d0c, __zend_filename=0x28c53d6b "Zend/zend_language_scanner.l", __zend_lineno=685, __zend_orig_filename=0x0, __zend_orig_lineno=0) at /usr/ports/lang/php5/work/php-5.3.2/Zend/zend_alloc.c:1983 #2 0x28ad465c in _efree (ptr=0x29994d0c, __zend_filename=0x28c53d6b "Zend/zend_language_scanner.l", __zend_lineno=685, __zend_orig_filename=0x0, __zend_orig_lineno=0) at /usr/ports/lang/php5/work/php-5.3.2/Zend/zend_alloc.c:2351 #3 0x28abb74c in zend_multibyte_read_script ( buf=0x284ff000 "<?php\n\n// ", '-' <repeats 75 times>, "\n//\n// PIVOTX - LICENSE:\n//\n// This file is part of PivotX. PivotX and all its parts are licensed under\n// the GPL "..., n=658) at zend_language_scanner.l:685 #4 0x28aba690 in open_file_for_scanning (file_handle=0xbfbfe934) at zend_language_scanner.l:263 #5 0x28aba8a8 in compile_file (file_handle=0xbfbfe934, type=8) at zend_language_scanner.l:331 #6 0x28af6fe7 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /usr/ports/lang/php5/work/php-5.3.2/Zend/zend.c:1186 #7 0x28a8a9fd in php_execute_script (primary_file=0xbfbfe934) at /usr/ports/lang/php5/work/php-5.3.2/main/main.c:2260 #8 0x28bc3173 in php_handler (r=0x290db058) at /usr/ports/lang/php5/work/php-5.3.2/sapi/apache2handler/sapi_apache2.c:655 And so on ... I also have the full backtrace for those interested. Regards, Hans PS! Should I file PR? _______________________________________________ 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 21 May 2010 07:51
* Hans F. Nordhaug <Hans.F.Nordhaug(a)hiMolde.no> [2010-05-17]: > OK, this problem is just not going away. Doing a reload of a page, the > segmentation fault will appear from 20-50% of the time. It's getting > more and more clear that this is a PHP bug in some way. I have > compiled PHP and Apache with debugging, disabled the Suhosin patch and > only suing two extensions: php5-xml and php5-session. All ports are > up-to-date. This is still on FreeBSD 8 with PHP 5.3.2. The text above is strongly reduced - see the complete message at http://lists.freebsd.org/pipermail/freebsd-ports/2010-May/061222.html The problem is "solved". Disabling the zend multibyte support removed the sporadic segmentation faults. 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" |