Hello,
we are using core protect since a few versions and have recently upgraded to 26.1.2 paper, sadly it seems that CO has issues with its sqlite db now. The old db get integrity problems on core protect start it cause the db integrity to get destroyed. Like unlinked indexes and something. I repaired the db once but on restart co just cause the same issue again.
I then deleted the CO db to start new but sadly it always says db busy even with 0 items in queue and the working and good new db.
Is there anyway to debug the "db is busy" because I do not know what it even means. Does it mean there is a DB connection issue or connection pool is full? DB lock?
Thanks for your help!
Hello,
we are using core protect since a few versions and have recently upgraded to 26.1.2 paper, sadly it seems that CO has issues with its sqlite db now. The old db get integrity problems on core protect start it cause the db integrity to get destroyed. Like unlinked indexes and something. I repaired the db once but on restart co just cause the same issue again.
I then deleted the CO db to start new but sadly it always says db busy even with 0 items in queue and the working and good new db.
Is there anyway to debug the "db is busy" because I do not know what it even means. Does it mean there is a DB connection issue or connection pool is full? DB lock?
Thanks for your help!