vdr issues

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Can I get some help? I am trying to use the vdr plugin with OMV. I have enabled the plugin as well as the extras. My card is an wintv hvr-1250. I use this card in a different linux machine regularly. I am able to get a scan of my local atsc channels. I have set the permissions on my "record" folder to read-write for both vdr and vdradmin-am.

      With live I get Error header too large

      With steamdev, nothing happens

      With vdradmin, Im occasionnally able to login. Sometimes I get an error message.

      Can't connect to VDR at localhost:6419: IO::Socket::INET: connect: Connection refused
      Please check if VDR is running and if VDR's svdrphosts.conf is configured correctly.

      I have tried enabling and disabling vdr, as well as all of the extras, individually to see if a any combination is successful.

      Here is my syslog if this helps. Thanks for any ideas!

      Display Spoiler
      Apr 23 23:31:38 OMV64 vdr: [858] [live] INFO: validating server ip '0.0.0.0'
      Apr 23 23:31:38 OMV64 vdr: [866] [live] INFO: attempt to listen on ip = '0.0.0.0'
      Apr 23 23:31:38 OMV64 vdr: [866] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No such file or directory
      Apr 23 23:31:38 OMV64 vdr: [858] ERROR (lirc.c,45): /var/run/lirc/lircd: No such file or directory
      Apr 23 23:31:38 OMV64 vdr: [858] ERROR: remote control LIRC not ready!
      Apr 23 23:33:12 OMV64 vdr: [1424] [live] INFO: validating server ip '0.0.0.0'
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 15
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 17
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 18
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 19
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 20
      Apr 23 23:33:12 OMV64 vdr: [1424] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 21
      Apr 23 23:33:12 OMV64 vdr: [1424] streamdev-server: error while loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
      Apr 23 23:33:12 OMV64 vdr: [1432] [live] INFO: attempt to listen on ip = '0.0.0.0'
      Apr 23 23:33:12 OMV64 vdr: [1432] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No such file or directory
      Apr 23 23:33:17 OMV64 vdr: [1424] ERROR: thread 1432 won't end (waited 5 seconds) - canceling it...
      Apr 23 23:34:17 OMV64 vdr: [1851] [live] INFO: validating server ip '0.0.0.0'
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 15
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 17
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 18
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 19
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 20
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 21
      Apr 23 23:34:17 OMV64 vdr: [1851] ERROR: error in /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf, line 22
      Apr 23 23:34:17 OMV64 vdr: [1851] streamdev-server: error while loading /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf
      Apr 23 23:34:17 OMV64 vdr: [1867] [live] INFO: attempt to listen on ip = '0.0.0.0'
      Apr 23 23:34:17 OMV64 vdr: [1867] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No such file or directory
      Apr 23 23:34:22 OMV64 vdr: [1851] ERROR: thread 1867 won't end (waited 5 seconds) - canceling it...
    • I know this is not an answer but just wanted to say I have the exact same issue, Scan of programmes works, but click on the 'Show' buttons, for Live, Streamdev and VDRAdmin AM, and I get a connection refused for Live and Streamdev and for VDRAdminAM I get:

      Can't connect to VDR at localhost:6419: IO::Socket::INET: connect: Connection refused
      Please check if VDR is running and if VDR's svdrphosts.conf is configured correctly.

      I have been searching for days for a solution, and have done some of the recommended changes in svdrphosts.conf when I eventually found it, but to no avail.

      Any help from anyone would be appreciated.
      -----------------------------------------------------------------------------------
      "I may be a confused
      ?( user but I have donated, so shouldn't you too!"

      Silverstone DS380B 4+8 Bay NAS Case - ASRock Z97E-ITX/ac - Intel i5 4590T - SuperMicro AOC-SAS2LP MV8 8Port SATA Card - 60GB SSD (OMV OS), 3 x 500GB 2.5" Internal HDD (Non-RAID Plugin Data Folders & Backups) and 8 x 3TB HotSwap HDD (Data RAID 6) - PowerWalker Inline UPS
    • All of you have the same problem at least. The issue is that the web interface of OMV stores to much data in cookies which interferes with other services. Try clearing the cookies in the browser and the problem should hopefully go away. With OMV 2.0 the use of cookies is switched to local storage instead which solves the problem. So when you upgrade to 2.0 clear the cookies and the problem should hopefully never occur again.

      However, @Atoms can you post the output of your /var/lib/vdr/plugins/streamdev-server/streamdevhosts.conf since it seems to some kind of error in that file.
    • Display Spoiler
      #
      # streamdevhosts This file describes a number of host addresses that
      # are allowed to connect to the streamdev server running
      # with the Video Disk Recorder (VDR) on this system.
      # Syntax:
      #
      # IP-Address[/Netmask]
      #

      127.0.0.1 # always accept localhost
      #192.168.100.0/24 # any host on the local net
      #204.152.189.113 # a specific host
      #239.255.0.0/16 # uncomment for IGMP multicast streaming
      #0.0.0.0/0 # any host on any net (DON'T DO THAT! USE AUTHENTICATION)
      192.168.11.2/65
      192.168.11.2/65
      192.168.11.2/65
    • Atoms wrote:

      Display Spoiler
      #
      # streamdevhosts This file describes a number of host addresses that
      # are allowed to connect to the streamdev server running
      # with the Video Disk Recorder (VDR) on this system.
      # Syntax:
      #
      # IP-Address[/Netmask]
      #

      127.0.0.1 # always accept localhost
      #192.168.100.0/24 # any host on the local net
      #204.152.189.113 # a specific host
      #239.255.0.0/16 # uncomment for IGMP multicast streaming
      #0.0.0.0/0 # any host on any net (DON'T DO THAT! USE AUTHENTICATION)
      192.168.11.2/65
      192.168.11.2/65
      192.168.11.2/65

      Could you try and remove the duplicated lines containing 192.168.11.2/65 and try and start VDR again? The plugin appends to the file currently so it will be multiple lines of the same. I'll have to fix that. :)
    • I am still working on this. I tried a few more things. Cleared all duplicates in the streamdevhosts.conf. Verified privileges to VDR and VDR-admin and video just to cover all options. Then ran tail -f /var/log/messages which I found in some documentation here projects.vdr-developer.org/git…tree/INSTALL?h=stable/2.0

      Display Spoiler

      ~# sudo service vdr restart
      Restarting Linux Video Disk Recorder: vdr
      Searching for plugins (VDR 2.0.3/2.0.0) (cache miss): live conflictcheckonly streamdev-server epgsearch quickepgsearch epgsearchonly xineliboutput.
      root@OMV64:~# tail -f /var/log/messages
      Jun 14 22:14:57 OMV64 kernel: [ 1961.791783] cx23885[0]: hauppauge eeprom: model=79571
      Jun 14 22:14:57 OMV64 kernel: [ 1961.791788] cx23885_dvb_register() allocating 1 frontend(s)
      Jun 14 22:14:57 OMV64 kernel: [ 1961.791794] cx23885[0]: cx23885 based dvb card
      Jun 14 22:14:57 OMV64 kernel: [ 1961.820211] MT2131: successfully identified at address 0x61
      Jun 14 22:14:57 OMV64 kernel: [ 1961.820217] DVB: registering new adapter (cx23885[0])
      Jun 14 22:14:57 OMV64 kernel: [ 1961.820222] DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
      Jun 14 22:14:57 OMV64 kernel: [ 1961.822250] cx23885_dev_checkrevision() Hardware revision = 0xa5
      Jun 14 22:14:57 OMV64 kernel: [ 1961.822261] cx23885[0]/0: found at 0000:03:00.0, rev: 4, irq: 17, latency: 0, mmio: 0xfe600000
      Jun 14 22:15:04 OMV64 vdr: [8536] [xine..put] Listening on address '127.0.0.1' port 37890
      Jun 14 22:15:09 OMV64 vdr: [8536] [xine..put] cXinelibOsdProvider: shutting down !
    • I did manage to get vdr-adminAM working by changing the port number, re-inputting the credentials, saving, then showing. It did take 5 tries to get it to start. No epg info is showing. This makes me think that the ATSC configuration in VDR is not correctly working.

      Streamdev had an update, which was installed, and I suspect it was to remove duplicate entries.

      Live still has the ERROR header too large
    • Seems weird, but if it works :) I have never used ATSC and I'm no expert in EPG issues so I can't be of any help there sadly.

      If you haven't done so already upgrade openmediavault-vdr-extras to 1.3 and you should hopefully not get any duplicated entries anymore.

      The too large header issue is still cookies. The header grows too large quite fast if you use the web interface of OMV a little while.
    • I noticed a few errors in my syslog. Does anyone have a moment to help clear these up

      Jun 18 23:08:29 OMV64 vdr: [7457] ERROR: error in /var/lib/vdr/svdrphosts.conf, line 14
      Display Spoiler

      Source Code

      1. #
      2. # svdrphosts This file describes a number of host addresses that
      3. # are allowed to connect to the SVDRP port of the Video
      4. # Disk Recorder (VDR) running on this system.
      5. # Syntax:
      6. #
      7. # IP-Address[/Netmask]
      8. #
      9. #127.0.0.1 # always accept localhost
      10. #192.168.100.0/24 # any host on the local net
      11. #204.152.189.113 # a specific host
      12. #0.0.0.0/0 # any host on any net (USE THIS WITH CARE!)
      13. 192.168.11.2/65
      Display All



      Jun 18 23:08:29 OMV64 vdr: [7465] [live] INFO: attempt to listen on ip = '0.0.0.0'
      Jun 18 23:08:29 OMV64 vdr: [7465] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No such file or directory

      Jun 18 23:08:29 OMV64 vdr: [7457] ERROR (lirc.c,45): /var/run/lirc/lircd: No such file or directory
      Jun 18 23:08:29 OMV64 vdr: [7457] ERROR: remote control LIRC not ready!

      The post was edited 1 time, last by HK-47 ().

    • concerning the svdrphosts.conf I was able to fix by removing the range. This seems strange to me as it was in this format but commented out. This solved that error

      The other error with the // I am still having trouble with.

      I tried

      Source Code

      1. cd /var/lib/vdr/plugins/live

      and

      Source Code

      1. ls

      shows nothing

      HK-47, thanks a bunch for helping me out!!!
      I really want to get this to work as I do not want to keep my mythTV box running in addition to this one. If VDR goes well, I will be upgrading to a bigger machine.
    • Weird, I don't see the // in your post anymore, maybe it only was visible with Tapatalk. I moved the log you posted to a codebox (which I suggest you use for logs in the future, button looks like: <>) and then saw that the line it complained about was the 192.168.11.2/65. :)

      VDR is a lot nicer than MythTV in my opinion. Tvheadend is nice too (easy to set up), but in my experience a bit to buggy. After understanding how to set up VDR I can't go back :)

      We don't use ATSC in my country so I can't really test anything related to it. I did however try to build the atscepg plugin without luck. As I understand it you need to patch VDR to make the plugin work. Maybe XMLTV and VDR could work instead? I've haven't had the time to test it with VDR yet, but XMLTV worked well with Tvheadend.
    • I tried xmltv2vdr out a bit and something like this could possibly work.
      1. Start by fetching xmltv-util: apt-get install xmltv-util --no-install-recommends
      2. Download and install the xmltv2vdr Perl script to /usr/local/bin: wget ftp://ftp.tvdr.de/vdr/Tools/xmltv2vdr-1.0.9.tar.gz -O - | tar xz --strip 1 -C /usr/local/bin xmltv2vdr-1.0.9/xmltv2vdr.pl.
      3. Login as a normal user instead of root. This user will fetch and push the data.
      4. Execute tv_find_grabbers to list available XMLTV grabbers and configure it. For example, tv_grab_eu_epgdata --configure will go through the initial configuration and let you select the channels to fetch data for. Then we run tv_grab_eu_epgdata > ~/.xmltv/channels.xml
      5. Now we need to create a channels.conf file that maps the channels. To make it easy to find all files we store everything in the ~/.xmltv directory for the time being.

        1. Copy channels conf cp /etc/vdr/channels.conf ~/.xmltv/channels.conf.
        2. From the README (modified paths):

        Source Code

        1. Look through the channel names that you have in ~/.xmltv/channels.xml and map
        2. them to an extra field that is in the local copy of ~/.xmltv/channels.conf (DO NOT
        3. MODIFY THE FILE (/etc/vdr/channels.conf) THAT VDR ACTUALLY USES OR YOU MIGHT BREAK IT!)
        4. For example: -
        5. in channels.xml : <channel id="sky-news.sky.com">
        6. in channels.conf : Sky News (TV):578166:I0C34D0M16B8T2G32Y0:T:27500:101:102,104:0:0:22080:0:0:0:sky-news.sky.com
        7. Note the extra field added at the end - don't forget the colon.
        Display All

      6. Now we only need to push the data to VDR. Execute xmltv2vdr.pl -p 6419 -x ~/.xmltv/channels.xml -c ~/.xmltv/channels.conf and check that it works.
      7. The only thing left to do is to add two scheduled jobs in OMV for the user you set up XMLTV with. The first one is to fetch XMLTV data once in a while:
        tv_grab_eu_epgdata > ~/.xmltv/channels.xml
        The second one is to push the data to VDR (don't forget to make sure this runs a bit after the first one, otherwise old data will be pushed):
        xmltv2vdr.pl -p 6419 -x ~/.xmltv/channels.xml -c ~/.xmltv/channels.conf
        Or if you want, you could add it as a single job:
        tv_grab_eu_epgdata > ~/.xmltv/channels.xml && xmltv2vdr.pl -p 6419 -x ~/.xmltv/channels.xml -c ~/.xmltv/channels.conf

      Don't forget to change tv_grab_eu_epgdata to the grabber you choose.
    • I have similar problems with the VDR plugin. I cannot grant it access to the media shared folder? The is no user nor group named VDR or VDR-Admin. If I create one it still has no access. Can someone help me figure out this archaic permissions system? The only way I can get the plugin to run is to not have a recording folder selected. Makes no sense whatsoever!

      Ok... So I used ACL to set permissions and now it ran. :)

      The post was edited 1 time, last by thebrett: Discovered a workaround... ().