Resolved Problem with REDIS after Virtuozzo update

[P_heck]

Hello,

my hoster has recently updated the Virtuozzo container with some massive problems afterwards. First access via SSH and access to Plesk console was not working anymore, but could be solved by this article.

Now Redis server is reloading each 2 minutes. I noticed this first by Logcheck sending me the following logs:

Mar 16 15:02:37 h2729830 run-parts[9932]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Mar 16 15:02:37 h2729830 run-parts[9932]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Mar 16 15:02:37 h2729830 run-parts[9938]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Mar 16 15:02:37 h2729830 run-parts[9938]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Mar 16 15:02:37 h2729830 run-parts[9944]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Mar 16 15:02:37 h2729830 run-parts[9944]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10051]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10051]: run-parts: executing /etc/redis/redis-server.post-down.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10058]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10058]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10064]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
Mar 16 15:04:07 h2729830 run-parts[10064]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example

Looking at the Redis logfile in /var/log/redis, I read the following sequence each 2 minutes:

23133:signal-handler (1552752082) Received SIGTERM scheduling shutdown...
23133:M 16 Mar 17:01:22.089 # User requested shutdown...
23133:M 16 Mar 17:01:22.090 * Saving the final RDB snapshot before exiting.
23133:M 16 Mar 17:01:22.115 * DB saved on disk
23133:M 16 Mar 17:01:22.115 * Removing the pid file.
23133:M 16 Mar 17:01:22.115 # Redis is now ready to exit, bye bye...
23448:M 16 Mar 17:01:22.342 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
23448:M 16 Mar 17:01:22.342 # Redis can't set maximum open files to 10032 because of OS error: Operation not permitted.
23448:M 16 Mar 17:01:22.342 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 3.0.6 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 23448
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           http://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

23448:M 16 Mar 17:01:22.343 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
23448:M 16 Mar 17:01:22.343 # Server started, Redis version 3.0.6
23448:M 16 Mar 17:01:22.343 # 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.
23448:M 16 Mar 17:01:22.346 * DB loaded from disk: 0.004 seconds
23448:M 16 Mar 17:01:22.349 * The server is now ready to accept connections on port 6379

Does anyone has an idea, how to repair this?

Cheers Peter

 

[P_heck]

Problem solved - for whatever reason the directory /var/run/redis has disappeared! After recreating it with the right ownership, it works again. Strange!