Início / computer / Perguntas / 1460823
Accepted
Amir Soleimani Borujerdi
Asked: 2019-07-18 03:36:08 +0800 CST

Serviço SonarQube

  • 772

Instalei o SonarQube no CentOS e o serviço Sonar está ativo e em execução. No arquivo de configuração, a porta de uso está definida como 9000. Mas a interface do usuário do Sonar não pode ser acessada em localhost:9000.

Este é o meu sonar.log:

2019.07.17 15:11:13 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2019.07.17 15:11:13 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.07.17 15:11:13 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch -Epath.conf=/opt/sonarqube/temp/conf/es
2019.07.17 15:11:13 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.07.17 15:11:13 INFO  app[][o.e.p.PluginsService] no modules loaded
2019.07.17 15:11:13 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.07.17 15:11:20 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2019.07.17 15:11:20 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*:/opt/sonarqube/lib/jdbc/postgresql/postgresql-42.2.5.jar org.sonar.server.app.WebServer /opt/sonarqube/temp/sq-process5654348533781620634properties
2019.07.17 15:11:29 INFO  app[][o.s.a.SchedulerImpl] Process[web] is up
2019.07.17 15:11:29 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='ce', ipcIndex=3, logFilenamePrefix=ce]] from [/opt/sonarqube]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*:/opt/sonarqube/lib/jdbc/postgresql/postgresql-42.2.5.jar org.sonar.ce.app.CeServer /opt/sonarqube/temp/sq-process1052960785390598020properties
2019.07.17 15:11:33 INFO  app[][o.s.a.SchedulerImpl] Process[ce] is up
2019.07.17 15:11:33 INFO  app[][o.s.a.SchedulerImpl] SonarQube is up
centos-7 services

1 respostas

  1. Best Answer

    Pela documentação

    Iniciando o Servidor Web

    A porta padrão é "9000" e o caminho de contexto é "/". Esses valores podem ser alterados em $SONARQUBE-HOME/conf/sonar.properties:

    sonar.web.host=192.0.0.1

    sonar.web.port=80

    sonar.web.context=/sonarqube

    Além disso, certifique-se de reiniciar o serviço após fazer qualquer alteração na configuração.

    • 0

relate perguntas