In-Memory Data Store
Loaded: loaded (/etc/systemd/system/redis.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Птн 2019-08-02 13:40:02 EEST; 1s ago
Process: 7458 ExecStop=/usr/local/bin/redis-cli shutdown (code=exited, status=1/FAILURE)
Process: 7456 ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FAILURE)
Main PID: 7456 (code=exited, status=1/FAILURE)
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Unit entered failed state.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Failed with result 'exit-code'.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Service hold-off time over, scheduling restart.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: Stopped Redis In-Memory Data Store.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Start request repeated too quickly.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: Failed to start Redis In-Memory Data Store.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Unit entered failed state.
Авг 02 13:40:02 m0nte-cr1st0 systemd[1]: redis.service: Failed with result 'start-limit-hit'.
https://askubuntu.com/questions/1089310/how-to-resolve-service-start-limit-hit
Обсуждают сегодня