cannot install redis-server on ubuntu 18.04
Asked Answered
I

5

17

I have upgraded to ubuntu 18.04 from 17.10. The redis-server package cannot be fully installed. I looked at /var/log/syslog and it says

==> /var/log/syslog <==
Jun  3 13:04:10 qaz-mko systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory
Jun  3 13:05:01 qaz-mko CRON[3429]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Start operation timed out. Terminating.
Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Failed with result 'timeout'.
Jun  3 13:05:40 qaz-mko systemd[1]: Failed to start Advanced key-value store.
Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 13.
Jun  3 13:05:40 qaz-mko systemd[1]: Stopped Advanced key-value store.
Jun  3 13:05:40 qaz-mko systemd[1]: Starting Advanced key-value store...
Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory

==> /var/log/redis/redis-server.log <==
3416:C 03 Jun 13:02:39.637 # Configuration loaded
3417:M 03 Jun 13:02:39.639 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
3423:C 03 Jun 13:04:10.121 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3423:C 03 Jun 13:04:10.121 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=3423, just started
3423:C 03 Jun 13:04:10.122 # Configuration loaded
3424:M 03 Jun 13:04:10.124 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address
3435:C 03 Jun 13:05:40.602 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3435:C 03 Jun 13:05:40.602 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=3435, just started
3435:C 03 Jun 13:05:40.602 # Configuration loaded
3436:M 03 Jun 13:05:40.604 # Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address

However then it times out and does not start the redis deamon. The config file is the one that came with the package.

Do you want to continue? [Y/n] Y
Setting up redis-server (5:4.0.9-1) ...
Job for redis-server.service failed because a timeout was exceeded.
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: timeout) since Sun 2018-06-03 12:47:34 EDT; 14ms ago
     Docs: http://redis.io/documentation,
           man:redis-server(1)
  Process: 2156 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS)
dpkg: error processing package redis-server (--configure):
 installed redis-server package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of redis:
 redis depends on redis-server (<< 5:4.0.9-1.1~); however:
  Package redis-server is not configured yet.
 redis depends on redis-server (>= 5:4.0.9-1); however:
  Package redis-server is not configured yet.

dpkg: error processing package redis (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 redis-server
 redis
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have tried creating the pid file by hand and giving it lots of permissions. But that does not seem to work.

sudo touch /var/run/redis/redis-server.pid
# sudo chown redis:redis /var/run/redis/redis-server.pid
# sudo chmod 777 /var/run/redis/redis-server.pid
# sudo ls -alh /var/run/redis/
total 0
drwxr-sr-x  2 redis redis  60 Jun  3 12:54 .
drwxr-xr-x 33 root  root  940 Jun  3 12:53 ..
-rwxrwxrwx  1 redis redis   0 Jun  3 12:54 redis-server.pid
Intimidate answered 3/6, 2018 at 17:0 Comment(0)
B
33

It is possible to get redis-server running even when IPv6 is disabled.

Simply remove the ::1 IPv6 loopback address from the bind config option (by default located in /etc/redis/redis.conf):

- bind 127.0.0.1 ::1
+ bind 127.0.0.1

Now redis will not try to use the IPv6 network.

Babu answered 11/2, 2019 at 11:35 Comment(1)
This is the correct answer. Adjust redis to it's surroundings and not vice versa.Cabernet
I
16

I found the culprit. I had disabled ipv6 a while back. I turned it back on and it installed fine and started up fine. You could probably alter the redis.conf file to force it to use IPv4 if it supports that mode only and then maybe you could run it without IPv6.

Intimidate answered 3/6, 2018 at 17:17 Comment(2)
Please accept this answer, since the question doesn't need attention anymore.Loudspeaker
This worked for me as well. In my case, I edited the /etc/sysctl.conf file and removed the following line: net.ipv6.conf.all.disable_ipv6 = 1Arroyo
D
2

I also failed to install redis-server and after trying many ways, I was able to install it on Windows using Ubuntu following these steps:

sudo apt-add-repository ppa:redislabs/redis
sudo apt-get update

then make sure u was install redis-tools & libglib2.0-0. If not, install these:

sudo apt-get install redis-tools
sudo apt-get install -y libglib2.0-0

next:

sudo apt-get install redis-server

Then start the Redis server like so:

sudo service redis-server start

U can read more on: https://redis.io/docs/getting-started/installation/install-redis-on-windows/

Diploma answered 29/3, 2022 at 19:17 Comment(0)
F
1

Well, I just had a similar issue upgrading from Ubuntu 16.04 to 18.04. The solution above (disabling ipv6) didn't help here. It could very well be me, but I also don't understand why that would help, as the important part of the error appears to be

Jun  3 13:05:40 qaz-mko systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory

Obviously, creating the file itself does not necessarily solve that issue. What does help, though, is to create the directory and give it the necessary permissions:

mkdir -p /var/run/redis
chown redis:redis /var/run/redis

It doesn't persist over reboots. While I'm still trying to figure out a solution for this, the quick and dirty work-around is to put the above lines into rc.local

Facing answered 28/6, 2020 at 15:35 Comment(0)
G
0

Possible remove PID from systemd Unit /etc/systemd/system/[email protected] can help

[Unit]
Description=redis cluster instance at port %i
After=network.target
Documentation=http://redis.io/documentation, man:redis-server(1)

[Service]
Type=forking
ExecStart=/usr/bin/redis-server /etc/redis/redis.conf \
--cluster-enabled yes \
--dbfilename dump_%i.rdb \
--port %i --cluster-config-file nodes_%i.conf \
--logfile /var/log/redis/redis-server_%i.log \
--supervised systemd

TimeoutStopSec=0
Restart=always
User=redis
Group=redis
RunTimeDirectory=redis

ExecStop=/usr/local/bin/redis-cli -h 127.0.0.1:%i shutdown

UMask=007
PrivateTmp=yes
LimitNOFILE=65535
PrivateDevices=yes
ProtectHome=yes
ReadOnlyDirectories=/
ReadWriteDirectories=-/var/lib/redis
ReadWriteDirectories=-/var/log/redis
ReadWriteDirectories=-/var/run/redis
CapabilityBoundingSet=~CAP_SYS_PTRACE

# redis-server writes its own config file when in cluster mode so we allow
# writing there (NB. ProtectSystem=true over ProtectSystem=full)
ProtectSystem=true
ReadWriteDirectories=-/etc/redis

[Install]
WantedBy=multi-user.target
Glabella answered 14/10, 2021 at 9:11 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.