Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button.  The answer will now appear with a checkmark.  Please be sure to always mark answers that resolve your issue as verified.  Your fellow Community members will appreciate it!  Learn more.

  • State Not Answered
  • Replies replies
    16
  • Subscribers subscribers
    11
  • Views views
    1360
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Presentation of search results(index) fails after reboot

JoeAtWork

I have Retain 4.8.1.0 running on SLES 12

If I reboot the retain server at 6:001 AM and right after I login to Retain I cannot search for about 5 minutes while the indexer loads or does something. 

I now see there are results returned but they do not get to the users web browser, an additional search and the result time is 150ms and the user can see the results of the query.

Does this mean I have to reindex my data?

Do I need to increase the apache/tomcat timeout to 6 minutes?

Thanks,
Joe


06:01:00, 622 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Load properties for indexing engine solrcloud
06:01:00, 628 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Loading properties from classloader...
06:01:00, 628 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loading properties from classloader...
06:01:00, 628 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loaded properties for solrcloud
06:01:00, 674 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Load properties for indexing engine solrcloud
06:01:00, 674 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Loading properties from classloader...
06:01:00, 674 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loading properties from classloader...
06:01:00, 674 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loaded properties for solrcloud
06:01:00, 675 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Load properties for indexing engine solrcloud
06:01:00, 675 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Loading properties from classloader...
06:01:00, 675 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loading properties from classloader...
06:01:00, 675 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loaded properties for solrcloud
06:01:01, 146 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Load properties for indexing engine solrcloud
06:01:01, 146 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Loading properties from classloader...
06:01:01, 146 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loading properties from classloader...
06:01:01, 146 [INFO ] [StartupThreadProcess] LocalIndexingFactory: Successfully loaded properties for solrcloud
06:01:19, 799 [INFO ] [StatsUpdater] SolrCloudIndexingStats: Stats updater launched
06:01:19, 813 [DEBUG] [StatsUpdater] SolrCloudIndexingStats: Stats update goes to sleep
06:01:19, 839 [TRACE] [SolrCloudUnindexedReaderThread] UnindexedHandlerThread: idsList == null || idsList.size() == 0
06:43:12, 676 [TRACE] [ActiveMQ Session Task] SolrCloudIndexingSearcher: searching with offset: 0, count: 25
06:43:12, 677 [INFO ] [ActiveMQ Session Task] SolrCloudIndexingSearcher: Performing search of: ( _query_:"*:*" )
06:43:12, 677 [INFO ] [ActiveMQ Session Task] SolrCloudIndexingSearcher: start=0 rows=25
06:43:12, 679 [DEBUG] [ActiveMQ Session Task] SolrCloudIndexingSearcher: SolrClient start query: q=+(+_query_:"*:*"+)+&fl=id,parentnode&timeAllowed=600000&facet.threads=8&facet=true&facet.query=+(+_query_:"subject_std:*"+)+&facet.query=+(+_query_:"from_std:*"+)++OR++(+_query_:"senderDisplay_std:*"+)+&facet.query=+(+_query_:"recipients_std:*"+)+&facet.query=+(+_query_:"sdomain_std:*"+)++OR++(+_query_:"rdomain_std:*"+)+&facet.query=+(+_q
uery_:"filename_std:*"+)+&facet.query=+(+_query_:"filedata_std:*"+)+&facet.query=+(+_query_:"categories_std:*"+)+&facet.query=itemType:Mail&facet.query=itemType:PhoneMessage&facet.query=itemType:Appointment&facet.query=itemType:Task&facet.query=itemType:Note&facet.query=itemType:SMS&facet.query=itemType:MMS&facet.query=itemType:PhoneCall&facet.query=itemType:BBPIN&facet.query=itemType:BBMsg&facet.query=itemType:FB2Wall&facet.query=item
Type:FB2Friend&facet.query=itemType:WhatsAppMessage&facet.query=itemType:WeChatMessage&facet.query=itemType:LinkedInMessage&facet.query=itemType:FacebookMessage&facet.query=itemType:InstagramMessage&facet.query=itemType:YouTubeMessage&facet.query=itemType:TwitterMessage&facet.query=itemType:SharePointMessage&facet.query=itemType:SkypeMessage&facet.query=itemType:FB2Like&facet.query=itemType:FB2Event&facet.query=itemType:FB2Status&facet
.query=itemType:FB2Comment&facet.query=itemType:FB2Search&facet.query=itemType:FB2Forward&facet.query=itemType:FB2Group&facet.query=itemType:FB2WebMail&facet.query=itemType:FB2Media&facet.query=itemType:FB2PageRating&facet.query=boxType:received&facet.query=boxType:sent&facet.query=boxType:personal&facet.query=boxType:draft&facet.query=litigationHold:false&facet.query=litigationHold:true&facet.query=confidential:false&facet.query=confi
dential:true&facet.limit=20&facet.sort=count&facet.field=tags_facet&fq=+(uuid:52F3C401-164D-0000-BE6D-616965623035)+&start=0&rows=25
06:48:13, 257 [DEBUG] [ActiveMQ Session Task] SolrCloudIndexingSearcher: Search elapsed milliseconds in indexer=300578
06:52:36, 252 [TRACE] [ActiveMQ Session Task] SolrCloudIndexingSearcher: searching with offset: 0, count: 25
06:52:36, 253 [INFO ] [ActiveMQ Session Task] SolrCloudIndexingSearcher: Performing search of: ( _query_:"*:*" )
06:52:36, 253 [INFO ] [ActiveMQ Session Task] SolrCloudIndexingSearcher: start=0 rows=25
06:52:36, 255 [DEBUG] [ActiveMQ Session Task] SolrCloudIndexingSearcher: SolrClient start query: q=+(+_query_:"*:*"+)+&fl=id,parentnode&timeAllowed=600000&facet.threads=8&facet=true&facet.query=+(+_query_:"subject_std:*"+)+&facet.query=+(+_query_:"from_std:*"+)++OR++(+_query_:"senderDisplay_std:*"+)+&facet.query=+(+_query_:"recipients_std:*"+)+&facet.query=+(+_query_:"sdomain_std:*"+)++OR++(+_query_:"rdomain_std:*"+)+&facet.query=+(+_q
uery_:"filename_std:*"+)+&facet.query=+(+_query_:"filedata_std:*"+)+&facet.query=+(+_query_:"categories_std:*"+)+&facet.query=itemType:Mail&facet.query=itemType:PhoneMessage&facet.query=itemType:Appointment&facet.query=itemType:Task&facet.query=itemType:Note&facet.query=itemType:SMS&facet.query=itemType:MMS&facet.query=itemType:PhoneCall&facet.query=itemType:BBPIN&facet.query=itemType:BBMsg&facet.query=itemType:FB2Wall&facet.query=item
Type:FB2Friend&facet.query=itemType:WhatsAppMessage&facet.query=itemType:WeChatMessage&facet.query=itemType:LinkedInMessage&facet.query=itemType:FacebookMessage&facet.query=itemType:InstagramMessage&facet.query=itemType:YouTubeMessage&facet.query=itemType:TwitterMessage&facet.query=itemType:SharePointMessage&facet.query=itemType:SkypeMessage&facet.query=itemType:FB2Like&facet.query=itemType:FB2Event&facet.query=itemType:FB2Status&facet
.query=itemType:FB2Comment&facet.query=itemType:FB2Search&facet.query=itemType:FB2Forward&facet.query=itemType:FB2Group&facet.query=itemType:FB2WebMail&facet.query=itemType:FB2Media&facet.query=itemType:FB2PageRating&facet.query=boxType:received&facet.query=boxType:sent&facet.query=boxType:personal&facet.query=boxType:draft&facet.query=litigationHold:false&facet.query=litigationHold:true&facet.query=confidential:false&facet.query=confi
dential:true&facet.limit=20&facet.sort=count&facet.field=tags_facet&fq=+(uuid:52F3C401-164D-0000-BE6D-616965623035)+&start=0&rows=25
06:52:36, 341 [DEBUG] [ActiveMQ Session Task] SolrCloudIndexingSearcher: Search elapsed milliseconds in indexer=87

  • 0 in reply to   

    after the db is re-indexed maybe it will be working better,  This virtual machine has 25gb of ram and never looks busy.  We reboot it because apache or tomcat eventually fail and users can't search or login to retain for archived mail.

  • 0 in reply to   

    Well I did the "Re-index Failed messages" button yesterday and it seemed that some searches would not work.  I look in the logs today and I see a lot of searches after my reboot that look good but one at 8:36 AM that did not finish till around 8:42 AM.  The query results show a query that took around 5 minutes.

    When I do a * query it normally shows me the number of messages I have in retain instantly.  But there are some times it does not work till after this large burst of disk traffic.

    Here is proof that after the reboot I think retain users were still doing successful queries:

    retain:~ # cat  /opt/beginfinite/retain/tomcat/logs/RetainServer.2021-12-07.log | grep "Search elapsed milliseconds in"
06:45:53, 781[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=200
06:46:00, 446[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=1550
08:14:08, 393[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=2274
08:14:09, 066[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=1028
08:14:11, 071[ajp-nio-48009-exec-8] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=1213
08:14:19, 156[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=3315
08:14:19, 211[ajp-nio-48009-exec-9] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=595
08:14:23, 668[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=1253
08:14:35, 500[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=289
08:14:52, 082[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=257
08:15:04, 562[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=265
08:15:16, 971[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=258
08:18:48, 548[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=296
08:18:49, 956[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=54
08:19:04, 018[ajp-nio-48009-exec-8] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=457
08:19:04, 835[ajp-nio-48009-exec-2] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=184
08:20:21, 608[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=136
08:20:24, 278[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=64
08:20:25, 103[ajp-nio-48009-exec-3] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=62
08:20:25, 526[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=62
08:20:25, 695[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=53
08:20:49, 349[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=233
08:20:50, 487[ajp-nio-48009-exec-2] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=104
08:28:56, 712[ajp-nio-48009-exec-9] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=280
08:29:08, 237[ajp-nio-48009-exec-3] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=163
08:29:10, 166[ajp-nio-48009-exec-7] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=65
08:29:40, 141[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=241
08:29:41, 449[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=71
08:31:04, 804[ajp-nio-48009-exec-8] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=247
08:31:25, 658[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=61
08:34:39, 707[ajp-nio-48009-exec-7] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=341
08:34:40, 767[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=83
08:34:52, 789[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=54
08:34:54, 659[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=55
08:34:56, 717[ajp-nio-48009-exec-4] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=41
08:35:02, 713[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=158
08:35:04, 933[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=98
08:35:07, 956[ajp-nio-48009-exec-1] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=102
08:36:11, 225[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=244
08:36:15, 513[ajp-nio-48009-exec-8] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=341
08:36:16, 748[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=225
08:41:42, 351[ajp-nio-48009-exec-6] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=302449
08:41:43, 394[ajp-nio-48009-exec-7] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=179199
08:44:02, 977[ajp-nio-48009-exec-10] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=743
08:44:04, 208[ajp-nio-48009-exec-2] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=388
08:44:07, 678[ajp-nio-48009-exec-5] [TRACE] SearchAjaxCommon: Search elapsed milliseconds in RetainIndex=203

    3

  • 0   in reply to 

    Joe, try to see it in this way ...

    After a reboot or restart of services it will take some time until all processes are ready to work. Retain needs a strong coffee to be back on duty.

    Some people need the same strong coffee in the morning.

    However do not hesitate to open a case!

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    as you can see I had 41 successful searches until the one took about 5 minutes.  This server was rebooted at 6am and you can see the first person kicking the tires was 645 AM, so I would say 45 minutes is enough coffee.  It appears there is something wrong with our server doing a search with just the asterisk character.  Once it does that search once the rest of the day doing a * search is fast.

  • 0   in reply to 

    Yes, 45 minutes is too much coffee! Too dangerous for health. Let support check your system!

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    Hi Diethmar,

    it might be our firewall as our subnets are routed via a firewall that may have a timeout on stateless https traffic.

    I am going to do a server on the same subnet and see if that shows the results after 297000ms... :-)  I also want to see if the timeout is apache, tomcat or javascript and see if I can extend that.  This server is not on the internet so I am not concerned at the moment about DOS protection measures.

    Thanks,

    Joe

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.