Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Upgrade 0.24->0.25 goes poorly.

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


RossBoylan at stanfordalumni

May 12, 2012, 7:22 PM

Post #1 of 9 (1078 views)
Permalink
Upgrade 0.24->0.25 goes poorly.

I'm running Debian testing in a chroot with the Marillat's
respositories. I just upgraded from 0.24 to 0.25 today, and can no
longer run mythbackend. I get the error
# date; /etc/init.d/mythtv-backend start
Sat May 12 14:05:56 PDT 2012
Starting MythTV server: mythbackend .
root [at] cor:/etc/mythtv#
Cannot login to database?

Would you like to configure the database connection now? [no]
[console is not interactive, using default 'no']

/var/log/mythtv/mythbackend.log has not been touched since the upgrade,
and I don't see much in any logs.

Using mysql command line I am able to login to mythconverg using the
same account and password as in /etc/mythtv/mysql.txt.

Hoping to get more diagnostics I did
# mythbackend --help
running as root. Immediately mythbackend started using all the CPU it
could and its memory use grew rapidly until the system became entirely
unresponsive. I got it back many minutes later after several processes
were killed by the out of memory monitor, one was killed after long
non-response, and mythbackend failed with an allocation error.

First, is the backend session run as root likely to have caused any
damage to myth or its database?

Second, how can I got login working again? It was fine before the
upgrade.

Here are some possibly relevant facts:
1. mysql is running in the chroot and the host system mysql is shut
down.
2. A few days ago the chroot disk filled (from mythtranscode "no more
queue slots" messages) and one of the mysql tables was reported corrupt
when I cleared space and restarted. myisamchk appeared to have fixed
it.
3. My initial upgrade failed with a message it could not find libicu,
and then the same login failures as shown above. I installed libicu.
4. I have fiddled with settings trying to get remote access to the
mythbacked. I did not succeed.
5. Even before the upgrade I got
Error parsing: /var/lib/mythtv/.mythtv/config.xml at line: 1 column: 1
on startup. That file is empty, though there is a config.xml~ file with
stuff in it.
6. I may have changed the system name after installing myth (though that
change may have preceded the myth install).
7. /var/lib/mythtv/.mythtv/mysql.txt is completely unlike the other
mysql.txt; different password and DBType=QMYSQL3. /var/lib/mythtv is the
home directory for the mythtv user, and the init.d script executes
mythbacked as user mythtv.
8. syslogging from the chroot is going to the host machine.
9. mysql (5.1) was upgraded at the same time as myth. mysql got a bunch
of security fixes, which perhaps could make it harder to access.

Thanks for any help.
Ross Boyan


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


keemllib at gmail

May 13, 2012, 9:13 AM

Post #2 of 9 (1044 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On 05/12/2012 09:22 PM, Ross Boylan wrote:
...
> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
> and I don't see much in any logs.
...

Hi;

Check your /etc/init.d/mythtv-backend file. It will tell you where your
logs are going. It won't be the file you looked at above. Expect:
--syslog sonething or --logpath somethingElse.

> 5. Even before the upgrade I got
> Error parsing: /var/lib/mythtv/.mythtv/config.xml at line: 1 column: 1
> on startup. That file is empty, though there is a config.xml~ file with
> stuff in it.

Copy a good config.xml file to the user's .mythtv directory whose running
the backend. That may be root, or if you're using the --user switch, that
user, most likely mythtv.

...
> Thanks for any help.

Lots of stuff going on here, but that's where a start.

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


RossBoylan at stanfordalumni

May 13, 2012, 9:57 AM

Post #3 of 9 (1044 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
> On 05/12/2012 09:22 PM, Ross Boylan wrote:
> ...
> > /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
> > and I don't see much in any logs.
> ...
>
> Hi;
>
> Check your /etc/init.d/mythtv-backend file. It will tell you where your
> logs are going. It won't be the file you looked at above. Expect:
> --syslog sonething or --logpath somethingElse.
It is the file I looked at. Here are the key parts of the init.d file

DAEMON=/usr/bin/mythbackend
ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile $RUNDIR/$NAME.pid"
start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
--chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS

One reason I was trying to run mythbackend manually was so I could see
error messages.

>
> > 5. Even before the upgrade I got
> > Error parsing: /var/lib/mythtv/.mythtv/config.xml at line: 1 column: 1
> > on startup. That file is empty, though there is a config.xml~ file with
> > stuff in it.
>
> Copy a good config.xml file to the user's .mythtv directory whose running
> the backend. That may be root, or if you're using the --user switch, that
> user, most likely mythtv.
>
Is 0.25 more sensitive to this and 0.24?
Ross
> ...
> > Thanks for any help.
>
> Lots of stuff going on here, but that's where a start.
>

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


keemllib at gmail

May 13, 2012, 10:15 AM

Post #4 of 9 (1045 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On 05/13/2012 11:57 AM, Ross Boylan wrote:
> On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
>> On 05/12/2012 09:22 PM, Ross Boylan wrote:
>> ...
>>> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
>>> and I don't see much in any logs.
...
>> Check your /etc/init.d/mythtv-backend file. It will tell you where your
>> logs are going. It won't be the file you looked at above. Expect:
>> --syslog sonething or --logpath somethingElse.
> It is the file I looked at. Here are the key parts of the init.d file
>
> DAEMON=/usr/bin/mythbackend
> ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile $RUNDIR/$NAME.pid"
> start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
> --chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS

--logpath must point to a directory, not a file. I understand from your original
post that --help didn't help, so: http://www.mythtv.org/wiki/Logging#File_Logging.
In other words: --logpath /var/log/mythtv.

>> Copy a good config.xml file to the user's .mythtv directory whose running
>> the backend. That may be root, or if you're using the --user switch, that
>> user, most likely mythtv.
>>
> Is 0.25 more sensitive to this and 0.24?

I remember seeing posts on this list saying that config.xml had been zeroed.
And I've had it happen to me too.

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


RossBoylan at stanfordalumni

May 13, 2012, 10:42 PM

Post #5 of 9 (1063 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On Sun, 2012-05-13 at 12:15 -0500, Bill Meek wrote:
> On 05/13/2012 11:57 AM, Ross Boylan wrote:
> > On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
> >> On 05/12/2012 09:22 PM, Ross Boylan wrote:
> >> ...
> >>> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
> >>> and I don't see much in any logs.
> ...
> >> Check your /etc/init.d/mythtv-backend file. It will tell you where your
> >> logs are going. It won't be the file you looked at above. Expect:
> >> --syslog sonething or --logpath somethingElse.
> > It is the file I looked at. Here are the key parts of the init.d file
> >
> > DAEMON=/usr/bin/mythbackend
> > ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile $RUNDIR/$NAME.pid"
> > start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
> > --chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS
>
> --logpath must point to a directory, not a file. I understand from your original
> post that --help didn't help, so: http://www.mythtv.org/wiki/Logging#File_Logging.
> In other words: --logpath /var/log/mythtv.
Thanks. That's much better.
>
> >> Copy a good config.xml file to the user's .mythtv directory whose running
> >> the backend. That may be root, or if you're using the --user switch, that
> >> user, most likely mythtv.
Yes, the user is mythtv. I copied the non-empty version of config.xml
over the file.
> >>
> > Is 0.25 more sensitive to this and 0.24?
>
> I remember seeing posts on this list saying that config.xml had been zeroed.
> And I've had it happen to me too.

After various false starts and dpkg-reconfigure's my latest log is this:
2012-05-13 21:57:41.204974 C [845/845] thread_unknown mythcommandlineparser.cpp:2534 (ConfigureLogging) - mythbackend version: [v0.25pre] www.mythtv.org
2012-05-13 21:57:41.205064 N [845/845] thread_unknown mythcommandlineparser.cpp:2536 (ConfigureLogging) - Enabled verbose msgs: general
2012-05-13 21:57:41.205978 N [845/845] thread_unknown logging.cpp:1176 (logStart) - Setting Log Level to LOG_INFO
2012-05-13 21:57:41.206415 I [845/845] thread_unknown logging.cpp:229 (FileLogger) - Added logging to the console
2012-05-13 21:57:41.206511 I [845/845] thread_unknown logging.cpp:238 (FileLogger) - Added logging to /var/log/mythtv/mythbackend.20120513215741.845.log
2012-05-13 21:57:41.206530 I [845/845] thread_unknown logging.cpp:425 (DatabaseLogger) - Added database logging to table logging
2012-05-13 21:57:41.234081 N [845/845] thread_unknown logging.cpp:1215 (logStart) - Setting up SIGHUP handler
2012-05-13 21:57:41.235416 N [845/845] thread_unknown mythdirs.cpp:51 (InitializeMythDirs) - Using runtime prefix = /usr
2012-05-13 21:57:41.235458 N [845/845] thread_unknown mythdirs.cpp:64 (InitializeMythDirs) - Using configuration directory = /var/lib/mythtv/.mythtv
2012-05-13 21:57:41.235745 I [845/845] CoreContext mythcorecontext.cpp:227 (Init) - Assumed character encoding: en_US.UTF-8
2012-05-13 21:57:41.237495 N [845/845] CoreContext mythcontext.cpp:477 (LoadDatabaseSettings) - Empty LocalHostName.
2012-05-13 21:57:41.237519 I [845/845] CoreContext mythcontext.cpp:481 (LoadDatabaseSettings) - Using localhost value of corn
2012-05-13 21:57:41.403991 N [845/845] CoreContext mythcorecontext.cpp:1270 (InitLocale) - Setting QT default locale to en_US
2012-05-13 21:57:41.404285 I [845/845] CoreContext mythcorecontext.cpp:1303 (SaveLocaleDefaults) - Current locale en_US
2012-05-13 21:57:41.404395 N [845/845] CoreContext mythlocale.cpp:121 (LoadDefaultsFromXML) - Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
2012-05-13 21:57:41.417933 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:41.417972 C [845/845] CoreContext schemawizard.cpp:135 (CompareAndWait) - MythTV database schema is old. Waiting to see if DB is being upgraded.
2012-05-13 21:57:42.422112 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:43.424333 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:44.427462 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:45.430694 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:46.433719 I [845/845] CoreContext schemawizard.cpp:117 (Compare) - Current MythTV Schema Version (DBSchemaVer): 1266
2012-05-13 21:57:46.433846 C [845/845] CoreContext schemawizard.cpp:179 (CompareAndWait) - Timed out waiting.
2012-05-13 21:57:46.434699 C [845/845] CoreContext dbutil.cpp:217 (BackupDB) - Database backups disabled. Skipping backup.
2012-05-13 21:57:46.437245 I [845/845] CoreContext schemawizard.cpp:316 (PromptForUpgrade) - Console is non-interactive, can't prompt user...
2012-05-13 21:57:46.437263 C [845/845] CoreContext schemawizard.cpp:341 (PromptForUpgrade) - Upgrading.
2012-05-13 21:57:46.437719 C [845/845] CoreContext dbcheck.cpp:495 (UpgradeTVDatabaseSchema) - Newest MythTV Schema Version : 1299
2012-05-13 21:57:46.445251 E [845/845] CoreContext videodbcheck.cpp:369 (doUpgradeVideoDatabaseSchema) - Unrecognized video database schema version. Unable to upgrade database.
2012-05-13 21:57:46.445272 E [845/845] CoreContext videodbcheck.cpp:372 (doUpgradeVideoDatabaseSchema) - Please see mythplugins/mythvideo/README.database for more information.
2012-05-13 21:57:46.445290 E [845/845] CoreContext videodbcheck.cpp:375 (doUpgradeVideoDatabaseSchema) - mythvideo.DBSchemaVer: '1011', VideoDBSchemaVer: '', DVDDBSchemaVer: ''
2012-05-13 21:57:46.445304 E [845/845] CoreContext dbcheck.cpp:509 (UpgradeTVDatabaseSchema) - Database Schema upgrade FAILED, unlocking.
2012-05-13 21:57:46.445505 E [845/845] CoreContext main_helpers.cpp:529 (run_backend) - Couldn't upgrade database to new schema

I'm not sure if the message about the old schema means mythbackend
actually did reach the database, or if it just reflects info cached
somewhere else. At any rate, the end is clearly a failure. I can't
find README.Database on my system.

Even info on whether this looks like a problem contacting/logging into
the database (which doesn't seem to be producing any logs, even when I
connect successfully from the command line with mysql) or something
after that would be useful.

Ross

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


mtdean at thirdcontact

May 13, 2012, 11:48 PM

Post #6 of 9 (1044 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On 05/14/2012 01:42 AM, Ross Boylan wrote:
> After various false starts and dpkg-reconfigure's my latest log is this:
...
> 2012-05-13 21:57:46.445251 E [845/845] CoreContext videodbcheck.cpp:369 (doUpgradeVideoDatabaseSchema) - Unrecognized video database schema version. Unable to upgrade database.
> 2012-05-13 21:57:46.445290 E [845/845] CoreContext videodbcheck.cpp:375 (doUpgradeVideoDatabaseSchema) - mythvideo.DBSchemaVer: '1011', VideoDBSchemaVer: '', DVDDBSchemaVer: ''

You have an unsupported MythVideo schema version from MythTV 0.20 or so
(>5yrs old) because you had used MythVideo, then quit installing it. To
fix it:

http://www.gossamer-threads.com/lists/mythtv/users/512916#512916

It is very important that you restore the pre-upgrade database backup
before attempting to fix your database and before attempting to upgrade
the database. Using the "failed to upgrade" database could leave your
database schema and/or data broken.

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


steltek at tcnnet

May 14, 2012, 12:51 AM

Post #7 of 9 (1045 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On 13/05/2012 19:15, Bill Meek wrote:
> On 05/13/2012 11:57 AM, Ross Boylan wrote:
>> On Sun, 2012-05-13 at 11:13 -0500, Bill Meek wrote:
>>> On 05/12/2012 09:22 PM, Ross Boylan wrote:
>>> ...
>>>> /var/log/mythtv/mythbackend.log has not been touched since the upgrade,
>>>> and I don't see much in any logs.
> ...
>>> Check your /etc/init.d/mythtv-backend file. It will tell you where your
>>> logs are going. It won't be the file you looked at above. Expect:
>>> --syslog sonething or --logpath somethingElse.
>> It is the file I looked at. Here are the key parts of the init.d file
>>
>> DAEMON=/usr/bin/mythbackend
>> ARGS="--daemon --logpath /var/log/mythtv/mythbackend.log --pidfile
>> $RUNDIR/$NAME.pid"
>> start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \
>> --chuid $USER --nicelevel $NICE --exec $DAEMON --
>> $ARGS
>
> --logpath must point to a directory, not a file. I understand from your
> original
> post that --help didn't help, so:
> http://www.mythtv.org/wiki/Logging#File_Logging.
> In other words: --logpath /var/log/mythtv.

This seems to be a bug in the package as I had the same problem on my
box (The log path is hardcoded in the /etc/init.d/mythtv-backend script
and not updated when going from 0.24 to 0.25).

- Michel

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


RossBoylan at stanfordalumni

May 14, 2012, 8:08 AM

Post #8 of 9 (1045 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On Mon, 2012-05-14 at 02:48 -0400, Michael T. Dean wrote:
> On 05/14/2012 01:42 AM, Ross Boylan wrote:
> > After various false starts and dpkg-reconfigure's my latest log is this:
> ...
> > 2012-05-13 21:57:46.445251 E [845/845] CoreContext videodbcheck.cpp:369 (doUpgradeVideoDatabaseSchema) - Unrecognized video database schema version. Unable to upgrade database.
> > 2012-05-13 21:57:46.445290 E [845/845] CoreContext videodbcheck.cpp:375 (doUpgradeVideoDatabaseSchema) - mythvideo.DBSchemaVer: '1011', VideoDBSchemaVer: '', DVDDBSchemaVer: ''
>
> You have an unsupported MythVideo schema version from MythTV 0.20 or so
> (>5yrs old) because you had used MythVideo, then quit installing it. To
> fix it:
That seems unlikely, since 0.24 was the first version I installed.
Ross
>
> http://www.gossamer-threads.com/lists/mythtv/users/512916#512916
>
> It is very important that you restore the pre-upgrade database backup
> before attempting to fix your database and before attempting to upgrade
> the database. Using the "failed to upgrade" database could leave your
> database schema and/or data broken.
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

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


mtdean at thirdcontact

May 14, 2012, 8:14 AM

Post #9 of 9 (1054 views)
Permalink
Re: Upgrade 0.24->0.25 goes poorly. [In reply to]

On 05/14/2012 11:08 AM, Ross Boylan wrote:
> On Mon, 2012-05-14 at 02:48 -0400, Michael T. Dean wrote:
>> On 05/14/2012 01:42 AM, Ross Boylan wrote:
>>> After various false starts and dpkg-reconfigure's my latest log is this:
>> ...
>>> 2012-05-13 21:57:46.445251 E [845/845] CoreContext videodbcheck.cpp:369 (doUpgradeVideoDatabaseSchema) - Unrecognized video database schema version. Unable to upgrade database.
>>> 2012-05-13 21:57:46.445290 E [845/845] CoreContext videodbcheck.cpp:375 (doUpgradeVideoDatabaseSchema) - mythvideo.DBSchemaVer: '1011', VideoDBSchemaVer: '', DVDDBSchemaVer: ''
>> You have an unsupported MythVideo schema version from MythTV 0.20 or so
>> (>5yrs old) because you had used MythVideo, then quit installing it. To
>> fix it:
> That seems unlikely, since 0.24 was the first version I installed.

Then you have a database with broken data. To fix it (at least the
identified breakage):

>> http://www.gossamer-threads.com/lists/mythtv/users/512916#512916
>>
>> It is very important that you restore the pre-upgrade database backup
>> before attempting to fix your database and before attempting to upgrade
>> the database. Using the "failed to upgrade" database could leave your
>> database schema and/or data broken.
>>

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

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.