Re: [cobalt-users] Apache not responding on port 80

["Peter Masloch" <peter@xxxxxxxxxxx>]

Try this: stop httpd and admserv in /etc/rc.d/init.d then do a "ps aux" and
make sure
that all httpd and ahttpd processes are gone. If not do a killall httpd and
killall ahttpd.
If this still doesn't work then you have something wrong in the httpd.conf
Peter


> Peter, I changed the original "Port   80" line (never got to change or add
to the "Listen   80"), first to 81 and then, realizing it
> could interfere with the rewrite rules that use port 81 for the admin GUI,
I tried others, to no avail, rebooting each time.
>
> Now the "error" log shows apache keeps trying, unsuccessfully, to bind to
port 81, and a socket cannot be established because the
> port appears taken.
>
> The odd thing is, I tried "killall httpd" (as suggested in a previous
incident in the archive), and rebooted, but it did not solve
> the problem.  The configuration files in   /etc/httpd/conf   all seem to
have "Port   80" but the information must be stored
> somewhere else since rebooting does not change the situation, that is,
port 80 remains without service.     Hints?
> )             -- George
>
>
> ----- Original Message -----
> From: "Peter Masloch" <peter@xxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Tuesday, July 02, 2002 19:17
> Subject: Re: [cobalt-users] Apache not responding on port 80
>
>
> Anything in the logfiles (error)? In which section of httpd.conf did you
> change the port?
> Peter
>
> ----- Original Message -----
> From: "George" <cobalt-users@xxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Tuesday, July 02, 2002 6:49 PM
> Subject: [cobalt-users] Apache not responding on port 80
>
>
> > Hello folks,
> >
> > After configuring a new RaQ4, I changed the PORT parameter in
> /etc/httpd/conf/httpd.conf
> > so instead of 80 it would serve http in a different port, something I
had
> done before with Apache running on other platforms.
> >
> > Since with the Cobalt it did not work, I immediately changed the PORT
> parameter back to 80, and restarted the server.  Now Apache
> > runs but does not serve on port 80 nor any of the others I tried, but it
> still gives you a message stating that access is forbidden
> > if you try to access the server thru port 81, for example.  This, to me,
> shows the server is basically ok, just misconfigured as to
> > the main port to serve.
> >
> > What should I do?  How do I revert it to serve normally on port 80?
> > Obviously without the web server accessible, the admin GUI is lost.
> >
> > Also, any hints as to how to configure it for service on a different
port
> (and still work!  ;-)  will be greatly appreciated.
> >
> > Thanks in advance!
> > -- George
> >
> > PS.  Is there any literature available about the internals of the Cobalt
> line?
>
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>
>