One of my mates, Jon, was seeing the following set of exceptions with Lotus Connections 3.0: -
[12/20/10 18:21:00:649 GMT] 00000051 DocumentIndex E com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid CLFRW0493E: Unable to start the document indexing service, please ensure that the PATH environment variable has been set.
[12/20/10 18:21:00:650 GMT] 00000051 DocumentIndex E com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid - PATH: /opt/IBM/WebSphere/AppServer/java/ibm_bin:/opt/IBM/WebSphere/AppServer/java/bin/:/opt/IBM/WebSphere/AppServer/java/jre/bin:/opt/IBM/WebSphere/AppServer/java/ibm_bin:/opt/IBM/WebSphere/AppServer/java/bin/:/opt/IBM/WebSphere/AppServer/java/jre/bin:/opt/IBM/WebSphere/AppServer/java/ibm_bin:/opt/IBM/WebSphere/AppServer/java/bin/:/opt/IBM/WebSphere/AppServer/java/jre/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
[12/20/10 18:21:00:651 GMT] 00000051 DocumentIndex E com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid CLFRW0493E: Unable to start the document indexing service, please ensure that the LD_LIBRARY_PATH environment variable has been set.
[12/20/10 18:21:00:652 GMT] 00000051 DocumentIndex E com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid - LD_LIBRARY_PATH: /opt/IBM/WebSphere/AppServer/bin:
[12/20/10 18:21:00:652 GMT] 00000051 DocumentIndex I com.ibm.lotus.connections.search.service.files.impl.DocumentIndexingServiceImpl isEnvironmentValid: false
At my suggestion, Jon set the LD_LIBRARY_PATH and PATH variables: -
export PATH=/opt/IBM/LotusConnections/data/search/stellent/dcs/oiexport:$PATH
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/LotusConnections/data/search/stellent/dcs/oiexport
This came from some previous experience with Lotus Quickr and also the Lotus Connections 2.5 Information Centre here.
Hope this is of use to someone else out there :-)
Subscribe to:
Post Comments (Atom)
-
After an unscheduled reboot of the VMs that host my K8s cluster, I was struggling to work out why the kubelet wasn't starting properly...
-
I hit a wee snag earlier today, whilst attempting to unpack some IBM software on my NAS. Being a command-line junkie, I'd SSH'd into...
-
I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair. This involved pressing a "Pair" button on one...
4 comments:
Yeah, thats perfect! I saw this error too!
Thanks a lot!!!
@Julius - excellent, thanks for letting me know
Just used this thanks Dave. Had the same error and setting the path as directed sorted it. Only change was that as I am on a clustered environment the path for the stellent/dcs etc was in the shared data location.
Awesome, it worked!
In Cluster env. here is the command:
export PATH=/opt/IBM/LotusConnections/data/shared/search/stellent/dcs/oiexport:$PATH
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/LotusConnections/data/shared/search/stellent/dcs/oiexport
Post a Comment