locked
fast 5.0.9 RRS feed

  • Question

  • Hi all,

     

    I am receiving the following errors in fast 5.0.9 Error received while searching tcp/servername :15150. Error: [18] No engine available for partition 0 No engine available for partition 1  Is there any sollutions about it?

     

    Best regards:

     

    Vladimir

     

     

    Wednesday, November 2, 2011 3:18 PM

Answers

  • Hello,

     

    The error [18] represents a 1018 error, which means that one or more partitions listed in the engines file could not be reached.  The cause for the issue should be able to be identified by a review of the %fastsearch%var\log\searchctrl logs for indicated partitions for all search nodes.  This problem is sometimes associated with core files being created in %fastsearcg%\bin.  You can let us know what is appearing in the searchctrl logs, but the best method to address this problem is for a new ticket be opened with Technical Support.

     

    Thanks!

    Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support

    Customer Service & Support                          Microsoft | Services

    • Proposed as answer by Rob Va - MSFT Friday, December 9, 2011 7:27 PM
    • Marked as answer by Rob Va - MSFT Friday, December 16, 2011 9:56 PM
    Thursday, December 1, 2011 9:13 PM

All replies

  • Hi Vladimir,

     

    The error 18 Do you see any non-response or outages reported in the fdispatch-15700.log?  Example:
    [2011-10-04 13:06:54.698] INFO fdispatch Search node fastnode1.domain.com:15725 up, partition 2, docstamp 1317681340

    [2011-10-04 13:07:53.478] WARNING fdispatch Search node fastdomain1.prod.f2.com.au:15725 down

     

    Also, do you see any errors in your fsearch logs?

     

    The nature of this issue can be critical, and I would suggest opening a service request with our Technical Support team for this issue.

     

    Also, just so you are aware, per our Microsoft Product Lifecycle page (http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=fast), after Dec 31, 2011, ESP 5.0.9 will be out of mainstream and extended support.  Do you have plans to move to a supported version of ESP, such as 5.3l or FastSearch for SharePoint?

     

    Thanks!

    Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support

    Customer Service & Support                          Microsoft | Services

    Wednesday, November 2, 2011 8:48 PM
  • Hello Rob,

    I have the same exact issue, and the errors you have posted are also exist. please advise what was might be causing this issue as well as what might also save this issue?

     

    but thing is Search is working fine on our website,,,

    Thanks very Much inadvance...

     

    Wednesday, November 9, 2011 9:17 AM
  • Thanks Rob,

     

    yep I am seeing them from time to time too

     

    I have got also :

     

     fdispatch (15700): Unable to start fsearch. Search node has problems, stopping fdispatch. 

     fsearch (1_288): Waiting for port range to become available 

     

    are those part of that issue too or it is something else?

     

    Best Regards


    Friday, November 11, 2011 10:08 AM
  • Hi Vladimir,

     

    Are you running on a Unix System?

    If so run a ps and see which processes are started from your fast user.

    It is pritty possible that you have not terminated processes (for exampel open and not used shell sessions, double fdispatch processes on the same partiotion and so on). Check on this and if so you need to kill the not terminated processes.

    Thursday, December 1, 2011 4:42 PM
  • Hello,

     

    The error [18] represents a 1018 error, which means that one or more partitions listed in the engines file could not be reached.  The cause for the issue should be able to be identified by a review of the %fastsearch%var\log\searchctrl logs for indicated partitions for all search nodes.  This problem is sometimes associated with core files being created in %fastsearcg%\bin.  You can let us know what is appearing in the searchctrl logs, but the best method to address this problem is for a new ticket be opened with Technical Support.

     

    Thanks!

    Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support

    Customer Service & Support                          Microsoft | Services

    • Proposed as answer by Rob Va - MSFT Friday, December 9, 2011 7:27 PM
    • Marked as answer by Rob Va - MSFT Friday, December 16, 2011 9:56 PM
    Thursday, December 1, 2011 9:13 PM