HI Ann
We have recently changed the version of the Sonarqube
we have upgraded from the community edition docker container to development as we have purchased it . We have used till 20 Jan 2022 version sonarqube:9.0.1-community upgrade was made to version sonarqube:9.2.4-community on that date . On 22 Jan 2022 we have upgraded to sonarqube:9.2.4-developer. Our last upgrade was done on 22 Feb 2022 to sonarqube:9.3.0-developer . After each upgrade we have run the recommended setup of the Sonarqube and yesterday we also did the
Additional database maintenance
We recommend refreshing your database’s statistics and rebuilding your database’s indices once you’ve finished the technical upgrade, but before you reanalyze your projects.
For PostgreSQL, that means executing VACUUM FULL . According to the PostgreSQL documentation:
They are no additional plugins installed
We still have the same error
**09:52:41** [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project poject-domain-model: Unable to load component class org.sonar.scanner.report.ActiveRulesPublisher: Unable to load component class org.sonar.api.batch.rule.internal.DefaultActiveRules: NullPointerException -> [Help 1]
We also notice this error the access log
10.2.4.25 - - [23/Feb/2022:09:52:40 +0000] "GET /api/project_branches/list?project=our.java.project-domain-model HTTP/1.1" 200 322 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw4"
10.2.4.25 - - [23/Feb/2022:09:52:40 +0000] "GET /api/project_pull_requests/list?project=our.java.project-domain-model HTTP/1.1" 200 341 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw5"
10.2.4.25 - - [23/Feb/2022:09:52:40 +0000] "GET /api/qualityprofiles/search.protobuf?project=our.java.project-domain-model HTTP/1.1" 200 2973 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw6"
10.2.4.25 - - [23/Feb/2022:09:52:40 +0000] "GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXoaQG1x52atAaxkctsL&ps=500&p=1 HTTP/1.1" 200 6579 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw7"
10.2.4.25 - - [23/Feb/2022:09:52:41 +0000] "GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXoaQG4p52atAaxkctto&ps=500&p=1 HTTP/1.1" 200 7859 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw8"
10.2.4.25 - - [23/Feb/2022:09:52:41 +0000] "GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXoaQG6y52atAaxkctuI&ps=500&p=1 HTTP/1.1" 200 11 "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw9"
10.2.4.25 - - [23/Feb/2022:09:52:41 +0000] "GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXoaQHDU52atAaxkct2Q&ps=500&p=1 HTTP/1.1" 200 - "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw+"
10.2.4.25 - - [23/Feb/2022:09:52:41 +0000] "GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXoaQHK352atAaxkct9N&ps=500&p=1 HTTP/1.1" 200 - "-" "ScannerMaven/3.9.1.2184/3.6.0" "AX8hItr661pKsMi0AAw/"
I have sanitised some of the data for security reasons .
Ragading the current errors . We see errors in the Jenkins that can’t finish the scan with the error I show you because of the module but I don’t see any error in our Sonarqube logs. We have at the moment the container logs pushing to CloudWatch. Is there any way to have a better trace on the container .