Thank you Colin,
It seems the database was somehow corrupted.
I compiled 2.6.21 from source that was able to read the database but not
write.
Save as xml, open with the buster version (3.4), save into mysql as new
database and all good.
sorry to bother you
kind regards
Sepp
--
Sent from: htt
Interesting. Thanks for the info.
Regards,
Adrien
> On Aug 15, 2019, at 11:31 AM, David G Hamblen wrote:
>
> "Open Anyway" works fine on mysql in GC 3.4 on Ubuntu 19.04. Once you open GC
> with the mysql backend, and do a "Save As" to an xml backend, it doesn't
> clear the lock on the mysql d
"Open Anyway" works fine on mysql in GC 3.4 on Ubuntu 19.04. Once you
open GC with the mysql backend, and do a "Save As" to an xml backend, it
doesn't clear the lock on the mysql database; so you'll get the lock
message. But definitely look at the trace file.
On 8/15/19 9:51 AM, Adrien Montel
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 log
Have a look in the gnucash trace file and see if there is anything
helpful there.
Colin
On Thu, 15 Aug 2019 at 09:48, sepp 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
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 s
