-
-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vrrp_script; Cannot find script docker in path - disabling #2381
Comments
As it says, keepalived cannot find the executable Further, keepalived does not manage a pipeline of processes; you need a shell to do that, so you need to create an executable script:
and suppose it is Also, keepalived does not read the stdout of a script that it executes, but retrieves the exit code, so you need to change the script to be:
This will exit with 1 (failure) if there is a container with the name haproxy, and 0 (success) if there is no such container. This may be the opposite of what you want. |
Thank you both, but its an issue with Keepalived and SElinux the solution is to use an external script and put it in the specified directory using this guide https://opensource-db.com/working-with-keepalived-and-selinux-ensuring-ha-and-security/
I found setting permissions as This took us days to figure out, so hopefully this will help someone :) |
Describe the bug
Keepalived is not running the one-liner that checks to see if a container is running or not running.
To Reproduce
Running the following;
gives the following error;
```Cannot find script docker in path - disabling````
Also the following is quite confusing, is this related?
Script user 'keepalived_script' does not exist
Expected behavior
The script should run
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS)
N/A
Configuration file:
Notify and track scripts
System Log entries
Did keepalived coredump?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: