Webinoly is just the perfect tool for NGINX experts. Give it a try!
0 votes

Hi, Can you please advise what I need to do to resolve this? I did webinoly -verify and I see:

webinoly -verify
Verifying integrity of the entire Webinoly system...

[ERROR] Redis service not running!
********      > > >  E R R O R < < <        ***********
********   System could not work properly   ***********

1 Answer

0 votes
by Expert
Best answer

For some reason Redis is not running in your server, try reloading the service:

sudo service redis-server reload

Or, try starting the service:

sudo service redis-server start


by Rookie


I noticed the redis plugin was reporting "not connected".

When I try running redis-server it starts but lots of issues -- is this something I did wrong or is there something wrong with my setup? Thanks

root@webg1:/var/www/domain.com/htdocs# redis-server

27227:C 22 Dec 2018 00:57:11.009 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

27227:C 22 Dec 2018 00:57:11.009 # Redis version=5.0.2, bits=64, commit=00000000, modified=0, pid=27227, just started

27227:C 22 Dec 2018 00:57:11.009 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf

27227:M 22 Dec 2018 00:57:11.010 * Increased maximum number of open files to 10032 (it was originally set to 4096).


           _.-``__ ''-._

      _.-``    `.  `_.  ''-._           Redis 5.0.2 (00000000/0) 64 bit

  .-`` .-```.  ```\/    _.,_ ''-._

 (    '      ,       .-`  | `,    )     Running in standalone mode

 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379

 |    `-._   `._    /     _.-'    |     PID: 27227

  `-._    `-._  `-./  _.-'    _.-'

 |`-._`-._    `-.__.-'    _.-'_.-'|

 |    `-._`-._        _.-'_.-'    |           http://redis.io

  `-._    `-._`-.__.-'_.-'    _.-'

 |`-._`-._    `-.__.-'    _.-'_.-'|

 |    `-._`-._        _.-'_.-'    |

  `-._    `-._`-.__.-'_.-'    _.-'

      `-._    `-.__.-'    _.-'

          `-._        _.-'


27227:M 22 Dec 2018 00:57:11.012 # Server initialized

27227:M 22 Dec 2018 00:57:11.012 # 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.

27227:M 22 Dec 2018 00:57:11.012 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

27227:M 22 Dec 2018 00:57:11.013 * DB loaded from disk: 0.001 seconds

27227:M 22 Dec 2018 00:57:11.013 * Ready to accept connections
by Expert

Hi sshanky,

Redis is running with "default" configuration, the output you are getting is normal under this condition and seems like is running fine. You can customize your redis.conf, but the default configuration is enough for the most cases.


by Rookie
It's running because I started it in the command line, but it wasn't running until I did that -- but I can't leave it like that because it will stop as soon as close the terminal.

Normally, on two of my Webinoly servers, Redis is not connected. Is there something we need to do to make it run? When I saw the error messages, I thought maybe the stack tries to start it, but then it stops? Seems like it should be running automatically without my intervention, right?

by Expert
Definitely, this is an issue related to your servers or your custom configuration.
by Rookie
edited by

Maybe redis just isn't starting automatically. Do you have any suggestions on how to diagnose this? I have two servers on different providers and both of them don't seem to be running. I have not made any changes to the servers other than to install webinoly.

sudo service redis-server restart works but then restarting the entire virtual machine stops it again and I have to sudo service redis-server restart again to make it connect.

by Expert
You can try modifying the Redis systemd service config file, this way you can have control about the exact moment redis is started on boot.

by Expert

This issue was fixed in v1.7.1 released today!

by Rookie

I updated today, restarted, and after making sure to enable the object cache, status is still "not connected".

$ sudo webinoly -version
Webinoly version: 1.7.1
Current stack version: 1.3
by Expert

Hi sshanky,

The latest update does not modify your currently installed stack, it only have effect over new installations. But don't worry!

First of all, be sure you have updated Webinoly to the latest version (v1.7.1): sudo webinoly -update

  • If your host is not starting Redis after reboot, you can manually enable this feature: sudo systemctl enable redis-server
  • If your host not recognize SWAP after reboot: sudo echo "/swapfile none swap sw 0 0" >> /etc/fstab
  • If you are affected by the 404 error introduced in v1.7.0 for WP sites with cache disabled: sudo webinoly -server-reset=nginx

Please, tell me if it works for you.


by Rookie

Hi, I already tried sudo systemctl enable redis-server but I would like these things to also happen on restart. I think I should add this to cron, right? Which user?

What about the other commands? It looks like I should not add the swap command to cron, it only needs to be run once, right? and the 404 error (I have not seen it yet) -- should I add that to cron or only run it once also?


by Rookie

Sorry, I was wrong about sudo systemctl enable redis-server. I just tried it and still in the Redis settings I see Redis Object Cache Status: Disconnected. However, what I tried in the past was service redis-server restart. I just tried this and it works -- Status: Connected.

by Expert
No, you don't need to add nothing at cron.

Be careful, I just listed the errors that were fixed in the latest release. Take only what you need, surely you were not affected by all of them, some of them only appears with certain cloud providers.

In the Redis case you only have to run this command once, after that everything should work fine and you never need to run this command again. The same for the SWAP and 404 solutions.

by Expert
Yes, you first need to start the Redis service and the other command is to ensure Redis start automatically at boot.
by Rookie
Thanks. At reboot the redis service never starts -- every time I reboot I have to do service redis-server restart. What is the best way to make sure this starts when i reboot?
by Expert

First of all, be sure Redis is running, then run the command to enable the automatic starting at boot.

You can check the service status: sudo systemctl status redis-server

In the "Loaded" line, see if service is loaded and enabled.

In the "Active" line, see if is active and running.

This issue is only happening on Vultr and is not a Webinoly issue, some other affected users already reported this issue as solved with the latest Webinoly release, I don't really know what is happening in your specific case.


Welcome to the Community site for Webinoly.

Our Optimized LEMP Web Server is a powerful set of commands for doing just about anything you could wish.

With Webinoly you can set up your NGINX web server in just one step.

* * * * * * *

To report a bug, please create a new issue on GitHub or ask a question here with the bug tag.
Webinoly Support Paypal Donations

PayPal · GitHub Sponsors · Bitcoin

It is very important that any visitor to the site read the disclaimer, terms of use and privacy and legal statement before start browsing.