Re: apache core dump signal 11 after portupgrade from 1.3.37 to 1.3.39, php5-5.2.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 1 Oct 2007, David Gessel wrote:

I posted to freebsd-stable@xxxxxxxxxxx, and followed the suggestion to disable modules, this seems a more apropos group to request support from for the following:

The details below are probably overkill. I've fixed the OpenSSL residual false package issue which has reduced warnings, and disabling mod.php in httpd.conf got the server working but with the following oddities:

Enabling mod.php (5.2.4) still causes Apache to fail on startup as below.
Disabling mod.php gets Apache running, but it doesn't, only since the update, read the virtual hosts section of httpd.conf. It is clearly reading the config file and configtest says "Syntax OK."

I did a portupgrade -ra to 1.3.39 and after a reboot found apache not running. I've poked around and haven't found much that's useful - signal 11 being sometimes associated with memory errors (a memory test comes up fine, though it is unlikely that an update would crack the RAM). Otherwise few hints. Any suggestions would be much appreciated.

The key details are - pkg_version -v -L = showed (among other updates simultaneously applied as listed below) that: apache+mod_ssl-1.3.37+2.8.28 < needs updating (port has 1.3.39+2.8.30)

After rebooting I get in /var/log/messages only
kernel: pid 1127 (httpd), uid 0: exited on signal 11 (core dumped)
and in /var/log/httpd-error.log only
[info] mod_unique_id: using ip addr xxx.xxx.xxx.xxx [correct localhost address] every time I "apachectl start" (and after setting apache.config log level to "debug")


Hi David,
I've seen this happen on FreeBSD systems when /usr/local/etc/php/extensions.ini is out of order. You can test this with 'php -v' if you have the command-line php interpreter installed. Running 'php -v' should also segfault if php extensions are the fault.

If thats the case, then commenting out each extension in /usr/local/etc/php/extensions.ini one by one while running 'php -v' will help you find the failing php extension. Once you find it, move that extension to the end of extensions.ini and try restarting apache.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux