Deployment Architecture

Odd Deployment Server Log Entry - Received message for an unsubscribed channel

Communicator

HttpPubSubConnection - Received message for an unsubscribed channel: deploymentServer/phoneHome/default/reply/host.com/deploymentClient

What does this mean? It seems like my deployment clients are being disconnected for an unknown reason.

Tags (1)

Communicator

In reference to SPL-30820... I'm on 4.1.3 and everything works yet I get a bunch of these:


08-11-2010 09:43:52.389 WARN DeploymentClient - Unable to send phonehome message to deployment server. Error status is: not_connected

08-11-2010 09:44:01.997 WARN DeploymentClient - Unable to send phonehome message to deployment server. Error status is: not_connected

08-11-2010 09:45:12.026 WARN NetUtils- Bad select for loop rv = -2

08-11-2010 09:45:12.026 WARN DeploymentClient - Unable to send phonehome message to deployment server. Error status is: not_connected

08-11-2010 09:45:22.536 WARN DeploymentClient - Unable to send phonehome message to deployment server. Error status is: not_connected

Hopefully they will go away with the upgrade to 4.1.4

Contributor

I am on 4.1.7 - i do have the same issue

0 Karma

Explorer

Hmm... I'm on 4.2.3 - still the same problem here...

Motivator

I am experiencing the same or at least very similar issue. I currently have case 44485 open, and apparently this is a known defect, SPL-30820. It appears to be an issue with SSL connections between deployment client and server. The scheduled target release as far as I know is 4.1.4.

Splunk Employee
Splunk Employee

Add in the following stanza to server.conf:

sessionTimeout = * The amount of time before a user session times out, expressed as a search-like time range * Examples include '24h' (24 hours), '3d' (3 days), '7200s' (7200 seconds, or two hours) * Defaults to '1h' (1 hour) example: sessionTimeout=8h

Communicator

I believe that is the session timeout for logged in users and has nothing to do with the SSL problem. 1 hour to do an SSL handshake? OUCH

0 Karma

Engager

I'm having the same problem - the message You presented in my case is actually following this one:

WARN DeploymentClient - Unable to send handshake message to deployment server. Error status is: not_connected

I have seen the same warning in question 2510 - unfortunatelly the user failed to solve this problem. Can anyone help with it? I just can't get the deployment running on Splunk 4.x to which we're trying to migrate.

Both sides have SSL enabled and are accepting connections on the standard 8089 ports. Both configurations are as simple as the first examples in the Documentation.

If anyone knows solution for this, please advise.

Thanks.

Don’t Miss Global Splunk
User Groups Week!

Free LIVE events worldwide 2/8-2/12
Connect, learn, and collect rad prizes and swag!