Possible packaging bug: libvarnishapi files installed as regular files instead of symlinks on Debian 13 #3

New Issue

MrUnknownDE · 2026-04-05T20:25:16+02:00

MrUnknownDE commented

2026-04-05 20:25:16 +02:00

Originally created by @eis488 on 3/31/2026

CloudPanel version(s) affected

2.5.3

Description

After updating a Debian 13 server running CloudPanel 2.5.3, I consistently get this warning when running ldconfig:

ldconfig: /lib/libvarnishapi.so.3 is not a symbolic link

Varnish itself is running correctly, so this does not appear to be a runtime failure. It looks like a packaging issue with the CloudPanel-provided varnish package.

Environment:

Debian 13 (Trixie)
CloudPanel 2.5.3
varnish 7.5.0-2+clp-trixie

How to reproduce

Install or update CloudPanel on Debian 13 (Trixie).
Ensure package varnish 7.5.0-2+clp-trixie is installed.
Run these commands:
- dpkg -L varnish | grep libvarnishapi
- ls -l /usr/lib/libvarnishapi.so /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0
- ls -li /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0
- readlink -f /lib
- ldconfig
Observe that /usr/lib/libvarnishapi.so, /usr/lib/libvarnishapi.so.3, and /usr/lib/libvarnishapi.so.3.1.0 are regular files instead of symlinks.
ldconfig prints: ldconfig: /lib/libvarnishapi.so.3 is not a symbolic link

Possible Solution

It looks like the package may be shipping the shared library files as regular files instead of the usual symlink chain.

Expected layout would be something like:

libvarnishapi.so -> libvarnishapi.so.3
libvarnishapi.so.3 -> libvarnishapi.so.3.1.0
libvarnishapi.so.3.1.0 as the real file

So this may be a packaging issue in varnish 7.5.0-2+clp-trixie.

Additional Context

The server is otherwise healthy after update and reboot:

booted successfully into kernel 6.12.74+deb13+1-cloud-amd64
systemctl --failed returns 0 failed units
varnish, nginx, mariadb, redis, docker, dovecot, postfix, and netdata are all running normally

Relevant observations:

dpkg -L varnish | grep libvarnishapi
/usr/lib/libvarnishapi.so
/usr/lib/libvarnishapi.so.3
/usr/lib/libvarnishapi.so.3.1.0

ls -l /usr/lib/libvarnishapi.so /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0
-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so
-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3
-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3.1.0

ls -li /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0
28995 -rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3
28996 -rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3.1.0

readlink -f /lib
/usr/lib

*Originally created by @eis488 on 3/31/2026* ### CloudPanel version(s) affected 2.5.3 ### Description After updating a Debian 13 server running CloudPanel 2.5.3, I consistently get this warning when running `ldconfig`: `ldconfig: /lib/libvarnishapi.so.3 is not a symbolic link` Varnish itself is running correctly, so this does not appear to be a runtime failure. It looks like a packaging issue with the CloudPanel-provided `varnish` package. Environment: - Debian 13 (Trixie) - CloudPanel 2.5.3 - varnish 7.5.0-2+clp-trixie ### How to reproduce 1. Install or update CloudPanel on Debian 13 (Trixie). 2. Ensure package `varnish 7.5.0-2+clp-trixie` is installed. 3. Run these commands: - `dpkg -L varnish | grep libvarnishapi` - `ls -l /usr/lib/libvarnishapi.so /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0` - `ls -li /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0` - `readlink -f /lib` - `ldconfig` 4. Observe that `/usr/lib/libvarnishapi.so`, `/usr/lib/libvarnishapi.so.3`, and `/usr/lib/libvarnishapi.so.3.1.0` are regular files instead of symlinks. 5. `ldconfig` prints: `ldconfig: /lib/libvarnishapi.so.3 is not a symbolic link` ### Possible Solution It looks like the package may be shipping the shared library files as regular files instead of the usual symlink chain. Expected layout would be something like: - `libvarnishapi.so -> libvarnishapi.so.3` - `libvarnishapi.so.3 -> libvarnishapi.so.3.1.0` - `libvarnishapi.so.3.1.0` as the real file So this may be a packaging issue in `varnish 7.5.0-2+clp-trixie`. ### Additional Context The server is otherwise healthy after update and reboot: - booted successfully into kernel `6.12.74+deb13+1-cloud-amd64` - `systemctl --failed` returns 0 failed units - `varnish`, `nginx`, `mariadb`, `redis`, `docker`, `dovecot`, `postfix`, and `netdata` are all running normally Relevant observations: `dpkg -L varnish | grep libvarnishapi` `/usr/lib/libvarnishapi.so` `/usr/lib/libvarnishapi.so.3` `/usr/lib/libvarnishapi.so.3.1.0` `ls -l /usr/lib/libvarnishapi.so /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0` `-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so` `-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3` `-rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3.1.0` `ls -li /usr/lib/libvarnishapi.so.3 /usr/lib/libvarnishapi.so.3.1.0` `28995 -rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3` `28996 -rw-r--r-- 1 root root 854864 Sep 17 2025 /usr/lib/libvarnishapi.so.3.1.0` `readlink -f /lib` `/usr/lib`

MrUnknownDE referenced this issue

2026-04-05 20:25:51 +02:00

issue #200

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/cloudpanel-ce#3