Your message dated Sun, 19 Aug 2018 12:24:01 +0200 with message-id <[email protected]> and subject line Re: Bug#900284: backport of redis-server fails to start and install fails if no ipv6 has caused the Debian Bug report #900284, regarding backport of redis-server fails to start and install fails if no ipv6 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 900284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900284 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: redis-server Version: 5:4.0.9-2~bpo9+1 Severity: important Hi there! The backport version of redis-server simply fails to get installed. Here's the log after doing "apt-get install -t stretch-backports redis-server": Setting up redis-server (5:4.0.9-2~bpo9+1) ... Job for redis-server.service failed because of unavailable resources or another system error. See "systemctl status redis-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript redis-server, action "start" failed. ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: resources) since Mon 2018-05-28 14:15:08 UTC; 7ms ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 1199 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) May 28 14:15:08 stigo systemd[1]: redis-server.service: Daemon never wrote its PID file. Failing. May 28 14:15:08 stigo systemd[1]: Failed to start Advanced key-value store. May 28 14:15:08 stigo systemd[1]: redis-server.service: Unit entered failed state. May 28 14:15:08 stigo systemd[1]: redis-server.service: Failed with result 'resources'. dpkg: error processing package redis-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (232-25+deb9u2) ... Errors were encountered while processing: redis-server E: Sub-process /usr/bin/dpkg returned an error code (1) The PID thing is in fact missleading. That's not the issue. After some investigations, it looks like I had this in my /etc/sysctl.conf: net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 Re-enabling ipv6 in my system, or disabling bind ::1 in /etc/redis/redis.conf made it work. I do believe that having ipv6 enabled by default is a very good idea, however, the package should at least succeed to be installed even without ipv6. Maybe the upstream daemon should be modified to test if it can bind on ::1 before doing it? I suppose that the backport version isn't the only one affected, and that the normal Sid/Buster version should also have this problem. Cheers, Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---On 08/19/2018 10:50 AM, Chris Lamb wrote: > Chris Lamb wrote: > >> […] > > Another gentle ping on this bug? > > > Regards, Hi Chris, I think it's fine to just close this bug without any further action. I don't have anymore issues when using puppet, I just told the module to not attempt to manage the service, and then it worked. Cheers, Thomas Goirand (zigo)
--- End Message ---
