https://community.splunk.com/t5/Getting-Data-In/HttpPubSubConnection-Unable-to-parse-message-from-PubSubSvr/m-p/432600#M95293 <P>Hi @analiaeg ,</P> <P>There could be several reasons to that log message...</P> <UL> <LI>Depending on the other messages before/after it, there could be a network connection issue between your Deployment client (DC) and Deployment server (DS). Please make sure there is no firewalls in between blocking the 8089 port that is needed for communication. One way to test the connection between the DS and DC is the telnet command to port 8089 on the DC to DS. Usually it is the case where there is a network connectivity issue somewhere with most customers.</LI> <LI>Or there have been cases where the sslPassword in server.conf under the "[sslConfig]" stanza maybe have been changed from the default (if you are using the default Splunk server.pem cert). Otherwise, it may not be the correct sslPassword for your own imported SSL server certificate.</LI> </UL> <P>More information about this stanza can be found here for your reference.</P> <PRE><CODE>&gt; server.conf sslPassword = &lt;password&gt; * Server certificate password. * Default is "password". </CODE></PRE> <P><A href="http://docs.splunk.com/Documentation/Splunk/7.1.1/admin/Serverconf">http://docs.splunk.com/Documentation/Splunk/7.1.1/admin/Serverconf</A></P> Sun, 28 Apr 2019 10:30:06 GMT rjteh_splunk 2019-04-28T10:30:06Z https://community.splunk.com/t5/Getting-Data-In/HttpPubSubConnection-Unable-to-parse-message-from-PubSubSvr/m-p/432599#M95292 <P>Does anybody why we have this error on Splunkd.log / index=_internal:</P> <P><STRONG>HttpPubSubConnection - Unable to parse message from PubSubSvr</STRONG></P> <P>Thank you in advance.</P> Fri, 26 Apr 2019 10:43:49 GMT https://community.splunk.com/t5/Getting-Data-In/HttpPubSubConnection-Unable-to-parse-message-from-PubSubSvr/m-p/432599#M95292 analiaeg 2019-04-26T10:43:49Z https://community.splunk.com/t5/Getting-Data-In/HttpPubSubConnection-Unable-to-parse-message-from-PubSubSvr/m-p/432600#M95293 <P>Hi @analiaeg ,</P> <P>There could be several reasons to that log message...</P> <UL> <LI>Depending on the other messages before/after it, there could be a network connection issue between your Deployment client (DC) and Deployment server (DS). Please make sure there is no firewalls in between blocking the 8089 port that is needed for communication. One way to test the connection between the DS and DC is the telnet command to port 8089 on the DC to DS. Usually it is the case where there is a network connectivity issue somewhere with most customers.</LI> <LI>Or there have been cases where the sslPassword in server.conf under the "[sslConfig]" stanza maybe have been changed from the default (if you are using the default Splunk server.pem cert). Otherwise, it may not be the correct sslPassword for your own imported SSL server certificate.</LI> </UL> <P>More information about this stanza can be found here for your reference.</P> <PRE><CODE>&gt; server.conf sslPassword = &lt;password&gt; * Server certificate password. * Default is "password". </CODE></PRE> <P><A href="http://docs.splunk.com/Documentation/Splunk/7.1.1/admin/Serverconf">http://docs.splunk.com/Documentation/Splunk/7.1.1/admin/Serverconf</A></P> Sun, 28 Apr 2019 10:30:06 GMT https://community.splunk.com/t5/Getting-Data-In/HttpPubSubConnection-Unable-to-parse-message-from-PubSubSvr/m-p/432600#M95293 rjteh_splunk 2019-04-28T10:30:06Z