From: Suman Nath (sknath@cs.cmu.edu)
Date: 02/03/03
As mentioned in the project handout, xindice database engine can be
started using the command "xindiceserver start".
However, the command does not produce any output (success or failure
message), so you may not see if the server is actually
running. Starting xindice may fail for many reasons. For example, when you
start xindice it creates a file "config/xindice.pid" listing the xindice
process id. Every time you try to start xindice, it checks for the
xindice.pid file, and starts only if there is no such file (which idealy
means there is no xindice server running). But if you turn off your PC
without shutting down the xindice server, the xindice.pid file will still
be there. So, when you try to start xindice next time, it will find the
xindice.pid file and will not start again, assuming another xindice
process is still running. Using "xindiceserver start" does not give any
indication of whether the xindice is started or failed to start in such
situations.
So, I recommend you to run the "./start" command, from the same directory,
to start xindice server. (xindiceserver is a script that executess the
"start" command and redirects all the output to /dev/null). If everything
goes fine, you should see the message "server running.." at the end.
Otherwise you should see the reason for failing.
You need to set the environment variables XINDICE_HOME and JAVA_HOME
before running "start".
Alternatively, if you run "xindiceserver start", make sure that no xindice
server is running and there is no config/xindice.pid file. You can also
try to edit the "xindiceserver" script to not to redirect the output to
/dev/null.
- Suman
This archive was generated by hypermail 2.1.5 : 02/03/03 EST