[mythtv-users] new recordings missing database fields after R5A22 upgrade

[Bruce Markey]

Byron Poland wrote:
> On 10/26/05, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>> Byron Poland wrote:
>>
>>> On 10/26/05, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>>>
>>>
>>>> Byron Poland wrote:
>>>>
>>>>> Here is the relevant part of my backend log on on startup:
>>>>>
>>>>> 2005-10-26 15:02:15.804 Using runtime prefix = /usr
>>>>> QSettings::sync: filename is null/empty
User doesn't have ~/.qt dir?

Missing "Current Schema Version:" message as of changeset 7260...

>>>>> 2005-10-26 15:02:15.953 New DB connection, total: 1
>>>>> 2005-10-26 15:02:15.991 Setting Lock for Database Schema upgrade. If
>>>>> you see a long pause here it means the Schema is already locked and is
>>>>> being upgraded by another Myth process.
>>>>> QSettings::sync: filename is null/empty
>>>>> 2005-10-26 15:02:16.005 New DB connection, total: 2
>>>>> 2005-10-26 15:02:16.013 Database Schema upgrade complete, unlocking.
...
>>> mysql> SELECT data FROM settings WHERE value = 'DBSchemaVer';
>>> +------+
>>> | data |
>>> +------+
>>> | 1099 |
>>> +------+
...
> 2005-10-26 16:07:36.115 Setting Lock for Database Schema upgrade. If
> you see a long pause here it means the Schema is already locked and is
> being upgraded by another Myth process.

Most likely you are inadvertently running an older version of
mythbackend. This would explain why you don't see the version
message, why it thinks the schema version number doesn't match
and why the basename field is not being filled in.

If there is more than one machine involved, check that you have
installed the same version on all machines. Run "locate mythbackend"
to see if there is more than one executable. If you start the
backend from a script, check the path in the script and if from
the commandline, check "which mythbackend".

--  bjm