Hello kind folks,

I've got a debian lenny installation set up as a testing webserver. Everything was working perfectly thanks to the folks here that is!

So here's my problem:

Upgraded to the latest lenny release and it seems to me that it has written over some files and my webserver has stopped serving!

Here's my findings so far:

I noticed that eth0 had an ipaddress of 192.168.1.2 and not the one I had assigned in /etc/network/interfaces which was 192.168.1.15 (there was no backup file created by the upgrade)so I changed that file as I had done before to:

# The primary network interface

# auto eth0

iface eth0 inet static
address 192.168.1.15
netmask 255.255.255.0
gateway 192.168.1.1 (that's my cheapo router with port forwarding to 192.168.1.15 already set up and was working!)

Then I added xxxx.dnsalias.org 192.168.1.15 to my /etc/hosts file (that had been overwritten too!)

I seem to remember that I had to create a /etc/resolve.conf file but that has been replaced by a link to a file that says "dont touch this file, it will be updated automatically" or someting like that.

At your mercy guys and gals! Please help!

Regards from Scotland (hope we beat the dutch on wednesday night in the world cup qualifier!)

add the option
to the eth0 iface

that should give your server the internet back

..ignorance, do you mean:

iface eth0 inet static dns-nameservers 192.168.1.1

or

iface eth0 inet static
dns-nameservers 192.168.1.1

or is it the same thing? ie one line or 2 lines?

Thanks for you help,

Sorry for being a linux dafty!

ok I thought you would just guess...
according to the setup you posted above, the file should look like:
That's how I ment it. The following commands, executed as root (in that sequence), will apply the settings:
Hope that gets your server serving again.

.. added the the line you suggested (never had to do that before the upgrade) the solution is no doubt more involved.

I can see the website from the server but have no access to the net from the server and cant access the server from a remote computer..oh joy!

Oh and eth0 reports as 192.168.1.15 must be that darn resolve.conf thingy!

My fault. I thought you needed to assign the ip 192.168.1.15, which is the ip the upgrade gave you. Just edit that file again and change the ip after the "address" statement to the one which your server is to be assigned (192.168.1.2 if I got it right now). Then use the two commands to apply the changes. Sorry for my mistake.

Hi again,

I can now see the internet from the server, so half way to the solution :-)

Here's the whole interfaces file, just in case something else is wrong:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

allow-hotplug eth0

# auto eth0

iface eth0 inet static
address 192.168.1.15
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 192.168.1.1

any ideas?

I am seeing the ip 192.168.1.15 in your 'interfaces' file again, if you want your server to have the ip 192.168.1.2, you will have to change that.

From what you said, you are probably running a webserver (apache?). To check if it's running, open a web browser in your LAN (or the LAN where the server is) and enter the server ip in the address field.

Hi again,

Sorry to confuse you, but you can be sure I'm a lot more confused than you! :-)

Ok just to clarify, yes I had everything working prior to the upgrade using the address 192.168.1.15.

After upgrade the eth0 address changed to 192.168.1.2 and some of my files were altered (I still suspect resolve.conf is the problem)

When I enter http://192.168.1.15 on the server I see my test web site in the browser.

Do you think any of the apache configs were changed during the upgarde?

Thanks for your help.

....netstat -tan|grep -E '80|10000'

Here's the output:

tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN
tcp 0 0 192.168.1.15:49644 77.242.194.130:80 ESTABLISHED
tcp 1 0 192.168.1.15:54050 205.234.175.175:80 CLOSE_WAIT
tcp 0 0 192.168.1.15:37035 209.85.229.157:80 ESTABLISHED
tcp 0 0 192.168.1.15:35914 75.126.162.205:80 ESTABLISHED
tcp 0 0 192.168.1.15:48589 212.140.233.207:80 ESTABLISHED
tcp 0 0 192.168.1.15:41621 209.85.229.167:80 ESTABLISHED
tcp 0 0 192.168.1.15:54053 205.234.175.175:80 ESTABLISHED
tcp 0 0 192.168.1.15:49643 77.242.194.130:80 ESTABLISHED
tcp 0 0 192.168.1.15:49646 77.242.194.130:80 ESTABLISHED
tcp 0 0 192.168.1.15:60075 209.85.229.156:80 ESTABLISHED
tcp 0 0 192.168.1.15:35913 75.126.162.205:80 ESTABLISHED
tcp 1 0 192.168.1.15:54051 205.234.175.175:80 CLOSE_WAIT
tcp 1 0 192.168.1.15:54055 205.234.175.175:80 CLOSE_WAIT
tcp 0 0 192.168.1.15:42244 209.85.229.164:80 ESTABLISHED
tcp 0 0 192.168.1.15:35915 75.126.162.205:80 ESTABLISHED
tcp 0 0 192.168.1.15:59142 64.158.223.128:80 TIME_WAIT
tcp 0 0 192.168.1.15:49641 77.242.194.130:80 ESTABLISHED
tcp 0 0 192.168.1.15:49642 77.242.194.130:80 ESTABLISHED
tcp 0 0 192.168.1.15:35917 75.126.162.205:80 ESTABLISHED
tcp 1 0 192.168.1.15:54052 205.234.175.175:80 CLOSE_WAIT
tcp 1 0 192.168.1.15:54054 205.234.175.175:80 CLOSE_WAIT
tcp 0 0 192.168.1.15:35916 75.126.162.205:80 ESTABLISHED
tcp 0 0 192.168.1.15:49645 77.242.194.130:80 ESTABLISHED
tcp 0 0 192.168.1.15:38163 209.85.229.113:80 ESTABLISHED
tcp6 0 0 :::80 :::* LISTEN

Any ideas what it means? :-)

This means there are a lot of connection from the internet to your web pages (tcp connections from a lot of internet ip's to port 80).

Hello again,

How come I can't connect to the my test site from a remote computer via the internet?

Any ideas what to try next to connect?

Seems after the upgrade the webserver is now listening on IPV6 and not on IPV4. How to I change this?

Found this info:

http://www.linux.com/community/blogs...ick-howto.html

Is echo "blacklist ipv6" >> /etc/modprobe.d/blacklist.conf the answer?
Any gurus out there?

Sorry, I don't know. If you start a new thread like "Why does Apache only listen to ipv6 ports?", more people will be looking at this issue ("no-reply-threads"), so you might catch one or two "gurus" by doing that. How about it?