How To Fix: Could not determine the server's fully qualified domain name

RegisterLogin

Webune Forums » Linux Hosting » How To Fix: Could not determine the server's fully qualified domain name

How To Fix: Could not determine the server's fully qualified domain name
Post Description: How To Fix: Could not determine the server's fully qualified domain name
Tags: How, To, Fix:, Could, not, determine, the, server's, fully, qualified, domain, name
This Post Was Posted On Nov 12, 2009 By toyer #773

How To Fix: Could not determine the server's fully qualified domain name by toyer

I am getting this error everytime I try to restart my apache server.

Code:

Starting httpd: httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

how can i fix this?

Leave Your Comments

Related Pages: [Add Your Website]

Post New Topic

Apr_sockaddr_info_get() Failed

Ajay

#5220 1

thanks for your help.its work

May 23, 2011 Reply Report abuse

abdoulkarim

#4685 2

jai un probleme de bleutooth dans mon telephone e51,il refuse de s'activé

Dec 10, 2010 Reply Report abuse

Jose

#4161 3

i have a debian lenny.
i edited the /etc/apache2/apache2.conf and at the end of the file, added:

servername here-the-name-of-your_server

it worked for me.

Jul 15, 2010 Reply Report abuse

CoderX

#3445 4

make sure you dont have a duplicate http.conf file. in my case i had /etc/httpd/conf/httpd.conf and /etc/httpd/conf.d/system-config-httpd.conf (from the configurator app).
renaming or deleting one should fix the issue

regards

Feb 10, 2010 Reply Report abuse

mandrake

#2767 5

some help with this please:

mandriva starting httpd: httpd: could not reliably determine the servers fully qualified domain name, using 127.0.0.1 for servername (98)address already in use: make_sock: could not bind to address [::]:80 (98)address already in use: make_sock: could not

Nov 09, 2009 Reply Report abuse

steve

#2598 6

tarting httpd: httpd: apr_sockaddr_info_get() failed for "my domain"
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]

Oct 17, 2009 Reply Report abuse

jessiesss

#960 7

what i need to know is how to fix need to be called by 3 domain names

Aug 02, 2009 Reply Report abuse

tiorios

#959 8

when httpd restart showing error fully qualified domain name. i tried on fqdn, ubuntu which both have apache2

Jul 31, 2009 Reply Report abuse

apah

#958 9

how about if i get this:

httpd: apr_sockaddr_info_get() failed for hostname httpd: could not reliably determine the servers fully qualified domain name, using 127.0.0.1 for servername

Jul 13, 2009 Reply Report abuse

comfi

#957 10

how do you make qualified domain name on your linux server?

Jul 12, 2009 Reply Report abuse

adhi

#956 11

getting same error

Jun 19, 2009 Reply Report abuse

Hoddi

#955 12

thanks, it works

Mar 05, 2008 Reply Report abuse

Boomer

#954 13

ah it was /etc/hosts.
thanks

Mar 05, 2008 Reply Report abuse

var

#953 14

http://tgrove.com/2007/12/02/httpd-apr_sockaddr_info_get-failed-for-hostname/

Mar 03, 2008 Reply Report abuse

helper

#952 15

also check this file:

/etc/hosts

make sure it matches your hostname

i was getting this error

starting httpd: httpd: apr_sockaddr_info_get() failed for hostname.domain

httpd: could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for servername

Mar 03, 2008 Reply Report abuse

View More Comments

Leave Your Comments...