Renovate exits with code 0 in the middle of the process

[florianmutter]

What would you like help with?

I think I found a bug

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.

GitHub

Please tell us more about your question or problem

In most of the runs renovate just stops when processing the last dependency (at least I think this is where it is). It exits with status code 0. Here is the end of the log of a "failed" run:

In a successful run it continues to list all the packages it finds:

Logs (if relevant)

Logs are to long for inline. File attached:
job-logs.txt

[rarkins]

It's unlikely that renovate is exiting itself without any message. Most likely is that the process or container is being killed by the OS or scheduler, such as for out of memory problems.

[florianmutter]

@rarkins Any idea how we could debug this?

[rarkins]

No

[florianmutter]

Since a few days the runs started to fail at the same step but now with this error log:

DEBUG: Content is not found for Maven url
       "url": "https://maven.pkg.github.com/fadi-nextgen-shop/ngshop/software/amazon/awssdk/bom/maven-metadata.xml",
       "statusCode": undefined
Error: The process '/usr/bin/docker' failed with exit code 1
    at ExecState._setResult (/home/runner/work/_actions/renovatebot/github-action/76d49712364696a06b60e8647df46b288fff0ddc/dist/index.js:1702:25)
    at ExecState.CheckComplete (/home/runner/work/_actions/renovatebot/github-action/76d49712364696a06b60e8647df46b288fff0ddc/dist/index.js:1685:18)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/renovatebot/github-action/76d49712364696a06b60e8647df46b288fff0ddc/dist/index.js:1579:27)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Pipe.<anonymous> (node:net:338:12)

[florianmutter]

Finally found some time to dig into this. It looks like node exits right at this line in fetch.ts:

await Promise.all(allManagerJobs);

The very next line is a log message that we do not see. This feels like there is a promise that does not resolve (see nodejs/node#29355 or nodejs/node#43162).

[maxbrunet]

I have been trying to debug the same issue for hours, I checked everything I could think of, there is no resource pressure, Renovate exits with code 0, and when it happens there is always at least 1 manager that does not reach this line:

renovate/lib/workers/repository/process/fetch.ts

Line 153 in e78fb57

logger.trace({ manager }, 'fetchManagerUpdates finished');

It is not consistent, but the bigger the repo, the more likely it is to occur. No way to tell why the Node process exits