dbus2vdr läuft Amok

Frodo · 1. Mai 2016

Habe heute mal wieder mein Logfile unter die Lupe genommen da der Load meines VDRs ungewöhnlich hoch ist, da fand ich direkt nach dem Start folgendes:

Spoiler anzeigen

Code

May  1 15:38:59 vdr4 vdr: [2255] VDR version 2.2.0 started
May  1 15:38:59 vdr4 vdr: [2255] switched to user 'vdr'
May  1 15:38:59 vdr4 vdr: [2255] codeset is 'UTF-8' - known
May  1 15:38:59 vdr4 vdr: [2255] override character table is 'ISO-8859-9'
May  1 15:38:59 vdr4 vdr: [2255] found 28 locales in /usr/share/locale
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-channellists.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-conflictcheckonly.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-dbus2vdr.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-dummydevice.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-epg2vdr.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearch.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-epgsearchonly.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-extrecmenu.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-femon.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-lcdproc.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-live.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] [live] INFO: validating server ip '0.0.0.0'
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-markad.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-menuorg.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-osdteletext.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-plex.so.2.2.0
May  1 15:38:59 vdr4 nvidia-persistenced: Started (2288)
May  1 15:38:59 vdr4 avahi-daemon[811]: Service "Music on vdr4" (/services/vdr-audio.service) successfully established.
May  1 15:38:59 vdr4 avahi-daemon[811]: Service "Pictures on vdr4" (/services/vdr-picture.service) successfully established.
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-quickepgsearch.so.2.2.0
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-restfulapi.so.2.2.0
May  1 15:38:59 vdr4 avahi-daemon[811]: Service "Recordings on vdr4" (/services/vdr-vdr.service) successfully established.
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: Port has been set to 8002!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: Ip has been set to 0.0.0.0!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: The EPG-Images will be loaded from /var/cache/vdr/epgimages!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: can not add webapp 'webapp'! Path '/var/lib/vdr/restfulapi/webapp' does not exist!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: trying to parse command line arguments
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: Port has been set to 8002!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: Ip has been set to 0.0.0.0!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: The EPG-Images will be loaded from /var/cache/vdr/epgimages!
May  1 15:38:59 vdr4 vdr: [2255] restfulapi: can not add webapp 'webapp'! Path '/var/lib/vdr/plugins/restfulapi/webapp' does not exist!
May  1 15:38:59 vdr4 vdr: [2255] RESTful-API Settings: port: 8002, ip: 0.0.0.0, eimgs: /var/cache/vdr/epgimages, cimgs: , webapp: , headers: activated
May  1 15:38:59 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-satip.so.2.2.0
May  1 15:39:00 vdr4 avahi-daemon[811]: Service "Videos on vdr4" (/services/vdr-video.service) successfully established.
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-scraper2vdr.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-skindesigner.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-softhddevice.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-tvguideng.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-vdrmanager.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-vnsiserver.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-weatherforecast.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-wirbelscan.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading plugin: /usr/lib/vdr/plugins/libvdr-dynamite.so.2.2.0
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/setup.conf
May  1 15:39:00 vdr4 vdr: [2289] dynamite udev monitor for subsystem dvb thread started (pid=2255, tid=2289, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] ERROR: unknown config parameter: PlayJump = 0
May  1 15:39:00 vdr4 vdr: [2255] ERROR: unknown config parameter: plex.DefaultViewMode = 0
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/sources.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/diseqc.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/scr.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/channels.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/timers.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/commands.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/reccmds.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/svdrphosts.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/remote.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/keymacros.conf
May  1 15:39:00 vdr4 vdr: [2255] ERROR: unknown plugin 'xineliboutput'
May  1 15:39:00 vdr4 vdr: [2255] registered source parameters for 'A - ATSC'
May  1 15:39:00 vdr4 vdr: [2255] registered source parameters for 'C - DVB-C'
May  1 15:39:00 vdr4 vdr: [2255] registered source parameters for 'S - DVB-S'
May  1 15:39:00 vdr4 vdr: [2255] registered source parameters for 'T - DVB-T'
May  1 15:39:00 vdr4 vdr: [2255] no DVB device found
May  1 15:39:00 vdr4 vdr: [2291] video directory scanner thread started (pid=2255, tid=2291, prio=high)
May  1 15:39:00 vdr4 vdr: [2290] video directory scanner thread started (pid=2255, tid=2290, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: channellists (0.0.5): Verwalte deine Kanallisten
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: conflictcheckonly (0.0.1): Direkter Zugriff auf epgsearch's Konflikt-Prüfungs-Menü
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: dbus2vdr (30): Steuerung des VDR über D-Bus
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: dummydevice (2.0.0): Output device that does nothing
May  1 15:39:00 vdr4 vdr: [2292] epg data reader thread started (pid=2255, tid=2292, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] new device number 1
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: epg2vdr (1.0.28-GIT): epg2vdr plugin
May  1 15:39:00 vdr4 vdr: [2292] reading EPG data from /var/cache/vdr/epg.data
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: epgsearch (1.0.1.beta5): Suche im EPG nach Wiederholungen und anderem
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: epgsearchonly (0.0.1): Direkter Zugriff auf epgsearch's Suchenmenu
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: extrecmenu (1.2.5-git): Erweitertes Aufzeichnungs-Menü
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: femon (2.2.2): DVB Signal Informationsanzeige (OSD)
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: lcdproc (0.0.10-jw9): LCDproc Ausgabe
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: live (0.3.0): Live Interactive VDR Environment
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: markad (0.1.5pre): Markiere Werbung
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: menuorg (0.5.1): Reorganisiert das Haupmenü
May  1 15:39:00 vdr4 vdr: [2255] loading menuorg config file from /var/lib/vdr/plugins/menuorg.xml
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: osdteletext (0.9.5): Zeigt den Videotext auf dem OSD an
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: plex (0.3.0): Plex for VDR Plugin
May  1 15:39:00 vdr4 vdr: [2255] cTimeMs: using monotonic clock (resolution is 1 ns)
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: quickepgsearch (0.0.1): Schnelle Suche nach Sendungen
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: restfulapi (0.2.6.1): Offers a RESTful-API to retrieve data from VDR
May  1 15:39:00 vdr4 vdr: [2296] [plex] Starting Controlserver...
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: satip (2.2.3): SAT>IP Geräte
May  1 15:39:00 vdr4 vdr: [2298] SATIP poller thread started (pid=2255, tid=2298, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] SATIP: Adding server '192.168.6.237|DVBS2-4|OctopusNet' CI: yes Quirks: none
May  1 15:39:00 vdr4 vdr: [2255] SATIP: Adding server '192.168.6.236|DVBS2-4|OctopusNet' CI: yes Quirks: none
May  1 15:39:00 vdr4 vdr: [2255] new device number 2
May  1 15:39:00 vdr4 vdr: [2255] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 0]
May  1 15:39:00 vdr4 vdr: [2299] SATIP#0 tuner thread started (pid=2255, tid=2299, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] new device number 3
May  1 15:39:00 vdr4 vdr: [2255] SATIP: Creating device CardIndex=2 DeviceNumber=2 [device 1]
May  1 15:39:00 vdr4 vdr: [2301] device 2 section handler thread started (pid=2255, tid=2301, prio=low)
May  1 15:39:00 vdr4 vdr: [2300] SATIP#0 section handler thread started (pid=2255, tid=2300, prio=high)
May  1 15:39:00 vdr4 vdr: [2302] SATIP#1 tuner thread started (pid=2255, tid=2302, prio=high)
May  1 15:39:00 vdr4 vdr: [2303] SATIP#1 section handler thread started (pid=2255, tid=2303, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: scraper2vdr (0.1.21): 'scraper2vdr' plugin
May  1 15:39:00 vdr4 vdr: scraper2vdr: using image directory /var/cache/vdr/epgimages/
May  1 15:39:00 vdr4 vdr: [2304] device 3 section handler thread started (pid=2255, tid=2304, prio=low)
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: skindesigner (1.0.2): Skin Designer
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: softhddevice (0.6.1rc1): Ein Software und GPU emulieres HD-Gerät
May  1 15:39:00 vdr4 vdr: [2255] new device number 4
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: tvguideng (0.3.0): TV Guide for Skindesigner Skins
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: vdrmanager (0.14): VDR-Manager plugin
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: vnsiserver (1.3.1): VDR-Network-Streaming-Interface (VNSI) Server
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: weatherforecast (0.2.0): Weatherforecast based on forecast.io
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: wirbelscan (0.0.9): DVB and pvrinput channel scan for VDR
May  1 15:39:00 vdr4 vdr: [2255] initializing plugin: dynamite (0.3.0): Empfangsgeräte während des Betriebs ein- und aushängen
May  1 15:39:00 vdr4 vdr: [2255] dynamite: softhddevice detected, leaving 1 additional slot(s) free
May  1 15:39:00 vdr4 vdr: [2255] dynamite: creating dynamic device slots as much as possible
May  1 15:39:00 vdr4 vdr: [2255] new device number 5
May  1 15:39:00 vdr4 vdr: [2255] new device number 6
May  1 15:39:00 vdr4 vdr: [2255] new device number 7
May  1 15:39:00 vdr4 vdr: [2255] new device number 8
May  1 15:39:00 vdr4 vdr: [2255] new device number 9
May  1 15:39:00 vdr4 vdr: [2255] new device number 10
May  1 15:39:00 vdr4 vdr: [2255] new device number 11
May  1 15:39:00 vdr4 vdr: [2255] new device number 12
May  1 15:39:00 vdr4 vdr: [2255] new device number 13
May  1 15:39:00 vdr4 vdr: [2255] new device number 14
May  1 15:39:00 vdr4 vdr: [2255] new device number 15
May  1 15:39:00 vdr4 vdr: [2255] udev: no devices found for dvb/DVB_DEVICE_TYPE=frontend
May  1 15:39:00 vdr4 vdr: [2255] setting primary device to 1
May  1 15:39:00 vdr4 vdr: [2255] assuming manual start of VDR
May  1 15:39:00 vdr4 vdr: [2255] SVDRP listening on port 6419
May  1 15:39:00 vdr4 vdr: [2255] skin "estuary4vdr" not available - using "lcars" instead
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/themes/lcars-default.theme
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: channellists
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: conflictcheckonly
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: dbus2vdr
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: mainloop started
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: dummydevice
May  1 15:39:00 vdr4 vdr: [2306] Socket Handler thread started (pid=2255, tid=2306, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: epg2vdr
May  1 15:39:00 vdr4 vdr: epg2vdr: Info: Calling mysql_library_init()
May  1 15:39:00 vdr4 vdr: epg2vdr: Set locale to 'de_DE.UTF-8'
May  1 15:39:00 vdr4 vdr: epg2vdr: detected UTF-8
May  1 15:39:00 vdr4 vdr: epg2vdr: Dictionary '/var/lib/vdr/plugins/epg2vdr//epg.dat' loaded
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: epgsearch
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/plugins/epgsearch/epgsearchcats.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/plugins/epgsearch/epgsearchmenu.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/plugins/epgsearch/epgsearchswitchtimers.conf
May  1 15:39:00 vdr4 vdr: [2255] loading /var/lib/vdr/plugins/epgsearch/timersdone.conf
May  1 15:39:00 vdr4 vdr: [2255] EPGSearch: loading /var/lib/vdr/plugins/epgsearch/epgsearchupdmail.templ
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: epgsearchonly
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: extrecmenu
May  1 15:39:00 vdr4 vdr: [2315] extrecmenu worker thread thread started (pid=2255, tid=2315, prio=high)
May  1 15:39:00 vdr4 vdr: [2314] EPGSearch: conflictcheck thread started (pid=2255, tid=2314, prio=high)
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: femon
May  1 15:39:00 vdr4 vdr: [2255] starting plugin: lcdproc
May  1 15:39:00 vdr4 vdr: [2313] EPGSearch: searchtimer thread started (pid=2255, tid=2313, prio=high)
May  1 15:39:00 vdr4 vdr: [2311] epg2vdr-update thread started (pid=2255, tid=2311, prio=high)
May  1 15:39:00 vdr4 vdr: epg2vdr: Calling mysql_init(2311)
May  1 15:39:00 vdr4 vdr: epg2vdr: SQL client character now 'utf8'
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.6
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: thread-pool for handling signal-emits started
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.7
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.8
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.9
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.10
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.11
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.12
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.13
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.14
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.15
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.16
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.17
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.18
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.19
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.20
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.21
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.22
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.23
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.24
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.25
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.26
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.27
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.28
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.29
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.30
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.31
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.32
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.33
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.34
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.35
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.36
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.37
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.38
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.39
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.40
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.41
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.42
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.43
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.44
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.45
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.46
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.47
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.48
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.49
May  1 15:39:00 vdr4 vdr: [2305] dbus2vdr: System: connected with unique name :1.50

Alles anzeigen

Die letzten Zeilen wiederholen sich bis zum herunterfahren des Systems, oder dem killen des vdr Prozesses. Ein geregelter Restart des VDRs ist nicht mehr möglich.

Ich vermute das es erst nach dem Update zu Kernel 4.4 von Xenial erstmals aufgetreten ist, aber genau weis ich es leider nicht ...

Hat jemand eine Idee wie ich den Auslöser für diesen Amoklauf herrausfinden kann?

3PO · 1. Mai 2016

Falscher User in der "/etc/dbus-1/system.d/de.tvdr.vdr.conf" eingetragen?

seahawk1986 · 1. Mai 2016

Was macht denn der dbus-daemon in der Zeit?

mini73 · 1. Mai 2016

Ist schon sehr merkwürdig. Als erstes kontrollieren, was der dbus-daemon evtl. treibt.
Xenial nutzt ja systemd, kdbus sollte aber nicht im Kernel sein. Oder hast du das manuell installiert? Gibt es ja als out-of-tree-Modul.

Ansonsten hatte ich leider noch keine Zeit für xenial, ich hoffe, die kommt bald...

Lars

Frodo · 1. Mai 2016

Zitat von 3PO

/etc/dbus-1/system.d/de.tvdr.vdr.conf

Code

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>


  <!-- Only user vdr can own the vdr-dbus-service -->
  <policy user="vdr">
    <allow own="de.tvdr.vdr"/>
  </policy>


  <!-- allow everyone to call vdr's methods -->
  <policy context="default">
    <allow send_destination="de.tvdr.vdr"/>
    <allow receive_sender="de.tvdr.vdr"/>
  </policy>


</busconfig>

Alles anzeigen

Dort habe ich nie was geändert.

Code

root@vdr4:~# ps -ef | grep dbus-daemon
message+   689     1  9 22:11 ?        00:00:14 dbus-daemon --system --fork
vdr       1639     1  0 22:11 ?        00:00:00 dbus-daemon --config-file=/var/lib/vdr/plugins/dbus2vdr/network.conf --address=tcp:host=vdr4,bind=*,port=0 --print-address

Nach dem downgrade zum wily Kernel das gleiche.

Am Kernel kann es aber nicht liegen, ich hatte vor ein paar Tagen meinen Wohnzimmer VDR neu aufgesetzt, der läuft nur mit Kernel 3.19 oder neuer da das Mainboard ein Intel Z170i Chipsatz mit 219i Netzwerk Chip hat mußte ich hier erst die Trusty Server Installation durchführen damit der neuere Kernel (4.2) installiert wurde. Dort gibt es aber keine Probleme mit dbus2vdr. Die yaVDR Installtions CD 0.6.1 ist hier leider durch den Kernel 3.13 bei neuerer Hardware nicht zu gebrauchen.

Unabhängig davon sollte der Kernel eigentlich egal sein, ich werde wohl den VDR neu installieren, das ist sowieso mal wieder fällig

dbus2vdr läuft Amok

Jetzt mitmachen!

Teilen

Benutzer online in diesem Thema