[SOLVED] servers fully qualified domain name

garyg007 · 07-20-2010, 03:52 PM

I am getting the following messages:

Quote:

starting web server: apache2apache2: apr_sockaddr_info_get() failed for Debian
apache2: could not reliably determine the servers fully qualified domain name
using 127.0.0.1 for ServerName

Any suggestions how I can fix this would be much appreciated.

Gary

ncsuapex · 07-20-2010, 03:57 PM

What's your /etc/hosts file look like and whats the result of running

Quote:

uname -a

?

garyg007 · 07-20-2010, 05:54 PM

Quote:

Originally Posted by ncsuapex

What's your /etc/hosts file look like and whats the result of running <uname -a>?

Thankyou for the response; requested info follows:

Code:

gary@Debian:~$ uname -a
Linux Debian 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010 i686 GNU/Linux
gary@Debian:~$

Code:

gary@Debian:~$ cat /etc/hosts
127.0.0.1 localhost

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.1.1 workgroup.domain.invalid workgroup
gary@Debian:~$

Gary

ncsuapex · 07-21-2010, 09:14 AM

Oh and forgot one other output:

Quote:

ifconfig

I haven't used debian in years so cant remember if they use eth0 as the first interface. But whatever the IP is for your main interface you need to add it to your etc hosts. Also you'll need to know your domain. Is this for your private home web site or for a company project you are working on?

You'll need to add a line like this to your /etc/hosts

192.168.1.101 debian.domain debian

The line translates to as follows:

IPaddress FQDN shortname

So change 192.168.1.101 to your IP, debain.domain to your FQDN and debian is your short name.

garyg007 · 07-21-2010, 07:10 PM

Thank you for the reply, ncsuapex.
This is a private home LAN. 3 desktops, a laptop and a upnp device (actually a directv hr21)

I am pretty much clueless when it comes to networks - I know almost enough to just start to understand what the documentation says and just enough to be extremely dangerous to a network.

I have a wireless router (Linksys WRT54GS) attached to the modem/router (speedstream 4300)

Code:

Debian:/home/gary# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3443 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3443 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:245207 (239.4 KiB)  TX bytes:245207 (239.4 KiB)

wlan1     Link encap:Ethernet  HWaddr 08:10:74:18:bb:bf  
          inet addr:192.168.1.111  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a10:74ff:fe18:bbbf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26466 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21267 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:24635013 (23.4 MiB)  TX bytes:3805982 (3.6 MiB)
          Interrupt:19 Memory:febe0000-febf0000 

Debian:/home/gary#

I updated the /etc/hosts; here is what it looks like now

Code:

Debian:/home/gary# cat /etc/hosts
127.0.0.1 localhost
#192.168.1.111 localhost Debian
192.168.1.111 workgroup.domain.invalid workgroup

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.1.1 workgroup.domain.invalid workgroup
Debian:/home/gary#

eth0 is missing from the display - I do not have a wired lan. Actually, a number of errors associated with eth0 occur during boot

I'm going to try an re-boot now and see what I broke.

Gary

ncsuapex · 07-22-2010, 10:53 AM

Ahhh yes if you're wireless than use the wlan1 info.

I suspect it didnt work from reading your /etc/hosts. Correct?

I would make these changes:

FROM:

Quote:

127.0.0.1 localhost
#192.168.1.111 localhost Debian
192.168.1.111 workgroup.domain.invalid workgroup

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.1.1 workgroup.domain.invalid workgroup

TO:

Quote:

127.0.0.1 localhost.localdomain localhost
#192.168.1.111 localhost Debian
192.168.1.111 debian.domain.invalid debian

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

You only need 127.0.01 in there once.

Im still not sure where you are getting the .domain.invalid from. Are you trying to use Windows network info? Are the linux box and the windows box part of a domain? If the linux box is independent from the windows, as in you dont need them to communicate to get your website up you dont need to use the windows domain info on your linux box. You can set your own linux domain for your linux box.

garyg007 · 07-23-2010, 09:08 AM

Thank you for the reply.

Quote:

I suspect it didnt work from reading your /etc/hosts. Correct?

That is correct.

"domain.invalid" is the domain name used by my ISP. It's what is specified in the modem/router

Quote:

Are the linux box and the windows box part of a domain?

Yes.

A few of the personal applications I use have no viable Linux alternatives - and they do not work with wine or the vm packages I have tried - so I keep a windows computer (for turbo-tax, Sony-reader and directv2pc)

For a while I tried to use remote-desktop to access linux from windows and windows from linux; It worked but was a real pain in the butt and not all that satisfactory.

Occasionally I want to move data between the two systems, but I can do that with a usb memory stick. So the windows domain name goes into the bit-bucket.

I've made the changes you suggested - and will post back the results.

Thanks again for the help

Gary

Worked - no longer get the error message during boot.