-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SonarQube version 9.6 breaks due to incompatible changes #24
Comments
Same issue here on CentOS 7 with Puppet6. Removing the PID line in /etc/systemd/system/sonar.service and disabling puppet solves it for now to get SonarQube running, however we need to do this manually after a Puppet Run to ensure it is running. Any solution yet? |
A new major release of this module is currently in the works: Could you check if the improved PID file handling and the new |
Setting pidfile => "../sonar-install/sonarqube-${version}/bin/linux-x86-64/SonarQube.pid" fixes it for us with 5.0.0 due to sonar_home being /opt/sonar/data and the only .pid I could trace is on the location /opt/sonar-install/sonarqube-${version}/bin/linux-x86-64/SonarQube.pid . |
Hi @fraenki I was wondering how this release is going - I'd like to use your module to install 9.7. Thank you! |
I'm currently pretty busy. Could you try the latest commit from the master branch? AFAICT it should work. The next major release should be out in december. |
Thanks for all of your work, I've been sticking with 9.5.0.56709 until your new version is ready. |
I found out what is causing this issue. The startup script As a result, the PID file setting was no longer working. This is finally fixed in version 5.1 of this module. SonarQube 9.8 successfully passed the acceptance tests. |
SonarQube version 9.4 and 9.5 work without any issues. Upgrading to 9.6.1.59531 causes the following error:
sonar.service: Can't open PID file /opt/sonar/data/SonarQube.pid (yet?) after start: Operation not permitted
If I manually change the permissions of the file system, I get the following error in the logs
The database must be manually upgraded. Please backup the database and browse /setup
But the web server never loads and /setup cannot be run.
Any ideas what the cause might be? Something different in 9.6?
The text was updated successfully, but these errors were encountered: