Simon Gröchenig <simon at sgroe.at> writes: > The problem probably occurs due to hourly backup tasks. These are > reading the GPKGs also during edit sessions. And that triggers the > errors. Sounds like you have a filesystem that doesn't work right, then, at least in terms of the locking sqlite needs. I think it's time for postgis in your shop.