Deployment Architecture

I removed a host from serverclass.conf for an app deployed via deployment server, why was the app not removed from that client until a manual restart?

sameera123
Explorer

I had pushed one app through deployment servers to 4 hosts.
Now we have removed one of the host entries from the serverclass.conf for that particular app, which means that it should delete the app from that host in which it was removed from the serverclass.conf.

But unfortunately, that App didn't get removed from that host. It was only removed after restarting the forwarder.

Do we really need to log on to the forwarders and restart the service to fully remove an app? Is there any other way to do this? Can you please explain?

0 Karma

Splunker2911
Loves-to-Learn

If you are removing client from a Serverclass on Forwarder Management, you need to checkin 'Restart Splunk' option availble on the deployed app and save it. After this, you can reload serverclass on CLI of Deployment server for the changes to take affect. And this will remove the app configuration on the host.

0 Karma

jitsinha
Path Finder

you can use following property in individual serverclass stanzas for auto restart.

restartSplunkd = true | false
* If true, restarts splunkd on the client when a member app or a directly configured app is updated.
* Can be overridden at the serverClass level and the serverClass:app level.
* Defaults to false

0 Karma
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...