Fw: Fw: httpd dead but subsys locked

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry for re-post, but I cant see any messages posted within last 2 days.

----- Original Message ----- 
From: "Nitin" <nitinmehta@xxxxxxxxxxxx>
To: <redhat-list@xxxxxxxxxx>
Sent: Saturday, May 15, 2004 7:48 PM
Subject: Fw: Fw: httpd dead but subsys locked


>
> ----- Original Message ----- 
> From: "Nitin" <nitinmehta@xxxxxxxxxxxx>
> To: <lists-redhat-replies@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Saturday, May 15, 2004 7:46 PM
> Subject: Re: Fw: httpd dead but subsys locked
>
>
> > now it says
> >
> > [crit] (98)Address already in use: make_sock: could not bind to port 80
> >
> > ???????
> >
> >
> > ----- Original Message ----- 
> > From: <lists-redhat-replies@xxxxxxxxxxxxxxxxxxxxx>
> > To: "Nitin" <nitinmehta@xxxxxxxxxxxx>
> > Sent: Saturday, May 15, 2004 7:19 PM
> > Subject: Re: Fw: httpd dead but subsys locked
> >
> >
> > > if:
> > >
> > >      https://<host>:434/<file>
> > >
> > > works, then https is running (just fine), just on the non-standard
> > > port.  as such, by default, you (and your users) won't be able to
> > > find it (you can use the syntax above on links to it from your http
> > > server pages if you want).
> > >
> > > with your httpd.conf having https on 434 a start/stop or restart
> > > won't do anything to "fix" the problem.
> > >
> > > your httpd.conf needs to be edited to change the 434 to 443.
> > > **however**, if you didn't set up your web server you should check
> > > with the person who did.  there may have been a reason that they did
> > > this. for instance, they may be trying to run multiple https servers
> > > on a single IPnumber. that won't work, (you can run multiple http
> > > servers on the same IPnumber, but not multiple https) so as a
> > > work-around they may have put one of the server instances on the
> > > non-standard port.
> > >
> > > if you set this up, and this is just a typo, edit the httpd.conf and
> > > change the 434 to 443 (look for other instances of this in the file).
> > > then stop the servers and then start them.
> > >
> > >
> > >
> > > ---------- Original Message ----------
> > > > From: Nitin <nitinmehta@xxxxxxxxxxxx>
> > > > To: lists-redhat-replies@xxxxxxxxxxxxxxxxxxxxx
> > > > Date: Saturday, May 15, 2004 07:04:58 PM +0530
> > > > Subject: Re: Fw: httpd dead but subsys locked
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: <lists-redhat-replies@xxxxxxxxxxxxxxxxxxxxx>
> > > > To: "Nitin" <nitinmehta@xxxxxxxxxxxx>
> > > > Sent: Saturday, May 15, 2004 4:47 PM
> > > > Subject: Re: Fw: httpd dead but subsys locked
> > > >
> > > >
> > > >> is this correct:
> > > >>
> > > >>   > Listen 80
> > > >>   > Listen 434
> > > >>
> > > >> as noted by others, the standard port for https is 443, so if your
> > > >> server is listening on a non-standard port that could give you the
> > > >> impression that https is down.
> > > >>
> > > >> [you can test this with a:
> > > >>
> > > >>    https://<host>:434/<file>
> > > >
> > > > works fine
> > > >
> > > > what do I fix in httpd.conf ?
> > > > though, I've checked using stop/start in the place of restart, but
> > > > to no use...
> > > >
> > > > Thanks again
> > > >
> > > >>
> > > >> and see if the https server responds.]
> > > >>
> > > >> if this is correct you need to fix the httpd.conf (in
> > > >> /etc/httpd/conf, assuming that that's really the one your servers
> > > >> use to start) and then *stop*/*start* (rather than *restart*) your
> > > >> web servers.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> ---------- Original Message ----------
> > > >> > From: Nitin <nitinmehta@xxxxxxxxxxxx>
> > > >> > To: redhat-list@xxxxxxxxxx
> > > >> > Date: Saturday, May 15, 2004 04:27:36 PM +0530
> > > >> > Subject: Fw: httpd dead but subsys locked
> > > >> >
> > > >> > Submitting again, cause, I couldn't see it in the
> > > >> > list.........Sorry if others could receive the mail.
> > > >> >
> > > >> > ----- Original Message -----
> > > >> > From: "Nitin" <nitinmehta@xxxxxxxxxxxx>
> > > >> > To: "General Red Hat Linux discussion list"
> > > >> > <redhat-list@xxxxxxxxxx> Sent: Saturday, May 15, 2004 3:24 PM
> > > >> > Subject: Re: httpd dead but subsys locked
> > > >> >
> > > >> >
> > > >> >> Sorry for delayed response from my side. I've been trying a lot
> > > >> >> of things.
> > > >> >>
> > > >> >> Anyways, there is no '/etc/httpd/conf.d' file, but there are
> > > >> >> many '/var/run/httpd.mm.xxxx.sem' files. Should I delete them
> > > >> >> all ? Acc to my knowledge, these are memory files or something..
> > > >> >>
> > > >> >> And "grep Listen /etc/httpd/conf/httpd.conf" displays :
> > > >> >>
> > > >> >> # Listen: Allows you to bind Apache to specific IP addresses
> > > >> >> # and/or Listen 3000
> > > >> >> # Listen 12.34.56.78:80
> > > >> >> # Listen 80
> > > >> >> # See also the <VirtualHost> and Listen directives.
> > > >> >> Listen 80
> > > >> >> Listen 434
> > > >> >>
> > > >> >> Thanks again for your continued support.
> > > >> >> Nitin
> > > >> >>
> > > >> >> ----- Original Message -----
> > > >> >> From: "Juan Martinez" <martinez@xxxxxxxxxxxxx>
> > > >> >> To: "General Red Hat Linux discussion list"
> > > >> >> <redhat-list@xxxxxxxxxx> Sent: Friday, May 14, 2004 9:33 PM
> > > >> >> Subject: Re: httpd dead but subsys locked
> > > >> >>
> > > >> >>
> > > >> >> > Are you sure it's 434 and not 443?  443 is the https
> > > >> >> > well-known port number.
> > > >> >> >
> > > >> >> > In any case, I've received this error message when I've tried
> > > >> >> > to configure 2 https sites to the same IP address using
> > > >> >> > name-based virtual hosts.  Only one can be configured per IP
> > > >> >> > address and name-based virtual hosts share the same IP
> > > >> >> > address.
> > > >> >> >
> > > >> >> > Make sure you've only got one configured.  Check your
> > > >> >> > httpd.conf file and look for additional configurations in
> > > >> >> > /etc/httpd/conf.d Apache would give you this error when it
> > > >> >> > encounters the 2nd site configured with the same IP address.
> > > >> >> >
> > > >> >> >
> > > >> >> > Juan
> > > >> >> >
> > > >> >> > On Fri, 2004-05-14 at 11:49, Nitin wrote:
> > > >> >> > > httpd is configured to listen at all ports. And by the way
> > > >> > "netstat -anp
> > > >> >> > > | grep 434" shows nothing, that, as far as I gather, means
> > > >> >> > > | no
> > > >> > connections
> > > >> >> on
> > > >> >> > > that port.
> > > >> >> > >
> > > >> >> > >
> > > >> >> > > ----- Original Message -----
> > > >> >> > > From: "Jason Staudenmayer" <jasons@xxxxxxxxxxxxxx>
> > > >> >> > > To: "'General Red Hat Linux discussion list'"
> > > >> >> > > <redhat-list@xxxxxxxxxx> Sent: Friday, May 14, 2004 9:13 PM
> > > >> >> > > Subject: RE: httpd dead but subsys locked
> > > >> >> > >
> > > >> >> > >
> > > >> >> > > > What's on port 434? Are your running on non-standard port?
> > > >> >> > > > Or typo?
> > > >> >> What's
> > > >> >> > > > on that port?
> > > >> >> > > > netstat -anp |grep 434
> > > >> >> > > >
> > > >> >> > > > -----Original Message-----
> > > >> >> > > > From: Nitin [mailto:nitinmehta@xxxxxxxxxxxx]
> > > >> >> > > > Sent: Friday, May 14, 2004 11:38 AM
> > > >> >> > > > To: General Red Hat Linux discussion list
> > > >> >> > > > Subject: Re: httpd dead but subsys locked
> > > >> >> > > >
> > > >> >> > > >
> > > >> >> > > > nothing suspecious in access_log but whenever i try to
> > > >> >> > > > start httpd
> > > >> >> > > error_log
> > > >> >> > > > records :
> > > >> >> > > >
> > > >> >> > > > >>>> [crit] (98)Address already in use: make_sock: could
> > > >> >> > > > >>>> not bind to
> > > >> >> port
> > > >> >> > > 434
> > > >> >> > > >
> > > >> >> > > > Thanks again
> > > >> >> > > > Nitin
> > > >> >> >
> > > >> >> >
> > > >> >> > --
> > > >> >> > redhat-list mailing list
> > > >> >> > unsubscribe
> > > >> >> > mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > > >> >> > https://www.redhat.com/mailman/listinfo/redhat-list
> > > >> >> >
> > > >> >>
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > redhat-list mailing list
> > > >> > unsubscribe
> > > >> > mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > > >> > https://www.redhat.com/mailman/listinfo/redhat-list
> > > >>
> > > >> ---------- End Original Message ----------
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > > ---------- End Original Message ----------
> > >
> > >
> > >



-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux