Red Hat Bugzilla – Bug 1235214
Redis fails to start due to config file errors
Last modified: 2015-08-05 09:28:06 EDT
Created attachment 1042687 [details] redis config Description of problem: I am doing a one compute and one controller deployment and the redis resource fails to start due to some config values in redis.conf which are set to undef. Version-Release number of selected component (if applicable): openstack-puppet-modules-2015.1.7-1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Do one controller and one compute deployment. 2. Check pcs status 3. Actual results: redis resource fails to start; redis(redis)[24096]: ERROR: start: Unknown error starting redis. output=; *** FATAL CONFIG FILE ERROR ***; Reading the configuration file, at line 62; >>> 'syslog-facility undef'; Invalid log facility. Must be one of USER or between LOCAL0-LOCAL7 Expected results: redis resource starts ok Additional info: Attaching redis.conf
Related to an upstream puppet-redis change https://github.com/arioch/puppet-redis/commit/edd7cb55931fe0336bfee475c738ac4b91308f98#diff-fe82d24487e48ff4b7f22a48744defa2R63
Reported upstream as https://github.com/arioch/puppet-redis/issues/41
verified :openstack-puppet-modules-2015.1.7-2.el7ost.noarch on virt-evn : pcs status --> looks clean [heat-admin@overcloud-controller-0 ~]$ sudo lsof -i :6379 -n -P COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME haproxy 22371 haproxy 1u IPv4 3273898 0t0 TCP 172.17.0.14:39929->172.17.0.12:6379 (ESTABLISHED) haproxy 22371 haproxy 2u IPv4 3273275 0t0 TCP 172.17.0.14:36392->172.17.0.14:6379 (ESTABLISHED) haproxy 22371 haproxy 35u IPv4 159720 0t0 TCP 192.0.2.8:6379 (LISTEN) ceilomete 25490 ceilometer 5u IPv4 1525437 0t0 TCP 192.0.2.12:48668->192.0.2.8:6379 (ESTABLISHED) redis-ser 26778 redis 4u IPv4 206353 0t0 TCP 172.17.0.14:6379 (LISTEN) redis-ser 26778 redis 6u IPv4 3273058 0t0 TCP 172.17.0.14:6379->172.17.0.12:53808 (ESTABLISHED) redis-ser 26778 redis 7u IPv4 3273276 0t0 TCP 172.17.0.14:6379->172.17.0.14:36392 (ESTABLISHED) redis-ser 26778 redis 8u IPv4 3273343 0t0 TCP 172.17.0.14:6379->172.17.0.13:57097 (ESTABLISHED) ceilomete 30818 ceilometer 5u IPv4 1881008 0t0 TCP 192.0.2.12:52703->192.0.2.8:6379 (ESTABLISHED)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548