sonarqube-ops

Would someone be able to assist on the error below? It is occurring on the start up of SonarQube 5.6 running on Java 8u71 and an Oracle database. This instance was just update from 5.2. I had the Puppet addon and uninstalled it as an attempt to solve the error. I confirm Elasticsearch is on port 9001 after startup. 2016.06.13 00:16:04 ERROR web[o.s.s.es.BulkIndexer] Fail to execute bulk index request: Bulk[671 index request(s) on index rules and type activeRule] org.elasticsearch.transport.RemoteTransportException: [sonar-1465791343547][inet[/127.0.0.1:9001]][indices:data/write/bulk] Caused by

Getting elasticsearch "can not run as root" error after upgrading from SonarQube 6.5 to 6.6. Nothing else changed. CentOS release 6.8 (Final) Java(TM) SE Runtime Environment (build 1.8.0_101-b13) java.lang.RuntimeException: can not run elasticsearch as root at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:106) ~[elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:195) ~[elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:342) [elasticsearch-5.6.2.jar:5.6.2] at org.elasticsearch.bootstrap

Trying to setup SonarQube on EC2 using what should be basic install settings. List item Setup a standard EC2 AWS LINUX Ami attached to M4 large SSH into EC2 instance Install JAVA Set to use JAVA8 wget https://sonarsource.bintray.com/Distribution/sonarqube/sonarqube-6.4.zip unzip into the /etc dir run sudo ./sonar.sh start Instance starts But when I try to go to the app it never comes up when I try either the IPv4 Public IP 187.187.87.87:9000 (ex not real IP) or try ec2-134-73-134-114.compute-1.amazonaws.com:9000 (not real IP either just for example) Perhaps it is my ignorance or me not

I'm trying to do Sonar Setup with Jacoco for Kotlin to generate Code Coverage report but it's not showing any code coverage. While checking Sonar Console it showing following error. Anyone has faced this issue before, any suggestion what could be miss. Meta info plugin using sonarqube version "2.6.1" gradleVersion = '3.0.1' kotlinVersion = '1.2.21' Sonarqube version = Version 6.7.1 (build 35068) - LGPL v3 Frustrating part is, my setup project generating blank code coverage report :(. PFA. Edit : Please find project structure snap. I'm adding sonar & Jacoco gradle file setup I'm using to

I am testing an upgrade to sonarqube 5.6 and have installed the ldap 2.0 plugin & copied the relevant configuration forward to my test 5.6 setup. The relevant config is sonar.security.realm=LDAP ldap.url=ldaps://xxxx:636 ldap.bindDn=uid=xxxx,ou=xxxx,dc=xxxx,dc=xxxx ldap.bindPassword=xxxx ldap.user.baseDn=dc=xxxx,dc=com ldap.user.request=(&(objectClass=person)(mail={login})) ldap.user.realNameAttribute=cn ldap.user.emailAttribute=mail I have the following set in conf/sonar.properties sonar.log.level=DEBUG On startup I see 2016.07.26 23:57:29 INFO web[o.s.p.l.LdapContextFactory] Test LDAP

Sonarqube official docker image, is not persisting any configuration changes like: creating users, changing root password or even installing new plugins . Once the container is restarted, all the configuration changes disappear and the installed plugins are lost. Even the projects' keys and their previous QA analytics data is unavailable after a restart. How can we persist the data when using Sonarqube's official docker image? Sonarqube image comes with a temporary h2 database engine which is not recommended for production and doesn't persist across container restarts. We need to setup a