Mailing List Archive: MythTV: Users

Database upgrade problems with weather

Index | Next | Previous | View Threaded

jsweepstakes at gmail

May 2, 2008, 8:14 AM

Post #1 of 11 (1192 views)
Permalink

Database upgrade problems with weather

When I updated my mythtv the database didn't like it and the weather part
broke, I tired running repairs but how can I fix it?
thank you!
-J

mtdean at thirdcontact

May 2, 2008, 8:33 AM

Post #2 of 11 (1157 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

On 05/02/2008 11:14 AM, J wrote:
> When I updated my mythtv the database didn't like it and the weather
> part broke, I tired running repairs but how can I fix it?
> thank you!

MythWeather /requires/ that you enable InnoDB tables in MySQL. If
anyone tells you, "Just do this ... to change it to use MyISAM," don't
follow their advice as it is broken advice that will break your Myth box.

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

jsweepstakes at gmail

May 2, 2008, 11:40 AM

Post #3 of 11 (1147 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

What is InnoDB? and how do I enable it?
-J

Message: 29
Date: Fri, 02 May 2008 11:33:07 -0400
From: "Michael T. Dean" <mtdean[at]thirdcontact.com>
Subject: Re: [mythtv-users] Database upgrade problems with weather
To: Discussion about mythtv <mythtv-users[at]mythtv.org>
Message-ID: <481B3433.1030900[at]thirdcontact.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 05/02/2008 11:14 AM, J wrote:
> When I updated my mythtv the database didn't like it and the weather
> part broke, I tired running repairs but how can I fix it?
> thank you!

MythWeather /requires/ that you enable InnoDB tables in MySQL. If
anyone tells you, "Just do this ... to change it to use MyISAM," don't
follow their advice as it is broken advice that will break your Myth box.

Mike

mtdean at thirdcontact

May 2, 2008, 12:19 PM

Post #4 of 11 (1133 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

(fixed top-posting/quoting)

On 05/02/2008 02:40 PM, J wrote:

> From: "Michael T. Dean"
>
> > On 05/02/2008 11:14 AM, J wrote:
> >
> >> When I updated my mythtv the database didn't like it and the
> >> weather part broke, I tired running repairs but how can I fix it?
> >> thank you!
> >
> > MythWeather /requires/ that you enable InnoDB tables in MySQL. If
> > anyone tells you, "Just do this ... to change it to use MyISAM,"
> > don't follow their advice as it is broken advice that will break
> > your Myth box.
>
> What is InnoDB?

It's a MySQL storage format.

> and how do I enable it?

Don't start the server with --skip-innodb and don't put the skip-innodb
option in the MySQL option file (/etc/my.cnf) (and don't do any of the
other things some crazy distro might do to disable InnoDB storage on
your MySQL server).

In other words, you're probably going to have to tell us what distro
you're using so someone using that same distro can tell you how to undo
what the distro did.

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

jsweepstakes at gmail

May 2, 2008, 6:46 PM

Post #5 of 11 (1127 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

I'm using ubuntu 7.10 about to upgrade to 8.04

in my.conf:
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa
100MB.
#skip-innodb

On 05/02/2008 02:40 PM, J wrote:

> From: "Michael T. Dean"
>

> > On 05/02/2008 11:14 AM, J wrote:
> >

> >> When I updated my mythtv the database didn't like it and the
> >> weather part broke, I tired running repairs but how can I fix it?
> >> thank you!

> >
> > MythWeather */requires/* that you enable InnoDB tables in MySQL. If
> > anyone tells you, "Just do this ... to change it to use MyISAM,"
> > don't follow their advice as it is broken advice that will break
> > your Myth box.

>
> What is InnoDB?

It's a MySQL storage format.

> and how do I enable it?

Don't start the server with --skip-innodb and don't put the skip-innodb
option in the MySQL option file (/etc/my.cnf) (and don't do any of the
other things some crazy distro might do to disable InnoDB storage on
your MySQL server).

In other words, you're probably going to have to tell us what distro
you're using so someone using that same distro can tell you how to undo
what the distro did.

Mike

mtdean at thirdcontact

May 2, 2008, 7:59 PM

Post #6 of 11 (1132 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

jsweepstakes at gmail

May 4, 2008, 9:20 AM

Post #7 of 11 (1089 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

On 05/02/2008 09:46 PM, J wrote:
> I'm using ubuntu 7.10 about to upgrade to 8.04
>
> in my.conf:
> # * InnoDB
> #
> # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
> # Read the manual for more InnoDB related options. There are many!
> # You might want to disable InnoDB to shrink the mysqld process by
> circa 100MB.
> #skip-innodb

>If InnoDB is enabled, it must be a different problem. What are the
>actual errors you get (copy/pasted or attached log would be best). You
>can write the mythtv-setup output to a log file with:

>mythtv-setup 2>&1 | tee ~/mythtv-setup.log

>Mike

I tired running that command but it told me that xprop cannot open that
display (I'm sshed in and I cannot get the xserver to pass through a
connection...)

the errors that the database outputs are:
rb:~$ *mysqlcheck -r -umythtv -p mythconverg*
mythconverg.archiveitems OK
mythconverg.callsignnetworkmap OK
mythconverg.capturecard OK
mythconverg.cardinput OK
mythconverg.channel OK
mythconverg.codecparams OK
mythconverg.credits OK
mythconverg.customexample OK
mythconverg.diseqc_config OK
mythconverg.diseqc_tree OK
mythconverg.displayprofilegroups OK
mythconverg.displayprofiles OK
mythconverg.dtv_multiplex OK
mythconverg.dtv_privatetypes OK
mythconverg.dvdbookmark OK
mythconverg.dvdinput OK
mythconverg.dvdtranscode OK
mythconverg.eit_cache OK
mythconverg.favorites OK
mythconverg.filemarkup OK
mythconverg.gallerymetadata OK
mythconverg.gamemetadata OK
mythconverg.gameplayers OK
mythconverg.housekeeping OK
mythconverg.inputgroup OK
mythconverg.inuseprograms OK
mythconverg.jobqueue OK
mythconverg.jumppoints OK
mythconverg.keybindings OK
mythconverg.keyword OK
mythconverg.movies_movies OK
mythconverg.movies_showtimes OK
mythconverg.movies_theaters OK
mythconverg.music_albumart OK
mythconverg.music_albums OK
mythconverg.music_artists OK
mythconverg.music_directories OK
mythconverg.music_genres OK
mythconverg.music_playlists OK
mythconverg.music_smartplaylist_categories OK
mythconverg.music_smartplaylist_items OK
mythconverg.music_smartplaylists OK
mythconverg.music_songs OK
mythconverg.music_stats OK
mythconverg.musicmetadata OK
mythconverg.musicplaylist OK
mythconverg.mythlog OK
mythconverg.mythweb_sessions OK
mythconverg.netflix OK
mythconverg.networkiconmap OK
mythconverg.newssites OK
mythconverg.oldfind OK
mythconverg.oldprogram OK
mythconverg.oldrecorded OK
mythconverg.people OK
mythconverg.phonecallhistory OK
mythconverg.phonedirectory OK
mythconverg.pidcache OK
mythconverg.playgroup OK
mythconverg.powerpriority OK
mythconverg.profilegroups OK
mythconverg.program OK
mythconverg.programgenres OK
mythconverg.programrating OK
mythconverg.recgrouppassword OK
mythconverg.record OK
mythconverg.record_tmp OK
mythconverg.recorded OK
mythconverg.recordedcredits OK
mythconverg.recordedfile OK
mythconverg.recordedmarkup OK
mythconverg.recordedprogram OK
mythconverg.recordedrating OK
mythconverg.recordedseek OK
mythconverg.recordingprofiles OK
mythconverg.recordmatch OK
mythconverg.romdb OK
mythconverg.schemalock OK
mythconverg.settings OK
mythconverg.storagegroup OK
mythconverg.streams OK
mythconverg.tvchain OK
mythconverg.upnpmedia OK
mythconverg.videocast OK
mythconverg.videocategory OK
mythconverg.videocountry OK
mythconverg.videogenre OK
mythconverg.videometadata OK
mythconverg.videometadatacast OK
mythconverg.videometadatacountry OK
mythconverg.videometadatagenre OK
mythconverg.videosource OK
mythconverg.videotypes OK
mythconverg.weatherdatalayout
*note : The storage engine for the table doesn't support repair
mythconverg.weatherscreens
note : The storage engine for the table doesn't support repair
mythconverg.weathersourcesettings
note : The storage engine for the table doesn't support repair*
mythconverg.websites OK

I don't think this will help much through?
-J

mtdean at thirdcontact

May 4, 2008, 10:20 AM

Post #8 of 11 (1096 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

On 05/04/2008 12:20 PM, J wrote:
> On 05/02/2008 09:46 PM, J wrote:
>
>> If InnoDB is enabled, it must be a different problem. What are the
>> actual errors you get (copy/pasted or attached log would be best). You
>> can write the mythtv-setup output to a log file with:
>> mythtv-setup 2>&1 | tee ~/mythtv-setup.log
> I tired running that command but it told me that xprop cannot open that
> display (I'm sshed in and I cannot get the xserver to pass through a
> connection...)
>

ssh -Y <hostname>

Then run the above command.

> the errors that the database outputs are:
> rb:~$ *mysqlcheck -r -umythtv -p mythconverg*

Completely different information.

> mythconverg.weatherdatalayout
> *note : The storage engine for the table doesn't support repair
> mythconverg.weatherscreens
> note : The storage engine for the table doesn't support repair
> mythconverg.weathersourcesettings
> note : The storage engine for the table doesn't support repair*
> mythconverg.websites OK
>
>
> I don't think this will help much through?

Normally it wouldn't, but it does conclusively prove that you have
InnoDB enabled and your weather tables were set up as InnoDB.

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

digitalaudiorock at gmail

May 4, 2008, 2:28 PM

Post #9 of 11 (1080 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

On Sun, May 4, 2008 at 12:20 PM, J <jsweepstakes[at]gmail.com> wrote:

>
> I tired running that command but it told me that xprop cannot open that
> display (I'm sshed in and I cannot get the xserver to pass through a
> connection...)
>

If you enable X11Forwarding in sshd on the backend and then ssh in
using "ssh -X -Y" it'll work.

> the errors that the database outputs are:
> rb:~$ mysqlcheck -r -umythtv -p mythconverg
> mythconverg.archiveitems OK
> mythconverg.callsignnetworkmap OK
> mythconverg.capturecard OK
> mythconverg.cardinput OK
> mythconverg.channel OK
> mythconverg.codecparams OK
> mythconverg.credits OK
> mythconverg.customexample OK
> mythconverg.diseqc_config OK
> mythconverg.diseqc_tree OK
> mythconverg.displayprofilegroups OK
> mythconverg.displayprofiles OK
> mythconverg.dtv_multiplex OK
> mythconverg.dtv_privatetypes OK
> mythconverg.dvdbookmark OK
> mythconverg.dvdinput OK
> mythconverg.dvdtranscode OK
> mythconverg.eit_cache OK
> mythconverg.favorites OK
> mythconverg.filemarkup OK
> mythconverg.gallerymetadata OK
> mythconverg.gamemetadata OK
> mythconverg.gameplayers OK
> mythconverg.housekeeping OK
> mythconverg.inputgroup OK
> mythconverg.inuseprograms OK
> mythconverg.jobqueue OK
> mythconverg.jumppoints OK
> mythconverg.keybindings OK
> mythconverg.keyword OK
> mythconverg.movies_movies OK
> mythconverg.movies_showtimes OK
> mythconverg.movies_theaters OK
> mythconverg.music_albumart OK
> mythconverg.music_albums OK
> mythconverg.music_artists OK
> mythconverg.music_directories OK
> mythconverg.music_genres OK
> mythconverg.music_playlists OK
> mythconverg.music_smartplaylist_categories OK
> mythconverg.music_smartplaylist_items OK
> mythconverg.music_smartplaylists OK
> mythconverg.music_songs OK
> mythconverg.music_stats OK
> mythconverg.musicmetadata OK
> mythconverg.musicplaylist OK
> mythconverg.mythlog OK
> mythconverg.mythweb_sessions OK
> mythconverg.netflix OK
> mythconverg.networkiconmap OK
> mythconverg.newssites OK
> mythconverg.oldfind OK
> mythconverg.oldprogram OK
> mythconverg.oldrecorded OK
> mythconverg.people OK
> mythconverg.phonecallhistory OK
> mythconverg.phonedirectory OK
> mythconverg.pidcache OK
> mythconverg.playgroup OK
> mythconverg.powerpriority OK
> mythconverg.profilegroups OK
> mythconverg.program OK
> mythconverg.programgenres OK
> mythconverg.programrating OK
> mythconverg.recgrouppassword OK
> mythconverg.record OK
> mythconverg.record_tmp OK
> mythconverg.recorded OK
> mythconverg.recordedcredits OK
> mythconverg.recordedfile OK
> mythconverg.recordedmarkup OK
> mythconverg.recordedprogram OK
> mythconverg.recordedrating OK
> mythconverg.recordedseek OK
> mythconverg.recordingprofiles OK
> mythconverg.recordmatch OK
> mythconverg.romdb OK
> mythconverg.schemalock OK
> mythconverg.settings OK
> mythconverg.storagegroup OK
> mythconverg.streams OK
> mythconverg.tvchain OK
> mythconverg.upnpmedia OK
> mythconverg.videocast OK
> mythconverg.videocategory OK
> mythconverg.videocountry OK
> mythconverg.videogenre OK
> mythconverg.videometadata OK
> mythconverg.videometadatacast OK
> mythconverg.videometadatacountry OK
> mythconverg.videometadatagenre OK
> mythconverg.videosource OK
> mythconverg.videotypes OK
> mythconverg.weatherdatalayout
> note : The storage engine for the table doesn't support repair
> mythconverg.weatherscreens
> note : The storage engine for the table doesn't support repair
> mythconverg.weathersourcesettings
> note : The storage engine for the table doesn't support repair
> mythconverg.websites OK
>
>
> I don't think this will help much through?
> -J
>

Those errors about the weather tables are normal, as innodb tables
don't aren't supported by that repair command.

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

jsweepstakes at gmail

May 4, 2008, 2:38 PM

Post #10 of 11 (1082 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

------------------------------
On 05/04/2008 12:20 PM, J wrote:
> On 05/02/2008 09:46 PM, J wrote:
>
>> If InnoDB is enabled, it must be a different problem. What are the
>> actual errors you get (copy/pasted or attached log would be best). You
>> can write the mythtv-setup output to a log file with:
>> mythtv-setup 2>&1 | tee ~/mythtv-setup.log
> I tired running that command but it told me that xprop cannot open that
> display (I'm sshed in and I cannot get the xserver to pass through a
> connection...)
>

>ssh -Y <hostname>

Then run the above command.

> the errors that the database outputs are:
> rb:~$ *mysqlcheck -r -u -p mythconverg*

>Completely different information.

> mythconverg.weatherdatalayout
> *note : The storage engine for the table doesn't support repair
> mythconverg.weatherscreens
> note : The storage engine for the table doesn't support repair
> mythconverg.weathersourcesettings
> note : The storage engine for the table doesn't support repair*
> mythconverg.websites OK
>
>
> I don't think this will help much through?

>Normally it wouldn't, but it does conclusively prove that you have
>InnoDB enabled and your weather tables were set up as InnoDB.

>Mike

That doesn't seam to give much info...

rb:~$ more mythtv-setup.log
* Stopping MythTV server: mythbackend [
OK ]
* Restarting MythTV server:
mythbackend No /usr/bin/mythbackend
fou
nd running; none killed.
[
OK ]
-J

mtdean at thirdcontact

May 4, 2008, 3:37 PM

Post #11 of 11 (1082 views)
Permalink

Re: Database upgrade problems with weather [In reply to]

On 05/04/2008 05:38 PM, J wrote:
>
>> On 05/02/2008 09:46 PM, J wrote:
>>>> If InnoDB is enabled, it must be a different problem. What are the
>>>> actual errors you get (copy/pasted or attached log would be best). You
>>>> can write the mythtv-setup output to a log file with:
>>>> mythtv-setup 2>&1 | tee ~/mythtv-setup.log
>>>>
>>> I tired running that command but it told me that xprop cannot open that
>>> display (I'm sshed in and I cannot get the xserver to pass through a
>>> connection...)
>> ssh -Y <hostname>
>> Then run the above command.
> That doesn't seam to give much info...
>
> rb:~$ more mythtv-setup.log
> * Stopping MythTV server: mythbackend [
> OK ]
> * Restarting MythTV server:
> mythbackend No /usr/bin/mythbackend
> fou
> nd running; none killed.

That was with mythtv-setup as the command?

I think Ubuntu calls the mythbackend binary mythbackend.real or
something like that, but I figured it would be easier to run mythtv-setup.

Perhaps:

mythtv-setup.real 2>&1 | tee ~/mythtv-setup.log

or

mythbackend.real 2>&1 | tee ~/mythbackend.log

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com