Try a plain netstat -tapn and post it here please. I suspect that the 434 is a typo and that it's really 443... ----- Original Message ----- From: "Nitin" <nitinmehta@xxxxxxxxxxxx> To: "General Red Hat Linux discussion list" <redhat-list@xxxxxxxxxx> Sent: Friday, May 14, 2004 10:49 AM Subject: Re: httpd dead but subsys locked > 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 > > > > ----- Original Message ----- > > From: "Jason Staudenmayer" <jasons@xxxxxxxxxxxxxx> > > To: "'General Red Hat Linux discussion list'" <redhat-list@xxxxxxxxxx> > > Sent: Friday, May 14, 2004 9:03 PM > > Subject: RE: httpd dead but subsys locked > > > > > > > Yeah missed that sorry. What's in the log file? Both access and error. > > > > > > -----Original Message----- > > > From: Nitin [mailto:nitinmehta@xxxxxxxxxxxx] > > > Sent: Friday, May 14, 2004 11:31 AM > > > To: General Red Hat Linux discussion list > > > Subject: Re: httpd dead but subsys locked > > > > > > > > > perhaps you didn't read the initial mail. I've checked, there are no PID > > > files in '/var/run' > > > > > > Thanks anyway for your time and concern > > > > > > ----- Original Message ----- > > > From: "Jason Staudenmayer" <jasons@xxxxxxxxxxxxxx> > > > To: "'General Red Hat Linux discussion list'" <redhat-list@xxxxxxxxxx> > > > Sent: Friday, May 14, 2004 8:50 PM > > > Subject: RE: httpd dead but subsys locked > > > > > > > > > > Find the PID file and remove it. Look in /var/run/ > > > > > > > > -----Original Message----- > > > > From: Nitin [mailto:nitinmehta@xxxxxxxxxxxx] > > > > Sent: Friday, May 14, 2004 11:13 AM > > > > To: General Red Hat Linux discussion list > > > > Subject: Re: httpd dead but subsys locked > > > > > > > > > > > > No output from "ps -axc | grep httpd". > > > > "service httpd restart" >>>> httpd dead but subsys locked > > > > > > > > Thanks again for ur help and time > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Benjamin J. Weiss" <benjamin@xxxxxxxxxx> > > > > To: "General Red Hat Linux discussion list" <redhat-list@xxxxxxxxxx> > > > > Sent: Friday, May 14, 2004 8:10 PM > > > > Subject: Re: httpd dead but subsys locked > > > > > > > > > > > > > From: "Nitin" <nitinmehta@xxxxxxxxxxxx> > > > > > > Thanks for your time, but I already did it.... > > > > > > Any other suggestions? > > > > > > > > > > Hm...okay, so you say that the server's up and running. What do you > > get > > > > > when you do a "ps -axc | grep httpd"? > > > > > > > > > > Also, what exactly is the error message you get when you do a > "service > > > > httpd > > > > > restart"? > > > > > > > > > > Ben > > > > > > > > > > > > > > > > > > > > > > Nitin > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Benjamin J. Weiss" <benjamin@xxxxxxxxxx> > > > > > > To: "General Red Hat Linux discussion list" > <redhat-list@xxxxxxxxxx> > > > > > > Sent: Friday, May 14, 2004 6:02 PM > > > > > > Subject: Re: httpd dead but subsys locked > > > > > > > > > > > > > > > > > > > From: "Nitin" <nitinmehta@xxxxxxxxxxxx> > > > > > > > >I'm facing this new problem. > > > > > > > >Everything was working OK, suddenly, https got killed and now, > > > > > > > >when I start it, it displays OK. But nothing actually happens, > no > > > > > > > >processes started. When I check the status, it displays "httpd > > > > > > > >dead but subsys locked." and surprisingly all websites (hosted > > > > > > > >on that server) are working fine. > > > > > > > > > > > > > > > >I cann't take chances to reboot the server. > > > > > > > >I've checked, there are no pid files and mesage file doesn't > > > display > > > > > > > >any errors either.... where or what else should I check? > > > > > > > > > > > > > > > >Please help me as soon as possible > > > > > > > > > > > > > > Nitin, > > > > > > > > > > > > > > A quick check of /etc/init.d/httpd shows the following code > > snippet: > > > > > > > > > > > > > > start() { > > > > > > > echo -n $"Starting $prog: " > > > > > > > check13 || exit 1 > > > > > > > daemon $httpd $OPTIONS > > > > > > > RETVAL=$? > > > > > > > echo > > > > > > > [ $RETVAL = 0 ] && touch /var/lock/subsys/httpd > > > > > > > return $RETVAL > > > > > > > } > > > > > > > > > > > > > > Now, you see the part that says "touch /var/lock/subsys/httpd" ? > > > When > > > > > > > Apache runs, it spawns a bunch of processes with their own > pid's, > > so > > > > the > > > > > > > script keeps track of whether or not it's running by creating > that > > > > file > > > > > > > (/var/lock/subsys/httpd) when it runs. Then when it stops, it > > > deletes > > > > > it. > > > > > > > > > > > > > > Check to see if that file exists. If it does, then delete it > and > > > try > > > > > > > running "service httpd restart" again, and see if it comes up. > > > > > > > > > > > > > > Ben > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > -- > > > > > 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 > > > > > > > > > > > > -- > > > > 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 > > > > > > > > > -- > > > 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 > > > > > > -- > > 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 > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
