Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

apache wont start sasy failed and thats all

Status
Not open for further replies.

robertd18

Technical User
Jan 14, 2003
32
US
Failed to start apache :
Starting httpd: [FAILED]

thats the error i get any sugg?
 
Yeah.

Tail Apache's error logfile in the background before you try to start the server again. Look in httpd.conf for an ErrorLog directive that does not appear in a virtual server configuration to find out where the log is.


On my system, I do:

tail -f /var/log/httpd/error_log &

Then I try to start the server again. Want the best answers? Ask the best questions: TANSTAAFL!
 
hmm well here is the logfile

[Thu Apr 10 12:44:57 2003] [info] Init: Initializing OpenSSL library
[Thu Apr 10 12:44:57 2003] [info] Init: Seeding PRNG with 136 bytes of entropy
[Thu Apr 10 12:44:57 2003] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Thu Apr 10 12:44:57 2003] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Thu Apr 10 12:44:57 2003] [debug] ssl_scache_dbm.c(416): Inter-Process Session Cache (DBM) Expiry: old: 0, new: 0, removed: 0
[Thu Apr 10 12:44:57 2003] [info] Init: Initializing (virtual) servers for SSL
[Thu Apr 10 12:44:57 2003] [info] Server: Apache/2.0.40, Interface: mod_ssl/2.0.40, Library: OpenSSL/0.9.6b
[Thu Apr 10 12:45:19 2003] [alert] (22003)Temporary failure in name resolution: mod_unique_id: unable to find IPv4 address of "server1.usasuperclicks.com"
Configuration Failed

and i changed the name of the IPv4 to an ip address

now the error we get is

Failed to start apache :
Starting httpd: (98)Address already in use: make_sock: could not bind to address 216.93.175.112:80
no listening sockets available, shutting down
[FAILED]

 
i dont know it was assigned to me by the server co and it is supposed to be directed to this server
 
never mind...we were using the newer version and found that we were missing some files so are going to use 1.3 instead
thanks
 
You may have the same problem with 1.3.x. In order for a virtual server to bind to an IP address, that IP address must be available on a network interface.

One problem that can crop up is NAT. The routeable address your ISP has assigned to you may not be the one bound to your server because of some NATting going on at your network border. If so, then you will need to direct Apache to bind to the non-routeable address to which incoming packets are routed. Want the best answers? Ask the best questions: TANSTAAFL!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top