Index: [Article Count Order] [Thread]

Date:  Fri, 26 Oct 2007 21:08:37 +0200
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:10968] Re: admserv not starting back
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200710262108.38132.bq (at mark) solarspeed.net>
In-Reply-To:  <291601c817f2$cd4eb0f0$5001010a@sales>
References:  <291601c817f2$cd4eb0f0$5001010a@sales>
X-Mail-Count: 10968

Hi Tushar,

> Starting admin web server: (98)Address already in use: make_sock: could not
> bind to address 0.0.0.0:444

Try this first - as root from SSH:

/etc/init.d/admserv stop
/etc/init.d/admserv start

If that still doesn't start up admserv, run this command: 

	netstat -tupan|grep :444

That will show you which process is still using port 444. The reported back 
information could look like this:

tcp        0      0 0.0.0.0:444                 0.0.0.0:*                   
LISTEN      15157/httpd.admsrv

So then you know that the process httpd.admserv with the PID 15157 is still 
using that port. Kill it off this way:

	kill -9 15157

Of course you need the "15157" to the Process ID (PID) that your netstat 
command did show.

-- 
With best regards,

Michael Stauber
http://www.solarspeed.net