Just now I had configured server

vhosts added

but when I start it i am getting

[root@cloud /]# /etc/rc.d/init.d/httpd start
Starting httpd: [Fri Jun 18 18:25:24 2010] [error] (EAI 3)Temporary failure in name resolution: Could not resolve host name yourhostname -- ignoring!
Warning: DocumentRoot [/www/your-domain/html] does not exist

Can anyone help me

Really, as it says.

yourhostname is not resolvable. fix it in DNS or add it to /etc/hosts.
/www/your-domain/html does not exist. create it.

How to add it sir

can you please tell me steps

Hi, nithinsha,
As it says - -- ignoring!, you can simply ignore this issue.
I suspect there might be some issues on the vhost configuration. It's the point why httpd cannot start.

what does error_log say? By default this file stored in /var/log/httpd/error_log*

nithinsha -

1. AlucardZero is absolutely correct. You need to:
a) make sure the "DocumentRoot" you specified actually exists (and has correct permissions) on your filesystem

b) if you're using vhosts, make sure the DNS name of your virtual host is actually defined in DNS

2. There are many, many tutorials, FAQs and howto's available that describe how to do both of these things.

There *are* no simple "1,2,3", rote, cookbook instructions anybody can give you.

'Hope that helps .. PSM

Sir,

Its rackspace cloud server

my host address is cloud.invign.net

can you could give me some tutorial links ..i kad check vhosts...DNS Name is right

1. make sure the "DocumentRoot" you specified actually exists (and has correct permissions) on your filesystem
The error says that it doesn't, you haven't shown any attempt to verify that it does.

2. Make sure that the *DNS Name you specified in your VHost section* actually exists. If your vhost is for "moose", then try to ping "moose". If your "vhost" is for "moose.cloud.invign.net", then make sure you can ping "moose.cloud.invign.net", "cloud.invign.net" and "moose".

3. Try this diagnostic:
Apache -S command l

4. Look in "/var/log/httpd/error_log". You were asked to do this, and you haven't shown any attempt to try.

5. Consider if you really need a "vhost" in the first place? Maybe all you need is a simple configuration!

'Hope that helps .. PSM

now i am not getting other errors

just httpd [Failed]

below is what i got from error_log


--------------------------------------------------------------------------[Sat Jun 19 18:16:51 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 19 18:16:51 2010] [notice] Digest: generating secret for digest authentication ...
[Sat Jun 19 18:16:51 2010] [notice] Digest: done
[Sat Jun 19 18:16:51 2010] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
[Sat Jun 19 20:29:14 2010] [notice] caught SIGTERM, shutting down
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
(21)Is a directory: httpd: could not open error log file /www/invign.com/logs/error_log.
Unable to open logs
------------------------------------------------------------------------

changed host to m.invign.com

OK - you've successfully fubar'ed your Apache configuration.

Do this:
1. Take a backup of any custom web content you've created (a simple "tar" file should be fine)

2. DE-INSTALL Apache ("yum remove" your Apache package)

3. Re-INSTALL Apache ("yum install" your Apache package: get a CLEAN INSTALL)

4. Verify that Apache works

5. Add your WEB CONTENT. Verify that it works.

6. STOP if everything's OK. DON'T make any other changes unless you NEED to, and unless you KNOW WHAT YOU'RE DOING.

and you might want to reread the apache docs page
http://httpd.apache.org/docs/2.2/

I tell people to study them " as if you ARE going to take a final exam on this"
because YOU ARE -- the web site .