All Apps and Add-ons

Alert manager exec errors in cluster

manderson7
Contributor

Since we've added our indexers into a cluster, we're getting the following exec error message:

message from  "/opt/splunk/etc/slave-apps/alert_manager/bin/alert_manager_scheduler.sh"
python: can't open file '/opt/splunk/etc/apps/alert_manager/bin/alert_manager_scheduler.py':
[Errno 2] No such file or directory

Which makes sense, because the apps are being deployed deployed to etc/slave-apps now. So I can change the .sh script to point to etc/slave-apps/alert-manager/bin/alert_manager_scheduler.py.
However, We're also deploying to our search heads, and the app will reside in etc/apps. So changing the path will break the script on the search heads. Can I just add the slave-apps path to the script and have both run, and one will work on the search heads and one will work on the indexers, and just live with the error messages that happen? Or will that cause the end of the world?

0 Karma
1 Solution

JDukeSplunk
Builder

Maybe put a symlink on the indexers? Won't have to worry about version creep on the files.

View solution in original post

JDukeSplunk
Builder

Maybe put a symlink on the indexers? Won't have to worry about version creep on the files.

0 Karma

manderson7
Contributor

Smart idea, thanks man.

0 Karma

JDukeSplunk
Builder

Maybe put a symlink on the indexers? Won't have to worry about version creep on the files.

Get Updates on the Splunk Community!

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to ...

Announcing the Migration of the Splunk Add-on for Microsoft Azure Inputs to Officially Supported Splunk ...