You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-users@xml.apache.org by Paul Caton <pa...@mama.stg.brown.edu> on 2002/02/15 17:21:17 UTC

How to kill Xindice ghost?

I installed Xindice on a box running Solaris 5.6 and started the
server with ./start. I got an error message telling me to amend a line
in a source file, and the command for creating the addressbook
collection didn't work, so I figured I would stop the server, fix the
source file, and recompile. However, the xindiceadmin shutdown -c /db
command didn't work either, so I decided to just kill the server
process. I did this, and checked that it was indeed dead by running ps
-A. Yet when I went to run ./start again, I'm getting a message saying
that "A Xindice instance is already running with PID 15938", even
though that process doesn't show up with any of the normal Unix
process-checking commands.

Is the process *really* running, and is just hidden from commands like
ps, or was some kind of state variable set in a Xindice file when I
first started the server and because I couldn't shut it down with
xindiceadmin shutdown the variable is still set?

Paul.

-- 
Paul Caton
Electronic Publications Editor
Women Writers Project

 e-mail: paul@mail.stg.brown.edu
    tel: (401) 863-3619
address: Box 1841, Brown University, Providence RI 02912

	


Re: How to kill Xindice ghost?

Posted by "Mark J. Stang" <ma...@earthlink.net>.
There is a flag file in the config directory.   It was called dbxml.pid,
try xindice.pid.   Anyway, delete it.  Xindice/dbXML is finding that
file.

I can never remember, so I have a file called "wontstart" with
instructions:-).

Mark

Paul Caton wrote:

> I installed Xindice on a box running Solaris 5.6 and started the
> server with ./start. I got an error message telling me to amend a line
> in a source file, and the command for creating the addressbook
> collection didn't work, so I figured I would stop the server, fix the
> source file, and recompile. However, the xindiceadmin shutdown -c /db
> command didn't work either, so I decided to just kill the server
> process. I did this, and checked that it was indeed dead by running ps
> -A. Yet when I went to run ./start again, I'm getting a message saying
> that "A Xindice instance is already running with PID 15938", even
> though that process doesn't show up with any of the normal Unix
> process-checking commands.
>
> Is the process *really* running, and is just hidden from commands like
> ps, or was some kind of state variable set in a Xindice file when I
> first started the server and because I couldn't shut it down with
> xindiceadmin shutdown the variable is still set?
>
> Paul.
>
> --
> Paul Caton
> Electronic Publications Editor
> Women Writers Project
>
>  e-mail: paul@mail.stg.brown.edu
>     tel: (401) 863-3619
> address: Box 1841, Brown University, Providence RI 02912
>
>


Re: How to kill Xindice ghost?

Posted by Brian Blakeley <br...@cogeco.ca>.
Or did I kill the server and therefore leave the PID file intact on my
server and therefore when I restart the server it finds the PID and believes
therefore that it is in fact still running.

You might want to have a look for the PID and try restarting the server
after deleting the little file.

Works for me.

Brian

PS: I often seem to have trouble shutting down the server and use CRTL-c in
the term window.


----- Original Message -----
From: "Paul Caton" <pa...@mama.stg.brown.edu>
To: <xi...@xml.apache.org>
Sent: Friday, February 15, 2002 11:21 AM
Subject: How to kill Xindice ghost?


> I installed Xindice on a box running Solaris 5.6 and started the
> server with ./start. I got an error message telling me to amend a line
> in a source file, and the command for creating the addressbook
> collection didn't work, so I figured I would stop the server, fix the
> source file, and recompile. However, the xindiceadmin shutdown -c /db
> command didn't work either, so I decided to just kill the server
> process. I did this, and checked that it was indeed dead by running ps
> -A. Yet when I went to run ./start again, I'm getting a message saying
> that "A Xindice instance is already running with PID 15938", even
> though that process doesn't show up with any of the normal Unix
> process-checking commands.
>
> Is the process *really* running, and is just hidden from commands like
> ps, or was some kind of state variable set in a Xindice file when I
> first started the server and because I couldn't shut it down with
> xindiceadmin shutdown the variable is still set?
>
> Paul.
>
> --
> Paul Caton
> Electronic Publications Editor
> Women Writers Project
>
>  e-mail: paul@mail.stg.brown.edu
>     tel: (401) 863-3619
> address: Box 1841, Brown University, Providence RI 02912
>
>
>