Upgrade and SonarQube not listening on network -


upgraded 5.6 6.1. sonar.properties are, , match 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 , running it's not listening on port 9000. os centos 6.6, selinux disabled. can find no errors in logs, indeed sonar.log has no entries @ all. have 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 permissions problem on logs. there log tracing lead other, clear problems.


Comments

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -