Starting Valkey using systemd (Ubuntu) - compiled without libsystemd support?

[melroy89]

Hi,

I'm really eager to move away from Redis to Valkey. However after downloading the "Focal" (I'm actually running Ubuntu 24.04) Valkey v8.0.0 standalone binary from the official site: https://valkey.io/download/.

I setup the systemd service file. I configured everything how I want Valkey to run. Everything seems fine, settings are good and permissions are good. Redis server is down.

And now I want to start Valkey via: sudo systemctl start valkey-server. And it starts, however the systemctl command seems to HANG. Checking the Valkey log says the following:

systemd supervision requested or auto-detected, but Valkey is compiled without libsystemd support

Why is the official Ubuntu binary not compiled with libsystemd support!???? Help? I don't want to compile from source, since I think this is not how you want to deliver your product to server admins.

Kind regards,
Melroy van den Berg

---

Ps. why are the .c, .d and .o files part of the tar.gz binary?

[melroy89]

Could you make USE_SYSTEMD=yes part of the release binary deployment?

[roshkhatri]

I am not sure if we should be building the release binaries with USE_SYSTEMD=yes.

We might want more views on this.

The README file mentions the same about building with systemd support.

valkey/README.md

Line 46 in 9827eef

To build with systemd support, you'll need systemd development libraries (such

@valkey-io/core-team can you take a look.

[melroy89]

The Binary Artifacts on the download page are literally named after the Ubuntu names:

Ubuntu is using systemd, so I want to use the binary artifacts under.. well.. Ubuntu with systemd, but this setup failed! I expect the pre-build binary to be able to run on the target machine, so it can be used for production with systemd.

arm64 / bionic (sha256)
x86_64 / bionic (sha256)
arm64 / focal (sha256)
x86_64 / focal (sha256)

[zuiderkwast]

Sounds reasonable. It is statically linked. Do we build this binary with TSL?

I believe TLS and systemd are basic. Those who want a binary without these can build from source.

@roshkhatri What's your concern?

[melroy89]

It also sounds reasonable to me :). If it's statically linked, there shouldn't be any platform specific issues.

Ps. Is there a reason why you have bionic and focal binaries, but no Noble yet? Does the binaries even matter if they are statically build? Or are they just use newer GCC & Glibc versions?

[melroy89]

OK.. I created a PR: #1107, this will introduce systemd support.

[melroy89]

SO a bit off-topic but maybe a good question anyways: Should we include Noble as well or?

My question: "Is there a reason why you have bionic and focal binaries, but no Noble yet? Does the binaries even matter if they are statically build? Or are they just use newer GCC & Glibc versions?" still remains.

[roshkhatri]

I think there is a PR open for it. I had reviewed it. Let me find out of its merged

[roshkhatri]

Ps. why are the .c, .d and .o files part of the tar.gz binary?

Yeah we should be fixing that.

[melroy89]

Problem line: https://github.com/valkey-io/valkey/blob/unstable/.github/workflows/call-build-linux-x86-packages.yml#L59C10-L59C50

[melroy89]

I did it myself. PR created: #1106

[roshkhatri]

Thank you so much @melroy89

[roshkhatri]

Thats a good Idea.

[roshkhatri]

Also the new patches are now released for 8.0.1 and 7.2.7 with this changes and other CVEs. Try them and let me know if that helped.

[melroy89]

I will tomorrow thanks! It's 1:30 am now.

[melroy89]

v8.0.1 looks great! Systemd support out of the box. And no more .c, .o, etc. files.. I can continue to finish by blog post now, without explaining how to build from source.

[roshkhatri]

Thats great! Looking forward to read the blog post