2017-12-14 8 views
0

Sonarqube가 aws에서 시작하지 않습니다. 나는 Sonar에 원격 PostgreSQL 데이터베이스를 사용하고 있지만 sonar는 동일한 구성을 사용하는 Windows 컴퓨터에서 로컬로 시작할 때 잘 작동합니다. sonarqube 6.7을 사용하고 있지만 6.6과 함께 시도했습니다. 같은 오류가 발생합니다. 나는 wrapper.conf에서 디버깅 할 로깅 수준을 변경하고이 내가 AWS에있어 출력 :Sonarqube 6.7 JVM에서 ping 응답을 받고 AWS에서 갑자기 멈추다

  Running SonarQube... 
      wrapper | --> Wrapper Started as Console 
      wrapper | Using tick timer. 
      wrapperp | server listening on port 32000. 
      wrapper | Command[0] : java 
      wrapper | Command[1] : -Dsonar.wrapped=true 
      wrapper | Command[2] : -Djava.awt.headless=true 
      wrapper | Command[3] : -Xms8m 
      wrapper | Command[4] : -Xmx32m 
      wrapper | Command[5] : -Djava.library.path=./lib 
      wrapper | Command[6] : -classpath 
      wrapper | Command[7] : ../ 
      wrapper | Command[8] : -Dwrapper.key=4VXP1SaL6A6VQM7x 
      wrapper | Command[9] : -Dwrapper.port=32000 
      wrapper | Command[10] : -Dwrapper.jvm.port.min=31000 
      wrapper | Command[11] : -Dwrapper.jvm.port.max=31999 
      wrapper | Command[12] : -Dwrapper.debug=TRUE 
      wrapper | Command[13] : -Dwrapper.pid=6447 
      wrapper | Command[14] : -Dwrapper.version=3.2.3 
      wrapper | Command[15] : -Dwrapper.native_library=wrapper 
      wrapper | Command[16] : -Dwrapper.cpu.timeout=10 
      wrapper | Command[17] : -Dwrapper.jvmid=1 
      wrapper | Command[18] : org.tanukisoftware.wrapper.WrapperSimpleApp 
      wrapper | Command[19] : org.sonar.application.App 
      wrapper | Launching a JVM... 
      jvm 1 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassL[email protected] 
      jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 
      jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 
      jvm 1 | 
      jvm 1 | Wrapper Manager: JVM #1 
      jvm 1 | Running a 64-bit JVM. 
      jvm 1 | Wrapper Manager: Registering shutdown hook 
      jvm 1 | Wrapper Manager: Using wrapper 
      jvm 1 | Load native library. One or more attempts may fail if platform specific libraries do not exist. 
      jvm 1 | Loading native library failed: libwrapper-linux-x86-64.so Cause: java.lang.UnsatisfiedLinkError: no wrapper-linux-x86-64 in java.library.path 
      jvm 1 | Loaded native library: libwrapper.so 
      jvm 1 | Calling native initialization method. 
      jvm 1 | Inside native WrapperManager initialization method 
      jvm 1 | Java Version : 1.8.0_151-b12 OpenJDK 64-Bit Server VM 
      jvm 1 | Java VM Vendor : Oracle Corporation 
      jvm 1 | 
      jvm 1 | Control event monitor thread started. 
      jvm 1 | WrapperManager.start([email protected], args[]) called by thread: main 
      jvm 1 | Startup runner thread started. 
      jvm 1 | Communications runner thread started. 
      jvm 1 | Open socket to wrapper...Wrapper-Connection 
      jvm 1 | Opened Socket from 31000 to 32000 
      jvm 1 | Send a packet KEY : 4VXP1SaL6A6VQM7x 
      jvm 1 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) 
      wrapperp | accepted a socket from 127.0.0.1 on port 31000 
      wrapperp | read a packet KEY : 4VXP1SaL6A6VQM7x 
      wrapper | Got key from JVM: 4VXP1SaL6A6VQM7x 
      wrapperp | send a packet LOW_LOG_LEVEL : 1 
      wrapperp | send a packet PING_TIMEOUT : 0 
      wrapperp | send a packet PROPERTIES : (Property Values) 
      wrapper | Start Application. 
      wrapperp | send a packet START : start 
      jvm 1 | Received a packet LOW_LOG_LEVEL : 1 
      jvm 1 | Wrapper Manager: LowLogLevel from Wrapper is 1 
      jvm 1 | Received a packet PING_TIMEOUT : 0 
      jvm 1 | PingTimeout from Wrapper is 0 
      jvm 1 | Received a packet PROPERTIES : (Property Values) 
      jvm 1 | Received a packet START : start 
      jvm 1 | calling WrapperListener.start() 
      jvm 1 | Waiting for WrapperListener.start runner thread to complete. 
      jvm 1 | WrapperListener.start runner thread started. 
      jvm 1 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. 
      jvm 1 | WrapperSimpleApp: invoking main method 
      jvm 1 | 2017.12.14 03:33:20 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /home/jisys/system/sonarqube-6.7/temp 
      jvm 1 | 2017.12.14 03:33:20 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001 
      jvm 1 | 2017.12.14 03:33:20 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/sonarqube-6.7/elasticsearch]: /sonarqube-6.7/elasticsearch/bin/elasticsearch -Epath.conf=/sonarqube-6.7/temp/conf/es 
      jvm 1 | 2017.12.14 03:33:20 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running 
      jvm 1 | Send a packet START_PENDING : 5000 
      wrapperp | read a packet START_PENDING : 5000 
      wrapper | JVM signalled a start pending with waitHint of 5000 millis. 
      jvm 1 | 2017.12.14 03:33:21 INFO app[][o.e.p.PluginsService] no modules loaded 
      jvm 1 | 2017.12.14 03:33:21 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin] 
      jvm 1 | Send a packet START_PENDING : 5000 
      jvm 1 | WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null 
      jvm 1 | WrapperListener.start runner thread stopped. 
      jvm 1 | returned from WrapperListener.start() 
      jvm 1 | Send a packet STARTED : 
      jvm 1 | Startup runner thread stopped. 
      wrapperp | read a packet START_PENDING : 5000 
      wrapper | JVM signalled a start pending with waitHint of 5000 millis. 
      wrapperp | read a packet STARTED : 
      wrapper | JVM signalled that it was started. 
      wrapperp | send a packet PING : ping 
      jvm 1 | Received a packet PING : ping 
      jvm 1 | Send a packet PING : ok 
      wrapperp | read a packet PING : ok 
      wrapper | Got ping response from JVM 
      jvm 1 | 2017.12.14 03:33:24 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1 
      jvm 1 | 2017.12.14 03:33:24 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped 
      jvm 1 | 2017.12.14 03:33:24 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped 
      jvm 1 | Wrapper Manager: ShutdownHook started 
      jvm 1 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook 
      jvm 1 | Send a packet STOP : 0 
      wrapperp | read a packet STOP : 0 
      wrapper | JVM requested a shutdown. (0) 
      wrapper | wrapperStopProcess(0) called. 
      wrapper | Sending stop signal to JVM 
      wrapperp | send a packet STOP : NULL 
      jvm 1 | Received a packet STOP : 
      jvm 1 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process. 
      jvm 1 | calling listener.stop() 
      jvm 1 | WrapperSimpleApp: stop(0) 
      jvm 1 | returned from listener.stop() -> 0 
      jvm 1 | shutdownJVM(0) Thread:Wrapper-Shutdown-Hook 
      jvm 1 | Send a packet STOPPED : 0 
      wrapperp | read a packet STOPPED : 0 
      wrapper | JVM signalled that it was stopped. 
      jvm 1 | Closing socket. 
      wrapperp | socket read no code (closed?). 
      wrapperp | server listening on port 32001. 
      jvm 1 | Wrapper Manager: ShutdownHook complete 
      jvm 1 | Server daemon shut down 
      wrapper | JVM exited normally. 
      wrapper | Signal trapped. Details: 
      wrapper | signal number=17 (SIGCHLD), source="unknown" 
      wrapper | Received SIGCHLD, checking JVM process status. 
      wrapper | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. 
      wrapper | <-- Wrapper Stopped 

답변

0

이것은 당신의 ElasticSearch 프로세스가 제대로 시작되지 않았 음을 나타냅니다.

a 확인할 사항 : a. es.log에 오류가 있는지 확인하십시오.

b. 구성에서 sonar.search.port를 확인하십시오. 설정 한 내용은 무엇입니까? 그 항구는 무료입니까?

+0

나는 es.log 파일에서 문제를 발견 elasticsearch 실행할 수 없습니다. java.lang.RuntimeException : elasticsearch를 루트로 실행할 수 없습니다. 다른 사용자로 sonarqube를 실행했는데 성공적으로 실행되었습니다. – Abhijay

0

es.log 파일에서 문제가 발견되었습니다. Elasticsearch가 루트 사용자로 실행되지 않았습니다. 다른 사용자로 sonarqube를 실행했고 성공적으로 실행했습니다.

은 내가 es.log 파일

java.lang.RuntimeException가에서이있어 : 루트