03:39:31.09 INFO  ==> about to run the command: timeout 90 valkey-cli -h valkey.openstack.svc.cluster.local -p 26379 --tls --cert /opt/bitnami/valkey/certs/tls.crt --key /opt/bitnami/valkey/certs/tls.key --cacert /opt/bitnami/valkey/certs/ca.crt sentinel get-primary-addr-by-name atmosphere
1:X 08 Jun 2026 03:42:41.299 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1:X 08 Jun 2026 03:42:41.299 * Valkey version=8.0.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:X 08 Jun 2026 03:42:41.299 * Configuration loaded
1:X 08 Jun 2026 03:42:41.299 * monotonic clock: POSIX clock_gettime
1:X 08 Jun 2026 03:42:41.300 * Running mode=sentinel, port=26379.
1:X 08 Jun 2026 03:42:41.390 * Sentinel ID is ec189fc48ec98a607fe05216e70822709d7fb45d
1:X 08 Jun 2026 03:42:41.390 # +monitor master atmosphere valkey-node-0.valkey-headless.openstack.svc.cluster.local 6379 quorum 2
1:X 08 Jun 2026 04:58:40.094 # Error accepting a client connection: error:0A000126:SSL routines::unexpected eof while reading (addr= laddr=127.0.0.1:26379)
1:X 08 Jun 2026 04:58:40.107 # waitpid() returned a pid (12473) we can't find in our scripts execution queue!