Does the same issue arise if the restart is split into a stop and start? My
thinking is that the stop IS working, but is taking longer than the script
expects, so the stop step fails when the program checks the PID to see if
it has shutdown properly. Then when the start happens the Apache has not
completely shutdown and is still holding the port. After the failure the
stop completes and the PID file is deleted. The PID file could be empty
because the startup creates the PID file, but can't write the PID to it
because the startup failed.
I'm just guessing though, as I don't have a CENTOS/RHEL system to look at.
I'm not even sure if my suggested scenario makes sense!
Cheers,
Cliff
On Sat, Mar 8, 2014 at 4:28 AM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> On Fri, Mar 7, 2014 at 5:37 AM, Tim Dunphy <bluethundr@xxxxxxxxx> wrote:
> >
> > Not really sure how to interpret that, unfortunately.
> >
> >
> > However looked for the pid file for apache and noticed that it DOESN'T
> > EXIST!
> >
> > [root@beta:~] #ls -l /var/run/httpd/
> > total 0
> >
> >
> > Well, that would explain why the init script isn';t able to kill the
> > process. Maybe puppet is doing something weird with that pid file? I
> don't
> > really know offhand, but I guess I will have to investigate that.
>
> Is one created at a successful startup? And how is puppet involved?
>
> --
> Les Mikesell
> lesmikesell@xxxxxxxxx
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
