[mythtv-users] 'Not allowed to upgrade the database'

[Michael T. Dean]

On 04/22/2013 10:41 AM, John Pilkington wrote:
> Hi:  I've just converted my main box from ATrpms-based 0.25.3 to 
> rpmfusion-based 0.26.0-7 under Fedora 17 x86_64. That also required a 
> move from nVidia 304.51 to 304.64.
>
> Most things seem ok, apart from MythTV.  Running mythtvsetup causes an 
> immediate return to the login screen.  When I first ran mythbackend it 
> said it needed the mysql_to_utc setting, and now it says:
>
>> 2013-04-22 15:19:48.713673 N  Using configuration directory = 
>> /home/John/.mythtv
>> 2013-04-22 15:19:48.713855 I  Assumed character encoding: en_GB.UTF-8
>> 2013-04-22 15:19:48.714528 N  Empty LocalHostName.
>> 2013-04-22 15:19:48.714544 I  Using localhost value of gateway12
>> 2013-04-22 15:19:48.719679 I  Added logging to the console
>>
>> This version of MythTV requires an updated database. (schema is 8 
>> versions behind)
>>
>> Please run mythtv-setup or mythbackend to update your database.
>>
>> Database Host: localhost
>> Database Name: mythconverg
>>
>> 2013-04-22 15:19:48.956082 I  Starting mythlogserver
>> 2013-04-22 15:19:48.959301 I  Starting IO manager (write)
>> 2013-04-22 15:19:48.959466 I  Starting process signal handler
>> 2013-04-22 15:19:48.967312 I  Starting IO manager (read)
>> 2013-04-22 15:19:48.967393 I  Starting process manager
>> 2013-04-22 15:19:48.968967 N  Setting QT default locale to en_GB
>> 2013-04-22 15:19:48.969062 I  Current locale en_GB
>> 2013-04-22 15:19:48.969131 N  Reading locale defaults from 
>> /usr/share/mythtv//locales/en_gb.xml
>> 2013-04-22 15:19:48.980609 I  Current MythTV Schema Version 
>> (DBSchemaVer): 1299
>> 2013-04-22 15:19:48.980648 W  Not allowed to upgrade the database.
>> 2013-04-22 15:19:48.983271 E  Couldn't upgrade database to new schema
>> 2013-04-22 15:19:49.413511 I  Added logging to mythlogserver at 
>> TCP:35327
>
>
>
> I'm doing this from the Konsole, just typing 'mythtvsetup' or 
> 'mythbackend', which is what I have usually done.  Am I running up 
> against a startup script or appearing as the wrong user, or on the 
> wrong host?

mythbackend can only update the database schema if run on the master 
backend.

However, it is /always/ recommended to run mythtv-setup to update the 
database schema after any upgrade.  mythtv-setup has a GUI that will 
show you what's going on and confirm that you do, in fact, want to 
upgrade the schema (which is a non-reversible process).

Please show the log output from running mythtv-setup so we can figure 
out why it's shutting down.

Mike