[phpa] Re: page not found errors....
- From: "Nick Lindridge" <nick@xxxxxxxxxxxxxxxxxxxxx>
- To: phpa@xxxxxxxxxxxxx
- Date: Wed, 6 Feb 2002 22:31:27 -0000 (GMT)
I'm working back through posts here.
The *very* interesting thing here is that you said the 'address may need to
change' errors happen a while after starting.
Is this definitely correct? For some reason there's no timestamp on the
messages.
If this happens it will spell disaster for phpa, *but*, it should only
happen when phpa starts up for the first time. And in fact, because the
cache generally won't exist at startup because it deletes on shutdown, this
message shouldn't occur even then.
If PHPA detects that the address may need to change for the cache, it
simply destroys and recreates it. This is not the right thing to do if it's
already started up, however I can't at the moment see why this would/could
happen, and so is not a case that phpa handles.
So, I need to know if people are seeing the message about the address
needing to change some time after startup, and I can go from there.
Nick
>
> Hi,
>
> Ok, before I came back to this issue I wanted to make absolutely sure
> it was phpa related...
>
> So I tested a day without phpa and than with phpa etc...
>
> After starting phpa everything works perfectly, you can notice a big
> speed increase, but after a while it starts giving "page not found
> errors.... Sometimes this takes a few hours before it starts, sometimes
> a whole day but at some point it always happens...
>
> Only way to stop this is to restart the web server....
>
> In the error log I get these entries at that point:
>
> [ [warn] shm - address may need to change
> [ [warn] shm - Recreating cache
> [ [warn] shm - Unable to get shm shm - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 10:30:48 2002] [notice] child pid 32252 exit signal
> Segmentation fault (11)
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 10:30:54 2002] [notice] child pid 32203 exit signal
> Segmentation fault (11)
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 10:30:55 2002] [notice] child pid 32202 exit signal
> Segmentation fault (11)
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 10:30:56 2002] [notice] child pid 32246 exit signal
> Segmentation fault (11)
> [Wed Feb 6 10:30:56 2002] [notice] child pid 32185 exit signal
> Segmentation fault (11)
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
>
> It's full of it......
>
> And when stopping and starting the web server:
>
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 12:32:50 2002] [notice] child pid 9817 exit signal
> Segmentation fault (11)
> [Wed Feb 6 12:32:50 2002] [notice] child pid 9815 exit signal
> Segmentation fault (11)
> [ [warn] shm - Unable to get shm header - Identifier removed
> [ [warn] shm cache disabled
> [Wed Feb 6 12:32:51 2002] [notice] child pid 9760 exit signal
> Segmentation fault (11)
> [ [warn] shm - Failed to stat the shm - Invalid argument
> [Wed Feb 6 12:32:54 2002] [notice] caught SIGTERM, shutting down
> [Wed Feb 6 12:33:05 2002] [notice] Apache/1.3.20 (Unix) mod_ssl/2.8.4
> OpenSSL/0.9.6b PHP/4.1.1 mod_auth_pam_external/0.1 FrontPage/4.0.4.3
> mod_perl/1.25 configured -- resuming normal operations
> [Wed Feb 6 12:33:05 2002] [notice] suEXEC mechanism enabled (wrapper:
> /usr/sbin/suexec)
> [Wed Feb 6 12:35:07 2002] [warn] child process 9911 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9913 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9918 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9922 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9925 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9937 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9958 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9962 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9966 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9969 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9971 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9972 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 9983 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:07 2002] [warn] child process 10008 still did not
> exit, sending a SIGTERM
> [Wed Feb 6 12:35:11 2002] [notice] caught SIGTERM, shutting down
> [Wed Feb 6 12:35:25 2002] [notice] Apache/1.3.20 (Unix) mod_ssl/2.8.4
> OpenSSL/0.9.6b PHP/4.1.1 mod_auth_pam_external/0.1 FrontPage/4.0.4.3
> mod_perl/1.25 configured -- resuming normal operations
>
> Anyone any ideas.....
>
> Thanks, Jan
>
>
> ------------------------------------------------------------------------
> www.php-accelerator.co.uk Home of the free PHP Accelerator
>
> To post, send email to phpa@xxxxxxxxxxxxx
> To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject
> unsubscribe
------------------------------------------------------------------------
www.php-accelerator.co.uk Home of the free PHP Accelerator
To post, send email to phpa@xxxxxxxxxxxxx
To unsubscribe, email phpa-request@xxxxxxxxxxxxx with subject unsubscribe
Other related posts:
