Child process terminated abruptly

[RabeeaEgbareia]

I got this exception while scanning my project: Any idea what's wrong here ?

Version:

[tdruez]

@RabeeaEgbareia You can try again disabling multiprocessing first, as suggested previously: https://github.com/nexB/scancode.io/issues/642#issuecomment-1496308424

[RabeeaEgbareia]

@tdruez It could take a lot of time since the project is large. I will try, but is there any other suggestion or workaround ? Btw: this link in the comment #642 is not valid (https://scancodeio.readthedocs.io/en/latest/scancodeio-settings.html#scancodeio-processes)

[tdruez]

https://scancodeio.readthedocs.io/en/latest/application-settings.html#scancodeio-processes

[tdruez]

It could take a lot of time since the project is large. I will try, but is there any other suggestion or workaround ?

The time it takes to complete is irrelevant at the moment, we need to figure out the issue first. Thus my suggestion for running the pipeline outside of any multiprocessing context. The goal is to determine if the issue is related to multiprocessing or not.

I cannot help you further until you can confirm that the pipeline is running fine with multiprocessing disabled, as suggested a while ago https://github.com/nexB/scancode.io/issues/642#issuecomment-1496326078

[RabeeaEgbareia]

@tdruez Ok, I started a new "scan_codebase" pipeline with "SCANCODEIO_PROCESSES=-1". I will update later here .. Thanks

[RabeeaEgbareia]

@tdruez Still failing (SCANCODEIO_PROCESSES=-1)

I have these messages as well:

[tdruez]

Have you restarted the whole app after changing the settings? It appears from your output that the multiprocessing is still enabled.

[RabeeaEgbareia]

@tdruez Yes.

This is my docker.env file

And then:

• docker compose build
• docker compose up