java.lang.OutOfMemoryError while starting , disk space usage

[NicoB (Nicolas Bontoux)]

@eraonel: please store logs in text files or at least use formatted blocks (``` marker) to share logs, otherwise it’s hardly readable.

Did you get a chance to check resource consumption as mentioned ?

@NicoB

Given your initial hardware limitation, it seems that it’s only fair to know monitor what is the amount/state of local resources (cpu, ram, io) as SonarQube starts up.

You can find some monitoring tips here:

Daily CPU spike at 3 AM

Hi there, I would advise to approach this from a simple monitoring/troubleshooting angle, independently from SonarQube at the top being: use your OS monitoring tools to verify whether it’s actually one of SonarQube’s Java process who is eating up the CPU if you narrow it down to SonarQube, then focus more specifically on JVM monitoring, to understand how processes’ resource consumption whenever you observe abnormal behaviour