Deployment Architecture

Why deployment of updated app through deployment server is not working?

manjunathmeti
Champion

I am trying to deploy updated apps through deployment server. Except one app all other apps are deployed, I checked logs there is checksum mismatch and client downloaded the app to a .bundle file but it is not installing. But when I deleted the old version of that app in clients app folder(etc/apps) then tried to deploy the new one, it worked! It happens with only one app there is no problems with others. Can anyone explain why this is happening?

Also saved_searches, macros and lookups are packaged in that app, does it causing problems?

0 Karma

s2_splunk
Splunk Employee
Splunk Employee

OK, so if you are using search head clustering (SHC), you cannot use the deployment server to distribute your apps, but need to use the SHC deployer instead.
Please review the documentation here, it clearly states at the top that:

Caution: You must use the deployer, not the deployment server, to distribute apps to cluster members. Use of the deployer eliminates the possibility of conflict with the run-time updates that the cluster replicates automatically by means of the mechanism described in "Configuration updates that the cluster replicates."
0 Karma

manjunathmeti
Champion

Actually I am using SHC deployer to deploy apps to search heads not deployment server! but still getting the same warning in logs. But there is no problem with another app deployed through same SHC deployer to SHs.

0 Karma

ppablo
Retired

Hi @manjunathmeti

I'm going to edit your post for clarity, but to make sure everything is clear for other users, you were actually using the SHC Deployer to update apps on the SHC Members this entire time, correct? Did you ever use the Deployment Server accidentally? You mentioned clients in your question which usually refers to deployment clients when talking about updating apps via deployment server.

SHC Deployer -> SHC Members (search heads)
Deployment Sever -> Deployment Clients (forwarders)

The warning you received sounds like you tried using the deployment server to override an app on SHC members.

0 Karma

s2_splunk
Splunk Employee
Splunk Employee

What log messages exactly do you see in splunkd.log on the deployment client? Are there no other messages that indicate why the the app may not have been installed?
Could be a problem with file permissions.

0 Karma

manjunathmeti
Champion

This is the warning I got: mysplunkapp was already installed via search head cluster deployer, UI, CLI, or REST API; it may not be overridden via deployment server; remove existing app=mysplunkapp via search head cluster deployer, UI, CLI, or REST API if you wish to install it via deployment server.

0 Karma
Get Updates on the Splunk Community!

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...

SignalFlow: What? Why? How?

What is SignalFlow? Splunk Observability Cloud’s analytics engine, SignalFlow, opens up a world of in-depth ...

Federated Search for Amazon S3 | Key Use Cases to Streamline Compliance Workflows

Modern business operations are supported by data compliance. As regulations evolve, organizations must ...