Mailing List Archive: MythTV: Users

hostname problem in MythArchive

Index | Next | Previous | View Threaded

J.Pilk at tesco

Aug 27, 2012, 3:53 PM

Post #1 of 16 (983 views)
Permalink

hostname problem in MythArchive

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?

TIA

John P
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

J.Pilk at tesco

Aug 28, 2012, 9:19 AM

Post #2 of 16 (965 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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 suspect this is also the cause of the lack of a progress log in
'Create an Archive' mode, Ticket #10505, but I don't think that's done
through mythburn.py and my hack doesn't change it. A usable Archive is
created.

A warning: while I was investigating this, a chmod called within
mythburn.py walked recursively all over my home directory. I've
commented that line out. There are some multi-delete sections too...

John P

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

seven at seven

Aug 28, 2012, 3:58 PM

Post #3 of 16 (958 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 29 August 2012 02:19, John Pilkington <J.Pilk [at] tesco> 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 suspect this is also the cause of the lack of a progress log in 'Create
> an Archive' mode, Ticket #10505, but I don't think that's done through
> mythburn.py and my hack doesn't change it. A usable Archive is created.
>
> A warning: while I was investigating this, a chmod called within
> mythburn.py walked recursively all over my home directory. I've commented
> that line out. There are some multi-delete sections too...
>
>
> John P
>
>
Semi OT: is mytharchive 0.25-fixes Storage Group friendly?

Tried using this for the first time since atleast 0.23 and it failed saying
it couldn't locate the file from either Videos or files.

Can anyone confirm?

Cheers,

Anthony

J.Pilk at tesco

Aug 29, 2012, 2:48 AM

Post #4 of 16 (950 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 28/08/12 23:58, Anthony Giggins wrote:
>
>
> On 29 August 2012 02:19, John Pilkington <J.Pilk [at] tesco
> <mailto:J.Pilk [at] tesco>> 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 suspect this is also the cause of the lack of a progress log in
> 'Create an Archive' mode, Ticket #10505, but I don't think that's
> done through mythburn.py and my hack doesn't change it. A usable
> Archive is created.
>
> A warning: while I was investigating this, a chmod called within
> mythburn.py walked recursively all over my home directory. I've
> commented that line out. There are some multi-delete sections too...
>
>
> John P
>
>
> Semi OT: is mytharchive 0.25-fixes Storage Group friendly?
>
> Tried using this for the first time since atleast 0.23 and it failed
> saying it couldn't locate the file from either Videos or files.
>
> Can anyone confirm?
>
> Cheers,
>
> Anthony
>

I've not used it before for anything other than recordings, now all from
dvb-t, and it seems ok with Storage Groups there. The problem above
will affect you if you have the 'Custom identifier' defined and you
haven't made the suggested edits in mythburn.py. What will happen then
depends on whatever ancient configuration it picks up.

Now 'Files' shows me my full (single box) file system and seems to work
on a short recording selected in that way; although when I selected a
file from the mythlink output folder its reported size was several TB,
mistaking Bytes for MBytes.

'Videos' doesn't show any directory structure, though. Most of my
videos are in iso format anyway. Maybe the magic should work there, but
I haven't tried. Their names are shown.

John

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

seven at seven

Aug 29, 2012, 4:57 AM

Post #5 of 16 (959 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 29 August 2012 19:48, John Pilkington <J.Pilk [at] tesco> wrote:

> On 28/08/12 23:58, Anthony Giggins wrote:
>
>>
>>
>> On 29 August 2012 02:19, John Pilkington <J.Pilk [at] tesco
>> <mailto:J.Pilk [at] tesco>> 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 suspect this is also the cause of the lack of a progress log in
>> 'Create an Archive' mode, Ticket #10505, but I don't think that's
>> done through mythburn.py and my hack doesn't change it. A usable
>> Archive is created.
>>
>> A warning: while I was investigating this, a chmod called within
>> mythburn.py walked recursively all over my home directory. I've
>> commented that line out. There are some multi-delete sections too...
>>
>>
>> John P
>>
>>
>> Semi OT: is mytharchive 0.25-fixes Storage Group friendly?
>>
>> Tried using this for the first time since atleast 0.23 and it failed
>> saying it couldn't locate the file from either Videos or files.
>>
>> Can anyone confirm?
>>
>> Cheers,
>>
>> Anthony
>>
>>
> I've not used it before for anything other than recordings, now all from
> dvb-t, and it seems ok with Storage Groups there. The problem above will
> affect you if you have the 'Custom identifier' defined and you haven't made
> the suggested edits in mythburn.py. What will happen then depends on
> whatever ancient configuration it picks up.
>
> Now 'Files' shows me my full (single box) file system and seems to work on
> a short recording selected in that way; although when I selected a file
> from the mythlink output folder its reported size was several TB, mistaking
> Bytes for MBytes.
>
> 'Videos' doesn't show any directory structure, though. Most of my videos
> are in iso format anyway. Maybe the magic should work there, but I haven't
> tried. Their names are shown.
>
> John
>
>
>
From the mythfrontend logs

2012-08-27 23:13:29.890521 E [4051/4051] CoreContext mythburn.cpp:448
(updateArchiveList) - MythBurn: failed to get file details for:
HomeMovies/2012Homemovie1.mkv

and lots of the same for other videos as browsing down the list on

MythTV Version : 0.25-3.md12 (1a671d0)
MythTV Branch : fixes/0.25
Network Protocol : 72
Library API : 0.25.20120408-1
QT Version : 4.7.2
Options compiled in:
linux release use_hidesyms using_alsa using_jack using_oss using_pulse
using_pulseoutput using_backend using_bindings_perl using_bindings_python
using_bindings_php using_dvb using_firewire using_frontend using_hdhomerun
using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu
using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_libudf
using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript
using_qtdbus using_v4l2 using_v4l1 using_x11 using_xrandr using_xv
using_bindings_perl using_bindings_python using_bindings_php
using_mythtranscode using_opengl using_vaapi using_vdpau
using_ffmpeg_threads using_live using_mheg using_libxml2 using_libudf

Cheers,

Anthony

seven at seven

Aug 29, 2012, 4:59 AM

Post #6 of 16 (950 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 29 August 2012 21:57, Anthony Giggins <seven [at] seven> wrote:

>
>
> On 29 August 2012 19:48, John Pilkington <J.Pilk [at] tesco> wrote:
>
>> On 28/08/12 23:58, Anthony Giggins wrote:
>>
>>>
>>>
>>> On 29 August 2012 02:19, John Pilkington <J.Pilk [at] tesco
>>> <mailto:J.Pilk [at] tesco>> 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 suspect this is also the cause of the lack of a progress log in
>>> 'Create an Archive' mode, Ticket #10505, but I don't think that's
>>> done through mythburn.py and my hack doesn't change it. A usable
>>> Archive is created.
>>>
>>> A warning: while I was investigating this, a chmod called within
>>> mythburn.py walked recursively all over my home directory. I've
>>> commented that line out. There are some multi-delete sections too...
>>>
>>>
>>> John P
>>>
>>>
>>> Semi OT: is mytharchive 0.25-fixes Storage Group friendly?
>>>
>>> Tried using this for the first time since atleast 0.23 and it failed
>>> saying it couldn't locate the file from either Videos or files.
>>>
>>> Can anyone confirm?
>>>
>>> Cheers,
>>>
>>> Anthony
>>>
>>>
>> I've not used it before for anything other than recordings, now all from
>> dvb-t, and it seems ok with Storage Groups there. The problem above will
>> affect you if you have the 'Custom identifier' defined and you haven't made
>> the suggested edits in mythburn.py. What will happen then depends on
>> whatever ancient configuration it picks up.
>>
>> Now 'Files' shows me my full (single box) file system and seems to work
>> on a short recording selected in that way; although when I selected a file
>> from the mythlink output folder its reported size was several TB, mistaking
>> Bytes for MBytes.
>>
>> 'Videos' doesn't show any directory structure, though. Most of my videos
>> are in iso format anyway. Maybe the magic should work there, but I haven't
>> tried. Their names are shown.
>>
>> John
>>
>>
>>
>
Yes I see the same size reporting issues but not using the 'Custom
Indentifer' so that shouldn't be a problem.

Cheers,

Anthony

J.Pilk at tesco

Aug 31, 2012, 3:17 AM

Post #7 of 16 (932 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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 suspect this is also the cause of the lack of a progress log in
> 'Create an Archive' mode, Ticket #10505, but I don't think that's done
> through mythburn.py and my hack doesn't change it. A usable Archive is
> created.
>
> A warning: while I was investigating this, a chmod called within
> mythburn.py walked recursively all over my home directory. I've
> commented that line out. There are some multi-delete sections too...
>
> John P

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.

John P

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Aug 31, 2012, 6:21 AM

Post #8 of 16 (928 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mikep at randomtraveller

Aug 31, 2012, 7:04 AM

Post #9 of 16 (922 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

J.Pilk at tesco

Aug 31, 2012, 7:13 AM

Post #10 of 16 (920 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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
>
>
> Mike

When? Never mind, what I have now seems to work. Thanks - to both you
and Raymond.

Chapter navigation seems prone to causing segfaults now, too, and I
hadn't noticed that before; but I haven't often used it, and I've been
using other tweaks as well. I doubt that they are the cause, but
nevertheless I suppose I may be 'getting to keep the pieces.'

Cheers,

John

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Aug 31, 2012, 7:27 AM

Post #11 of 16 (922 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

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
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mikep at randomtraveller

Aug 31, 2012, 9:56 AM

Post #12 of 16 (922 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 31/08/12 15:27, Michael T. Dean wrote:
> 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.
>
Ah. I would have expected to see a commented-out example, as you often find in
other config files.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Aug 31, 2012, 10:51 AM

Post #13 of 16 (918 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 08/31/2012 12:56 PM, Mike Perkins wrote:
> On 31/08/12 15:27, Michael T. Dean wrote:
>> 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.
>>
> Ah. I would have expected to see a commented-out example, as you often
> find in other config files.
>

We couldn't use a commented-out example because the Perl bindings don't
use a real XML parser to read it, and so they used the commented-out
example (thus the comment in the most-recent commit message shown on
that page :).

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

J.Pilk at tesco

Aug 31, 2012, 12:23 PM

Post #14 of 16 (926 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 31/08/12 18:51, Michael T. Dean wrote:
> On 08/31/2012 12:56 PM, Mike Perkins wrote:
>> On 31/08/12 15:27, Michael T. Dean wrote:
>>> 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.
>>>
>> Ah. I would have expected to see a commented-out example, as you often
>> find in other config files.
>>
>
>
> We couldn't use a commented-out example because the Perl bindings don't
> use a real XML parser to read it, and so they used the commented-out
> example (thus the comment in the most-recent commit message shown on
> that page :).
>
> Mike

So does this mean that I ought to try

<DBLocalHostName>what_your_frontend_is_called</DBLocalHostName>

in the frontend section where I suggested making the change above? Or
would that, at present, be even more than usual not covered by the
non-guarantee? Really this means 'do the python bindings, at present,
support both DBHostName and DBLocalHostName and make the appropriate
connections without changes to the python script?'.

As I have it now it seems that the 'Success' message isn't getting into
the DB - or maybe it just isn't accessible by other components - and the
'Play Created DVD' doesn't play; an .iso file is created and I can play
it as a video, and burn it as I usually do with k3b, but it might not
burn within MythArchive.

TIA,

John

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Sep 1, 2012, 5:57 AM

Post #15 of 16 (914 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 08/31/2012 03:23 PM, John Pilkington wrote:
> So does this mean that I ought to try
>
> <DBLocalHostName>what_your_frontend_is_called</DBLocalHostName>
>
> in the frontend section where I suggested making the change above? Or
> would that, at present, be even more than usual not covered by the
> non-guarantee? Really this means 'do the python bindings, at present,
> support both DBHostName and DBLocalHostName and make the appropriate
> connections without changes to the python script?'.

You want

<LocalHostName>profile_identifier</LocalHostName>

and need to place it where indicated at

https://github.com/MythTV/mythtv/blob/fixes/0.25/mythtv/contrib/config_files/config.xml

The name, "LocalHostName", is actually a bit of a misnomer--it's meant
to identify the profile you want to use for the application. Since the
default profile name is the host name, the mysql.txt/config.xml name for
the setting became LocalHostName (as in LocalHostName /override/).
We'll be changing it to a better name when we get a chance (something
like ProfileID).

And, FWIW, specifying a profile ID using LocalHostName is well supported
by all MythTV applications and should be well supported by both the Perl
and Python bindings.

> As I have it now it seems that the 'Success' message isn't getting
> into the DB - or maybe it just isn't accessible by other components -
> and the 'Play Created DVD' doesn't play; an .iso file is created and I
> can play it as a video, and burn it as I usually do with k3b, but it
> might not burn within MythArchive.

I don't know MythArchive, so all I can suggest is to test using a proper
LocalHostName override (in your mysql.txt and/or config.xml
file(s)--make sure it uses whichever one(s) you change. Based on other
comments in the thread, it sounds like that should fix any issues.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

J.Pilk at tesco

Sep 1, 2012, 7:57 AM

Post #16 of 16 (909 views)
Permalink

Re: hostname problem in MythArchive [In reply to]

On 01/09/12 13:57, Michael T. Dean wrote:
> On 08/31/2012 03:23 PM, John Pilkington wrote:
>> So does this mean that I ought to try
>>
>> <DBLocalHostName>what_your_frontend_is_called</DBLocalHostName>
>>
>> in the frontend section where I suggested making the change above? Or
>> would that, at present, be even more than usual not covered by the
>> non-guarantee? Really this means 'do the python bindings, at present,
>> support both DBHostName and DBLocalHostName and make the appropriate
>> connections without changes to the python script?'.
>
> You want
>
> <LocalHostName>profile_identifier</LocalHostName>
>
> and need to place it where indicated at
>
> https://github.com/MythTV/mythtv/blob/fixes/0.25/mythtv/contrib/config_files/config.xml
>
>
> The name, "LocalHostName", is actually a bit of a misnomer--it's meant
> to identify the profile you want to use for the application. Since the
> default profile name is the host name, the mysql.txt/config.xml name for
> the setting became LocalHostName (as in LocalHostName /override/). We'll
> be changing it to a better name when we get a chance (something like
> ProfileID).
>
> And, FWIW, specifying a profile ID using LocalHostName is well supported
> by all MythTV applications and should be well supported by both the Perl
> and Python bindings.
>
>> As I have it now it seems that the 'Success' message isn't getting
>> into the DB - or maybe it just isn't accessible by other components -
>> and the 'Play Created DVD' doesn't play; an .iso file is created and I
>> can play it as a video, and burn it as I usually do with k3b, but it
>> might not burn within MythArchive.
>
> I don't know MythArchive, so all I can suggest is to test using a proper
> LocalHostName override (in your mysql.txt and/or config.xml
> file(s)--make sure it uses whichever one(s) you change. Based on other
> comments in the thread, it sounds like that should fix any issues.
>
> Mike

Thanks very much for the clarification, Mike. With that addition to
config.xml, and another run through most of the frontend setup, the
working directories are where they should be. I've created a small DVD
.iso file, which plays as a Video and in vlc, and 'Play created DVD'
within the Archive utilities works too. I haven't seen any breakages in
a quick set of tests elsewhere.

I renamed mysql.txt but it got recreated. config.xml seems to be doing
its thing with the python bindings, though, and hasn't been overwritten
on restarting myth.

Cheers,

John

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads