You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug man keepalived states that the exit codes should be the following:
0 if OK
1 if unable to malloc memory
2 if cannot initialise subsystems
3 if running with --config-test and configuration cannot be run
4 if running with --config-test and there are configuration errors
but keepalived will run after modifying the configuration
5 if running with --config-test and script security hasn't been
enabled but scripts are configured.
But I get return code 6 when running keepalived --config-test --use-file example.conf versus a config file with no script security enabled and scripts configured.
To Reproduce
Any steps necessary to reproduce the behaviour:
Build docker image, run it with --entrypoint /bin/ash and exec to container
Paste the configuration from the configuration file section to example.conf
keepalived --config-test --use-file example.conf
echo $?
Expected behavior
Keepalived --config-test exits with exit code 5
Distro (please complete the following information):
Name: alpine
Version: 3.20.2
Architecture: x86_64
Details of any containerisation or hosted service (e.g. AWS)
Keepalived is run in alpine container built by make docker
Configuration file:
virtual_server_group test {
<ommited>
}
virtual_server group test {
lvs_sched mh
lvs_method TUN
protocol TCP
real_server <ommited> {
delay_loop 5
HTTP_GET {
http_protocol 1.1
url {
path /
status_code 200-400
}
}
MISC_CHECK {
misc_path /bin/ash
}
}
}
Notify and track scripts
None
System Log entries
SECURITY VIOLATION - check scripts are being executed but script_security not enabled.
// Not really system logs, but the output of keepalived --config-test
Describe the bug
man keepalived
states that the exit codes should be the following:But I get return code 6 when running
keepalived --config-test --use-file example.conf
versus a config file with no script security enabled and scripts configured.To Reproduce
Any steps necessary to reproduce the behaviour:
--entrypoint /bin/ash
andexec
to containerexample.conf
keepalived --config-test --use-file example.conf
echo $?
Expected behavior
Keepalived --config-test exits with exit code 5
Keepalived version
Distro (please complete the following information):
Details of any containerisation or hosted service (e.g. AWS)
Keepalived is run in alpine container built by
make docker
Configuration file:
Notify and track scripts
System Log entries
Did keepalived coredump?
Additional context
I believe this enum
is the cause.
I suggest refining manpages and docs.
The text was updated successfully, but these errors were encountered: