Deployment Architecture

Why am I unable to add the deployment server as a search peer to the Distributed Management Console?

brdr
Contributor

Hi Support,

I'm configuring Distributed Management Console. The DMC will reside on cluster master. I've added indexers, search head, license master, and now trying to add the deployment server (ourserver) for DMC to monitor. When I go into Distributed search on DMC, I get following messages (see below) when adding deployment server. How do I go about adding the deployment server to the 'Overview', distributed topology? Thx.

08-01-2016 12:10:40.713 -0400 ERROR HttpClientRequest - HTTP client error: Connection reset by peer (while accessing http://ourserver:8089/services/server/info)
08-01-2016 12:10:40.713 -0400 WARN  AdminHandler:DistributedSearchHandler - While attempting to add peer at uri=http://ourserver:8089 , no http response was received with a Date header.  Cannot check skew.
08-01-2016 12:10:40.713 -0400 INFO  KeyManagerLocalhost - Sending public key to search peer: http://ourserver:8089
0 Karma
1 Solution

sjohnson_splunk
Splunk Employee
Splunk Employee

Usually when you connect to the management port you should be using https://ourserver:8089 NOT http.

View solution in original post

sjohnson_splunk
Splunk Employee
Splunk Employee

Usually when you connect to the management port you should be using https://ourserver:8089 NOT http.

brdr
Contributor

Doh! Thx for pointing that out. All okay now.

0 Karma
Get Updates on the Splunk Community!

Splunk Community Platform Survey

Hey Splunk Community, Starting today, the community platform may prompt you to participate in a survey. The ...

Observability Highlights | November 2022 Newsletter

 November 2022Observability CloudEnd Of Support Extension for SignalFx Smart AgentSplunk is extending the End ...

Avoid Certificate Expiry Issues in Splunk Enterprise with Certificate Assist

This blog post is part 2 of 4 of a series on Splunk Assist. Click the links below to see the other ...