Mailing List Archive: MythTV: Users

ERROR: Master backend tried to connect back to itself!

Index | Next | Previous | View Threaded

michael.tiller at gmail

Nov 28, 2009, 7:48 AM

Post #1 of 8 (1538 views)
Permalink

ERROR: Master backend tried to connect back to itself!

I've got a problem where my backend isn't using my PVR-150 and my HD-PVR for
some reason. Worked after my upgrade to 0.22 but I think a reboot messed
something up. I checked the logs and found that my backend seems to be
restarting (or spawning a subprocess, not really sure what is going one)
every 20 seconds. I get sections in my log like the one below repeated
every 20 seconds or so:

2009-11-28 08:44:37.803 Using runtime prefix = /usr
2009-11-28 08:44:37.805 Using configuration directory = /home/mythtv/.mythtv
2009-11-28 08:44:37.807 Empty LocalHostName.
2009-11-28 08:44:37.809 Using localhost value of mythmc
2009-11-28 08:44:37.816 New DB connection, total: 1
2009-11-28 08:44:37.820 Connected to database 'mythconverg' at host:
localhost
2009-11-28 08:44:37.822 Closing DB connection named 'DBManager0'
2009-11-28 08:44:37.824 Connected to database 'mythconverg' at host:
localhost
2009-11-28 08:44:37.827 Current MythTV Schema Version (DBSchemaVer): 1244
2009-11-28 08:44:37.830 MythBackend: Starting up as the master server.
2009-11-28 08:44:37.835 New DB connection, total: 2
2009-11-28 08:44:37.838 Connected to database 'mythconverg' at host:
localhost
2009-11-28 08:44:37.840 New DB connection, total: 3
2009-11-28 08:44:37.842 Connected to database 'mythconverg' at host:
localhost
*2009-11-28 08:44:38.524 ERROR: Master backend tried to connect back to
itself!
2009-11-28 08:44:38.534 ERROR: Master backend tried to connect back to
itself!
*2009-11-28 08:44:39.540 ret_pid(0) child(9993) status(0x0)
2009-11-28 08:44:40.053 ret_pid(9993) child(9993) status(0x0)
2009-11-28 08:44:40.055 External Tuning program exited with no error
2009-11-28 08:44:40.065 New DB scheduler connection
2009-11-28 08:44:40.067 Connected to database 'mythconverg' at host:
localhost
2009-11-28 08:44:40.069 Scheduler, Warning: Listings source 'Dish Network'
is defined, but is not attached to a card input.
2009-11-28 08:44:40.073 Scheduler, Warning: Listings source 'Digital
Broadcast' is defined, but is not attached to a card input.
2009-11-28 08:44:40.076 Scheduler, Warning: Listings source 'Comcast' is
defined, but is not attached to a card input.
2009-11-28 08:44:40.091 Enabling Upnpmedia rebuild thread.

I have no idea what is going on here and/or what this has to do with my
other issue (of not finding some of my recording devices) but it doesn't
look good. Any ideas?

--
Mike

knowledgejunkie at gmail

Nov 28, 2009, 8:25 AM

Post #2 of 8 (1494 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

2009/11/28 Michael Tiller <michael.tiller [at] gmail>:

> 2009-11-28 08:44:40.069 Scheduler, Warning: Listings source 'Dish Network'
> is defined, but is not attached to a card input.
> 2009-11-28 08:44:40.073 Scheduler, Warning: Listings source 'Digital
> Broadcast' is defined, but is not attached to a card input.
> 2009-11-28 08:44:40.076 Scheduler, Warning: Listings source 'Comcast' is
> defined, but is not attached to a card input.
> 2009-11-28 08:44:40.091 Enabling Upnpmedia rebuild thread.
>
> I have no idea what is going on here and/or what this has to do with my
> other issue (of not finding some of my recording devices) but it doesn't
> look good. Any ideas?

I'm wondering if your hostname has recently changed?

If so:

Make sure in mythtv-setup that your hostname/IP configuration for
mythbackend is correct. You probably need to recreate your capture
cards in mythtv-setup (choose the "Delete All Capture Cards" option on
the capture cards page first to completely remove the old entries) to
ensure that they are configured for your current hostname. Then,
you'll need to re-attach your existing video sources to their
respective inputs on the input connections page.

You do not need to touch your video source/channels configuration, as
these are globally configured and hostname agnostic.

Cheers,
Nick

--
Nick Morrott

MythTV Official wiki: http://mythtv.org/wiki/
MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

michael.tiller at gmail

Nov 28, 2009, 8:26 AM

Post #3 of 8 (1488 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

All,

Well, it stopped now. No idea why (after doing it for two days). I did
restart the backend, perhaps that had something to do with it. Perhaps I
managed (somehow) to have two backends running at once. No idea. Anyway,
it has gone away (although I'm still troubled as to how it happened in the
first place).

Thanks for your suggestion Nick, I'll look into that.

--
Mike

On Sat, Nov 28, 2009 at 10:48 AM, Michael Tiller
<michael.tiller [at] gmail>wrote:

> I've got a problem where my backend isn't using my PVR-150 and my HD-PVR
> for some reason. Worked after my upgrade to 0.22 but I think a reboot
> messed something up. I checked the logs and found that my backend seems to
> be restarting (or spawning a subprocess, not really sure what is going one)
> every 20 seconds. I get sections in my log like the one below repeated
> every 20 seconds or so:
>
> 2009-11-28 08:44:37.803 Using runtime prefix = /usr
> 2009-11-28 08:44:37.805 Using configuration directory =
> /home/mythtv/.mythtv
> 2009-11-28 08:44:37.807 Empty LocalHostName.
> 2009-11-28 08:44:37.809 Using localhost value of mythmc
> 2009-11-28 08:44:37.816 New DB connection, total: 1
> 2009-11-28 08:44:37.820 Connected to database 'mythconverg' at host:
> localhost
> 2009-11-28 08:44:37.822 Closing DB connection named 'DBManager0'
> 2009-11-28 08:44:37.824 Connected to database 'mythconverg' at host:
> localhost
> 2009-11-28 08:44:37.827 Current MythTV Schema Version (DBSchemaVer): 1244
> 2009-11-28 08:44:37.830 MythBackend: Starting up as the master server.
> 2009-11-28 08:44:37.835 New DB connection, total: 2
> 2009-11-28 08:44:37.838 Connected to database 'mythconverg' at host:
> localhost
> 2009-11-28 08:44:37.840 New DB connection, total: 3
> 2009-11-28 08:44:37.842 Connected to database 'mythconverg' at host:
> localhost
> *2009-11-28 08:44:38.524 ERROR: Master backend tried to connect back to
> itself!
> 2009-11-28 08:44:38.534 ERROR: Master backend tried to connect back to
> itself!
> *2009-11-28 08:44:39.540 ret_pid(0) child(9993) status(0x0)
> 2009-11-28 08:44:40.053 ret_pid(9993) child(9993) status(0x0)
> 2009-11-28 08:44:40.055 External Tuning program exited with no error
> 2009-11-28 08:44:40.065 New DB scheduler connection
> 2009-11-28 08:44:40.067 Connected to database 'mythconverg' at host:
> localhost
> 2009-11-28 08:44:40.069 Scheduler, Warning: Listings source 'Dish Network'
> is defined, but is not attached to a card input.
> 2009-11-28 08:44:40.073 Scheduler, Warning: Listings source 'Digital
> Broadcast' is defined, but is not attached to a card input.
> 2009-11-28 08:44:40.076 Scheduler, Warning: Listings source 'Comcast' is
> defined, but is not attached to a card input.
> 2009-11-28 08:44:40.091 Enabling Upnpmedia rebuild thread.
>
> I have no idea what is going on here and/or what this has to do with my
> other issue (of not finding some of my recording devices) but it doesn't
> look good. Any ideas?
>
> --
> Mike
>
>

mtdean at thirdcontact

Nov 28, 2009, 9:35 AM

Post #4 of 8 (1494 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

On 11/28/2009 10:48 AM, Michael Tiller wrote:
> I've got a problem where my backend isn't using my PVR-150 and my HD-PVR for
> some reason. Worked after my upgrade to 0.22 but I think a reboot messed
> something up. I checked the logs and found that my backend seems to be
> restarting (or spawning a subprocess, not really sure what is going one)
> every 20 seconds. I get sections in my log like the one below repeated
> every 20 seconds or so:
>
...
> 2009-11-28 08:44:38.524 ERROR: Master backend tried to connect back to
> itself!
> 2009-11-28 08:44:38.534 ERROR: Master backend tried to connect back to
> itself!
>
...
> I have no idea what is going on here and/or what this has to do with my
> other issue (of not finding some of my recording devices) but it doesn't
> look good. Any ideas?

We really need a good backtrace with debug symbols to /fix/ this issue.
http://www.mythtv.org/wiki/Debugging (again, 9months later, still asking
Ubuntu users to finish up the Ubuntu section with specifics).

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

michael.tiller at gmail

Nov 28, 2009, 12:38 PM

Post #5 of 8 (1485 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

On Sat, Nov 28, 2009 at 12:35 PM, Michael T. Dean
<mtdean [at] thirdcontact>wrote:

> We really need a good backtrace with debug symbols to /fix/ this issue.
> http://www.mythtv.org/wiki/Debugging (again, 9months later, still asking
> Ubuntu users to finish up the Ubuntu section with specifics).
>

Sorry, I assumed this was probably a configuration issue more than a bug.
Is there something that makes you think it is a bug? I'm only asking
because I'm not really very good at being able to distinguish the two.

> Mike
>
>
--
Mike

mtdean at thirdcontact

Nov 28, 2009, 12:58 PM

Post #6 of 8 (1482 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

On 11/28/2009 03:38 PM, Michael Tiller wrote:
> On Sat, Nov 28, 2009 at 12:35 PM, Michael T. Dean wrote:
>
>> We really need a good backtrace with debug symbols to /fix/ this issue.
>> http://www.mythtv.org/wiki/Debugging (again, 9months later, still asking
>> Ubuntu users to finish up the Ubuntu section with specifics).
> Sorry, I assumed this was probably a configuration issue more than a bug.
> Is there something that makes you think it is a bug? I'm only asking
> because I'm not really very good at being able to distinguish the two.

http://www.gossamer-threads.com/lists/mythtv/dev/408168#408168
http://www.gossamer-threads.com/lists/mythtv/commits/297745#297745

Huge thanks to Mario for filling in the Ubuntu debug section at
http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages .
All the info you need is now there.

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

michael.tiller at gmail

Nov 28, 2009, 1:08 PM

Post #7 of 8 (1483 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

On Sat, Nov 28, 2009 at 3:58 PM, Michael T. Dean <mtdean [at] thirdcontact>wrote:

> On 11/28/2009 03:38 PM, Michael Tiller wrote:
>
> On Sat, Nov 28, 2009 at 12:35 PM, Michael T. Dean wrote:
>>
>>
>>> We really need a good backtrace with debug symbols to /fix/ this issue.
>>> http://www.mythtv.org/wiki/Debugging (again, 9months later, still asking
>>> Ubuntu users to finish up the Ubuntu section with specifics).
>>>
>> Sorry, I assumed this was probably a configuration issue more than a bug.
>> Is there something that makes you think it is a bug? I'm only asking
>> because I'm not really very good at being able to distinguish the two.
>>
>
> http://www.gossamer-threads.com/lists/mythtv/dev/408168#408168
> http://www.gossamer-threads.com/lists/mythtv/commits/297745#297745
>

Ah, I see. It wasn't clear to me that this was a known issue. I thought
your response was more of a "well if you want help, give us a backtrace". I
didn't realize there was some existing context for knowing this was in the C
code. At least I didn't realize it. That is why I was puzzled since the
debugging page specifically talks about crashes and this wasn't a crash.

> Huge thanks to Mario for filling in the Ubuntu debug section at
> http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages . All
> the info you need is now there.

I'm a bit confused. According to the link you gave me, ticket #3720 was
closed two years ago. If I dig up debugging information, is there an open
ticket I should report it to? I couldn't find a way to search the existing
tickets (which seems a bit odd in an of itself).

--
Mike

mtdean at thirdcontact

Nov 28, 2009, 1:22 PM

Post #8 of 8 (1478 views)
Permalink

Re: ERROR: Master backend tried to connect back to itself! [In reply to]

On 11/28/2009 04:08 PM, Michael Tiller wrote:
> On Sat, Nov 28, 2009 at 3:58 PM, Michael T. Dean wrote:
>
>> On 11/28/2009 03:38 PM, Michael Tiller wrote:
>>
>> On Sat, Nov 28, 2009 at 12:35 PM, Michael T. Dean wrote:
>>
>>>> We really need a good backtrace with debug symbols to /fix/ this issue.
>>>> http://www.mythtv.org/wiki/Debugging (again, 9months later, still asking
>>>> Ubuntu users to finish up the Ubuntu section with specifics).
>>> Sorry, I assumed this was probably a configuration issue more than a bug.
>>> Is there something that makes you think it is a bug? I'm only asking
>>> because I'm not really very good at being able to distinguish the two.
>> http://www.gossamer-threads.com/lists/mythtv/dev/408168#408168
>> http://www.gossamer-threads.com/lists/mythtv/commits/297745#297745
> Ah, I see. It wasn't clear to me that this was a known issue. I thought
> your response was more of a "well if you want help, give us a backtrace". I
> didn't realize there was some existing context for knowing this was in the C
> code. At least I didn't realize it. That is why I was puzzled since the
> debugging page specifically talks about crashes and this wasn't a crash.
>
>> Huge thanks to Mario for filling in the Ubuntu debug section at
>> http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages . All
>> the info you need is now there.
> I'm a bit confused. According to the link you gave me, ticket #3720 was
> closed two years ago. If I dig up debugging information, is there an open
> ticket I should report it to? I couldn't find a way to search the existing
> tickets (which seems a bit odd in an of itself).

#3270 fixed all known locations where we have code that could result in
an event loop. We need to identify new locations so they can be fixed.

If you're able to identify such a location (by doing as Daniel suggested
and adding an abort--or even with a gdb breakpoint--to stop execution
when the error is printed) and capture a backtrace, just upload it to a
new ticket that mentions an event loop and whose description contains
the entire error message about the master backend connecting to itself.

Thanks,
Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads