Re: [APC-DEV] APC + Apache SIGHUP

On Thu, Oct 8, 2009 at 3:07 AM, Gopal V <[email protected]> wrote:
> Nathan Clemons wrote:
>
>> We do some pretty standard Apache log rotation on our web cluster with
>> logrotate; move the file to an archival point, send a SIGHUP to Apache
>> so it releases the open file handle, and then bzip2 up the data for
>> archival purposes.
>
> I'm almost sure this is an apache thing and nothing apc can really do
> about it.
>
> [Thu Oct 08 15:23:27 2009] [notice] SIGHUP received. =A0Attempting to res=
tart
> We hit mshutdown - 9345
> apache2: Could not reliably determine the server's fully qualified domain
> name, using 127.0.1.1 for ServerName
> We hit minit - 9345
>
> is what my apache2 says. Just to be double+good, I put a couple of
> printfs in module init/module shutdown code. And I can see that
> a SIGHUP essentially stops and restarts the php modules directly.
>
>> isn't something we particularly like, since we're caching our
>> localization data inside of APC (using apc_store).
>
> So basically the apc module init is called again in the parent
> process after it gets a SIGHUP. It's not that apc is clearing
> its cache or handling the HUP, apache is essentially doing an
> internal soft restart.
>
> http://httpd.apache.org/docs/2.2/stopping.html#hup
>

Thanks, I didn't actually realize that it restarted APC/PHP on a
SIGHUP. Are you familiar with whether or not this occurs during a
SIGUSR1? The Apache documentation is unclear about module reloading.
From my testing, it seems like it does, but I'm not completely sure
about that.

Thanks for the help,

--Nathan Clemons