[GNC] I can no longer connect to mysql after upgrading to Debian Buster

[Adrien Monteleone]

The lock message means GnuCash crashed or was not properly shut down.

While you can bypass this for XML and Sqlite with "Open Anyway", MySQL might not play nice.

You might have to login to the MySQL console to fix things there.

In addition to checking the tracefile, I’d also check the MySQL logs. (which might need to be turned on, or increase their verbosity)

Before you get too far down a rabbit hole trying to fix this, be certain if you are running MySQL proper, or MariaDB (a near drop in replacement shipped by many distros) as there may be some differences.

Regards,
Adrien

> On Aug 14, 2019, at 12:58 PM, sepp <sepp at mail.moosbauer.net> wrote:
> 
> Hi
> 
> Sorry, I do not even know if this belongs here but I am a little lost
> 
> I am a happy GnuCash user for years and have used Mysql as a backend for
> quite some time. Now I upraded Debian from Stretch to Buster and can no
> longer connect to the Mysql Database. Yes I can connect in the shel using
> the same credentials ...
> 
> 1st "Gnucash caould obtainm the lock for mysql://...
> When I select Open Anyway I get a message Unable to save to databse with the
> option cancel. Selecting cancel just reproduces the message so I have to
> kill it from the shell
> When I select Open RO -> Unable to save to database. Book is marked
> read-only. Close option just reproduces the message - again killing in the
> shell
> Gnucash Version 3.4 Build ID: 3.4+ (2018-12-30)
> 
> any advice is very much apreciated
> 
> Thank you kind regards
> Sepp