none
Could not connect to Config Server RRS feed

  • Question

  • Hi,

    I've installed ESP 5.3 with SP3 slipstreamed as a single-node on a Windows Server 2008 R2 64-bit virtual guest. The installation worked as excepted, but when I go to the ESP Admin GUI, I get the error below:

    Could not connect to Config Server at host ... port 16005

    All services are running according to nctrl status, the forward and reverse nslookup are also working. This is the configserver.log:

    [2011-06-08 12:22:42.201] VERBOSE    systemmsg Starting Config Server on port 16005 (PID: 2068)
    [2011-06-08 12:22:42.232] INFO       systemmsg Found more recent tmp config file: c:\esp\etc\CSConfig.xml.swp
    [2011-06-08 12:22:42.232] INFO       systemmsg Found more recent tmp config file: c:\esp\etc\PipelineConfig.xml.swp
    [2011-06-08 12:22:42.342] INFO       systemmsg Found more recent tmp config file: c:\esp\etc\CSUniCfg.xml.swp
    [2011-06-08 12:22:42.373] INFO       systemmsg Started Config Server on port 16005 (PID: 2068)
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:14196 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:16700 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:16200 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:16065 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:16710 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:16098 raised exception - socket.error: [Errno 10061] Connection refused.
    [2011-06-08 12:22:43.264] WARNING    systemmsg ReRegister() to module at myserver.mycompany.com:14000 raised exception - socket.error: [Errno 10061] Connection refused.
    old errno: 3
    new errno: 2
    old errno: 3
    new errno: 2
    old errno: 3
    new errno: 2
    ..
    ..
    old errno: 3
    new errno: 2
    old errno: 3
    new errno: 2
    old errno: 3
    new errno: 2
    old errno: 3
    new errno: 2
    [2011-06-08 12:23:42.043] VERBOSE    systemmsg Inactive CORBA module 'ContentDistributor' at n/a responded to our pings, reregistering
    [2011-06-08 12:23:42.045] VERBOSE    systemmsg CORBA Module (ContentDistributor) has changed from 'n/a:0' to 'myserver.mycompany.com:16100'
    [2011-06-08 12:23:42.410] VERBOSE    systemmsg Inactive CORBA module 'ResourceService' at n/a responded to our pings, reregistering
    [2011-06-08 12:23:42.429] VERBOSE    systemmsg CORBA Module (ResourceService) has changed from 'n/a:0' to 'myserver:16095'
    [2011-06-08 12:23:42.773] VERBOSE    systemmsg Inactive CORBA module 'DeploymentManager' at n/a responded to our pings, reregistering
    [2011-06-08 12:23:42.786] VERBOSE    systemmsg CORBA Module (DeploymentManager) has changed from 'n/a:0' to 'myserver:16093'
    [2011-06-08 12:23:42.918] VERBOSE    systemmsg Inactive CORBA module 'IndexingDispatcher (webcluster)' at n/a responded to our pings, reregistering
    [2011-06-08 12:23:42.920] VERBOSE    systemmsg CORBA Module (IndexingDispatcher (webcluster)) has changed from 'n/a:0' to 'myserver.mycompany.com:0'
    [2011-06-08 12:24:43.062] WARNING    systemmsg Module (WebAnalyzer) at myserver.mycompany.com:16700 is not responding
    [2011-06-08 12:24:43.062] VERBOSE    systemmsg The ping call resulted in the following exception: Timeout
    [2011-06-08 12:24:43.062] VERBOSE    systemmsg Module (WebAnalyzer) at myserver.mycompany.com:16700 not responding, marking as inactive
    [2011-06-08 12:24:53.446] VERBOSE    systemmsg Inactive module at myserver.mycompany.com:16700 responded to our pings, requesting registration

    Any tips?

     

     

     


    Brgds Jonas
    Wednesday, June 8, 2011 12:23 PM

Answers

  • Hi Jonas,

     

    Please make sure you have completely disabled IPv6.  The release notes include the following statement: ESP does not support IPv6, neither on server nor on network. Since IPv6 is enabled by default on Windows 2008, this has to be disabled before installing and running ESP. A workaround is to create a DWORD registry key with value 0xFF at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6 \Parameters\DisabledComponents. Reboot the server after this change, and run 'ping localhost' - should be directed to '127.0.0.1'. (Before this, a ping to localhost would result in 'Reply from ::1: time<1ms').

     

    Also, please note that you should at least install esp.5.3.sp3.searchengine.patch02 for ESP to be supported on 2008 R2, although we would recommend installing SP4 and the latest patches on top of it.

     

    Thanks,

    Patrick

     


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch
    Wednesday, June 8, 2011 12:41 PM

All replies

  • Hi Jonas,

     

    Please make sure you have completely disabled IPv6.  The release notes include the following statement: ESP does not support IPv6, neither on server nor on network. Since IPv6 is enabled by default on Windows 2008, this has to be disabled before installing and running ESP. A workaround is to create a DWORD registry key with value 0xFF at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6 \Parameters\DisabledComponents. Reboot the server after this change, and run 'ping localhost' - should be directed to '127.0.0.1'. (Before this, a ping to localhost would result in 'Reply from ::1: time<1ms').

     

    Also, please note that you should at least install esp.5.3.sp3.searchengine.patch02 for ESP to be supported on 2008 R2, although we would recommend installing SP4 and the latest patches on top of it.

     

    Thanks,

    Patrick

     


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch
    Wednesday, June 8, 2011 12:41 PM
  • Hi Patrick,

    I have disabled IPv6 in my FAST Search for SharePoint 2010 installation, and still can see the same messages:

    From ConfigFile:

    [2012-02-08 10:42:31.283] WARNING    systemmsg ConfigurationChanged(ProcessorServer, ('tpatgicfst02.takedapharm.tpna.com', 13398)) to module at tpatgicfst02.takedapharm.tpna.com:13398 timed out, putting message to the inactive queue since 5 requeues failed
    [2012-02-08 10:42:33.221] WARNING    systemmsg ConfigurationChanged(ProcessorServer, ('tpatgicfst02.takedapharm.tpna.com', 13395)) to module at tpatgicfst02.takedapharm.tpna.com:13395 timed out, putting message to the inactive queue since 5 requeues failed
    [2012-02-08 10:42:41.814] WARNING    systemmsg ConfigurationChanged(ProcessorServer, ('tpatgicfst02.takedapharm.tpna.com', 13396)) to module at tpatgicfst02.takedapharm.tpna.com:13396 timed out, putting message to the inactive queue since 5 requeues failed
    [2012-02-08 10:42:44.142] WARNING    systemmsg ConfigurationChanged(ProcessorServer, ('tpatgicfst02.takedapharm.tpna.com', 13398)) to module at tpatgicfst02.takedapharm.tpna.com:13398 timed out, requeueing into the inactive queue
    [2012-02-08 10:42:46.314] WARNING    systemmsg ConfigurationChanged(ProcessorServer, ('tpatgicfst02.takedapharm.tpna.com', 13397)) to module at tpatgicfst02.takedapharm.tpna.com:13397 timed out, requeueing into the inactive queue
    [2012-02-08 10:42:49.142] WARNING    systemmsg Module (ProcessorServer) at tpatgicfst03.takedapharm.tpna.com:13397 is not responding
    [2012-02-08 10:42:49.142] VERBOSE    systemmsg The ping call resulted in the following exception: socket.error: [Errno 10060] The operation timed out.
    [2012-02-08 10:42:49.142] VERBOSE    systemmsg Module (ProcessorServer) at tpatgicfst03.takedapharm.tpna.com:13397 not responding, marking as inactive
    [2012-02-08 10:42:49.142] WARNING    systemmsg Module (ProcessorServer) at tpatgicfst03.takedapharm.tpna.com:13398 is not responding
    [2012-02-08 10:42:49.142] VERBOSE    systemmsg The ping call resulted in the following exception: socket.error: [Errno 10060] The operation timed out.
    [2012-02-08 10:42:49.142] VERBOSE    systemmsg Module (ProcessorServer) at tpatgicfst03.takedapharm.tpna.com:13398 not responding, marking as inactive
    [2012-02-08 10:42:49.142] WARNING    systemmsg Module (ProcessorServer) at tpatgicfst03.takedapharm.tpna.com:13396 is not responding

    I am not sure if this issue is causing indexing latency getting worse and worse. I am getting 2 docs every five minutes, really small xml files.

    Any other suggestions?

    Thanks

    Thursday, February 9, 2012 8:09 PM