In article CAOZy0enCsMUGAdp631bhuARosUo6TUQJp=zym4L3ccSN6-9ddQ@mail.gmail.com, Tim Dunphy bluethundr@gmail.com wrote:
ok thanks for the tip!
So I did a netstat as you suggested and this is what I found:
[root@beta:~] #netstat -natp | grep 80 tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 2354/python2.6 tcp 0 0 0.0.0.0:8010 0.0.0.0:* LISTEN 8198/python2.6 tcp 0 0 0.0.0.0:8013 0.0.0.0:* LISTEN 8198/python2.6 tcp 0 0 166.78.8.98:8081 0.0.0.0:* LISTEN 10950/java tcp 0 0 0.0.0.0:28017 0.0.0.0:* LISTEN 2289/mongod tcp 0 1 166.78.8.98:33612 72.52.4.74:80 SYN_SENT 17471/wget tcp 0 672 166.78.8.98:22 24.38.100.4:35265 ESTABLISHED 5680/sshd tcp 0 0 :::995 :::* LISTEN 1806/couriertcpd tcp 0 0 :::110 :::* LISTEN 1800/couriertcpd tcp 0 0 :::80 :::* LISTEN 31589/httpd
And it does look as if it's apache that's taking up port 80 and nothing else.
I also checked /var/run/httpd and saw that it was EMPTY! No pid file to be found. I had a look at the puppet manifests and couldn't see ANYTHING that could be causing the pid file to go missing.
Does anyone have any suggestions on how I can track down why the pid file keeps disappearing?
It's probably a case of piecing together bits of evidence, e.g.
- "ps -fp 31589" to see when the process started.
- Compare that with /var/log/httpd/error_log* - apache logs a message there when it starts up.
- Do "ls -ld /var/run/httpd" to see when /var/sun/httpd was last changed (due to the deletion of httpd.pid)
- Look through logfiles in /var/log and /var/log/httpd for anything that happened just at that time.
- Kill off the httpd process manually using "kill 31589" (or whatever) and check with "ps -ef" that all instances of httpd disappear.
- Start it up again with "service httpd start" and then watch more closely.
Hope you manage to find an explanation!
Cheers Tony