• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue REDIS server failing to start

Christopher-James

Basic Pleskian
Hi, I've been running redis server successfully for a while now, upon a log error that was sent to me it's unable to start.

Please see the log output below.

Uninstalling and re-installing does nothing, restarting does nothing

Code:
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Starting Redis persistent key-value database...
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Started Redis persistent key-value database.
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: redis.service: main process exited, code=exited, status=1/FAILURE
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Unit redis.service entered failed state.
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: redis.service failed.

Code:
 Execution exec has failed with exit code 3, stdout: ● redis.service - Redis persistent key-value database
   Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/redis.service.d
           └─limit.conf
   Active: failed (Result: exit-code) since Fri 2023-01-27 10:44:55 GMT; 5min ago
 Main PID: 89885 (code=exited, status=1/FAILURE)

Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Starting Redis persistent key-value database...
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Started Redis persistent key-value database.
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: redis.service: main process exited, code=exited, status=1/FAILURE
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: Unit redis.service entered failed state.
Jan 27 10:44:55 656c9ec.online-server.cloud systemd[1]: redis.service failed.
, stderr:
 
This is more likely not a plesk issue since plesk does not come with redis to begin with.

The best suggestion I could tell you is to review whatever log files there is and see what the actual issue is because just looking at what systemd is providing you is not enough information to go off of, actual logs usually gives you more details.

Alternatively, according to this post on stackoverflow, you could try running the follow command to see what is wrong:
sudo /usr/bin/redis-server /etc/redis.conf
 
Back
Top