Hi everyone, I hope everyone is fine ![]()
- Redis version: 6.0
- Icinga 2 version (
icinga2 --version): 2.15.0 - Icinga DB version (
icingadb --version): 1.4.0-gc271de7 - Server operating system and version: Debian12
- Docker version: 28.1.1
All my icinga components are running under docker.
I am currently trying to make an icinga master working with redis sentinel.
Icingadb does connect through the sentinel port but doesn’t recognize any commands except for “info”…
2025-08-07T08:08:37.200Z INFO icingadb Connecting to Redis at 'redis+tls://XX.XX.XX.XX:YYYYY'
2025-08-07T08:08:37.224Z FATAL icingadb ERR unknown command `xread`, with args beginning with: `block`, `1000`, `streams`, `icinga:schema`, `0-0`,
can't perform "[xread block 1000 streams icinga:schema 0-0]"
github.com/icinga/icinga-go-library/redis.WrapCmdErr
github.com/icinga/icinga-go-library@v0.7.2/redis/utils.go:15
github.com/icinga/icinga-go-library/redis.(*Client).XReadUntilResult
github.com/icinga/icinga-go-library@v0.7.2/redis/client.go:282
main.checkRedisSchema
github.com/icinga/icingadb/cmd/icingadb/main.go:390
main.run
github.com/icinga/icingadb/cmd/icingadb/main.go:98
main.main
github.com/icinga/icingadb/cmd/icingadb/main.go:37
runtime.main
runtime/proc.go:283
runtime.goexit
runtime/asm_amd64.s:1700
can't read Redis schema version
main.checkRedisSchema
github.com/icinga/icingadb/cmd/icingadb/main.go:394
main.run
github.com/icinga/icingadb/cmd/icingadb/main.go:98
main.main
github.com/icinga/icingadb/cmd/icingadb/main.go:37
runtime.main
runtime/proc.go:283
runtime.goexit
runtime/asm_amd64.s:1700
When I try to reach the redis instance behind sentinel, directly on its port, it just works fine. Schema is read, and icingadb is ready to write into it.
I know the documentation says icingadb supports redis from version 6.2 but the older version we have works anyway… not through sentinel though. Redis upgrade is not scheduled right now.
I cannot find anything on the forum or internet regarding this issue, like nobody had stumbled upon it. Maybe I’m dumb as hell and missed one tiny detail (as always lol), but we cannot understand where’s the issue (with the team that’s handling the redis sentinel stuff).
This post suggests me that it worked at some point (or should work now) => https://icinga.com/blog/new-redis-open-source-server-packages-for-icinga-db/
Do you have any idea?
Cheers,