-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
st2actionrunner talk to redis question #423
Comments
2024-07-01 11:07:48,299 INFO [-] Using config files: /etc/st2/st2.conf,/etc/st2/st2.docker.conf,/etc/st2/st2.user.conf |
thanks @fdrab for your input. the st2 services are having problems locating the redis master. any help you or other people can provide is appreciated. error message for st2api. my st2scheduler has the similar error message of not able to locate redis master
here is my setup for redis
redis values.yaml
in st2client pod, using redis-cli, i was able to locate my redis master
|
can't say I'm an expert on any of this, what does your redis section of the values.yaml look like? |
did you solve this? |
For anyone facing this, set the redis.sentinel.usePassword to false explicitly. the default value is true. Also avoid having "=" in password (maybe some other special chars as well) as they get url encoded. |
no. i switched my redis setup to a master-secondary mode instead of using the sentinel mode. this got me going for now. |
how does the st2actionrunner know what ip and port the redis server is running on?
I would expect some sort of environment variable passed into the action runner container but I don't see that.
Is the redis port somehow mapped to all pods?
The text was updated successfully, but these errors were encountered: