My apache error_log is filled with a reoccurrence of the following several times daily. Can anyone steer me in the right direction to address this. mod_watch, OpenSSL, and mod_ssl seem updated. Here's what I am seeing:

[Thu Sep 03 03:18:37 2009] [notice] Apache/2.2.8 (Unix) DAV/2 PHP/5.1.6 mod_ssl/2.2.8 OpenSSL/0.9.8e-fips-rhel5 mod_watch/4.3 configured -- resuming normal operations
[Thu Sep 03 03:18:40 2009] [notice] child pid 6823 exit signal Segmentation fault (11)
[Thu Sep 03 03:19:04 2009] [notice] child pid 6837 exit signal Segmentation fault (11)
[Thu Sep 03 03:19:26 2009] [notice] child pid 6858 exit signal Segmentation fault (11)
[Thu Sep 03 03:20:34 2009] [notice] child pid 6822 exit signal Segmentation fault (11)
[Thu Sep 03 03:20:35 2009] [notice] child pid 8551 exit signal Segmentation fault (11)
[Thu Sep 03 03:20:38 2009] [notice] child pid 6839 exit signal Segmentation fault (11)
[Thu Sep 03 03:23:55 2009] [notice] child pid 8543 exit signal Segmentation fault (11)

Any help would be greatly appreciated. Iworx 3.0.4

When did this start doing this?

I'm not sure, but I've noticed it has been cropping up a lot more recently. Do you think one of the modules is causing it?

Everything I can find points to php(sometimes python) being the culprit. Have you done any updates to Apache or PHP recently?

I haven't. I'll go and update both modules and let you know how it goes.

hello, any progress on this one? i have the same [notice]:

Apache/2.2.8 (Unix) DAV/2 PHP/5.1.6 mod_ssl/2.2.8 OpenSSL/0.9.8e-fips-rhel5 mod_watch/4.3 configured -- resuming normal operations

and this is producing a Segmentation Fault (11).

sure would like to know what is going on with this one.

update your php.ini's memory_limit its prolly at 8MB

I run a fairly stout Cacti instance so mine is super high; double whatever you have (Probably 16MB)

[knightmare@blitzcore ~]$ grep memory_limit /etc/php.ini
memory_limit = 106M ; Maximum amount of memory a script may consume
[knightmare@blitzcore ~]$


Default
[root@TheName ~]# grep memory_limit /etc/php.ini
memory_limit = 16M ; Maximum amount of memory a script may consume
[root@TheName ~]#

actually, it is set to 32MB. has been for some months now and we just started getting the seg faults showing up recently. i got this server to generate some core files on the seg faults and used gdb to do a backtrace. the only thing that stood out was that mod_watch (used for updating statistics and fancy graphs, etc...) seemed to be the exit point before producing the seg fault. i checked for an updated version of mod_watch, but ours is current.

Core was generated by `/usr/sbin/httpd -k start'.
Program terminated with signal 11, Segmentation fault.
[New process 8231]
#0 0x0000000000423add in ap_strcasecmp_match ()
(gdb) bt full
#0 0x0000000000423add in ap_strcasecmp_match ()
No symbol table info available.
#1 0x00002b7130655cda in watchLog (r=0x0) at mod_watch.c:557
key = <value optimized out>
data = (struct shEntry *) 0x109f2d30
#2 0x0000000000426cfa in ap_run_log_transaction ()
No symbol table info available.
#3 0x0000000000440fc7 in ap_process_request ()
No symbol table info available.
#4 0x000000000043e44c in ap_process_http_connection ()
No symbol table info available.
#5 0x000000000043a802 in ap_run_process_connection ()
No symbol table info available.
#6 0x0000000000444d11 in child_main ()
No symbol table info available.
#7 0x0000000000444f84 in make_child ()
No symbol table info available.
#8 0x0000000000445027 in startup_children ()
No symbol table info available.
#9 0x0000000000445aef in ap_mpm_run ()
No symbol table info available.
#10 0x0000000000421838 in main ()
No symbol table info available.