topic Re: deployment server clients not showing up in Deployment Architecture

deployment server clients not showing up

dglass0215 — Tue, 17 Sep 2019 15:48:19 GMT

Hello,

When I view the deployment clients under forwarder management, not all my clients are being displayed. Every time I add a client, I can see that the client indeed does download the apps but is not displayed as a client. Currently the deployment server lists 40 clients. And every time I add a client it just stays at 40. Any help is appreciated.

David

Re: deployment server clients not showing up

harsmarvania57 — Wed, 18 Sep 2019 08:32:56 GMT

Can you please confirm whether new universal forwarder has different GUID ? You can find GUID in $SPLUNK_HOME/etc/instance.cfg on Universal Forwarder.

Re: deployment server clients not showing up

gcusello — Wed, 30 Sep 2020 02:13:17 GMT

Hi dglass0215,
new clients are installed or cloned by another one? if cloned, check hostname in $SPLUNK_HOME/etc/system/local/server.conf and $SPLUNK_HOME/etc/system/local/inputs.conf.

Bye.
Giuseppe

Re: deployment server clients not showing up

dglass0215 — Wed, 18 Sep 2019 14:05:48 GMT

I think this is the problem! Gotta love splunk answers! Faster response then actual support!

However why would I have multiple machines with the same GUID in instance.cfg, and more importantly, What do i do to fix it?

Thanks!

Re: deployment server clients not showing up

harsmarvania57 — Wed, 18 Sep 2019 14:15:15 GMT

If you are cloning machines or splunk forwarder is installed in base image then you'll get same GUID on all new server installation.

To clear GUID on new builds, follow this process https://docs.splunk.com/Documentation/Forwarder/7.3.1/Forwarder/Makeauniversalforwarderpartofahostimage

To create new GUID on existing installation, perform below steps (When you perform below steps, double check hostname in $SPLUNK_HOME/etc/system/local/server.conf and $SPLUNK_HOME/etc/system/local/inputs.conf , if those are not correct then you can change those when you are performing below steps)

Stop Splunk
Remove $SPLUNK_HOME/etc/instance.cfg
Start Splunk (This will create new instance.cfg automatically)