I noticed that I can co-install valkey-server and redis-server, as they
have no declared conflicts, and no file conflicts as well. But they
listen on the same port (6379), and if I install valkey-server while I
have redis-server also installed, valkey will fail to start:
Unpacking valkey-server (7.2.5+dfsg1-2ubuntu3~24.04) over
(7.2.5+dfsg1-2ubuntu3~24.04) ...
Selecting previously unselected package valkey-tools.
Preparing to unpack .../valkey-tools_7.2.5+dfsg1-2ubuntu3~24.04_amd64.deb ...
Unpacking valkey-tools (7.2.5+dfsg1-2ubuntu3~24.04) ...
Setting up valkey-tools (7.2.5+dfsg1-2ubuntu3~24.04) ...
Setting up valkey-server (7.2.5+dfsg1-2ubuntu3~24.04) ...
Created symlink /etc/systemd/system/valkey.service →
/usr/lib/systemd/system/valkey-server.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/valkey-server.service →
/usr/lib/systemd/system/valkey-server.service.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
Processing triggers for man-db (2.12.0-4build2) ...
It doesn't fail the package installation, which is good, but the service
is obviously not running, and can't be started:
Sep 20 16:25:03 n-valkey systemd[1]: Starting valkey-server.service - Advanced
key-value store...
Sep 20 16:25:03 n-valkey systemd[1]: valkey-server.service: Main process
exited, code=exited, status=1/FAILURE
Sep 20 16:25:03 n-valkey systemd[1]: valkey-server.service: Failed with result
'exit-code'.
Sep 20 16:25:03 n-valkey systemd[1]: Failed to start valkey-server.service -
Advanced key-value store.
The log file has the reason:
1307:C 20 Sep 2024 16:25:04.678 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
1307:C 20 Sep 2024 16:25:04.678 * Valkey version=7.2.5, bits=64,
commit=166f604f, modified=1, pid=1307, just started
1307:C 20 Sep 2024 16:25:04.678 * Configuration loaded
1307:M 20 Sep 2024 16:25:04.678 * monotonic clock: POSIX clock_gettime
1307:M 20 Sep 2024 16:25:04.679 * Running mode=standalone, port=6379.
1307:M 20 Sep 2024 16:25:04.679 # Warning: Could not create server TCP
listening socket 127.0.0.1:6379: bind: Address already in use
1307:M 20 Sep 2024 16:25:04.679 # Failed listening on port 6379 (tcp), aborting.
Is this known and expected, or should it have a conflicts? I'm not sure
about the debian policy in this case of conflicting ports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081000
Title:
Backport version from Oracular to Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valkey/+bug/2081000/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
