[Solved stopping vdr and with process-template]ERROR: unknown config parameter:... in yaVDR 0.4 with vdr-testing

jbjbjb · April 19, 2012 at 12:45 AM

Hi.

I have those errors (in syslog) when the computer starts:

Code

Apr 18 21:06:55 yaVDR04 vdr: [1226] ERROR: lircd connection broken, trying to reconnect every 3.0 seconds
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: DisableVPS = 0
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: DoubleEpgAction = 0
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: DoubleEpgTimeDelta = 15
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: LiveBufferSize = 15
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: MixEpgAction = 0
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: noEPGList = 
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: noEPGMode = 0
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown config parameter: PrimaryLimit = 0
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: unknown plugin 'osdteletext'
Apr 18 21:08:02 yaVDR04 vdr: [1268] ERROR: empty key macro
Apr 18 21:08:02 yaVDR04 vdr: [1406] [live] ERROR: Unable to load cert/key (/var/lib/vdr/plugins/live/live.pem//var/lib/vdr/plugins/live/live-key.pem): No existe el fichero o el directorio

Display More

I made:

Code

sudo process-template /var/lib/vdr/setup.conf

but the errors keeps on.

What else can I do to solve them?.

Thanks and regards.
jbjbjb

hotzenplotz5 · April 19, 2012 at 7:55 AM

var/lib/vdr -> user vdr owner vdr

so : process-template --owner=vdr --group=vdr /var/lib/vdr/setup.conf

Quote

process-template --help
USAGE
process-template [--owner <uid>] [--group <gid>] [--mode <permisson mask>] [--output <output file>]
[--data <key=value>] [--database <database file>] <filename>

process-template [-h|--help]

DESCRIPTION
process-template generates files from template snippets found under the directory
/usr/share/yavdr/templates with optional templates under /etc/yavdr/templates_custom
using the template language clearsilver and a hdf database at location /var/lib/yavdrdb.hdf.

OPTIONS
--owner <uid> Generated file gets the owner <uid>
--group <gid> Generated file gets the group <gid>
--mode <permission mask> Generated file gets the permission <permisson mask>
--output <output file> Generated file uses the corresponding templates for <filename>
but is written to <output file>. Useful for files in different
home directories generated by the same template.
--data <key=value> Additional database key value pairs for usage in the templates.
--database <database file> Normally the database /var/lib/yavdrdb.hdf is used. This can be
overwritten by this option.

Display More

jbjbjb · April 19, 2012 at 11:48 PM

Quote from hotzenplotz5

process-template --owner=vdr --group=vdr /var/lib/vdr/setup.conf

Quote from hotzenplotz5

var/lib/vdr -> user vdr owner vdr

so : process-template --owner=vdr --group=vdr /var/lib/vdr/setup.conf

Hi.

Done:

Code

sudo process-template --owner=vdr --group=vdr /var/lib/vdr/setup.conf

but same result than before. Errors appear again in syslog after reboot.

Regards.
jbjbjb

mini73 · April 20, 2012 at 9:56 AM

Hi,

These are options from old vdr patches. Just stop vdr, delete them from setup.conf and restart the vdr.

Lars.

jbjbjb · April 20, 2012 at 10:31 AM

Ok, I will delete the parameters or I will mark as comment line (#). I guess that there is a nonsense to keep them if they are not used.

Anyway, the last time I run:
#> sudo process-template /var/lib/vdr/setup.conf

I lost all the vdr configuration I had made manually, and I had to reconfigure vdr. But this time, this behaviour does not have happened, and remains the configuration I had. Is that normal/correct?

Regards.
jbjbjb

mini73 · April 20, 2012 at 12:00 PM

Hi,

process-template restores the given file on base of the templates in /usr/share/yavdr/templates and your custom templates at /etc/yavdr/templates_custom. I don't think, that this is "the right thing (tm)" for the setup.conf, but at the moment, it is like it is.
I think it depends if your vdr is running or not, while you start process-template.
If vdr is running, the file gets changed but vdr will overwrite it at the next stop.
Otherwise the file will be overwritten and your settings are lost.

Hm, we have to think about removing setup.conf from the templates.
I will discuss this with the team.

Lars.

jbjbjb · April 20, 2012 at 9:42 PM

Quote from mini73

Hi,

process-template restores the given file on base of the templates in /usr/share/yavdr/templates and your custom templates at /etc/yavdr/templates_custom. I don't think, that this is "the right thing (tm)" for the setup.conf, but at the moment, it is like it is.
I think it depends if your vdr is running or not, while you start process-template.
If vdr is running, the file gets changed but vdr will overwrite it at the next stop.
Otherwise the file will be overwritten and your settings are lost.

Hm, we have to think about removing setup.conf from the templates.
I will discuss this with the team.

Lars.

Hi Lars.

You are absolutely right, I did "sudo stop vdr", then I launch "sudo process-template /var/lib/vdr/setup.conf", then rebooted, and after reboot the errors for parameters had dissapeared.

Thanks for the clue.

Regards.
Javier

mini73 · April 21, 2012 at 11:16 AM

Hi,

Digging through the events of yavdr, setup.conf will only be created with process-template after an install. (thanks hoplo!)
On an upgrade, the setup.conf won't be overwritten.

It's just not a good idea to recreate the setup.conf with process-template unless you misconfigured your system and want a fresh start.

Anyway, if you have such messages of unknown parameters just delete them by hand if you don't want them. On the other side they don't really hurt...

Lars.

Participate now!