SonarQube v9.5 has been EOL since SonarQube v9.6 was released, so I suggest upgrading to SonarQube v9.9 LTS and letting us know if you still face the issue!
It looks like you already have DEBUG logging turned, so there’s no further logging available.
I’m not quite sure, if it is at all related to git.
I remove the line completly from sonar-project.properties file. sonar.scm.provider=git
And still the issue is the same.
Updating the SonarQube to 9.9 is somewhat difficult because there are plenty of other projects affected.
I also don’t understand, how the version of SonarQube on the server affects the behavior of the sonar-scanner on the client side.
What is the scanner about to do after the line
Could it be because of I’m running the Java version on Alpine Linux on arm architecture (aarch64) ???
All other project (that are using the same SonarQube V9.5 Server) are performing fine.
One difference is, that only the problematic project is performing the scan on an ARM machine.
As I mentioned, it would be best to see if you can reproduce the error on a supported version (v9.9 LTS), even if it’s just a test version, to see if the behavior can be reproduced.