Problem with installation on Debian 13, computer hangs after several hours

[JohannesE]

I am running VDR on a debian server for many years.
Last year i bought an Sundtek SkyTV Ultimate Dual UHD and it worked without problems.

After an upgrade to debian 13, the server is working unstable, it hangs after several hours.
Because the server was upgraded over several debian versions, i decided to do a fresh install on a new SSD on the same computer, but i get the same behavior.

To examin the problem, I checked the logfiles, in dmesg i found messages like these:

[Jan24 12:42] audit: type=1400 audit(1769254930.432:150): apparmor="DENIED" operation="open" class="file" profile="kea-dhcp4" name="/opt/lib/libmediaclient.so" pid=1013100 co>
[Jan24 13:17] audit: type=1400 audit(1769257021.913:151): apparmor="ALLOWED" operation="open" class="file" profile="unix-chkpwd" name="/opt/lib/libmediaclient.so" pid=1020843>
[  +0,000014] audit: type=1400 audit(1769257021.913:152): apparmor="ALLOWED" operation="file_mmap" class="file" profile="unix-chkpwd" name="/opt/lib/libmediaclient.so" pid=10>
[Jan24 13:30] audit: type=1400 audit(1769257801.376:153): apparmor="ALLOWED" operation="open" class="file" profile="unix-chkpwd" name="/opt/lib/libmediaclient.so" pid=1023718>
[  +0,000006] audit: type=1400 audit(1769257801.376:154): apparmor="ALLOWED" operation="file_mmap" class="file" profile="unix-chkpwd" name="/opt/lib/libmediaclient.so" pid=10>

After some investigation i found the file the file /etc/ld.so.preload, which loads /opt/lib/libmediaclient.so.
For testing, i removed this file and without it, i get no longer server hang-ups and the messages in demsg also have disappeared.
But without this preload, VDR is no longer working.

Is there any other way to load this shared library? It should only be loaded for programs that require it.

The VDR version, which is included in the stable debian version is 2.6.9-3. Could this be a problem?

The VDR server has no graphical desktop.
When the server hangs, it responds to a network ping, but it is not possible to login to the server with ssh or on a local console.
But i can login to local consoles in advance and run tools like dmesg, htop or similar. Then, when the server hangs, i still can switch between these consoles (Alt-F1, Alt-F2...) and read the output of these tools.

What can i do to get the server running stable?

[Sundtek]

So basically just ssh is blocked? Possibly there are some apparmor items which block it, can you check for other items in the logfile which show something else than ALLOWED?
Possibly the new distribution came with some new rules on board which interfere. Maybe you can join the discord chat so we can chat about your problem (that might be fastest)?

You have a few options at that point (to get VDR work with it).

The discord chat is here:
https://discord.gg/AR5QJhyNnw

I have installed Trixie on our side, but cannot reproduce any problem - so I will need your help to see what's going on for you.

[JohannesE]

Thanks for your reply. Yesterday i was not at home, so i could not answer.

i did a little more testing:
I restored the ld.so.preload file and stopped VDR with "systemctl stop vdr"; the server is running now for nearly 24 h and didn't hang.

I still get the apparmor warnings, most logfile entries are with "ALLOWED", the only message that contains "DENIED" is this one (it repeates every 60 minutes):
audit: type=1400 audit(1769459579.441:264): apparmor="DENIED" operation="open" class="file" profile="kea-lfc" name="/opt/lib/libmediaclient.so" pid=306381 comm="kea-lfc" requested_mask="r" denied_mask="r" fsuid=115 ouid=0

So maybe the server hangup is more a problem with VDR than the USB driver.
Did you also run VDR on the debian trixie? How long did you let it run? Here the server sometimes runs for several hours or half a day before it gets unstable, sometimes it happens very quickly.

I think i will do some more testing without any VDR plugins, just a minimal installation and maybe i will test a more recent VDR version.
What logfiles would be interesting to examine the problem further?