[CentOS] weird apache issue
Tim Dunphy
bluethundr at gmail.com
Fri Mar 7 13:20:21 UTC 2014
ok thanks for the tip!
So I did a netstat as you suggested and this is what I found:
[root at 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?
Thanks!
Tim
On Fri, Mar 7, 2014 at 7:32 AM, Tony Mountifield <tony at softins.co.uk> wrote:
> In article <
> CAOZy0en0x_wrBZkVjZUpaTYMOD7Z_VTBOMorMukEDknrWNfQMA at mail.gmail.com>,
> Tim Dunphy <bluethundr at gmail.com> wrote:
> > Hey guys,
> >
> > Well it took a little while for me to be able to reproduce this. It
> seems
> > that this problem is intermittent and sporadic.
> >
> > But I tried running a sh -x /etc/init.d/httpd restart command once I
> > reallized I had another incident of this and this is what I saw as the
> > output:
> >
>
> > + /bin/bash -c 'ulimit -S -c 0 >/dev/null 2>&1 ; /usr/sbin/httpd'
> > (98)Address already in use: make_sock: could not bind to address [::]:80
> > (98)Address already in use: make_sock: could not bind to address
> 0.0.0.0:80
> > no listening sockets available, shutting down
>
> >
> > Not really sure how to interpret that, unfortunately.
> >
> >
> > However looked for the pid file for apache and noticed that it DOESN'T
> > EXIST!
> >
> > [root at 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.
> >
> > Thanks for all your input.
>
> Have a look to see what process is actually doing the listening on port 80:
>
> # netstat -natp
>
> Look for a local address with a port of 80 and a state of LISTEN.
>
> The final column shows you the PID and program name.
>
> Cheers
> Tony
> --
> Tony Mountifield
> Work: tony at softins.co.uk - http://www.softins.co.uk
> Play: tony at mountifield.org - http://tony.mountifield.org
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
More information about the CentOS
mailing list