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!

Finding Based Detections General Availability

Overview  We’ve come a long way, folks, but here in Enterprise Security 8.4 I’m happy to announce Finding ...

Get Your Hands Dirty (and Your Shoes Comfy): The Splunk Experience

Hands-On Learning and Technical Seminars  Sometimes, you just need to see the code. For those looking for a ...

What’s New in Splunk Observability Cloud: January Feature Highlights & Deep Dives

Splunk Observability Cloud continues to evolve, empowering engineering and operations teams with advanced ...