|
Do you have another web server instance that has grabbed that port? Any existing server would need to be specified to just bind to the old address. Scott Mildenberger > -----Original Message----- > From: Steve McKay [mailto:steve.mckay@southtrust.com] > Sent: Wednesday, January 22, 2003 1:34 PM > To: web400@midrange.com > Subject: [WEB400] Re: Multiple web instances assistance and comments > > > I configured an additional IP address on our current NIC > using CFGTCP option > 1 and attempted to start a Apache test instance on that > address, port 80. > Received the following message every 5 seconds for 5 minutes (as the > documentation states will happen) and the test instance shut > itself down: > > Message ID . . . . . . : HTP803D Severity . . . . . > . . : 10 > Message type . . . . . : Diagnostic > Date sent . . . . . . : 01/22/03 Time sent . . . . . . : > 14:26:56 > > Message . . . . : HTTP Server waiting for address > 10.10.18.54 port 80 to > become available. > Cause . . . . . : The HTTP server is attempting to bind to address > 10.10.18.54 on port 80, but the TCP interface or port is > currently not > available. The server is retrying the socket bind > operation. The error > number is 3420. Error numbers and their meanings are: > - 3420: Port already in use >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.