In the event of the
Starting httpd: (98)Address already in use: make_sock: could not bind to
address 0.0.0.0:80 no listening sockets available, shutting down
error
Follow this procedure
login su in server
/sbin/fuser 80/tcp
80/tcp: [process number] <--------this denotes a proceses using port 80
kill -9 [process number]
Then run /etc/rc.d/init.d/httpd start
Regards
Paul
----- Original Message -----
From: "Richard C. Barker Sr." <rc (at mark) probass.com>
To: <coba-e (at mark) bluequartz.org>
Sent: Tuesday, September 12, 2006 3:28 PM
Subject: [coba-e:06859] WebServer unable to start
> Since update of on SolarSpeed Server
> Dependencies Resolved
> Transaction Listing:
> Update: httpd.i386 0:2.0.52-28.ent.centos4 - base
> Update: httpd-manual.i386 0:2.0.52-28.ent.centos4 - base
> Update: httpd-suexec.i386 0:2.0.52-28.ent.centos4 - base
> Update: mod_ssl.i386 1:2.0.52-28.ent.centos4 - base
> Update: openssl.i686 0:0.9.7a-43.11 - update
> Update: pam_krb5.i386 0:2.1.8-1 - base
> Update: sendmail.i386 0:8.13.1-3.RHEL4.5 - base
> Update: sendmail-cf.i386 0:8.13.1-3.RHEL4.5 - base
> Update: sendmail-doc.i386 0:8.13.1-3.RHEL4.5 - base
> Update: yum.noarch 0:2.4.3-1.c4 - base
> *Performing the following to resolve dependencies:
> Install: python-elementtree.i386 0:1.2.6-4.2.1 - base
> Install: python-sqlite.i386 0:1.1.7-1.2 - base
> Install: python-urlgrabber.noarch 0:2.9.8-2 - base
> Install: sqlite.i386 0:3.3.3-1.2 - base*
>
> Sep 12 10:00:04 grouper httpd: (98)Address already in use: make_sock:
> could not bind to address 0.0.0.0:443
> Sep 12 10:00:04 grouper httpd: no listening sockets available, shutting
> down
> Sep 12 10:00:04 grouper httpd: Unable to open logs
>
> Will not Listen on Port 80
>
> RC
>
>
> --
> Richard C. Barker Sr.
> CEO & President
> 1-800-510-3139
> ProBass Networks Inc.
> http://www.probassnetworks.net
> http://www.probass.net
>
> ******************************************************************
> DISCLAIMER : -
> This e-mail is confidential and intended only for the use
> of the individual or entity named above and may contain
> information that is privileged. If you are not the intended
> recipient, you are notified that any dissemination, distribution
> or copying of this e-mail is strictly prohibited. If you have
> received this email in error, please notify us immediately
> by return email or telephone and destroy the original message.
> Thank you.
>
>
>
>
--
This message has been scanned for viruses and
dangerous content by Swift Internet, and is
believed to be clean.