Neueste Beiträge

Seiten: 1 ... 6 7 [8] 9 10
71
I have an update:

I deleted the /etc/ld.so.preload-file and added a file override.conf to /etc/systemd/system/vdr.service.d/ and /etc/systemd/system/sundtek.service.d

The override.conf file contains these two lines:
[Service]
Environment=LD_PRELOAD=/opt/lib/libmediaclient.so

I removed all VDR plugings and other packages related to VDR, except vdr and vdr-plugin-vnsiserver.

With this configuration, the server runs stable and VDR works; i can connect with KODI from a remote PC.
It was running for more than 36 hours without any problem.

Then i restored the file /etc/ld.so.preload which contains only one line "/opt/lib/libmediaclient.so" and executed "systemctl daemon-reload" (no reboot); after a few hours, the same problem happened again.

For debugging, i logged into all 6 local tty-consoles with user "root" on the server directly after booting.
In one console, i ran "htop", in another console i ran "dmesg -w" and some other logs in other consoles.

After a few hours, i noticed the server had the problem. During this time, VDR was in idle mode, no KODI was runnig.
On the local console, the htop output was freezed, but it showed no high cpu or memory usage. In the dmesg output, i had a lot of apparmor warnings with name="/opt/lib/libmediaclient.so", similar like in my first post.
I can switch between these consoles with <Alt>-F1/2/3...
When i enter a command in a console, e.g., "ls", it doesn't respond. But then, after pressing <CTRL>-C, i get the output of the ls command.

Then i deleted the file /etc/ld.so.preload and executed "systemctl daemon-reload", always with <CTRL>-C afterwards. After doing this, the server seemed to operate normal.
I tried to restart VDR with "systemctl restart vdr", but this command did not finish, i had to press <CTRL>-C.
I tried it multiple times and also with stop and start separately.

Then i did a reboot, it took a long time to shut down (several minutes).
After rebooting, i checked the VDR log (journalctl -u vdr).

There you can see some error messages from the failed vdr start before reboot:

Jan 30 13:26:00 srv1 systemd[1]: Starting vdr.service - Video Disk Recorder...
Jan 30 13:26:00 srv1 vdr[35811]: [35811] VDR version 2.6.9 started
Jan 30 13:26:00 srv1 vdr[35811]: [35811] switched to user 'vdr'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] codeset is 'UTF-8' - known
Jan 30 13:26:00 srv1 vdr[35811]: [35811] found 28 locales in /usr/share/locale
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'alb,sqi'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'bos'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'bul'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'chi,zho'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'eus,baq'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'iri,gle'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'jpn'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'lav'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'ltz'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'mlt'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'por'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no locale for language code 'smi'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.6.9
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/setup.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/sources.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/diseqc.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/scr.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/channels.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/timers.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/commands.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/reccmds.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/svdrphosts.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35811] loading /var/lib/vdr/keymacros.conf
Jan 30 13:26:00 srv1 vdr[35811]: [35813] video directory scanner thread started (pid=35811, tid=35813, prio=low)
Jan 30 13:26:00 srv1 vdr[35811]: [35814] epg data reader thread started (pid=35811, tid=35814, prio=high)
Jan 30 13:26:00 srv1 vdr[35811]: [35811] registered source parameters for 'A - ATSC'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] registered source parameters for 'C - DVB-C'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] registered source parameters for 'S - DVB-S'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] registered source parameters for 'T - DVB-T'
Jan 30 13:26:00 srv1 vdr[35811]: [35811] detected /dev/dvb/adapter1/frontend0
Jan 30 13:26:00 srv1 vdr[35811]: [35811] detected /dev/dvb/adapter0/frontend0
Jan 30 13:26:00 srv1 vdr[35811]: [35814] reading EPG data from /var/cache/vdr/epg.data
Jan 30 13:26:00 srv1 vdr[35811]: [35811] ERROR (dvbdevice.c,1945): /dev/dvb/adapter0/frontend0: Kein passendes Gerät bzw. keine passende Adresse gefunden
Jan 30 13:26:00 srv1 vdr[35811]: [35811] ERROR (dvbdevice.c,1945): /dev/dvb/adapter1/frontend0: Kein passendes Gerät bzw. keine passende Adresse gefunden
Jan 30 13:26:00 srv1 vdr[35811]: vdr: no primary device found - using first device!
Jan 30 13:26:00 srv1 vdr[35811]: [35811] no DVB device found
Jan 30 13:26:00 srv1 vdr[35811]: [35811] initializing plugin: vnsiserver (1.8.3): VDR-Network-Streaming-Interface (VNSI) Server
Jan 30 13:26:00 srv1 vdr[35811]: [35811] ERROR: invalid primary device number: 1
Jan 30 13:26:00 srv1 vdr[35811]: [35811] ERROR: no primary device found - using first device!
Jan 30 13:26:00 srv1 vdr[35811]: [35811] ERROR: invalid primary device number: 1
Jan 30 13:26:00 srv1 vdr[35811]: [35813] video directory scanner thread ended (pid=35811, tid=35813)
Jan 30 13:26:00 srv1 vdr[35811]: [35814] epg data reader thread ended (pid=35811, tid=35814)
Jan 30 13:26:01 srv1 vdr[35811]: [35811] deleting plugin: vnsiserver
Jan 30 13:26:01 srv1 vdr[35811]: [35811] max. latency time 0 seconds
Jan 30 13:26:01 srv1 vdr[35811]: [35811] exiting, exit code 2
Jan 30 13:26:01 srv1 systemd[1]: vdr.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 30 13:26:01 srv1 systemd[1]: vdr.service: Failed with result 'exit-code'.
Jan 30 13:26:01 srv1 systemd[1]: Failed to start vdr.service - Video Disk Recorder.
Jan 30 13:26:01 srv1 systemd[1]: vdr.service: Consumed 864ms CPU time, 121.7M memory peak.


So for me i have a solution, but maybe it would be interesting to find out why the servers hangs when the ld.so.preload file is installed.
Do you have any ideas, which logfiles i could check?
72
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von tweak am Januar 29, 2026, 05:56:17 Nachmittag »
Danke für den Tipp.
ich werde das mal versuchen, ansonsten einen neuen bestellen.
73
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von Sundtek am Januar 28, 2026, 07:54:19 Vormittag »
Der Tuner ist über 10 Jahre alt, der wurde damals noch von einer Partnerfirma entwickelt, von der wir uns getrennt haben und anschließend die Geräte selber entwickelt haben. DVB-S/S2/S2X wurde erst ab 2018 direkt von uns entwickelt...

Stecke den Tuner direkt an und schau Dir auch die BER an, wenn eventuell hilft auch ein längeres USB Kabel.

Teste mal
/opt/bin/mediaclient --testastra -d /dev/dvb/adapter0/frontend0
/opt/bin/mediaclient --readsignal=10 -d /dev/dvb/adapter0/frontend0
74
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von tweak am Januar 27, 2026, 11:25:27 Nachmittag »
Ein Thema habe ich noch, ich nutze den Tuner für tvheadend. Habe jedoch vereinzelt mit Continuty Errors zu kämpfen, so das das Bild einfriert.

Kann das an der Spannungsversorgung liegen? Der Tuner steckt auf einem aktive. USB Hub.

Empfang ist bei 92% und Qualität ebenfalls bei 90%.

Danke für die Hilfe
75
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von tweak am Januar 27, 2026, 04:25:30 Nachmittag »
Danke für die rasche Rückmeldung!
Das war exakt die Ursache.
Download klappt nun und (Respekt) klappt out-of-Box mit Rocky 10.

LG
76
This sounds like a driver / kernel problem.

- Check the system logs.
- Also check the memory utilisation during runtime.

I highly doubt that this has anything to do with our driver.

The good thing seems to be that it is reproducible, the closer you can narrow it down workarounds or other fixes could be applied.

From your description it sounds like a problem with the SSD or controller for it.
77
> with "hang" you mean the network connectivity problem?

It's not just a network connectivity problem.
It is also not possible to login on a local console.

I can log in locally or by SSH over network, before the server hangs.
Then i wait until it hangs; when i try to execute a command, e.g. "ls", nothing happens at first, i get no response. After pressing <Ctrl>-C, i get the output of the ls-command.
Starting of other programs is also not possible.

Also, the 'poweroff'-command does not work. The server starts to shut down, but then at some point it hangs and can only be restarted be a a power cycle.

Yesterday in the evening, i uninstalled all VDR plugins except vdr-plugin-vnsiserver. Then i connected with KODI from a different computer and did some testing.

Watching television worked. I started a recording and tried to watch a recorded movie while another one was recorded. In this situation, the problem happened again and i had to restart the server.
It seems, the error is triggered by some actions from VDR, but it also happens after some time when i only startup the server with no KODI client connected.
78
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re: Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von Sundtek am Januar 27, 2026, 11:59:43 Vormittag »
Hi,

was geht da nicht? Die Links sind seit ca 15 Jahren gleich. Im August letzten Jahres hatten einige "Security" Websites einen fehlerhaften Scanner auf das Web losgelassen welcher Websites mit Shellscripts als böswillig eingestuft hat, das hat sich aber mittlerweile wieder gelegt. Die Auswirkung war dass einige Internet-Anbieter den Link zum Treiber blockiert haben.
Solltest Du selber einen Filter auf dem Router installiert haben, aktualisiere diesen.

Zitat
sudo -s
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod +x sundtek_netinst.sh
./sundtek_netinst.sh
79
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Sundtek SkyTV Ultimate IV mit Rocky-Linux
« Letzter Beitrag von tweak am Januar 27, 2026, 11:57:59 Vormittag »
Hallo,
ich versuche gerade Aufgrund Systemumstellung meinen Sundtek-Tuner mit Rocky-Linux einzurichten.
Jedoch scheitere ich schon daran, dass die Downloads nicht funktionieren.

Könnte mir bitte jemand einen funktionierenden Link für das Installations-Script zur Verfügung stellen?

Danke!
mfG
80
with "hang" you mean the network connectivity problem?

The DENIED message should be fine because kea-lfc doesn't need libmediaclient.so.

You can always isolate the LD_PRELOAD to VDR only by modifying the vdr systemd startscript.

It's difficult to have the same setup as you do, so I'd prefer to isolate the problem on your side to fix your problem.
Seiten: 1 ... 6 7 [8] 9 10