1 |
On Tuesday 13 Dec 2011 19:20:57 Todd Goodman wrote: |
2 |
> * Grant <emailgrant@×××××.com> [111213 14:07]: |
3 |
> > Has anyone else noticed this sort of behavior from apache-2.2.21-r1: |
4 |
> > |
5 |
> > # /etc/init.d/apache2 restart |
6 |
> > |
7 |
> > * Stopping apache2 ... [ ok ] |
8 |
> > * Starting apache2 ... |
9 |
> > * start-stop-daemon: /usr/sbin/apache2 is already running [ ok ] |
10 |
> > |
11 |
> > # /etc/init.d/apache2 restart |
12 |
> > |
13 |
> > * apache2 not running (no pid file) |
14 |
> > * Starting apache2 ... [ ok ] |
15 |
> > |
16 |
> > It probably happens about half the time I restart apache2. Nothing in |
17 |
> > /var/log/apache2/error_log besides: |
18 |
> > |
19 |
> > [notice] caught SIGTERM, shutting down |
20 |
> > [notice] Apache/2.2.21 (Unix) configured -- resuming normal operations |
21 |
> > |
22 |
> > - Grant |
23 |
> |
24 |
> I've seen that for years. I always assumed it was because the apache2 |
25 |
> stop didn't complete before the apache2 start tried to start when I use |
26 |
> /etc/init.d/apache2 restart. |
27 |
> |
28 |
> Instead I do an /etc/init.d/apache2 stop; ps aux | egrep apache until I |
29 |
> see all the threads are gone and then a /etc/init.d/apache2 start |
30 |
|
31 |
+1 |
32 |
|
33 |
If there aren't many threads a quick restart will work fine, but if there are |
34 |
many threads hanging around then you may be better off to stop, wait, then |
35 |
start. |
36 |
-- |
37 |
Regards, |
38 |
Mick |