Renovate intermittently failing because of "SIGSEGV" signal #30141
Unanswered
amimas
asked this question in
Request Help
Replies: 1 comment 9 replies
-
use our gitlab pipeline template to run renovate on gitlab runner |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
Other
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
{'platform': 'gitlab', 'version': '~37'}
Please tell us more about your question or problem
Hi,
I'm self-hosting renovate and recently it started to fail intermittently. When it fails, I have the following error in the terminal output but no relevant info about this in the log.
The way I run renovate is following:
yarn
with followingpackage.json
and relevantyarn.lock
file.yarn renovate
(frompackage.json
above). Below is my GitLab CI config for running renovate.As you can see, I'm running renovate in the GitLab pipeline using node v20. The process runs on AWS EC2 instance type
t3.medium
, which has 2 CPU and 4GB memory.This has been working fine for several years. As of 2 weeks ago, renovate started to fail intermittently with the signal error I mentioned above. I had enabled renovate to keep itself up-to-date. Going through all the pipelines where it failed, I think it started failing when renovate was updated from 37.408.3 -> 37.414.1.
Going through the changelog of that version range, I'm not sure what (or if any) of them are the root cause. I also can't find any relevant info in the log file. It just abruptly ends wherever renovate process failed.
Not sure how to provide a reproducible public repo/execution. Could you please help or advise what I can do next?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions