Apache not responding after update

[emmaytch]

Hi

I have a LAMP which was working fine until I installed some critical updates.

Now it only responds on localhost not the ip of the server.

All ports are open - firewall has been disabled (it is an internal server only).

netstat -ant gives:

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN

I have checked ports.conf and even included Listen 8000 - which also does not work.

Apache, php and mysql are all working ok as I can access our internal database/webpages via 127.0.0.1 - but absolutely nothing on 10.0.1.1 (the server's public address).

The server can communicate with other PC's, and can also be ssh'd.

Hopefully someone will know what this is as I have been scratching my head for a couple of days now.

Thanks

 

[RhythmAce]

Your interface setup got changed some how. Do ifconfig and see what "inet addr" is. It should be the ip you had before.

 

[emmaytch]

It is the same address and the PC is reporting the correct settings for eth0.

ifconfig shows everything it should. You can see why I've been scratching my head!

The fact that I can ssh into it from another PC shows the address is routable.

 

[RhythmAce]

Yes indeed. I just wasn't sure if you were using an ip or hostname to ssh into the server. Then I would guess that apache isn't listening for that address. By default apaches listens for all addresses on port 80. You can change this via the "Listen" directive. For example:

Listen 192.168.1.10:80

Apache will ignore all addresses but that one. On the other hand, if you have:

Listen *:80

this will tell apache to listen for all addresses on port 80. If this is what you have, then is there a remote chance that http traffic is no longer being forwarded to that machine from your router? How about your logs, do they give any clues? What got installed during the update? Maybe that will point us in the right direction.

 

[emmaytch]

Thanks for the replies.

I had tried changing ports.conf to include port 8000, just in case 80 was binding to something other than apache. It didn't work either.

The logs are fine. No errors. It shows that I have used apache on 127.0.0.1 As I said, it works fine there.

There is no internal router! The server sits in an environment that is thin ethernet - so it's daisy-chained.

All addresses on the server are correct. It is listening on port 80, the firewall is off.

As for the update, it was about 50 packages! I know it included apache2, mysql and php - so all of them got hit.

I removed apache and php from the server and then re-installed them. So far this has not made a difference.

 

[emmaytch]

I think I have found the problem - and it isn't apache's fault.

route gives the following

Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth0
default 10.0.0.4 0.0.0.0 UG 0 0 0 eth0

10.0.0.4 is our squid proxy on another machine.

There is no mention of the apache server's own ip (10.0.1.1) which will explain why it doesn't respond.

Now all I have to do is sort that somehow!