SonarQube background tasks failing

Report a bug
#1

Hi,

We have the problem that the background tasks fail. This happens every two or three days. The only way to help is to restart the instance. In the logs there are two timeout exceptions.

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    Sonar Qube Verison: 8.5.0-developer
  • error observed (wrap logs/code around triple quote ``` for proper formatting)

log java.lang.IllegalStateException: connect timed out

at com.sonarsource.C.D.D.G.A(Unknown Source)

and

Caused by: java.net.SocketTimeoutException: connect timed out

at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

#2

Hi, I guess this happens with projects that have the Pull Request decoration feature enabled right?

Please give us more context: SQ version, SQ edition, which ALM are you using (github, gitlab, etc).

One of the possible root cause on such issue is DNS caching, when SQ and the ALM are hosted on Kubernetes or something similar. It this the case here? How do you operate SonarQube?

#3

Hello, yes, we use the pull request decorator for gitlab. Sonarqube and Gitalb operate on the same Kubernetes (eks cluster).

  • SQ Version: 8.5.0
  • SQ Edition: Developer
  • Gitlab Version: 13.5.3
#4

I’m not a kubernetes expert, but that looks exactly like if your GitLab IP/address get updated inside your K8 cluster, and SonarQube stick with the “old” address.