FS#70613 - [redis] Timeout settings warning
Attached to Project:
Community Packages
Opened by Dick MIddleton (nottledim) - Tuesday, 27 April 2021, 12:41 GMT
Last edited by freswa (frederik) - Tuesday, 27 April 2021, 14:07 GMT
Opened by Dick MIddleton (nottledim) - Tuesday, 27 April 2021, 12:41 GMT
Last edited by freswa (frederik) - Tuesday, 27 April 2021, 14:07 GMT
|
Details
Description:
I get this message in journald from redis. "Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit." Googling about it seems this error is because redis is not compiled with systemd. Something to do with BUILD_WITH_SYSTEMD setting in Makefile. Apparently upstream it defaults to "no" and needs to be "yes". It seems unlikely but I thought it should be confirmed. https://github.com/redis/redis/issues/7217 https://serverfault.com/questions/1031891/redis-service-hangs-with-systemctl-and-type-notify Additional info: * package version(s) 6.2.2 * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by freswa (frederik)
Tuesday, 27 April 2021, 14:07 GMT
Reason for closing: Not a bug
Additional comments about closing: It is compiled with systemd support and the appropriate timeouts are set.
Tuesday, 27 April 2021, 14:07 GMT
Reason for closing: Not a bug
Additional comments about closing: It is compiled with systemd support and the appropriate timeouts are set.
If the return value from redisCommunicateSystemd which is a wrapper around sd_notify [2] is greater than 0 then you see the notice meaning redis communicated with systemd successfully.
[1] https://github.com/redis/redis/blob/6.2.2/src/server.c#L6067
[2] https://man.archlinux.org/man/sd_notify.3#RETURN_VALUE