Replies: 1 comment 1 reply
-
Somehow there's a permission problem writing to the SQLite location in the container. Are you running with read Only FS, or with openshift, etc? Please provide full config, any customizations, etc. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
BitBucket Data Center, renovateVersion": 38.142.7
Please tell us more about your question or problem
I`m running renovate self-hosted with BitBucket Data Center edition using the renovate-ce helm-chart. Everything runs file for several days and all of a sudden log file starts logging:
Initially I was still on image 8.4.0 with ran renovate 38.104.0 but before writing here I tried upgrading to 8.7.0 which runs renovate 38.142.7 however the upgrade did not resolve the issue.
Since it is a relatively new and simple setup for the moment I redeployed from scratch to get it work but this is the 2nd time it happens and I would like to get some help if possible.
Scale down/restart does not help, in fact at first also it logs:
SQLite is running at the default spot /tmp/renovate backed up by a PVC provisioned by cephfs RWO.
Now that I'm reporting this I saw there is a config for
"sqliteVerbose": false,
which I have missed so far and maybe it was worth enabling but it is too late now.As it is not a critical tool yet I have redeployed renovate without backing up /tmp/renovate by a PVC by rootfs operator, basically trying to isolate if it is renovate or the PVC although we are using it for quite some time now and never had issues like this so far.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions