Hardware: VPS Server Debian 9 I have access to my server : Through SSH Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no If yes, please explain:
Description of my issue
I tried to install yunohost on a fresh debian 9 server. The installation fails, apparently the redis package cannot be configured because the redis server wont start with systemd.
the output of systemctl status redis.service
_ redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-06-21 12:21:24 UTC; 7min ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Process: 17465 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=226/NAMESPACE)
Process: 17462 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE)
Jun 21 12:21:24 vps48834 systemd[1]: Failed to start Advanced key-value store.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:21:24 vps48834 systemd[1]: Stopped Advanced key-value store.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 21 12:21:24 vps48834 systemd[1]: Failed to start Advanced key-value store.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:21:24 vps48834 systemd[1]: redis-server.service: Failed with result 'exit-code'.
17498:C 21 Jun 12:33:37.500 # systemd supervision requested, but NOTIFY_SOCKET not found
17499:M 21 Jun 12:33:37.502 * Increased maximum number of open files to 10032 (it was originally set to 1024).
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 3.2.6 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 17499
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | http://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
17499:M 21 Jun 12:33:37.503 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
17499:M 21 Jun 12:33:37.503 # Server started, Redis version 3.2.6
17499:M 21 Jun 12:33:37.503 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
17499:M 21 Jun 12:33:37.503 * The server is now ready to accept connections on port 6379
cat /var/log/daemon.log | grep redis
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Jun 21 12:51:43 vps48834 run-parts[17864]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Jun 21 12:51:43 vps48834 run-parts[17870]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory
Jun 21 12:51:43 vps48834 run-parts[17874]: run-parts: executing /etc/redis/redis-server.pre-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 21 12:51:43 vps48834 run-parts[17881]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Jun 21 12:51:43 vps48834 run-parts[17887]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Jun 21 12:51:43 vps48834 run-parts[17893]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory
Jun 21 12:51:43 vps48834 run-parts[17897]: run-parts: executing /etc/redis/redis-server.pre-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 21 12:51:43 vps48834 run-parts[17904]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Jun 21 12:51:43 vps48834 run-parts[17910]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Jun 21 12:51:43 vps48834 run-parts[17916]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory
Jun 21 12:51:43 vps48834 run-parts[17920]: run-parts: executing /etc/redis/redis-server.pre-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 21 12:51:43 vps48834 run-parts[17927]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:51:43 vps48834 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Jun 21 12:51:43 vps48834 run-parts[17933]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Jun 21 12:51:44 vps48834 run-parts[17939]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory
Jun 21 12:51:44 vps48834 run-parts[17943]: run-parts: executing /etc/redis/redis-server.pre-down.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 21 12:51:44 vps48834 run-parts[17950]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Failed to set invocation ID on control group /system.slice/redis-server.service, ignoring: Operation not permitted
Jun 21 12:51:44 vps48834 run-parts[17956]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Jun 21 12:51:44 vps48834 run-parts[17962]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory
Jun 21 12:51:44 vps48834 run-parts[17966]: run-parts: executing /etc/redis/redis-server.pre-down.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 21 12:51:44 vps48834 run-parts[17973]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Unit entered failed state.
Jun 21 12:51:44 vps48834 systemd[1]: redis-server.service: Failed with result 'resources'