It usually means that GnuCash is not quitting cleanly. Are there any errors in
the tracefile? (https://wiki.gnucash.org/wiki/Tracefile).
In the SQL backend it's actually a record in the gnclock table, so a simpler
work-around would be to use the postgres CLI to remove that record.
Regards,
John Ralls
> On Apr 5, 2024, at 22:14, Bryan B. wrote:
>
> For some reason, GnuCash has started having some issue when I'm opening it
> where it will say "Could not obtain lock file for
> postgres://postgres@localhost/gnucash_personal"
> Then it gives a few options to use the file anyway, such as to use it in
> read-only mode, etc.
>
> I found a temporary work around by opening it anyway, saving it to xml,
> dropping then recreating my postgresql database, and then reopening the xml
> file and resaving it to the postgresql database.
>
> Any ideas on why this would be happening and how to resolve it?
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
