Upgraded from 5.6 to 6.1. Sonar.properties are, and they match what was there before:
sonar.jdbc.username=sonar
sonar.jdbc.password=sonar
sonar.jdbc.url=jdbc:mysql://10.120.8.27:3306/sonar?useUnicode=true&characterEncoding=utf8&rewriteBatchedStatements=true&useConfigs=maxPerformance
sonar.web.javaOpts=-Xmx768m -XX:MaxPermSize=160m -XX:+HeapDumpOnOutOfMemoryError
sonar.web.host=10.120.8.27
sonar.web.context=/sonar
sonar.web.port=9000
SonarQube starts and is running but it's not listening on port 9000. OS is CentOS 6.6, SElinux disabled. I can find no errors in the logs, indeed sonar.log has no entries at all. What have I missed?
ps -ef|grep sonar
sonar 1325 1 0 12:06 ? 00:00:00
/opt/sonar/bin/linux-x86-64/./wrapper
/opt/sonar/bin/linux-x86-64/../../conf/wrapper.conf
wrapper.syslog.ident=SonarQube
wrapper.pidfile=/opt/sonar/bin/linux-x86-64/./SonarQube.pid
wrapper.daemonize=TRUE
sonar 1327 1325 2 12:06 ? 00:00:25 java
-Djava.awt.headless=true -Xms3m -Xmx3m -Djava.library.path=./lib -classpath
../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-6.1.jar
-Dwrapper.key=byv_fqDBq6Ok__mi -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.debug=TRUE -Dwrapper.pid=1325 -Dwrapper.version=3.2.3
-Dwrapper.native_library=wrapper -Dwrapper.service=TRUE
-Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimpleApp org.sonar.application.App
sonar 1545 1327 99 12:06 ? 00:24:20
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64/jre/bin/java
-Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonar/temp
-javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64/jre/lib/management-agent.jar
-cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer
/opt/sonar/temp/sq-process7944098912777335007properties
Was a permissions problem on the logs. From there log tracing lead to other, but clear problems.
Related
In our online cluster, we got lots of such warning:
2020-01-21 09:08:00,711 INFO org.apache.hadoop.util.JvmPauseMonitor: Detected pause in JVM or host machine (eg GC): pause of approximately 2328ms
No GCs detected
As it showed, there is no GC, but jvm just paused.
We noticed that the waring happens every 1 minute, and when such warning happens, cpu usage of cmf-agent increase to 80%. So we try shutdown cmf-agent, after cmf-agent is down, the waring just gone.
We have disabled Cloudera Manager jstack monitoring, what else cloudera managager agent do will cause jvm pause?
we are using CDH 5.4.14.
Edit at 2020-01-22:
/usr/java/default/bin/java -Dproc_namenode -Xmx1000m -Dhdfs.audit.logger=INFO,RFAAUDIT -Dsecurity.audit.logger=INFO,RFAS -Djava.net.preferIPv4Stack=true -Dhadoop.log.dir=/var/log/hadoop-hdfs -Dhadoop.log.file=hadoop-cmf-hdfs-NAMENODE-1350.log.out -Dhadoop.home.dir=/opt/cloudera/parcels/CDH-5.14.4-1.cdh5.14.4.p0.3/lib/hadoop -Dhadoop.id.str=hdfs -Dhadoop.root.logger=INFO,RFA -Djava.library.path=/opt/cloudera/parcels/GPLEXTRAS-5.14.4-1.cdh5.14.4.p0.3/lib/hadoop/lib/native:/opt/cloudera/parcels/CDH-5.14.4-1.cdh5.14.4.p0.3/lib/hadoop/lib/native -Dhadoop.policy.file=hadoop-policy.xml -Djava.net.preferIPv4Stack=true -Xms210453397504 -Xmx210453397504 -Xmn24g -XX:SurvivorRatio=2 -XX:+UseCompressedOops -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCMSCompactAtFullCollection -XX:CMSFullGCsBeforeCompaction=0 -XX:+CMSParallelRemarkEnabled -XX:+DisableExplicitGC -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70 -XX:SoftRefLRUPolicyMSPerMB=0 -verbose:GC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -XX:+PrintAdaptiveSizePolicy -XX:+PrintReferenceGC -XX:+UseGCLogFileRotation -XX:+PrintClassHistogramAfterFullGC -XX:+PrintClassHistogramBeforeFullGC -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=200M -Xloggc:/var/log/hadoop-hdfs/nn.gc.log -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh -Dhadoop.security.logger=INFO,RFAS org.apache.hadoop.hdfs.server.namenode.NameNode
I am working in SonarQube the process is fully running in command prompt but the web page is not displaying. I changed the address and port in the sonar properties but still the web page is not displaying.
If I load webpage it is showing as connection refused.
D:\>cd D:\Development_Avecto\Sonar\sonarqube-6.7\bin\windows-x86-64
D:\Development_Avecto\Sonar\sonarqube-6.7\bin\windows-x86-64>StartSonar.bat
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
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 | 2018.01.05 17:49:09 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory D:\Development_Avecto\Sonar\sonarqube-6.7\temp
jvm 1 | 2018.01.05 17:49:09 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1 | 2018.01.05 17:49:11 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [D:\Development_Avecto\Sonar\sonarqube-6.7\elasticsearch]: C:\Program Files\Java\jre1.8.0_121\bin\java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -Xms512m -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=D:\Development_Avecto\Sonar\sonarqube-6.7\elasticsearch -cp lib/* org.elasticsearch.bootstrap.Elasticsearch -Epath.conf=D:\Development_Avecto\Sonar\sonarqube-6.7\temp\conf\es
jvm 1 | 2018.01.05 17:49:11 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2018.01.05 17:49:13 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2018.01.05 17:49:13 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | 2018.01.05 17:49:23 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
jvm 1 | 2018.01.05 17:49:23 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [D:\Development_Avecto\Sonar\sonarqube-6.7]: C:\Program Files\Java\jre1.8.0_121\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=D:\Development_Avecto\Sonar\sonarqube-6.7\temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*;./lib/server/*;D:\Development_Avecto\Sonar\sonarqube-6.7\lib\jdbc\h2\h2-1.3.176.jar org.sonar.server.app.WebServer D:\Development_Avecto\Sonar\sonarqube-6.7\temp\sq-process1476121489817180909properties
jvm 1 | 2018.01.05 17:51:08 INFO app[][o.s.a.SchedulerImpl] Process[web] is up
jvm 1 | 2018.01.05 17:51:08 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='ce', ipcIndex=3, logFilenamePrefix=ce]] from [D:\Development_Avecto\Sonar\sonarqube-6.7]: C:\Program Files\Java\jre1.8.0_121\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=D:\Development_Avecto\Sonar\sonarqube-6.7\temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*;./lib/server/*;./lib/ce/*;D:\Development_Avecto\Sonar\sonarqube-6.7\lib\jdbc\h2\h2-1.3.176.jar org.sonar.ce.app.CeServer D:\Development_Avecto\Sonar\sonarqube-6.7\temp\sq-process446994653925487374properties
jvm 1 | 2018.01.05 17:51:13 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
jvm 1 | 2018.01.05 17:51:13 INFO app[][o.s.a.SchedulerImpl] SonarQube is up
After long search, below solution worked for me.
I have tried disabling proxy and hit the sonar server URL (http://127.0.0.50:9111/). It worked. Since I need proxy setup, i have added my ip and port in the exceptions of proxy.
Thanks everyone who extended help here. :)
Config file entry is
sonar.web.host=127.0.0.50
sonar.web.port=9111
cloned sonarjs plugin from github | sonarjs plugin
created jar file via, mvn install command
copied jar file into sonarqube-5.6.6/extensions/plugins/
Now, when trying to start sonar server, it stops with following message:
Running SonarQube...
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
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 | 2017.11.29 22:17:20 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /home/sd2labs/ mycomputer/sonarqube-5.6.6/temp
jvm 1 | 2017.11.29 22:17:20 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djava.net.preferIPv4Stack=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/home/sd2labs/mycomputer/sonarqube-5.6.6/temp -javaagent:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/management-agent.jar -cp ./lib/common/:./lib/search/ org.sonar.search.SearchServer /home/sd2labs/mycomputer/sonarqube-5.6.6/temp/ sq-process8688307264383931251properties
jvm 1 | 2017.11.29 22:17:28 INFO app[o.s.p.m.Monitor] Process[es] is up
jvm 1 | 2017.11.29 22:17:28 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.io.tmpdir=/home/sd2labs/mycomputer/sonarqube-5.6.6/temp -javaagent:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/management-agent.jar -cp ./lib/common/:./lib/server/:/home/sd2labs/mycomputer/sonarqube-5.6.6/lib/jdbc/mysql/mysql-connector-java-5.1.35.jar org.sonar.server.app.WebServer /home/sd2labs/mycomputer/sonarqube-5.6.6/temp/ sq-process1772881744825311451properties
jvm 1 | 2017.11.29 22:17:33 INFO app[o.s.p.m.Monitor] Process[es] is stopping
jvm 1 | 2017.11.29 22:17:34 INFO app[o.s.p.m.Monitor] Process[es] is stopped
wrapper | <-- Wrapper Stopped
What am I doing wrong?
Most probably you have 2 plugin version for SonarJS in your /extensions/plugins/. Remove the one, you don't need (the one provided by default)
I have installed Sonar qube 6.1. I have started sonar by executing sonar.sh start and checked status with sonar.sh status. After few seconds, sonar stopping itself by writing below statements in the wrapper.log file. Please help me on this issue to get resolve.
2017.05.04 07:01:13 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-6.1/temp
2017.05.04 07:01:13 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/java/jdk1.8.0_111/jre/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonarqube-6.1/temp -javaagent:/usr/java/jdk1.8.0_111/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /opt/sonarqube-6.1/temp/sq-process4451619261882420874properties
2017.05.04 07:01:23 INFO app[][o.s.p.m.Monitor] Process[es] is up
2017.05.04 07:01:23 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/java/jdk1.8.0_111/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonarqube-6.1/temp -javaagent:/usr/java/jdk1.8.0_111/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/opt/sonarqube-6.1/lib/jdbc/h2/h2-1.3.176.jar org.sonar.server.app.WebServer /opt/sonarqube-6.1/temp/sq-process3625744255132410453properties
2017.05.04 07:01:25 INFO app[][o.s.p.m.Monitor] Process[es] is stopping
2017.05.04 07:01:26 INFO app[][o.s.p.m.Monitor] Process[es] is stopped
es is ElasticSearch, a component that indexes your data to accelerate searching. Maybe your indexes are corrupted. You can rebuild them by removing contents of ${SONARQUBE_HOME}/data/es/ directory, and retry.
After rebooting our Sonar Server running an up-to-date Amazon Linux it would not start.
2017.01.27 10:36:42 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonar/temp
2017.01.27 10:36:42 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121 0.b13.29.amzn1.x86_64/jre/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonar/temp -javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.29.amzn1.x86_64/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /opt/sonar/temp/sq-process7514074371677370036properties
2017.01.27 10:36:51 INFO app[][o.s.p.m.Monitor] Process[es] is up
2017.01.27 10:36:51 INFO app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.29.amzn1.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/opt/sonar/temp -javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.29.amzn1.x86_64/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/opt/sonar/lib/jdbc/postgresql/postgresql-9.4.1209.jre7.jar org.sonar.server.app.WebServer /opt/sonar/temp/sq-process6553321235832962376properties
2017.01.27 10:36:54 INFO app[][o.s.p.m.Monitor] Process[es] is stopping
2017.01.27 10:36:54 ERROR app[][o.s.p.m.Monitor] Process[web] failed to start
2017.01.27 10:36:54 INFO app[][o.s.p.m.Monitor] Process[es] is stopped
<-- Wrapper Stopped
The above indicates you need to read /var/log/sonar/web.log
The postgres jar above /opt/sonar/lib/jdbc/postgresql/postgresql-9.4.1209.jre7.jar is a bad smell, so on a hunch I downloaded the latest version,
which fixed the problem.
I imagine this will be fixed by the Sonar team pretty soon but this posted here in the hope that it helps.