Issue with SonarQube Upgrade to 10.8.1 – Startup Probe Fails and Readiness Probe Fails

SonarQube Server / Community Build
, ,
1

Hello SonarQube Community,

I recently upgraded my SonarQube instance from version 10.6 to 10.8.1 on Kubernetes (AKS). After upgrading, I encountered issues with the SonarQube pods, and they are failing to start due to the following errors in the pod logs:

  1. Startup Probe Failure:

    Startup probe failed: Get "http://10.244.8.240:9000/api/system/status": dial tcp 10.244.8.240:9000: connect: connection refused

  2. Readiness Probe Failure:

    Readiness probe failed: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

This issue appears to occur right after the upgrade. Previously, everything worked fine with version 10.6.

Environment Details:

  • SonarQube Version: 10.8.1
  • Kubernetes Version: 1.29.4
  • Helm Chart Version: Latest (sonarqube/sonarqube)
  • Ingress Controller: NGINX
  • Database: PostgreSQL (hosted on Azure)

Actions Taken:

  • Verified the database connection and confirmed it is properly configured.
  • Checked SonarQube logs and verified the startup and readiness probes are pointing to the correct endpoints.
  • Restarted the pods multiple times, but the issue persists.

Error Logs from Pod:

Startup probe failed: Get "http://10.244.8.240:9000/api/system/status": dial tcp 10.244.8.240:9000: connect: connection refused
Readiness probe failed: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Questions:

  1. Is this issue related to the changes made in the default ingress.ingressClassName from the Helm chart after the upgrade to 10.8.1?
  2. Are there any additional configuration changes needed in version 10.8.1 for the probes to pass, especially related to ingress or service configurations?
  3. How can I further troubleshoot or resolve these probe failures?

Thank you,
Tanish

2

@ganncamp Can you please here? It’s a blocker for us.

3

Please do not tag individuals not involved in a thread.

I created a topic, when can I expect a response?

This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.

Be patient

  • Wait a few days before bumping a topic that hasn’t received a response.
  • Do not @name mention individuals not involved in the topic.
4

you should create a value.ymal file and added this to it that should solve it i had similar issue today and works then run the update helm upgrade -f values.yaml --install -n sonarqube sonarqube sonarqube/sonarqube
readinessProbe:
initialDelaySeconds: 300 # Increase initial delay
timeoutSeconds: 60
periodSeconds: 10
successThreshold: 1
failureThreshold: 3

livenessProbe:
initialDelaySeconds: 360 # Increase initial delay
timeoutSeconds: 60
periodSeconds: 10
successThreshold: 1
failureThreshold: 3

startupProbe:
initialDelaySeconds: 300 # Increase initial delay
timeoutSeconds: 60
periodSeconds: 10
successThreshold: 1
failureThreshold: 3

1 Like