package redis-server 5:4.0.8-2 failed to install/upgrade: installed redis-server package post-installation script subprocess returned error exit status 1

Bug #1752207 reported by Chris McDonough
78
This bug affects 17 people
Affects Status Importance Assigned to Milestone
redis (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After apt-get dist-upgrade tonight on bionic.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: redis-server 5:4.0.8-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Tue Feb 27 20:12:16 2018
ErrorMessage: installed redis-server package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-02-24 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180224)
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt 1.6~alpha7ubuntu2
SourcePackage: redis
Title: package redis-server 5:4.0.8-2 failed to install/upgrade: installed redis-server package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris McDonough (chrism-plope) wrote :
Revision history for this message
Chris McDonough (chrism-plope) wrote :

More info:

```
chrism  ~  ls /var/run/redis/
 chrism  ~  sudo systemctl start redis
Job for redis-server.service failed because a timeout was exceeded.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
 chrism  ~  journalctl -xe
-- The result is RESULT.
Feb 27 20:18:40 bionictest sudo[30491]: pam_unix(sudo:session): session closed f
Feb 27 20:18:40 bionictest systemd[1]: redis-server.service: Service hold-off ti
Feb 27 20:18:40 bionictest systemd[1]: redis-server.service: Scheduled restart j
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit redis-server.service has been scheduled, as
-- the configured Restart= setting for the unit.
Feb 27 20:18:40 bionictest systemd[1]: Stopped Advanced key-value store.
-- Subject: Unit redis-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit redis-server.service has finished shutting down.
Feb 27 20:18:40 bionictest systemd[1]: Starting Advanced key-value store...
-- Subject: Unit redis-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit redis-server.service has begun starting up.
Feb 27 20:18:40 bionictest systemd[1]: redis-server.service: Can't open PID file
```

tags: removed: need-duplicate-check
Revision history for this message
Chris McDonough (chrism-plope) wrote :

Moar:

```
root@bionictest:/var/log/redis# tail redis-server.log
30526:C 27 Feb 20:18:40.937 # Configuration loaded
30527:M 27 Feb 20:18:40.938 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
30868:C 27 Feb 20:20:11.428 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
30868:C 27 Feb 20:20:11.428 # Redis version=4.0.8, bits=64, commit=00000000, modified=0, pid=30868, just started
30868:C 27 Feb 20:20:11.428 # Configuration loaded
30869:M 27 Feb 20:20:11.429 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
31269:C 27 Feb 20:21:41.977 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
31269:C 27 Feb 20:21:41.977 # Redis version=4.0.8, bits=64, commit=00000000, modified=0, pid=31269, just started
31269:C 27 Feb 20:21:41.977 # Configuration loaded
31279:M 27 Feb 20:21:41.978 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
```

Revision history for this message
Chris McDonough (chrism-plope) wrote :

I had ipv6 disabled on my network interface. Reenabling it allowed redis to start up fine.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in redis (Ubuntu):
status: New → Confirmed
Revision history for this message
Sogos (thibault-cordier) wrote :

Related to ipv6 (disabled on the server)

Replaced

bind 127.0.0.1 ::1

by

bind 127.0.0.1

Revision history for this message
Jeff (carpenter-jeff+alert) wrote :

This bug also affects redis-server 5:4.0.9-1 under Ubuntu 18.04.1.

Revision history for this message
Riccardo Magliocchetti (riccardo) wrote :

Any chance the fix for this can be cherry-picked in bionic?
https://github.com/antirez/redis/commit/afc4b36c1026a4fab0e6c50af09c6bd18adc17d5

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.