[mythtv-users] Mytharchive error on 0.26

[Jos Hoekstra]

Op 28-10-2012 16:41, Mike Perkins schreef:
> On 28/10/12 12:08, Jos Hoekstra wrote:
>> Op 28-10-2012 12:11, Mike Perkins schreef:
>>> On 28/10/12 11:01, Jos Hoekstra wrote:
>>>>
>>>> Hmmmm, you're on to something here, they do differ(excluding my own 
>>>> edits) and I
>>>> read further down that by default these are linked to 
>>>> /etc/mythtv/config.xml.
>>>> However, both differ quite a lot from /etc/mythtv/config.xml and it 
>>>> seems that
>>>> they're supposed to be different, added the LocalHostName to all 
>>>> and will have
>>>> to see how that goes.
>>>> After reboot it doesn't seem to improve the double filename-issue.
>>>> Here's my edited ~/.mythtv/config.xml:
>>>> <Configuration>
>>>>    <UPnP>
>>>>      <UDN>
>>>>        <MediaRenderer>obscured</MediaRenderer>
>>>>      </UDN>
>>>>    </UPnP>
>>>>    <LocalHostName>frontend</LocalHostName>
>>>>    <Database>
>>>>      <PingHost>1</PingHost>
>>>>      <Host>192.168.1.5</Host>
>>>>      <UserName>mythtv</UserName>
>>>>      <Password>passwd</Password>
>>>>      <DatabaseName>mythconverg</DatabaseName>
>>>>      <Port>3306</Port>
>>>>    </Database>
>>>>    <WakeOnLAN>
>>>>      <Enabled>0</Enabled>
>>>> <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
>>>>      <SQLConnectRetry>5</SQLConnectRetry>
>>>>      <Command>echo 'WOLsqlServerCommand not set'</Command>
>>>>    </WakeOnLAN>
>>>> </Configuration>
>>>>
>>>> and /etc/mythtv/config.xml:
>>>> <Configuration>
>>>>    <UPnP>
>>>>      <MythFrontend>
>>>>        <DefaultBackend>
>>>>          <!--
>>>> Set the <LocalHostName> hostname override below only if you want to 
>>>> use
>>>> something other than the machine's real hostname for identifying 
>>>> settings
>>>> in the database.  This is useful if your hostname changes often, as
>>>> otherwise you'll need to reconfigure mythtv every time.
>>>>
>>>> NO TWO HOSTS MAY USE THE SAME VALUE
>>>> -->
>>>>          <LocalHostName>frontend</LocalHostName>
>>>>          <DBHostName>192.168.1.5</DBHostName>
>>>>          <DBUserName>mythtv</DBUserName>
>>>>          <DBPassword>password</DBPassword>
>>>>          <DBName>mythconverg</DBName>
>>>>          <DBPort>3306</DBPort>
>>>>        </DefaultBackend>
>>>>      </MythFrontend>
>>>>    </UPnP>
>>>> </Configuration>
>>>>
>>>> If anyone sees anything wrong here, I'd like to know ;)
>>>>
>>> In the first one, the UPnP section stands alone. In the second, the 
>>> UPnP
>>> section wraps the database section. This might mean it *never* gets 
>>> parsed
>>> properly where it is needed.
>>>
>>> This may be your problem. You also mention above:
>>>
>>> "However, both differ quite a lot from /etc/mythtv/config.xml and it 
>>> seems that
>>> they're supposed to be different"
>>>
>>> No, I don't think they are. These describe the *machine* to the 
>>> backend. The
>>> only time you would ever want these to be different is when you are 
>>> doing some
>>> special testing and need another host identifier or database
>>> username/password. Make all ~/.mythtv be links to /etc/mythtv and 
>>> this will
>>> ensure that your config is consistent wherever you run from.
>>>
>> The second one is default provided by mythbuntu-packages except for 
>> LocalHostName.
>> It doesn't seem to matter for this problem though :/
>>
> Missing the point. In XML any <something> must be matched by a 
> </something> later on otherwise the XML will not parse (ie be 
> ignored/create errors). XML clauses must be properly nested inside 
> each other. Okay there are variations on this but they don't apply to 
> your problem either.
>
> In your first example the <UPnP> ... </UPnP> does /not/ surround the 
> <LocalHostName> clause, in the second it does. This means that the XML 
> reads entirely differently.
>
> If the second example is the supplied default I would suggest that is 
> the correct layout. (You could always check the wiki for the correct 
> layout :P) Edit your version to imitate that.
>
> This is my own config.xml, but I'm running Debian:
>
> micheal at ruby:~/.mythtv$ cat config.xml
> <Configuration>
>   <UPnP>
>     <UDN>
> <MediaRenderer>77c00cd4-69bd-4406-a8db-74d30649554d</MediaRenderer>
>     </UDN>
>     <MythFrontend>
>       <DefaultBackend>
>         <DBHostName>ruby</DBHostName>
>         <DBUserName>mythtv</DBUserName>
>         <DBPassword>xxxxxx</DBPassword>
>         <DBName>mythconverg</DBName>
>         <DBPort>0</DBPort>
>       </DefaultBackend>
>     </MythFrontend>
>   </UPnP>
> </Configuration>
> micheal at ruby:~/.mythtv$
>
> Note the <UPnP> clause wraps everything else.
>
I understand that part, however it is what is supplied by default by 
mythbuntu and I only changed the name of the frontend.
http://code.mythtv.org/trac/browser/mythtv/mythtv/contrib/config_files/config.xml?rev=16b232a56480538fcca2115be31f636bde253e40 
seems to contradict you however?
Whatever is in there, doesn't seem to influence the behaviour in 
mytharchive however.
A default config seems to error on not finding the file via 
myth://192.168.1.5:6543/filename.mpg and with nfs and adding it in the 
database with RecordedFilePrefix with the frontends local mount I get 
the same error not finding /mnt/video/filename.mpg/filename.mpg.

*sigh* ;)

Jos