[mythtv-users] New web app for setup and replacement for mythweb -- Force start in setup mode
Peter Bennett
pb.mythtv at gmail.com
Mon Jun 19 13:25:50 UTC 2023
On 6/18/23 09:40, Peter Bennett wrote:
>
> On 6/18/23 08:27, John wrote:
>> mythtv-light_34~Pre-280-g3efbdee593-0_amd64_jammy
>>
>> No problems encountered with a new clean database .
>>
>> However I wanted to check that an upgrade of an existing database was
>> ok.
>>
>> On attempting to import my production datbase MythTV Schema Version
>> (DBSchemaVer): 1376.
>>
>> I had issues which I could only rectify in mythtv-setup. This is to
>> be expected as the two machines have a different tuner configuration.
>>
>> The problem was that the backend either wouldn't start due to
>>
>> (UpgradeTVDatabaseSchema) Not allowed to upgrade the database.
>>
>> Ran mythtv-setup, which did the schema upgrade fine.
>>
>> The backend then crashed on startup due to the incompatible tuner
>> configuration.
>>
>> Deleted all tuners in mythtv-setup then reconfigured using the web
>> interface without problems.
>>
>> So a means of forcing the backend to start in configuration mode is
>> needed.
>>
>>
>>
> If you start mythbackend with an out of date schema. it should update
> the schema. It normally prompts the operator for whether to update the
> schema. Perhaps that defaulted to "no" ?
>
> For the crash due to incompatible tuner configuration - what you
> suggest makes sense, you need a way to get into configuration mode. I
> will set up a command line option for that.
>
> Peter
>
I have added a new command line option webonly to mythbackend startup
that starts it in web server only mode. Can you test whether this solves
the problem?
Peter
More information about the mythtv-users
mailing list