• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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