Frontend IP error on cold start

Bug #567686 reported by Mykal F
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Mykal F

Bug Description

On a cold start of my Mythbuntu front/back end I get an error that indicates that an IP address was set up incorrectly and cannot connect to backend, when I only used the basic default install. After which everything seems to run fine. What is interesting is that if I exit the fronted and then go back to the fronted the error does not happen. The error does not happen if I cold start the computer without the 950Q usb tuner, I even left my PCTV HD usb tuner in and it was OK. Something happening because of the 950Q tuner?

Revision history for this message
Thomas Mashos (tgm4883) wrote :

Marking as incomplete since this has been open awhile with no work being done.

Is this still and issue? Sounds like the 950q is causing networking to start up later

Changed in mythbuntu:
status: New → Incomplete
Revision history for this message
Mykal F (jmykal69) wrote :

After gaining more experience with Myth. I don't believe the IP error is caused by a DVB device. I'm using several types and do get the error from time to time still. What I think is happening is the Frontend is trying to contact the Backend before it's ready during the boot process. As I stated earlier I can either select "ok" or even exit the Frontend then reenter the Frontend and not have any more problems.

Revision history for this message
Thomas Mashos (tgm4883) wrote :

My gut feeling is this is caused by the backend changes we made requiring udev to finish starting before starting the backend. The fix for that would be to have the frontend wait for the backend to finish starting before it tries to start. Similar to what was done with the backend waiting for mysql.

Mario, can you comment on that?

Changed in mythbuntu:
status: Incomplete → New
assignee: nobody → Thomas Mashos (tgm4883)
Revision history for this message
Mario Limonciello (superm1) wrote :

Before we speculate at all, we really need to make sure this is a problem with *current* packages. There have been all sorts of changes to the way upstart gets things up and running these days and this bug was filed quite a while back originally.

Can the op please indicate what package versions this is occurring with?

Changed in mythbuntu:
status: New → Incomplete
assignee: Thomas Mashos (tgm4883) → Mykal F (jmykal69)
Revision history for this message
Mykal F (jmykal69) wrote : Re: [Bug 567686] Re: Frontend IP error on cold start

This is on the LTS 10.04 Mythbuntu.

--- On Thu, 12/2/10, Mario Limonciello <email address hidden> wrote:

From: Mario Limonciello <email address hidden>
Subject: [Bug 567686] Re: Frontend IP error on cold start
To: <email address hidden>
Date: Thursday, December 2, 2010, 6:40 AM

Before we speculate at all, we really need to make sure this is a
problem with *current* packages.  There have been all sorts of changes
to the way upstart gets things up and running these days and this bug
was filed quite a while back originally.

Can the op please indicate what package versions this is occurring with?

** Changed in: mythbuntu
       Status: New => Incomplete

** Changed in: mythbuntu
     Assignee: Thomas Mashos (tgm4883) => Mykal F (jmykal69)

--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/567686

Title:
  Frontend IP error on cold start

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Incomplete

Bug description:
  On a cold start of my Mythbuntu front/back end I get an error that indicates that an IP address was set up incorrectly and cannot connect to backend, when I only used the basic default install. After which everything seems to run fine. What is interesting is that if I exit the fronted and then go back to the fronted the error does not happen. The error does not happen if I cold start the computer without the 950Q usb tuner, I even left my PCTV HD usb tuner in and it was OK. Something happening because of the 950Q tuner?

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mythbuntu/+bug/567686/+subscribe

Revision history for this message
Thomas Mashos (tgm4883) wrote :

On Thu, Dec 2, 2010 at 10:57 AM, Mykal F <email address hidden> wrote:

> This is on the LTS 10.04 Mythbuntu.
>
> --- On Thu, 12/2/10, Mario Limonciello <email address hidden> wrote:
>
> From: Mario Limonciello <email address hidden>
> Subject: [Bug 567686] Re: Frontend IP error on cold start
> To: <email address hidden>
> Date: Thursday, December 2, 2010, 6:40 AM
>
> Before we speculate at all, we really need to make sure this is a
> problem with *current* packages. There have been all sorts of changes
> to the way upstart gets things up and running these days and this bug
> was filed quite a while back originally.
>
> Can the op please indicate what package versions this is occurring with?
>
> ** Changed in: mythbuntu
> Status: New => Incomplete
>
> ** Changed in: mythbuntu
> Assignee: Thomas Mashos (tgm4883) => Mykal F (jmykal69)
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/567686
>
> Title:
> Frontend IP error on cold start
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> Incomplete
>
> Bug description:
> On a cold start of my Mythbuntu front/back end I get an error that
> indicates that an IP address was set up incorrectly and cannot connect to
> backend, when I only used the basic default install. After which everything
> seems to run fine. What is interesting is that if I exit the fronted and
> then go back to the fronted the error does not happen. The error does not
> happen if I cold start the computer without the 950Q usb tuner, I even left
> my PCTV HD usb tuner in and it was OK. Something happening because of the
> 950Q tuner?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/mythbuntu/+bug/567686/+subscribe
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/567686
>
> Title:
> Frontend IP error on cold start
>

What version of MythTV are you using though?

dpkg -l mythtv-backend

Revision history for this message
Mykal F (jmykal69) wrote :

MythTV version 23.

Revision history for this message
Thomas Mashos (tgm4883) wrote :

Thanks Mikal. Can you post the output of "dpkg -l myth*" If this is
something we fixed in the packaging (which is what I suspect) it would be in
a specific revision number, not the main mythtv version number.

Thanks,

Thomas

On Sun, Dec 5, 2010 at 9:33 PM, Mykal F <email address hidden> wrote:

> MythTV version 23.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/567686
>
> Title:
> Frontend IP error on cold start
>

Revision history for this message
Mykal F (jmykal69) wrote :

I hope this helps.
||/ Name Version Description
+++-==============-==============-============================================
ii mythtv-backend 0.23.0+fixes24 A personal video recorder application (serve

Revision history for this message
Thomas Mashos (tgm4883) wrote :

Can you widen the window when you do that, the fixes24 should actually have
3 more numbers (ie. fixes24648)

Thomas

On Mon, Dec 6, 2010 at 9:21 PM, Mykal F <email address hidden> wrote:

> I hope this helps.
> ||/ Name Version Description
>
> +++-==============-==============-============================================
> ii mythtv-backend 0.23.0+fixes24 A personal video recorder application
> (serve
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/567686
>
> Title:
> Frontend IP error on cold start
>

Revision history for this message
Mario Limonciello (superm1) wrote :

I'm not sure it's relevant - that's certainly a 0.23 based build. The fix was applied to 0.24 builds..

Is the OP planning on upgrading to 0.24 anytime?

Thomas Mashos (tgm4883)
Changed in mythbuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.