SonarQube version 9.6 breaks due to incompatible changes about puppet-sonarqube HOT 7 CLOSED

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?

from puppet-sonarqube.

A new major release of this module is currently in the works:
https://github.com/markt-de/puppet-sonarqube/blob/master/CHANGELOG.md

Could you check if the improved PID file handling and the new $pidfile parameter solve this issue for you?

from puppet-sonarqube.

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 .

from puppet-sonarqube.

Hi @fraenki I was wondering how this release is going - I'd like to use your module to install 9.7. Thank you!

from puppet-sonarqube.

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.

from puppet-sonarqube.

Thanks for all of your work, I've been sticking with 9.5.0.56709 until your new version is ready.

from puppet-sonarqube.

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

I found out what is causing this issue. The startup script sonar.sh got a major overhaul in SonarQube 9.6:
SonarSource/sonarqube@2f1b46f

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.

from puppet-sonarqube.