Package Details: sonarqube 7.2.1-1

Git Clone URL: https://aur.archlinux.org/sonarqube.git (read-only)
Package Base: sonarqube
Description: An open source platform for continuous inspection of code quality
Upstream URL: http://www.sonarqube.org/
Licenses: LGPL3
Conflicts: sonarqube-lts
Provides: sonarqube
Submitter: gizyou
Maintainer: dNhax
Last Packager: dNhax
Votes: 17
Popularity: 1.798504
First Submitted: 2015-11-08 17:36
Last Updated: 2018-06-30 09:32

Latest Comments

MoroS commented on 2018-07-10 18:36

@attila123: Just to supplement dNhax's answer, you got the "Permission denied", because SonerQube operates on a system service level and assumes, that it has that very level of file system access. That being said, you can easily run it like you mentioned as root (although you should use "systemctl start sonarqube" to be on the safe side and let SystemD manage it as a service).

dNhax commented on 2018-07-10 17:25

@attila123: After package installation, start or enable sonarqube.service with systemd.

attila123 commented on 2018-07-10 15:08

What is the easiest way to get it running (locally, kind of just to try out)? According to https://docs.sonarqube.org/display/SONAR/Get+Started+in+Two+Minutes I tried to run it as normal user (/usr/share/sonarqube/bin/linux-x86-64/sonar.sh console), and got some permission problems (not sure what it was, maybe some log file). I tried it running as root, but then got jvm 1 | 2018.07.10 16:50:11 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1 and /var/log/sonarqube/es.log contains the problem: java.lang.RuntimeException: can not run elasticsearch as root

I run it again as normal user to note down the permission problems:

$ /usr/share/sonarqube/bin/linux-x86-64/sonar.sh console
Running SonarQube...
wrapper  | ERROR: Could not write pid file /usr/share/sonarqube/bin/linux-x86-64/./SonarQube.pid: Permission denied
Unable to open logfile ../../logs/sonar.log: Permission denied

I ended up brute force fixing the permission problems:

sudo chown -R $USER:mygroup /usr/share/sonarqube
sudo chown -R $USER:mygroup /var/log/sonarqube

Not it works, but I am not sure how is it supposed to work.

dNhax commented on 2018-07-03 16:17

Those warnings are harmless and can be ignored.

MoroS commented on 2018-07-02 17:39

@dNhax: upgraded. Works like a charm. :)

Just one question about this:

warning: could not get file information for usr/share/sonarqube/extensions/plugins/sonar-python-plugin-1.10.0.2131.jar
warning: could not get file information for usr/share/sonarqube/temp/README.txt

It doesn't do anything harmful (in my case at least). I was just wondering if this is related to the "Non-default plugins have been deleted." message seen a bit later? As in part of the cleaning up process?

dNhax commented on 2018-06-28 06:00

@MoroS: Yes, this is the same issue I stumbled upon.

I will upgrade the package after work and streamline the package upgrade process to follow the SonarQube upgrade instructions more closely (https://docs.sonarqube.org/display/SONAR/Upgrading).

MoroS commented on 2018-06-27 10:57

Ok, found another issue.

The /usr/share/sonarqube/extensions/plugins has "duplicates" of the following plugins ("duplicates", because they're different versions):

  • sonar-csharp-plugin-7.0.1.4822.jar
  • sonar-csharp-plugin-7.2.0.5463.jar
  • sonar-java-plugin-5.2.0.13398.jar
  • sonar-java-plugin-5.4.0.14284.jar
  • sonar-python-plugin-1.10.0.2131.jar
  • sonar-python-plugin-1.9.1.2080.jar
  • sonar-scm-git-plugin-1.4.0.1037.jar
  • sonar-scm-git-plugin-1.4.1.1128.jar
  • sonar-typescript-plugin-1.6.0.2388.jar
  • sonar-typescript-plugin-1.7.0.2893.jar
  • sonar-xml-plugin-1.5.0.1373.jar
  • sonar-xml-plugin-1.5.1.1452.jar

From what I see here is that probably some of them were installed via AUR (owner: root) and some by sonar itself (owner: sonarqube). The ones installed by SonarQube are the older ones, so is anyone has an issue with Sonar not starting, check this dir first.

MoroS commented on 2018-06-27 10:48

@dNhax: Got the same, but nothing a little "--overwrite use/share/*" could not handle. ;)

What I've got now is that I'm trying to start the service and it shuts down after a few seconds. From the logs I found that there's a DB upgrade needed (running the embedded one, don't need anything more). Does anyone have a good way of doing this quickly? The SystemD service just shuts down after a few seconds, so no luck in navigating to the "/setup" URL.

dNhax commented on 2018-06-18 17:01

I updated the package to version 7.2.

! This update may require manual intervention !

After an update from 7.1 to 7.2, libraries in extensions/plugins were duplicated and had to be removed manually. Since I could not replicate this issue on other machines I hesitated to work around this issue.

Please provide feedback if you experience something similar.

rutorai.pf commented on 2018-02-18 10:06

@dNhax: Wonderful, it's already done and it's works. Thank you. +1 vote :-)

All comments