## February 4, 2003

### Hiccup

Wow! That was weird. My web site was unavailable for about an hour this afternoon, till I noticed something amiss and restarted it.

From the logs, it looks like the trouble started at 16:49. The error_log shows

[Tue Feb 04 16:49:02 2003] [notice] child pid 12411 exit signal Bus error (10) [Tue Feb 04 16:49:03 2003] [notice] child pid 12665 exit signal Bus error (10)

followed by a slew of such errors, up to 17:51, when I tried an apachectl restart. That didn’t work, and the error log recorded

[Tue Feb 04 17:51:25 2003] [notice] SIGHUP received. Attempting to restart [Tue Feb 04 17:51:27 2003] [notice] seg fault or similar nasty error detected in the parent process

Did an apachectl start, and it finally started up:

[Tue Feb 04 17:52:16 2003] [notice] Digest: generating secret for digest authentication ... [Tue Feb 04 17:52:16 2003] [notice] Digest: done [Tue Feb 04 17:52:17 2003] [warn] pid file /usr/local/apache2/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? [Tue Feb 04 17:52:17 2003] [notice] Apache/2.0.44 (Unix) DAV/2 PHP/4.3.0 configured -- resuming normal operations

In all these years, I’ve never had Apache die on me like that. Anyone know why it would suddenly up and die one sunny Tuesday afternoon?

Posted by distler at February 4, 2003 6:26 PM

TrackBack URL for this Entry:   http://golem.ph.utexas.edu/cgi-bin/MT-3.0/dxy-tb.fcgi/91

### Re: Hiccup

See http://dan.drydog.com/apache2php.html. Evidently, there is a problem when you have apache + PHP 4.5 + PCRE (regular expresions enabled) that causes this. I started getting it, too. Very annoying.

Posted by: Glen Campbell on April 7, 2004 1:30 PM | Permalink | Reply to this

### Re: Hiccup

I’ve had this problem ever since upgrading to Apache 2.0.49 and PHP 4.3.6 (from apache 2.0.48 and php 4.3.4) - curious if anyone has a solution other then downgrading.
-mark

Posted by: Mark on May 9, 2004 12:40 PM | Permalink | Reply to this

### Re: Hiccup

I’m having this issue as well. Weird thing is that, if it’s a standard HTML page, it loads in the browser before the error hits. If the page is PHP, though, the error hits and the page never loads. Very odd. Works fine in 2.0.48 but 2.0.49 just outright refuses. (PHP is 4.3.7 so I don’t think it’s PCRE. Might be, though, I guess.)

Posted by: Stu Hicks on June 22, 2004 9:40 PM | Permalink | Reply to this

Post a New Comment