Teamsite search is not working

Hi All,

Previously teamsite search was working. Today i have got that the services are stopped on search server. So i tried to start it again but when i am trying to start it then the services stoped with the msg "Error 1067: The process termineted unexpectdly".

As it was working till yesterday so what cud be the wrong with it?

Nidhi A

Find more posts tagged with

Comments

nipper

You need to look in the logs and post any interesting information.

Has anything changed since it was working ?

Also what rev of TS and what OS are you running on

Nidhi_Agrawal

Hi,
This is copying the iw.tsindex.log log content here.

[19 Jun 2007 13:41:55,093] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:42:07,989] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:42:19,470] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:42:30,827] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:42:42,198] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:42:53,665] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:43:05,132] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:43:16,503] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:43:27,874] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:43:39,244] INFO com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Looking for event system ...
[19 Jun 2007 13:43:40,043] FATAL com.interwoven.hunter.index.Listener (WrapperSimpleAppMain) - Listener is unable to connect to the event subsystem
[19 Jun 2007 13:43:40,043] FATAL com.interwoven.hunter.index.IndexServer (WrapperSimpleAppMain) - Error in initialization of the Index Manager
java.lang.RuntimeException: Error initializing Listener for Interwoven
at com.interwoven.hunter.index.Listener.(Listener.java:95)
at com.interwoven.hunter.index.IndexServer.startListeners(IndexServer.java:314)
at com.interwoven.hunter.index.IndexServer.work(IndexServer.java:255)
at com.interwoven.hunter.index.IndexServer.main(IndexServer.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:136)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NamingException: Failed to connect to JNDI provider [Root exception is java.net.ConnectException: Connection refused: connect]
at org.exolab.jms.jndi.mipc.IpcJndiInitialContextFactory.openConnection(Unknown Source)
at org.exolab.jms.jndi.mipc.IpcJndiInitialContextFactory.getInitialContext(Unknown Source)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.(InitialContext.java:195)
at com.interwoven.hunter.index.Listener.init(Listener.java:108)
at com.interwoven.hunter.index.Listener.(Listener.java:72)
... 9 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.(Socket.java:309)
at java.net.Socket.(Socket.java:124)
at org.exolab.core.ipc.TcpService.(TcpService.java:122)
at org.exolab.core.ipc.Client.(Client.java:91)
... 17 more
[19 Jun 2007 13:43:40,043] INFO com.interwoven.hunter.index.Reaper (Thread-0) - Shutdown IndexServer
[19 Jun 2007 13:43:40,043] INFO com.interwoven.hunter.index.Reaper (Thread-0) - Shutdown IndexManager
[19 Jun 2007 13:43:40,057] WARN com.interwoven.hunter.index.BranchMapping (Thread-0) - Initial database is empty, i.e. no indexed branches
[19 Jun 2007 13:43:40,291] INFO com.interwoven.hunter.index.Indexer (Thread-0) - BulkIndexer-0 Freeze requested.
[19 Jun 2007 13:43:40,291] INFO com.interwoven.hunter.index.Indexer (Thread-0) - IncrementalIndexer-0 Freeze requested.
[19 Jun 2007 13:43:40,291] INFO com.interwoven.hunter.index.Indexer (Thread-0) - Shutting down Indexer BulkIndexer-0 (will stop after current job)
[19 Jun 2007 13:43:40,291] INFO com.interwoven.hunter.index.Indexer (IncrementalIndexer-0) - IncrementalIndexer-0 is frozen.

Nidhi

nipper

Listener is unable to connect to the event subsystem

Your event subsystem is not running. Can't search without it.

What DB are you using for the event subsystem ? Check the logs.

Also what OS and TS rev ?

Nidhi_Agrawal

Hi nipper,

I am using TS 6.5 and Windows OS 2003 SP1.
Please tell me how can up the event system?

Nidhi A

nipper

Control Panel -> Services

Interwoven Event Subsystem - Start

Now if it does not start properly, then you need to determine why (usually DB related)

Nidhi_Agrawal

Hi,

When I tried to start the event subsystem it is start and then stopped.
I am not able to run the event subsystem.
I am attaching the error doc here.

Control Panel -> Services

Interwoven Event Subsystem - Start

Now if it does not start properly, then you need to determine why (usually DB related)

nipper

That does not help, you need to find the error logs for the event subsystem, typically in iwhome/local/logs/eventsub*.log (there are 3, start it again and see which gets information added and post the new stuff).

Also, what DB are you using, if it is the default DB then there are a number of known issues with the size of it.

Nidhi_Agrawal

Hi,

I am using the default database.
I am not finding any new log. It is same as i sent it earlier.

Nidhi A

That does not help, you need to find the error logs for the event subsystem, typically in iwhome/local/logs/eventsub*.log (there are 3, start it again and see which gets information added and post the new stuff).

Also, what DB are you using, if it is the default DB then there are a number of known issues with the size of it.

Nidhi_Agrawal

Hi,

Here are the contents of eventsubd_err.log file

OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.exolab.core.foundation.DatabaseIOException: containsRoot failed org.exolab.core.foundation.DatabaseIOException: lookup failed org.exolab.core.foundation.DatabaseIOException: readObject failed for id 131120 with java.io.EOFException
at org.exolab.core.database.recman.PMDTransactionCache.containsRoot(PMDTransactionCache.java:140)
at org.exolab.core.database.recman.PMDSession.bind(PMDSession.java:129)
at org.exolab.jms.persistence.ObjectAdapter.createIdRoot(Unknown Source)
at org.exolab.jms.persistence.ObjectAdapter.(Unknown Source)
at org.exolab.jms.persistence.DatabaseService.createJdbmAdapter(Unknown Source)
at org.exolab.jms.persistence.DatabaseService.(Unknown Source)
at org.exolab.jms.persistence.DatabaseService.instance(Unknown Source)
at org.exolab.jms.server.JmsServer.registerServices(Unknown Source)
at org.exolab.jms.server.JmsServer.init(Unknown Source)
at org.exolab.jms.server.JmsServer.main(Unknown Source)

Nidhi A

moonkhanna

org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.exolab.core.foundation.DatabaseIOException: containsRoot failed org.exolab.core.foundation.DatabaseIOException: lookup failed org.exolab.core.foundation.DatabaseIOException: readObject failed for id 131120 with java.io.EOFException
at org.exolab.core.database.recman.PMDTransactionCach e.containsRoot(PMDTransactionCache.java:140)
at org.exolab.core.database.recman.PMDSession.bind(PM DSession.java:129)
at org.exolab.jms.persistence.ObjectAdapter.createIdR oot(Unknown Source)

I feel your openjms db has got corrupted from the above information. For a quick solution, just rename the openjms.db file in iw-home\eventsubsystem\ something folder to openjmsdb.bak and start your eventsubsystem again. That will solve your problem but at the same time will create a new openjms.db file.

I would recommend here to migrate to an external database at the earliest if you are planning to use Search. Else just switch off your eventsubsystem.

If in case, you do not want to lose your previous event information, contact Interwoven Support

Adam Stoller

Hi All,

Previously teamsite search was working. Today i have got that the services are stopped on search server. So i tried to start it again but when i am trying to start it then the services stoped with the msg "Error 1067: The process termineted unexpectdly".

As it was working till yesterday so what cud be the wrong with it?

Nidhi A

Uhm - not sure if this is the same error 1067 - but that used to be the error message that was thrown whenever your TS license was invalid -- you might want to double check all your license files and verify that none of the servers had their hostnames or network cards or stuff like that changed ...

Migrateduser

There are two options.
1.) Disable the eventsubsystem (and also switch the dependency off in search.properties). You loose all the updates-reflection in the indexes for the modified content.

2.) Use some commercial RDBMS (flat file is just for the demo puporses and its strongly recomended not to use it in production)

Nidhi_Agrawal

Hi ,

I didnt find any file named as openjms.db in iw-home\eventsubsystem\ and inside its sub directories. Only openjms.policy file is there.

Nidhi A

org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.exolab.core.foundation.DatabaseIOException: containsRoot failed org.exolab.core.foundation.DatabaseIOException: lookup failed org.exolab.core.foundation.DatabaseIOException: readObject failed for id 131120 with java.io.EOFException
at org.exolab.core.database.recman.PMDTransactionCach e.containsRoot(PMDTransactionCache.java:140)
at org.exolab.core.database.recman.PMDSession.bind(PM DSession.java:129)
at org.exolab.jms.persistence.ObjectAdapter.createIdR oot(Unknown Source)

I feel your openjms db has got corrupted from the above information. For a quick solution, just rename the openjms.db file in iw-home\eventsubsystem\ something folder to openjmsdb.bak and start your eventsubsystem again. That will solve your problem but at the same time will create a new openjms.db file.

I would recommend here to migrate to an external database at the earliest if you are planning to use Search. Else just switch off your eventsubsystem.

If in case, you do not want to lose your previous event information, contact Interwoven Support

moonkhanna

pls attach your jmsconfignew.xml file from iw-home\eventsubsystem\conf

nipper

Search throughout your sys for that file. Event though I use SQL server, I still have the openjms.db file.

Nidhi_Agrawal

Hi,

It was my mistake. File is there.
And with the help of all you guys suggestions I am able to run my seacrh.
The problem was big database. File rename works for me.
To solve it permanently I have to look to configure my database.

thanks to all to solve this problem.

Nidhi A

Migrateduser

Search throughout your sys for that file. Event though I use SQL server, I still have the openjms.db file.

Nipper, This is the file lying around after you had the default setting run some time. Delete this (and openJMS.lock) and it will not be created again.

Migrateduser

Hi,

It was my mistake. File is there.
And with the help of all you guys suggestions I am able to run my seacrh.
The problem was big database. File rename works for me.
To solve it permanently I have to look to configure my database.

thanks to all to solve this problem.

Nidhi A

Nidhi,
You can delete te old file rather than renaming it, because this cannot be used anyways. The default flat file is only for the dummy purpose and it is not recomendid to be used in the actual setups. Coming 6.7.1 is supposed to come with the Derby (java based DB) and will be replacement for the OOTB flat DB.

See the support site KB articles for the details on supported RDBMS and how to configure them with eventSubsystem.

--hemant

Nidhi_Agrawal

Hi Hemant,

Ya, looking nice suggestion. I will delete the old file.
Also we are planning to configure our own database.

Nidhi,
You can delete te old file rather than renaming it, because this cannot be used anyways. The default flat file is only for the dummy purpose and it is not recomendid to be used in the actual setups. Coming 6.7.1 is supposed to come with the Derby (java based DB) and will be replacement for the OOTB flat DB.

See the support site KB articles for the details on supported RDBMS and how to configure them with eventSubsystem.

--hemant

Thanks,
Nidhi A