10:12:44.86 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 02 Jul 2026 10:15:55.063 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1:X 02 Jul 2026 10:15:55.063 * Valkey version=8.0.2, bits=64, commit=00000000, modified=1, pid=1, just started
1:X 02 Jul 2026 10:15:55.063 * Configuration loaded
1:X 02 Jul 2026 10:15:55.063 * monotonic clock: POSIX clock_gettime
1:X 02 Jul 2026 10:15:55.063 * Running mode=sentinel, port=26379.
1:X 02 Jul 2026 10:15:55.066 * Sentinel ID is ec189fc48ec98a607fe05216e70822709d7fb45d
1:X 02 Jul 2026 10:15:55.066 # +monitor master atmosphere valkey-node-0.valkey-headless.openstack.svc.cluster.local 6379 quorum 2
1:X 02 Jul 2026 10:49:35.261 # +tilt #tilt mode entered
1:X 02 Jul 2026 10:50:05.326 # -tilt #tilt mode exited
1:X 02 Jul 2026 11:00:19.561 # +tilt #tilt mode entered
1:X 02 Jul 2026 11:00:49.661 # -tilt #tilt mode exited
1:X 02 Jul 2026 11:21:23.067 # +tilt #tilt mode entered
1:X 02 Jul 2026 11:21:53.127 # -tilt #tilt mode exited
1:X 02 Jul 2026 11:22:12.761 # +tilt #tilt mode entered
1:X 02 Jul 2026 11:22:12.761 # Error accepting a client connection: Connection reset by peer (addr= laddr=127.0.0.1:26379)
1:X 02 Jul 2026 11:22:12.861 # waitpid() returned a pid (10918) we can't find in our scripts execution queue!
1:X 02 Jul 2026 11:22:42.801 # -tilt #tilt mode exited