[mythtv-users] hostname problem in MythArchive

[Michael T. Dean]

On 08/31/2012 10:04 AM, Mike Perkins wrote:
> On 31/08/12 14:21, Michael T. Dean wrote:
>> On 08/31/2012 06:17 AM, John Pilkington wrote:
>>> On 28/08/12 17:19, John Pilkington wrote:
>>>> On 27/08/12 23:53, John Pilkington wrote:
>>>>> Since installing 0.25-fixes on my main box I've had problems with
>>>>> MythArchive.  I think this may be because the config settings are
>>>>> defined by the frontend but are being read using the hostname of the
>>>>> backend.  The lines in the mythburn.py script read
>>>>>
>>>>> DB = MythTV.MythDB()
>>>>> configHostname = DB.gethostname()
>>>>>
>>>>> I've tried a direct hack in mythburn.py that looked hopeful.  What 
>>>>> would
>>>>> be the way of getting the frontend's 'Custom Identifier' from the DB
>>>>> instead?
>>>>>
>>>>
>>>> OK, it works for me (in creation of a playable DVD) if the 'Custom
>>>> identifier' from Frontend Setup > General > page 2 is used as
>>>> configHostname.
>>>>
>>>> If defined it's LocalHostName in ~/.mythtv/mysql.txt.  Isn't that the
>>>> file that's being phased out?  config.xml doesn't have it and I 
>>>> haven't
>>>> found it in the DB.
>>>
>>> I opened Ticket #11059 on this but it's been closed as fixed in 0.26
>>>
>>> My guess is that before then the easiest fix is to edit
>>>  ~/.mythtv/config.xml like this:
>>>
>>> <MythFrontend>
>>> <DefaultBackend>
>>> <DBHostName>localhost</DBHostName>
>>> <DBUserName>mythtv</DBUserName>
>>> <DBPassword>mythtv</DBPassword>
>>> <DBName>mythconverg</DBName>
>>> <DBPort>3306</DBPort>
>>> </DefaultBackend>
>>> <DBHostName>what_your_frontend_is_called</DBHostName> ## This line
>>> </MythFrontend>
>>>
>>> ... but I suppose this could screw something else up.  I haven't 
>>> tried it, but
>>> it would be easier than editing mythburn.py, which is quite large 
>>> and belongs
>>> to root.
>>
>> There is no DBHostName.
>>
>> https://github.com/MythTV/mythtv/blob/fixes/0.25/mythtv/contrib/config_files/config.xml 
>>
>>
> In the example in the link, it clearly uses 'DBHostName' - despite the 
> comment.
>

It's not an example.  It's a comment saying to /add/ LocalHostName.

DBHostName is to say where the DB is located, not to change what they 
said needs changing.

Mike