(solved) yavdr 0.5-beta Server nach Installation und Update Bild ruckeln und Ton stottern

  • Hallo nachdem ich meine sehr gute laufende Server Installation durch einen dummen Fehler zerschossen habe stand heute eine Neuinstallation an. Nach Installation und apt-get update + apt-get dist-upgrade habe ich nun das Problem das das Bild extrem ruckelt und der Ton stottert. Im Syslog sehe ich Ring Buffer Overflows. Hat jmd. ne idee woher das nun kommt? Bzw. welche Logfiles könnten bei der Eingrenzung helfen?
    Bin für Tipps dankbar


    Grüße


    Drops


    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: femon
    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: iptv
    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: live
    Oct 11 22:20:10 vdr-server vdr: [1230] LIVE: initial file cache has 82 entries and needs 377394 bytes of data!
    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: epgsearch
    Oct 11 22:20:10 vdr-server vdr: [1230] loading /var/lib/vdr/plugins/epgsearch/epgsearchcats.conf
    Oct 11 22:20:10 vdr-server vdr: [1230] loading /var/lib/vdr/plugins/epgsearch/epgsearchmenu.conf
    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: markad
    Oct 11 22:20:10 vdr-server vdr: [1230] starting plugin: dynamite
    Oct 11 22:20:10 vdr-server vdr: [1230] dynamite: startup channel is 1
    Oct 11 22:20:10 vdr-server vdr: [1230] skin "anthra_1920_FSE" not available - using "sttng" instead
    Oct 11 22:20:10 vdr-server vdr: [1230] loading /var/lib/vdr/themes/sttng-default.theme
    Oct 11 22:20:10 vdr-server vdr: [1230] remote control LIRC - keys known
    Oct 11 22:20:10 vdr-server vdr: [1230] switching to channel 1
    Oct 11 22:20:10 vdr-server vdr: [1230] OSD size changed to 720x480 @ 1
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: Action Lock
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: try to connect to system bus
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: connect to system bus successful
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: Action Unlock
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: new message, object /org/freedesktop/DBus, interface org.freedesktop.DBus, member NameAcquired
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: NameAcquired: get ownership of name de.tvdr.vdr
    Oct 11 22:20:10 vdr-server vdr: [1488] LIRC remote control thread started (pid=1230, tid=1488)
    Oct 11 22:20:10 vdr-server vdr: [1489] receiver on device 1 thread started (pid=1230, tid=1489)
    Oct 11 22:20:10 vdr-server vdr: [1487] EPGSearch: conflictcheck thread started (pid=1230, tid=1487)
    Oct 11 22:20:10 vdr-server vdr: [1485] VDR XVDR Server thread started (pid=1230, tid=1485)
    Oct 11 22:20:10 vdr-server vdr: [1484] streamdev server thread started (pid=1230, tid=1484)
    Oct 11 22:20:10 vdr-server vdr: [1484] Streamdev: Listening (VTP) on port 2004
    Oct 11 22:20:10 vdr-server vdr: [1484] Streamdev: Listening (HTTP) on port 3000
    Oct 11 22:20:10 vdr-server vdr: [1486] [live] INFO: attempt to listen on ip = '0.0.0.0'
    Oct 11 22:20:10 vdr-server vdr: [1486] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): Datei oder Verzeichnis nicht gefunden
    Oct 11 22:20:10 vdr-server vdr: [1482] dbus2vdr: new message, object /Recording, interface org.freedesktop.DBus.Introspectable, member Introspect
    Oct 11 22:20:10 vdr-server rsyslogd-2177: imuxsock begins to drop messages from pid 1230 due to rate-limiting
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Service resolved: vdr-client.local to Recordings on vdr-client
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Resolved type _nfs._tcp on vdr-client.local
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: media is mounted on /media/Video/vdr-client/ for server vdr-client.local and share /srv/video
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Service resolved: vdr-client.local to Videos on vdr-client
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Resolved type _nfs._tcp on vdr-client.local
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: media is mounted on /media/Musik/vdr-client/ for server vdr-client.local and share /srv/audio
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Service resolved: vdr-client.local to Music on vdr-client
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Resolved type _nfs._tcp on vdr-client.local
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: media is mounted on /media/Bilder/vdr-client/ for server vdr-client.local and share /srv/picture
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Service resolved: vdr-client.local to Pictures on vdr-client
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Resolved type _nfs._tcp on vdr-client.local
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: media is mounted on /srv/vdr/video.00/vdr-client/ for server vdr-client.local and share /srv/share/vdr
    Oct 11 22:20:10 vdr-server avahi-mounter[1390]: Service resolved: vdr-client.local to Recordings on vdr-client
    Oct 11 22:20:10 vdr-server kernel: [ 22.980921] init: wait-for-job-state (vdr-frontendvdr) main process (1094) killed by TERM signal
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Server startup complete. Host name is vdr-server.local. Local service cookie is 1698931542.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "Videos on vdr-server" (/services/vdr-video.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "Recordings on vdr-server" (/services/vdr-vdr.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "SVDRP on vdr-server" (/services/vdr-svdrp.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "Pictures on vdr-server" (/services/vdr-picture.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "Music on vdr-server" (/services/vdr-audio.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-daemon[1397]: Service "vdr-server" (/services/udisks.service) successfully established.
    Oct 11 22:20:11 vdr-server avahi-mounter[1390]: Resolved type _nfs._tcp on vdr-server.local
    Oct 11 22:20:12 avahi-mounter[1390]: last message repeated 7 times
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:733 for /srv/audio (/srv/audio)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:802 for /srv/picture (/srv/picture)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:853 for /srv/share/vdr (/srv/share/vdr)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:707 for /srv/video (/srv/video)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:725 for /srv/audio (/srv/audio)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:688 for /srv/picture (/srv/picture)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:723 for /srv/share/vdr (/srv/share/vdr)
    Oct 11 22:20:12 vdr-server rpc.mountd[1402]: authenticated mount request from 10.240.183.104:819 for /srv/video (/srv/video)
    Oct 11 22:20:14 vdr-server ntpdate[1025]: adjust time server 91.189.94.4 offset 0.016893 sec
    Oct 11 22:20:15 vdr-server kernel: [ 27.264020] eth0: no IPv6 routers present
    Oct 11 22:20:58 vdr-server dbus[1178]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
    Oct 11 22:20:58 vdr-server dbus[1178]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
    Oct 11 22:20:58 vdr-server polkitd[1766]: started daemon version 0.104 using authority implementation `local' version `0.104'
    Oct 11 22:20:58 vdr-server dbus[1178]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Oct 11 22:20:58 vdr-server dbus[1178]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
    Oct 11 22:21:01 vdr-server rsyslogd-2177: imuxsock lost 47 messages from pid 1230 due to rate-limiting
    Oct 11 22:21:01 vdr-server vdr: [1484] Streamdev: Accepted new client (VTP) 10.240.183.104:34350
    Oct 11 22:21:01 vdr-server vdr: [1484] streamdev-server TUNE S19.2E-1-1107-17502: Priority unknown - using 0
    Oct 11 22:21:01 vdr-server vdr: [1484] Streamdev: Setting data connection to 10.240.183.104:34042
    Oct 11 22:21:01 vdr-server vdr: [2033] receiver on device 2 thread started (pid=1230, tid=2033)
    Oct 11 22:21:01 vdr-server vdr: [2032] streamdev-livestreaming thread started (pid=1230, tid=2032)
    Oct 11 22:21:01 vdr-server vdr: [2031] streamdev-writer thread started (pid=1230, tid=2031)
    Oct 11 22:21:01 vdr-server vdr: [2034] TS buffer on device 2 thread started (pid=1230, tid=2034)
    Oct 11 22:21:44 vdr-server vdr: [1485] XVDR: Timers state changed (1)
    Oct 11 22:21:44 vdr-server vdr: [1485] XVDR: Requesting clients to reload timers
    Oct 11 22:21:47 vdr-server vdr: [2033] buffer usage: 70% (tid=2032)
    Oct 11 22:21:47 vdr-server vdr: [2033] buffer usage: 80% (tid=2032)
    Oct 11 22:21:47 vdr-server vdr: [2033] buffer usage: 90% (tid=2032)
    Oct 11 22:21:48 vdr-server vdr: [2033] ERROR: 1 ring buffer overflow (188 bytes dropped)
    Oct 11 22:21:54 vdr-server vdr: [2033] ERROR: 27932 ring buffer overflows (5251216 bytes dropped)
    Oct 11 22:21:55 vdr-server vdr: [2033] buffer usage: 20% (tid=2032)
    Oct 11 22:21:57 vdr-server vdr: [2033] buffer usage: 70% (tid=2032)
    Oct 11 22:21:58 vdr-server vdr: [2033] buffer usage: 80% (tid=2032)
    Oct 11 22:21:58 vdr-server vdr: [2033] buffer usage: 90% (tid=2032)
    Oct 11 22:21:59 vdr-server vdr: [2033] buffer usage: 60% (tid=2032)
    Oct 11 22:21:59 vdr-server vdr: [2033] buffer usage: 70% (tid=2032)
    Oct 11 22:21:59 vdr-server vdr: [2033] buffer usage: 80% (tid=2032)
    Oct 11 22:22:00 vdr-server vdr: [2033] buffer usage: 90% (tid=2032)
    Oct 11 22:22:00 vdr-server vdr: [2033] ERROR: 4290 ring buffer overflows (806520 bytes dropped)
    Oct 11 22:22:06 vdr-server vdr: [2033] ERROR: 19200 ring buffer overflows (3609600 bytes dropped)
    Oct 11 22:22:06 vdr-server vdr: [2033] buffer usage: 20% (tid=2032)
    Oct 11 22:22:10 vdr-server vdr: [2033] buffer usage: 70% (tid=2032)
    Oct 11 22:22:10 vdr-server vdr: [2033] buffer usage: 80% (tid=2032)
    Oct 11 22:22:11 vdr-server vdr: [2033] buffer usage: 90% (tid=2032)
    Oct 11 22:22:12 vdr-server vdr: [2033] ERROR: 6036 ring buffer overflows (1134768 bytes dropped)
    .
    .
    .

    Alt-VDR1: Siemens D1184-B11, PIII 800Mhz, 256mb Ram, Samsung 500GB HD, DVB-S TT 2.3 full_ts,DVB-S Skystar 2, Intel PRO/1000 MT, AV-Board 1.3
    Software: easyvdr 0.6.10


    Server: Asrock Alive NF7G HD720P , 2GB RAM, Teevi s470, Technotrend S2 1600, Technotrend S2 S2 3200, yavdr0.5, Headless Streaming Server
    Client: ZBOX ID41e, 4GB RAM, SSD yavdr0.5, Pollin X10 FB, softhddevice
    Test-Client: Raspberry PI, Openelec

    Einmal editiert, zuletzt von drops ()

  • Moin!


    Ich rate mal, dass du "headless" im WFE aktiviert hast und per streamdev guckst?
    Welche Version hat der Client?


    Lars.

  • Hallo Lars,


    korrekt geraten. Sowohl CLient als auch Server laufen mit der yavdr0.5-beta. Bis zum gestrigen Distri-Upgrade sind auch beide nahezu perfekt gelaufen. Bei beiden habe ich gestern ein Distri-Upgrade durchgeführt. Da ich aber am Server schon einige Spiel und Bastelaktionen hinter mir hatte habe ich gestern dann noch eine Neuinstallation mit anschliessendem Distr-Upgrade durchgeführt. Ich ärger mich jetzt nur das ich vor dem Upgrade keinen Test mit dem Client durchgeführt habe. Sonst hätte ich jetzt genauer eingrenzen können wer das Problem verursacht. Da die Buffer Overflows aber auf dem Server zu sehen sind vermute ich das die Fehler schon hier passieren. Oder liege ich hier falsch? (Hardware siehe Signatur)


    Grüße


    Martin

    Alt-VDR1: Siemens D1184-B11, PIII 800Mhz, 256mb Ram, Samsung 500GB HD, DVB-S TT 2.3 full_ts,DVB-S Skystar 2, Intel PRO/1000 MT, AV-Board 1.3
    Software: easyvdr 0.6.10


    Server: Asrock Alive NF7G HD720P , 2GB RAM, Teevi s470, Technotrend S2 1600, Technotrend S2 S2 3200, yavdr0.5, Headless Streaming Server
    Client: ZBOX ID41e, 4GB RAM, SSD yavdr0.5, Pollin X10 FB, softhddevice
    Test-Client: Raspberry PI, Openelec

  • Moin!


    Dass die Versionen gleich sind, ist schon mal gut.
    Auf dem Server laufen die Puffer voll, weil der Client sie nicht schnell genug abholt. Also kann das Problem auch auf dem Client sein.
    Wenn du den Client stoppst, gehen ja die Overflows weg (vermute ich).
    Ein Blick ins Client-Log könnte auch helfen.


    Lars.

  • du hast recht es scheint ein Problem auf dem Client zu sein. Streaming auf einen anderen PC funktioniert. Am Client läuft das syslog mit folgender Meldung zu:


    Oct 12 14:22:10 vdr-client vdr: video/vdpau: missed frame (2699/2656)
    Oct 12 14:22:10 vdr-client vdr: video: audio/video difference too big
    Oct 12 14:22:10 vdr-client vdr: video: 20:27:51.291+8888 357 240/\ms 189+6 v-buf
    Oct 12 14:22:10 vdr-client vdr: video/vdpau: missed frame (2700/2658)
    Oct 12 14:22:10 vdr-client vdr: video: audio/video difference too big
    Oct 12 14:22:10 vdr-client vdr: video: 20:27:51.311+8888 339 240/\ms 189+7 v-buf

    Alt-VDR1: Siemens D1184-B11, PIII 800Mhz, 256mb Ram, Samsung 500GB HD, DVB-S TT 2.3 full_ts,DVB-S Skystar 2, Intel PRO/1000 MT, AV-Board 1.3
    Software: easyvdr 0.6.10


    Server: Asrock Alive NF7G HD720P , 2GB RAM, Teevi s470, Technotrend S2 1600, Technotrend S2 S2 3200, yavdr0.5, Headless Streaming Server
    Client: ZBOX ID41e, 4GB RAM, SSD yavdr0.5, Pollin X10 FB, softhddevice
    Test-Client: Raspberry PI, Openelec

  • Moin!


    Tja, da kann ich dir leider nicht weiterhelfen.
    Irgendwie "taugen" die Video/Audio-Daten nicht so richtig, die am Client ankommen...


    Lars.

  • Hallo Lars,


    trotzdem danke für deine Unterstützung. Ich habe mittlerweile den Client neu aufgesetzt. Aktuell ist Bild und Ton i.O. Allerdings habe ich noch kein Distri-Upgrade gemacht. Daran traue ich mich so kurz vorm Länderspiel nicht. Somit lag das Problem klar am Client. Werd morgen mal ein Distri-Upgrade machen und schauen was dann passiert.


    Grüße


    Martin

    Alt-VDR1: Siemens D1184-B11, PIII 800Mhz, 256mb Ram, Samsung 500GB HD, DVB-S TT 2.3 full_ts,DVB-S Skystar 2, Intel PRO/1000 MT, AV-Board 1.3
    Software: easyvdr 0.6.10


    Server: Asrock Alive NF7G HD720P , 2GB RAM, Teevi s470, Technotrend S2 1600, Technotrend S2 S2 3200, yavdr0.5, Headless Streaming Server
    Client: ZBOX ID41e, 4GB RAM, SSD yavdr0.5, Pollin X10 FB, softhddevice
    Test-Client: Raspberry PI, Openelec

  • Moin Moin,


    hab mich heute morgen noch ans Dist-Upgrade gewagt. Der Fehler tritt nicht wieder auf. Somit ist das Problem durch eine Neuinstallation erst mal gelöst. Danke für die Unterstützung.


    Grüße


    Drops

    Alt-VDR1: Siemens D1184-B11, PIII 800Mhz, 256mb Ram, Samsung 500GB HD, DVB-S TT 2.3 full_ts,DVB-S Skystar 2, Intel PRO/1000 MT, AV-Board 1.3
    Software: easyvdr 0.6.10


    Server: Asrock Alive NF7G HD720P , 2GB RAM, Teevi s470, Technotrend S2 1600, Technotrend S2 S2 3200, yavdr0.5, Headless Streaming Server
    Client: ZBOX ID41e, 4GB RAM, SSD yavdr0.5, Pollin X10 FB, softhddevice
    Test-Client: Raspberry PI, Openelec

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!