ERROR: Quality Gate check timeout exceeded - View details on

We are using SonarQube Community Edition Version 9.9 (build 65466)

  • how is SonarQube deployed: Helm
  • We have deployed the SonarQube on Azure Kubernetes Service using helm chart by following this
  • We have made changes in values.yaml as per our requirement and deployed using Azure DevOps pipelines.

Issue–>

  • Till last Friday the SonarQube is working perfectly, but now we are facing issue with Scan Analysis.
    The issue is not permanent but it is failing with “ERROR: Quality Gate check timeout exceeded - View details on”.

What have you tried so far →

We have tried setting parameters: sonar.qualitygate.wait=true and sonar.qualitygate.timeout=600 ( we even tried keeping a larger timeout 2000s as well) but this didn’t solve the error.

Summary

2024-05-14T09:18:41.0742177Z 09:18:40.587 INFO: ------------- Check Quality Gate status
2024-05-14T09:18:41.0742482Z 09:18:40.587 INFO: Waiting for the analysis report to be processed (max 300s)
https://europe.sonarqube.ingapps.net/api/ce/task?id=AY92ZZeeROSsJEtvG32V | time=42ms
2024-05-14T09:23:33.1714246Z 09:23:33.170 DEBUG: GET 200 https://europe.sonarqube.ingapps.net/api/ce/task?id=AY92ZZeeROSsJEtvG32V | time=38ms
2024-05-14T09:23:38.2111226Z 09:23:38.210 DEBUG: GET 200 https://europe.sonarqube.ingapps.net/api/ce/task?id=AY92ZZeeROSsJEtvG32V | time=39ms
2024-05-14T09:23:43.2193899Z 09:23:43.218 INFO: ------------------------------------------------------------------------
2024-05-14T09:23:43.2202069Z 09:23:43.219 INFO: EXECUTION FAILURE
2024-05-14T09:23:43.2202890Z 09:23:43.219 INFO: ------------------------------------------------------------------------
2024-05-14T09:23:43.2270947Z 09:23:43.220 INFO: Total time: 5:22.528s
2024-05-14T09:23:43.3113787Z 09:23:43.310 INFO: Final Memory: 23M/80M
2024-05-14T09:23:43.3115283Z 09:23:43.311 INFO: ------------------------------------------------------------------------
2024-05-14T09:23:43.3167678Z ##[error]09:23:43.312 ERROR: Error during SonarScanner execution
09:23:43.312 ERROR: Quality Gate check timeout exceeded - View details on SonarQube
2024-05-14T09:23:43.3175314Z 09:23:43.312 ERROR: Error during SonarScanner execution
2024-05-14T09:23:43.3175939Z 09:23:43.312 ERROR: Quality Gate check timeout exceeded - View details on SonarQube
2024-05-14T09:23:43.3176820Z ##[error]09:23:43.312 ERROR:
09:23:43.312 ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.
2024-05-14T09:23:43.3177288Z 09:23:43.312 ERROR:
2024-05-14T09:23:43.3177622Z 09:23:43.312 ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.
2024-05-14T09:23:43.6477087Z ##[error]The process ‘/home/vsts/work/_tasks/SonarQubeAnalyze_6d01813a-9589-4b15-8491-8164aeb38055/5.20.0/sonar-scanner/bin/sonar-scanner’ failed with exit code 2
2024-05-14T09:23:43.6527457Z ##[section]Finishing: SonarQubeAnalyze

Please let me know if you need any more details.

Thanks,
Abhilash

Hi All,

Any update on this? Can someone check.

Thanks,
Abhilash

Hi,

Welcome to the community!

I suggest checking the project’s Background Tasks page to see how long it took to process the report. If it was longer than 5min, then you probably need to grant more resources to your server.

 
Ann

Hi Ann,

Thanks for your response.

We have deleted all the entries from DB as well for Pending and In_Progress tasks. Still for new run it was going in Pending.

We have same infra configuration setup for another SonarQube portal, where it was working fine. Even we tried with simple Hello World java code but still the same issue.

Also, we have checked the CPU and Memory utilization is also very minimum. Please see attached screenshots from Sonarqube pod from last 7days.

Below is the resources allocated from values.yaml

Hi,

You do realize you’ve thrown away analyses, right?

You need to figure out why the task being processed is taking so long. I’d start by checking the server logs.

 
Ann

Hi,

As I stated we are running Sonarqube on Azure Kubernetes Service(AKS) as Pod. So if you can provide the commands or any troubleshooting steps with AKS then we will check.

Hi,

As I stated, you need to understand why server-side processing of the analysis report is taking so long. I would start by looking at your server logs, specifically ce.log.

 
Ann

Below are the ce.logs

Summary
2024.05.10 18:32:45 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@4117e84b (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 19:54:01 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@7acba064 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 19:54:44 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@695a1cb5 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 20:48:46 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@299a4748 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 21:58:55 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@17ff7435 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 22:52:39 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@146f7062 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 22:53:10 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@791833d2 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 22:54:23 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@53416769 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024.05.10 22:54:50 WARN  ce[][c.z.h.pool.PoolBase] HikariPool-1 - Failed to validate connection org.postgresql.jdbc.PgConnection@6bc9945c (This connection has been closed.). Possibly consider using a shorter maxLifetime value.

Hi,

The docs may help.

 
Ann

Hi Ann,

Thanks for your help.
The issue has been fixed after restarting the DB service. Now every analysis task is being processed.

Thanks,
Abhilash

1 Like

Hi Ann,

Thanks for your help.
The issue has been fixed after restarting the DB service. Now every analysis task is being processed.

Thanks,
Abhilash