Warning

massive

massive

Verified User
Joined
Feb 16, 2006
Messages
299
Hi,
I am gettings these warnings :

Could not determine the server's fully qualified domain name, using 127.0.0.1
> [Tue Feb 28 16:26:38 2006] [warn] NameVirtualHost 207.210.229.99:80 has no VirtualHosts
> [Tue Feb 28 16:26:38 2006] [warn] NameVirtualHost 207.210.229.99:443 has no VirtualHosts
> [Tue Feb 28 16:26:38 2006] [warn] NameVirtualHost 207.210.229.79:443 has no VirtualHosts

Do you know why?
 
The warnings are normal and can be ignored. They are caused when you have added IP addresses through DirectAdmin but haven't put any users on them yet.
 
I remember the other warnings before but this :
httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

How i can change this warning?
 
Make sure you have your hostname setup properly. What do you get if you run hostname on the command line?
 
Then your hostname isn't setup.

Use man hostname to find out how to change you hostname and be sure to update DirectAdmin to reflect the changes as well (admin level -> Administrator settings)
 
Jon and massive,

The best way to change the hostname is through the DA control panel, logged in as admin.

It's under Administrator Settings.

If you just use the hostname command through a shell there's a lot of required stuff that won't get done.

Jeff
 
jlasman said:
If you just use the hostname command through a shell there's a lot of required stuff that won't get done.
Click to expand...

I think that's the case regardless of which way you do it, unless the few things that aren't changed by DirectAdmin were fixed in the last version but undocumented.
 
We've been doing it through the DA control panel for some time.

The most important issue is the special /etc/virtual/hostname.example.com directory.

Jeff
 
You shouldn't have to do any of this; DA is supposed to manage it.

I've asked John to look at, and comment on, this thread.

Jeff
 
Hello,

If this is debian, there was a bug in the hostname.sh script.
It was using the redhat style hostname saving. It's been fixed a while back.. (make sure you update DA), but the only real change was it added:

echo host.name.com > /etc/hostname

Which is what's needed to save the hostname for the reboot.

The redhats/linuxses, it's set in:
/etc/sysconfig/network

John
 
Hello,

If this is debian, there was a bug in the hostname.sh script.
It was using the redhat style hostname saving. It's been fixed a while back.. (make sure you update DA), but the only real change was it added:

echo host.name.com > /etc/hostname

Which is what's needed to save the hostname for the reboot.

The redhats/linuxses, it's set in:



John

It is Centos
I changed the hostname in /etc/sysconfig/network
but after the reboot the hostname is still www.

I opened /var/log/messages to see the problem and :

Mar 2 13:31:31 www kernel: host=www, domain=
 
Not sure then.. it's probably being set somewhere else during the boot process on your box.
So, there are 2 options..
1)either try and hunt down 1 line of code in hundreds of boot scripts
2) Find a script that's run last, and piggyback a hostname reset in it.

eg:
/etc/init.d/directadmin, add the bold bit:
Code: 
start() {
        echo -n "Starting DirectAdmin: "
        daemon $PROGBIN
        echo
        touch $PROGLOCK
        [b]hostname -v your.hostname.com[/b]
}
It's a bit of a hack, but should work.

John
 
It worked. But i will search which script stops it.
Thank you very much anyway!
 
You must log in or register to reply here.
Back
Top