apache segfault (11)
Hi :) I'm having a very big problem with latest apache from ports under 5.2.1. First let me say that all my ports are up-to-date. Now, I use Apache+php+mysql with Horde for webmail. Since a couple of days, the webmail is almost impossible to use, login in takes forever and usually ends with an error page saying couldn't get http://www.domain.com/horde/blablabla.php In the Apache logs (debug), I only get this: [notice] child pid 68233 exit signal Segmentation fault (11) I tried to look everywhere but couldn't find a answer for this problem. The top command issue a regular line, no strange processes eating the CPU... Any idea ? Thanks in advance and let me know if you need more information. apache+mod_ssl-1.3.31+2.8.18_3 php4-4.3.7_1 Regards, Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: apache segfault (11)
Selon BSDBoy [EMAIL PROTECTED]: Did you use any nonstandard optimizations while compiling apache? Also let Nope, nothing. us know if apache is running in chroot environment. Could u also paste about No, it is a default install, no chroot. 30 lines from the last of the apache log? Also did you portupgrade -a after u cvsuped the port tree? uname -a please. Yes, of course I portugraded :) uname -a: FreeBSD mcp.lphp.local 5.2.1-RELEASE-p8 FreeBSD 5.2.1-RELEASE-p8 #0: Tue Jun 8 11:30:17 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MCP i386 Apache logs: [Wed Jun 9 16:02:26 2004] [info] mod_unique_id: using ip addr 192.168.0.1 Processing config directory: /usr/local/etc/horde Processing config file: /usr/local/etc/horde/httpd.conf.horde Processing config file: /usr/local/etc/horde/httpd.conf.imp Processing config file: /usr/local/etc/horde/httpd.conf.kronolith Processing config file: /usr/local/etc/horde/httpd.conf.mnemo Processing config file: /usr/local/etc/horde/httpd.conf.nag Processing config file: /usr/local/etc/horde/httpd.conf.turba [Wed Jun 9 16:02:27 2004] [info] (2)No such file or directory: make_sock: for port 443, setsockopt: (SO_ACCEPTFILTER) [Wed Jun 9 16:02:27 2004] [info] (2)No such file or directory: make_sock: for port 80, setsockopt: (SO_ACCEPTFILTER) [Wed Jun 9 16:02:27 2004] [info] mod_unique_id: using ip addr 192.168.0.1 [Wed Jun 9 16:02:28 2004] [notice] Apache/1.3.31 (Unix) PHP/4.3.7 mod_ssl/2.8.18 OpenSSL/0.9.7c-p1 configured -- resuming normal operations [Wed Jun 9 16:02:28 2004] [info] Server built: Jun 9 2004 10:41:36 [Wed Jun 9 16:02:28 2004] [notice] Accept mutex: flock (Default: flock) [Wed Jun 9 16:07:58 2004] [error] [client 82.120.59.186] request failed: URI too long [Wed Jun 9 16:12:07 2004] [notice] child pid 68233 exit signal Segmentation fault (11) [Wed Jun 9 16:12:56 2004] [error] [client 192.168.0.2] File does not exist: /usr/local/www/horde/favicon.ico [Wed Jun 9 16:34:12 2004] [notice] child pid 68633 exit signal Segmentation fault (11) [Wed Jun 9 16:35:12 2004] [notice] child pid 68158 exit signal Segmentation fault (11) Thanks for helping. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: apache segfault (11)
On Wednesday 09 June 2004 21:32, BSDBoy wrote: Looks rather strange to me because I can't find anything offending which may cause the child processes to segfault. Could u make deinstall apache+plugins, make clean, cvsup the port tree and remake it? Did it help??? That was the first thing I did actually... I even rebuilt the world/kernel. No change whatsoever :( I'm really concern about this problem. Basically what it does is: - I go on horde/imp login page - I enter user/pass then click on login - the browser does not move for about 30 seconds (until the apache segfault) - I get the cannot load blablabla.php error - if I then try again to login, sometimes it works right away, sometimes, I get the same problem. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
