Environment:
Rocky Linux 10
grommunio-admin-api-1.20.37.mcb44ef4-57.2
valkey-8.0.9-1.el10_2
Rocky Linux 10 provides Valkey instead of Redis. The active service is:
valkey.service
There is no redis@grommunio.service unit. Valkey itself works correctly:
systemctl is-active valkey.service
active
valkey-cli -h 127.0.0.1 ping
PONG
However, the Admin Dashboard displays the Redis service as inactive because the Admin API configuration hardcodes redis@grommunio.service here:
https://github.com/grommunio/admin-api/blob/master/data/config.yaml.in#L29
The same obsolete unit name is also hardcoded in the Polkit service whitelist:
https://github.com/grommunio/admin-api/blob/master/data/polkit-10-grommunio.rules#L21
Changing the dashboard entry from:
unit: redis@grommunio.service
to:
unit: valkey.service
makes the dashboard display the correct active status.
The Redis protocol connection is not the problem. Valkey is compatible and the application works. Only the hardcoded systemd unit name and Polkit whitelist are incorrect.
Suggested fix:
Make the Redis/Valkey systemd unit configurable at build or package time, similar to the existing PHP_FPM_SERVICE placeholder. Packages for RHEL/Rocky Linux 10 should use valkey.service in both config.yaml.in and polkit-10-grommunio.rules.
Environment:
Rocky Linux 10
grommunio-admin-api-1.20.37.mcb44ef4-57.2
valkey-8.0.9-1.el10_2
Rocky Linux 10 provides Valkey instead of Redis. The active service is:
valkey.service
There is no redis@grommunio.service unit. Valkey itself works correctly:
systemctl is-active valkey.service
active
valkey-cli -h 127.0.0.1 ping
PONG
However, the Admin Dashboard displays the Redis service as inactive because the Admin API configuration hardcodes redis@grommunio.service here:
https://github.com/grommunio/admin-api/blob/master/data/config.yaml.in#L29
The same obsolete unit name is also hardcoded in the Polkit service whitelist:
https://github.com/grommunio/admin-api/blob/master/data/polkit-10-grommunio.rules#L21
Changing the dashboard entry from:
unit: redis@grommunio.service
to:
unit: valkey.service
makes the dashboard display the correct active status.
The Redis protocol connection is not the problem. Valkey is compatible and the application works. Only the hardcoded systemd unit name and Polkit whitelist are incorrect.
Suggested fix:
Make the Redis/Valkey systemd unit configurable at build or package time, similar to the existing PHP_FPM_SERVICE placeholder. Packages for RHEL/Rocky Linux 10 should use valkey.service in both config.yaml.in and polkit-10-grommunio.rules.