GJN13 Super Contributor.
Super Contributor.
646 views

HPSM9.41: KM Search engine errors in log and indexer status shows Idle

Dear Experts,

I have installed KM search engine and appled the patch for SM9.41KM, search engine windows service created KM,

I have configured the KM search server in SM, and verified the server, it says Search Engine Connected, after that i have done Full ReIndex on Knowledge,Incident and Interaction libraries, and each library states shows Online and Docs numbers are showing in the screen, i checked KMUpdate Process running in system status, when i check the Manage KM update indexter status shows "Idle" all the time,

I have searched in search Knowledge base, did true search, it returns 550+  documents, i can see the below errors in sm.log file.

13759( 14737) 02/11/2016 09:20:42 JS I Updating Collection: Incident_Library

13759( 14737) 02/11/2016 09:20:42 JS I checking for pending updates

13759( 14737) 02/11/2016 09:20:42 JS I index complete in: 61 milliseconds

13759( 14737) 02/11/2016 09:20:42 JS I indexresult for Incident_Library: 0

13759( 14737) 02/11/2016 09:20:42 JS I Updating Collection: Interaction_Library

13759( 14737) 02/11/2016 09:20:42 JS I checking for pending updates

13759( 14737) 02/11/2016 09:20:42 JS I index complete in: 24 milliseconds

13759( 14737) 02/11/2016 09:20:42 JS I indexresult for Interaction_Library: 0

13759( 14737) 02/11/2016 09:20:43 JS I Updating Collection: Knowledge_Library

13759( 14737) 02/11/2016 09:20:43 JS I checking for pending updates

13759( 14737) 02/11/2016 09:20:43 JS I index complete in: 61 milliseconds

13759( 14737) 02/11/2016 09:20:43 JS I indexresult for Knowledge_Library: 0

13759( 14737) 02/11/2016 09:20:43 Core: KnownError_Library is down or does not exist

13759( 14737) 02/11/2016 09:20:43 [Ljava.lang.StackTraceElement;@11ae79a

java.lang.NullPointerException

at com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch.getIndexStatistics(KMSolrSearch.java:951)

at com.hp.ov.sm.server.utility.GenericServerThread.symanContinue(Native Method)

at com.hp.ov.sm.server.utility.GenericServerThread.run(GenericServerThread.java:58)

13759( 14737) 02/11/2016 09:20:43 JS I Index statistics not clear.

13759( 14737) 02/11/2016 09:20:43 Core: Problem_Library is down or does not exist

13759( 14737) 02/11/2016 09:20:43 [Ljava.lang.StackTraceElement;@15fc279

java.lang.NullPointerException

at com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch.getIndexStatistics(KMSolrSearch.java:951)

at com.hp.ov.sm.server.utility.GenericServerThread.symanContinue(Native Method)

at com.hp.ov.sm.server.utility.GenericServerThread.run(GenericServerThread.java:58)

13759( 14737) 02/11/2016 09:20:43 JS I Index statistics not clear.

13759( 14737) 02/11/2016 09:20:43 Core: KnownError_Library is down or does not exist

13759( 14737) 02/11/2016 09:20:43 [Ljava.lang.StackTraceElement;@10b4b5b

java.lang.NullPointerException

at com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch.getIndexStatistics(KMSolrSearch.java:951)

at com.hp.ov.sm.server.utility.GenericServerThread.symanContinue(Native Method)

at com.hp.ov.sm.server.utility.GenericServerThread.run(GenericServerThread.java:58)

13759( 14737) 02/11/2016 09:20:43 Core: Problem_Library is down or does not exist

13759( 14737) 02/11/2016 09:20:43 [Ljava.lang.StackTraceElement;@9d8dab

java.lang.NullPointerException

at com.hp.ov.sm.server.plugins.knowledgemanagement.solr.KMSolrSearch.getIndexStatistics(KMSolrSearch.java:951)

at com.hp.ov.sm.server.utility.GenericServerThread.symanContinue(Native Method)

at com.hp.ov.sm.server.utility.GenericServerThread.run(GenericServerThread.java:58)

Kindly let me know whether KM is working or not? and what shall i do to get the Indexr status as "Running".

Thanks,

Jagan

Tags (1)
0 Likes
3 Replies
Highlighted
Abhijit K Acclaimed Contributor.
Acclaimed Contributor.

Re: HPSM9.41: KM Search engine errors in log and indexer status shows Idle

Hi,

This is the common issue as Known Error as seperate module does not exist now. It was in Older version of SM.

You simple diable this library removing in from indexing hence whenever index runs it will not search for Known error documents.

Regards,

Abhijit K

0 Likes
GJN13 Super Contributor.
Super Contributor.

Re: HPSM9.41: KM Search engine errors in log and indexer status shows Idle

Thanks Abhijit for quick reply,

but why indexer status still shows as "Idle" ? i s there any thing we need to check to change the status to  "Running",

i have checked in our test environment , indexer status shows "Running" like below

KMUpdate : Scheduled

Idle Time:  00:02:21

Indexer Status: Running

Knowledgebase: Knowledge_Library

Total Records: 12

Current record : 3

But in production system indexer status "Idle" all the time though i can able to search the documents in ess.do page

KMUpdate : Scheduled

Idle Time:  00:02:21

Indexer Status: Idle

Knowledgebase:

Total Records:

Current record :

Kindly let me know

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: HPSM9.41: KM Search engine errors in log and indexer status shows Idle

KMUpdate will only show as 'running' when it is actually processing records that reside within the kmknowledgebaseupdates table. If no records exist to process it remains in an idle state. Every five minutes KMUpdate will check to see if records exist in the table and if so submit them to the search engine. That is when it is 'running'.

Earlier you said you peformed a true search and 500+ records returned in the Hitlist. If that is the case then KMUpdate did process records so it was 'running' at that time. 

If you submit a new Knowlege Document and - after 30 minutes - it does not return in the search results then it is possible KMUpdate is hung. To check this:

1. SM Command Line
2. Enter the following and search to access the 'schedule' file: sch
3. When you're at empty Schedule record the following in the Name field and click search: KMUpdate
4. You should now see the schedule record for the KMUpdate background process
5. What is the value in the Status field? If it is Application Failed then that is why the index is not longer running

Brett Alan Christlieb
Technical Consultant IV | Technical Support Engineer IV | Advanced Support Engineer IV
Service Manager Level 3 Support SWAT Team

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.