Database connection issues with Mythbuntu 9.04 x64

Bug #358173 reported by Dave Johansen
2
Affects Status Importance Assigned to Milestone
Mythbuntu
Fix Released
Critical
Unassigned

Bug Description

Sometimes when I start up my machine (combined frontend/backend) it says that it could not connect to the backend and nothing shows up in Upcoming Recordings unless a recording is in progress or I add a new recording ( already reported and probably related bug https://bugs.launchpad.net/mythbuntu/+bug/356789 ).

Revision history for this message
Dave Johansen (davejohansen) wrote :
Revision history for this message
Nick Fox (nickj-fox) wrote : Re: [Bug 358173] Re: Database connection issues with Mythbuntu 9.04 x64

Do you have a HDHomeRun device configured?

-Nick

On Wed, Apr 8, 2009 at 10:20 PM, daveisfera <email address hidden> wrote:

>
> ** Attachment added: "backend log from a boot where it does not give me the
> error message about not being able to connect to the backend"
> http://launchpadlibrarian.net/25092048/mythbackend.log
>
> --
> Database connection issues with Mythbuntu 9.04 x64
> https://bugs.launchpad.net/bugs/358173
> You received this bug notification because you are a member of Mythbuntu
> Developers, which is subscribed to Mythbuntu.
>

Revision history for this message
Dave Johansen (davejohansen) wrote :

> Do you have a HDHomeRun device configured?
>
> -Nick

No, I am using a DViCO FusionHDTV7 Dual Express to capture ATSC OTA channels.

Revision history for this message
Dave Johansen (davejohansen) wrote :

I was able to get it to give me the error about it not being able to connect to the backend, and I have attached the backend log.

Revision history for this message
MarcRandolph (mrand) wrote :

Marking as confirmed... another report and possible solution was proposed here:
http://www.gossamer-threads.com/lists/mythtv/users/376165
which points to Bug 326768 (https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.0/+bug/326768)

Mario and others, I don't know how wide spread this might be, but I could see this possibly being a big deal, so marking it critical for now. Please change if you don't agree.

Changed in mythbuntu:
importance: Undecided → High
status: New → Confirmed
MarcRandolph (mrand)
Changed in mythbuntu:
importance: High → Critical
Revision history for this message
Nick Fox (nickj-fox) wrote :

Have you tried repairing the tables in the mythconverg db? This could cause the select to fail and make it think its not connected. Acording to your log it gets to that point.

Revision history for this message
Dave Johansen (davejohansen) wrote :

Ya, in the related bug report ( https://bugs.launchpad.net/mythbuntu/+bug/356789 ) that I opened before I noticed that it was a more widespread problem (this bug report), I repaired the tables and also ran mysqlcheck (it said everything was ok) and it did not fix the problem.

Revision history for this message
MarcRandolph (mrand) wrote :

@daveisfera, can you try the work-around proposed by the link I posted previously on this bug?

Revision history for this message
Dave Johansen (davejohansen) wrote :

Sorry, but I actually did a clean install of the daily build from today (4-12-09) and it appears to have resolved the problem, so I can't reproduce the issue. I'll keep an eye out for it and see if it pops back up again.

Changed in mythbuntu:
status: Confirmed → Fix Released
Revision history for this message
Dave Johansen (davejohansen) wrote :

After 2-3 restarts, this problem popped up again, but the proposed fix ( https://lists.ubuntu.com/archives/ubuntu-server-bugs/2009-February/009799.html which says to remove the "& wait" from the $NOHUP_NICENESS command in the /usr/bin/mysqld_safe script) seems to have fixed the database errors and the other related issue ( https://bugs.launchpad.net/mythbuntu/+bug/356789 ).

Revision history for this message
Nick Fox (nickj-fox) wrote :
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.