Forum Moderators: phranque

Message Too Old, No Replies

No Such Process when Restarting Apache

Is this something to be concerned about?

         

carfac

5:55 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi:

Many times, when I restart my server, I get messages like this:

killall: kill -TERM 40405: No such process
killall: kill -TERM 40393: No such process
killall: kill -TERM 40356: No such process
killall: kill -TERM 40305: No such process
killall: kill -TERM 40304: No such process
killall: kill -TERM 40303: No such process
killall: kill -TERM 40302: No such process
killall: kill -TERM 40301: No such process
killall: kill -TERM 40300: No such process
killall: kill -TERM 40299: No such process
killall: kill -TERM 40298: No such process
killall: kill -TERM 40297: No such process
killall: kill -TERM 40296: No such process

is this something to be worried about? What does this mean?

Thanks!

dave

EliteWeb

6:01 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



apachectl stop

a fun command to stop apache then do a apachectl start -if yer doing this than hMmmmMm

carfac

7:13 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



No, I am running kill `cat /usr/local/apache/logs/httpd.pid then the restart. Should I use stop instead?

dave

ggrot

7:14 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Kill is always the last resort. Tell apache to stop on it's own as was explained above, then if that doesn't work - try kill.

andreasfriedrich

7:22 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



This analogy might help:

Just like you will ask some children that trespas on your property to steal cherries from your trees to leave instead of killing them right from the start you should give any daemon the chance to shutdown gracefully and on its own before killing it ;).

Andreas

amoore

7:30 pm on Feb 5, 2003 (gmt 0)

10+ Year Member



You might as well use apachectl or your /etc/init.d/httpd script since they do some cleanup and more gracefully start and stop apache. Just for the record, though, they use kill to control the apache daemon, too. Perhaps it's a misnomer, but it's used to send signals to processes, not commit felonious acts of murder on children.

carfac

7:31 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Everyone:

OK, thanks a lot. I have a little shut-down-restart script I run, I will take that line out, and add the one you all suggest! I appreciate your help! (As always!)

dave

carfac

7:36 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi:

I'm Back!

OK, I did it with a call to apachectl and the command stop. I just ran that, and got this:

/my/pth/to/apachectl stop: httpd stopped
killall: kill -TERM 44394: No such process
killall: kill -TERM 44406: No such process
killall: kill -TERM 44384: No such process
killall: kill -TERM 44539: No such process
killall: kill -TERM 44402: No such process
killall: kill -TERM 44405: No such process
killall: kill -TERM 44391: No such process
killall: kill -TERM 44398: No such process

There were more, but you get the idea...

Is this something to be concerned about? Are these just processes that were used a coiuple times, and are "hibernating" or waiting for another user to log on, so no worries?

Thanks!

dave

carfac

7:38 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Oh, nevermind- I FORGOT to comment out Killall!

NEVERMIND!

dave

andreasfriedrich

7:51 pm on Feb 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I was only referring to the unfriendly signals like SIGKILL or SIGTERM (you donīt ask the children to kill themselves). I do realize that in signal terms you would probably use a kill SIGINT to request that the children interrupt what they are doing ;)

Andreas