[arch-general] 11/23 update caused httpd to coredump?

David C. Rankin drankinatty at suddenlinkmail.com
Tue Dec 3 01:26:33 UTC 2019


On 11/27/2019 06:45 PM, David C. Rankin wrote:
> On 11/24/2019 03:57 PM, David C. Rankin wrote:
>> Dev,
>>
>>   This is a strange one. After updates on 11/23, httpd began segfaulting --
>> repeatedly:
>>
>>> l /var/log/httpd/error_log*
>> -rw-r--r-- 1 root root 24306171 Nov 24 14:48 /var/log/httpd/error_log
>> -rw-r--r-- 1 root root      625 Nov 24 00:00 /var/log/httpd/error_log.1
>> -rw-r--r-- 1 root root     1742 Nov 21 13:19 /var/log/httpd/error_log.2
>> -rw-r--r-- 1 root root      504 Nov 10 00:00 /var/log/httpd/error_log.3
>> -rw-r--r-- 1 root root     1754 Nov  3 00:00 /var/log/httpd/error_log.4
>>
>> I have a second server that confirms this exact same behavior:
>>
>>> l /var/log/httpd/error_log*
>> -rw-r--r-- 1 root root 25049142 Nov 24 14:48 /var/log/httpd/error_log
>> -rw-r--r-- 1 root root     1137 Nov 24 00:00 /var/log/httpd/error_log.1
>> -rw-r--r-- 1 root root     1752 Nov 17 00:01 /var/log/httpd/error_log.2
>> -rw-r--r-- 1 root root      504 Nov 10 00:00 /var/log/httpd/error_log.3
>> -rw-r--r-- 1 root root     1754 Nov  3 00:01 /var/log/httpd/error_log.4
>>
>>
>> The log file size jumped from 625 bytes to 24306171 bytes (1137->25049142 on
>> the other server) in just a matter of hours. The old log contains, in its
>> entirety:
>>
> <snip>
> 
> Just a follow-up, all is back to normal since the 11/24 update:
> 
> [Sun Nov 24 14:48:40.734427 2019] [core:notice] [pid 898] AH00051: child pid
> 1128862 exit signal Segmentation fault (11), possible coredump in /etc/httpd
> [Sun Nov 24 14:48:40.734535 2019] [core:notice] [pid 898] AH00051: child pid
> 1128863 exit signal Segmentation fault (11), possible coredump in /etc/httpd
> [Sun Nov 24 14:48:41.876097 2019] [mpm_prefork:notice] [pid 898] AH00170:
<snip>
> [Mon Nov 25 12:12:22.566164 2019] [core:notice] [pid 677] AH00094: Command
> line: '/usr/bin/httpd -D FOREGROUND'
> 
> No clue what happened with the 11/23 updates that originally caused the issue.
> Gremlins...
> 

Damn,

  Whatever it is came back after updates on 12/1

-rw-r--r--  1 root root 71509927 Dec  2 19:22 error_log
-rw-r--r--  1 root root 24306916 Dec  1 00:00 error_log.1
-rw-r--r--  1 root root      625 Nov 24 00:00 error_log.2
-rw-r--r--  1 root root     1742 Nov 21 13:19 error_log.3
-rw-r--r--  1 root root      504 Nov 10 00:00 error_log.4

  Same error both server and server is down until reloaded, e.g.

[Mon Dec 02 19:22:36.265040 2019] [core:notice] [pid 677] AH00051: child pid
3290821 exit signal Segmentation fault (11), possible coredump in /etc/httpd
[Mon Dec 02 19:22:36.265147 2019] [core:notice] [pid 677] AH00051: child pid
3290823 exit signal Segmentation fault (11), possible coredump in /etc/httpd
[Mon Dec 02 19:22:36.265255 2019] [core:notice] [pid 677] AH00051: child pid
3290824 exit signal Segmentation fault (11), possible coredump in /etc/httpd

  Any idea on on what is triggering this?


-- 
David C. Rankin, J.D.,P.E.


More information about the arch-general mailing list