On Fri, Jul 28, 2006 at 06:41:24PM +0200, Joost de Heer wrote:
> > Cannot assign requested address: make_sock: could not bind
> > to address 208.97.158.169:1443
> > no listening sockets available, shutting down
> > Unable to open logs
>
> Is the network up before you start Apache? If your machine doesn't have
> this IP address yet, it'll fail.
Well, of course. The machine has a number of IP addresses bound to
the same interface. That indeed is the problem.
I didn't even consider that because there's another web server bound
to that same IP address. In fact there's a number of web servers
that run and they are get spawned by an init.d script called "httpd".
The reason I didn't consider it is because of this:
$ ls /etc/rc2.d/ | egrep '(ifp|httpd)'
S20httpd
S20httpd2
S91ifp_httpd
S20httpd starts the server listening on port 80, and S91ifp_httpd
starts the server listening on port 83/1443. So, logically you would
think the interface is up when S91 runs if port 80 is coming up.
I guess there's some Dreamhost magic happening in the background to
make the port 80 server wait until the interface is up. I've got a
support request into Dreamhost, but of course they will think it's
not their problem since I'm running my own init.d script. That S91
script is the last in the run-level so the interfaces are coming up
some other way.
That's one of the problems with using a "managed" dedicated server.
> May I ask why you're binding on a specific address, instead of all
> interfaces?
Multiple web servers.
--
Bill Moseley
moseley@xxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|