Running: sudo service redis-server stop

Gets the log:

869:M 29 May 21:13:24.281 * Background saving terminated with success
869:M 30 May 08:53:50.717 * 1 changes in 900 seconds. Saving...
869:M 30 May 08:53:50.808 * Background saving started by pid 30587
869:signal-handler (1527701629) Received SIGTERM scheduling shutdown...
869:M 30 May 10:33:50.397 # User requested shutdown...
869:signal-handler (1527701630) Received SIGTERM scheduling shutdown...
869:M 30 May 10:33:50.960 # There is a child saving an .rdb. Killing it!
869:M 30 May 10:33:50.960 * Saving the final RDB snapshot before exiting.
869:signal-handler (1527701632) Received SIGTERM scheduling shutdown...
869:signal-handler (1527701632) Received SIGTERM scheduling shutdown...
869:signal-handler (1527701633) Received SIGTERM scheduling shutdown...
869:signal-handler (1527701634) Received SIGTERM scheduling shutdown...
869:signal-handler (1527701635) Received SIGTERM scheduling shutdown...

... forever.

By chance, I noticed that apt/ubuntu's check-new-release was running and hogging the CPU. Perhaps related to:

4963 https://github.com/antirez/redis/issues/4963

??

redis --version
Redis server v=4.0.6 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=cda88f8771eb168a

Comment From: yoav-steinberg

@stuz5000 does this still happen? If so please ping @lamby as he might be able to help you since it seems like a distro issue.