Search Engine: Elastic

Article ID: 128284, created on Feb 10, 2016, last review on Nov 26, 2018

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3
  • Operations Automation 7.4
  • Operations Automation 6.0


Apache log files are not getting updates for webspaces hosted on NG web server.

The following error is logged to /var/log/messages continuously:

Feb 10 10:49:51 ngweb1 /usr/sbin/log-dumper[548274]: Error on communication with redis: READONLY You can't write against a read only slave.

Another symptom of the problem can be failed "Creating virtual host directory structure" tasks with the output of:

User 'eXXXXXXX' does not exist


redis package has been updated on the NG web host(s) from a foreign repository to higher version that supported, which also could bring the read-only configuration.

[root@ngweb1 ~]# yum info redis
Loaded plugins: fastestmirror, rhnplugin, security
Loading mirror speeds from cached hostfile
 * cloudlinux-x86_64-server-6:
 * epel:
Installed Packages
Name        : redis
Arch        : x86_64
Version     : 3.2.11
Repo        : epel

[root@ngweb1 ~]# grep read-only /etc/redis.conf
# Since Redis 2.6 by default slaves are read-only.
slave-read-only yes

This may occur if Cloudlinux updates enabled imunify360 repository automatically (/etc/yum.repos.d/cloudlinux-imunify360.repo).


1. Disable all foreign repositories, the only YUM repos to be left are:


2. Downgrade redis package:

# yum downgrade redis

3. Stop Redis

# service redis stop

4. Delete or move RDB dump from /var/lib/redis/

5. In PCP > Infrastructure > Service Nodes > node_name > 'General' tab press Sync data to redis button

6. Wait for Dump webspace data to redis task to finish.

7. Start Redis

# service redis start

Please be aware that Redis shutdown causes downtime of customers' websites. Please also make sure /etc/redis.conf file does not contain slave-read-only setting set to "yes" afterwards.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d 0871c0b47b3b86ae3b1af4c2942cd0ce 8c199f0ee4305da1a577740620df4a51 55fe109b4b4fe3fbb893f22dbb85a41a 31987597efff5a3a9ce779cc203bbe5e

Email subscription for changes to this article
Save as PDF