Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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
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!)
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.
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.
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?