I am not able to run nifi in window server 2016 even though I change to java 8
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
C:\Users\HelloWorld\Desktop\nifi-1.16.1-bin\nifi-1.16.1\bin>run-nifi.bat
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi...
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Command: C:\Program Files\Java\jdk1.8.0_202\bin\java.exe -classpath C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\conf;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\logback-classic-1.2.11.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\logback-core-1.2.11.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-api-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-nar-utils-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-properties-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-property-utils-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-runtime-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-stateless-api-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-stateless-bootstrap-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\slf4j-api-1.7.36.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Dcurator-log-only-first-connection-issue-as-error-level=true -Djavax.security.auth.useSubjectCredsOnly=true -Djava.security.egd=file:/dev/urandom -Dzookeeper.admin.enableServer=false -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.properties.file.path=C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\conf\nifi.properties -Dnifi.bootstrap.listen.port=54233 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\\logs org.apache.nifi.NiFi
2022-05-11 23:20:59,078 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read pid file C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\run\nifi.pid; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-05-11 23:20:59,078 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read status file C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\run\nifi.status; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-05-11 23:20:59,078 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 964
Related
I am getting below error while starting sonarqube
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2020.01.03 10:31:26 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory
/sonarqube/sonarqube-7.9.1/temp
2020.01.03 10:31:26 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2020.01.03 10:31:26 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1,
logFilenamePrefix=es]] from [/sonarqube/sonarqube
-7.9.1/elasticsearch]: /sonarqube/sonarqube-7.9.1/elasticsearch/bin/elasticsearch
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on2020.01.03 10:31:26 INFO app[]
Waiting for Elasticsearch to be up and running
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will l
likely be removed in a future release.
Unrecognized VM option 'UseParNewGC'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
2020.01.03 10:31:26 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]:
2020.01.03 10:31:26 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2020.01.03 10:31:26 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
FATAL StatusLogger Interrupted before Log4j Providers could be loaded.
java.lang.InterruptedExceptionjava.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1261)
at java.base/java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:317)
at org.apache.logging.log4j.util.ProviderUtil.lazyInit(ProviderUtil.java:121)
at org.apache.logging.log4j.util.ProviderUtil.hasProviders(ProviderUtil.java:108)
at org.apache.logging.log4j.LogManager.<clinit>(LogManager.java:89)
at org.elasticsearch.common.unit.ByteSizeValue.<clinit>(ByteSizeValue.java:39)
at org.elasticsearch.common.network.NetworkService.<clinit>(NetworkService.java:57)
at org.elasticsearch.transport.TransportSettings.<clinit>(TransportSettings.java:74)
at org.elasticsearch.client.transport.TransportClient.newPluginService(TransportClient.java:105)
at org.elasticsearch.client.transport.TransportClient.buildTemplate(TransportClient.java:135)
at org.elasticsearch.client.transport.TransportClient.<init>(TransportClient.java:277)
at org.sonar.application.es.EsConnectorImpl$MinimalTransportClient.<init>
(EsConnectorImpl.java:103)
at org.sonar.application.es.EsConnectorImpl.buildTransportClient(EsConnectorImpl.java:89)
at org.sonar.application.es.EsConnectorImpl.getTransportClient(EsConnectorImpl.java:74)
at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:61)
at org.sonar.application.process.EsManagedProcess.checkStatus(EsManagedProcess.java:88)
at org.sonar.application.process.EsManagedProcess.checkOperational(EsManagedProcess.java:73)
at org.sonar.application.process.EsManagedProcess.isOperational(EsManagedProcess.java:58)
org.sonar.application.process.ManagedProcessHandler.refreshState(ManagedProcessHandler.java:201)
org.sonar.application.process.ManagedProcessHandler$EventWatcher.run(ManagedProcessHandler.java:258)
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the
classpath. Using SimpleLogger to log to the consol
e...
<-- Wrapper Stopped
Java -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on
openjdk version "11.0.5" 2019-10-15 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.5+10-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode, sharing)
Need help to resolve this issue
The error that's causing Sonarqube to exit is Unrecognized VM option 'UseParNewGC'. This indicates you have a JAVA_OPTIONS (or command-line parameter) - set to +XX:UseParNewGC. As UseParNewGC was dropped in Java 10, this option can be safely removed.
I am getting below error in sonar.log. I have installed Sonarqube 7.1 version in AWS Other Linux OS. Java -version is openjdk version "1.8.0_201". And nginx.repo configuration is:-
[nginx]
name=nginx repo
baseurl=http://nginx.org/packages/rhel/7/x86_64/
gpgcheck=0
enabled=1
Error logs:- sonar.log
--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2019.09.27 13:13:26 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/efs/sonar/temp
2019.09.27 13:13:26 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.09.27 13:13:26 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/efs/sonar/elasticsearch]: /opt/efs/sonar/elasticsearch/bin/elasticsearch -Epath.conf=/opt/efs/sonar/temp/conf/es
2019.09.27 13:13:26 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.09.27 13:13:27 INFO app[][o.e.p.PluginsService] no modules loaded
2019.09.27 13:13:27 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.09.27 13:13:52 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2019.09.27 13:13:52 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/efs/sonar]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-0.amzn2.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/efs/sonar/temp -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*:/opt/efs/sonar/lib/jdbc/mysql/mysql-connector-java-5.1.42.jar org.sonar.server.app.WebServer /opt/efs/sonar/temp/sq-process3612618067556786670properties
Fri Sep 27 13:13:55 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Fri Sep 27 13:13:56 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
2019.09.27 13:13:59 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
2019.09.27 13:13:59 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
2019.09.27 13:13:59 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
2019.09.27 13:13:59 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped
Adding wrapper.conf
wrapper.java.command=java
wrapper.java.additional.1=-Dsonar.wrapped=true
wrapper.java.additional.2=-Djava.awt.headless=true
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=../../lib/jsw/*.jar
wrapper.java.classpath.2=../../lib/common/*.jar
wrapper.java.classpath.3=../../lib/*.jar
wrapper.java.library.path.1=./lib
wrapper.app.parameter.1=org.sonar.application.App
wrapper.java.initmemory=8
wrapper.java.maxmemory=32
wrapper.console.format=PM
wrapper.console.loglevel=INFO
wrapper.logfile=../../logs/sonar.log
wrapper.logfile.format=M
wrapper.logfile.loglevel=INFO
wrapper.syslog.loglevel=NONE
wrapper.console.title=SonarQube
wrapper.single_invocation=true
wrapper.ntservice.name=SonarQube
wrapper.ntservice.displayname=SonarQube
wrapper.ntservice.description=SonarQube
wrapper.ntservice.dependency.1=
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.disable_restarts=TRUE
wrapper.ping.timeout=0
wrapper.shutdown.timeout=300
wrapper.jvm_exit.timeout=300
List of plugins installed until now under /opt/efs/sonar/extension/plugins folder:-
sonar-apigee-plugin-2.0.0.jar
sonar-auth-bitbucket-plugin-1.0.jar
sonar-csharp-plugin-7.0.1.4822.jar
sonar-flex-plugin-2.4.0.1222.jar
sonar-java-plugin-5.2.0.13398.jar
sonar-javascript-plugin-4.1.0.6085.jar
sonar-php-plugin-2.13.0.3107.jar
sonar-python-plugin-1.9.1.2080.jar
sonar-scm-git-plugin-1.4.0.1037.jar
sonar-scm-svn-plugin-1.7.0.1017.jar
sonar-typescript-plugin-1.6.0.2388.jar
sonar-xml-plugin-2.0.1.2020.jar
After giving 644 permission to *.jar plugin it started working
Based on all the examples I've read I thought setting up NiFi as a cluster would be easy. Apparently I can't get it to work. I'm using NiFi 1.5. I only have 2 host and pretended that there was a third, but NiFi is not starting as a cluster. These are the changes I've made to the config files.
state-management.xml file
<cluster-provider>
<id>zk-provider</id>
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
<property name="Connect String">etl-1:2181,etl-2:2181,etl-3:2181</property>
<property name="Root Node">/ssd/nifi-1.5.0</property>
<property name="Session Timeout">10 seconds</property>
<property name="Access Control">Open</property>
</cluster-provider>
zookeeper.properities file
dataDir=./state/zookeeper
server.1=etl-1:2888:3888
server.2=etl-2:2888:3888
server.3=etl-3:2888:3888
nifi.properties file
nifi.zookeeper.connect.string=etl-1:2181,etl-2:2181,etl-3:2181
nifi.zookeeper.root.node=/ssd/nifi-1.5.0
nifi.cluster.is.node=yes
nifi.cluster.node.address=etl-2 (this is set to etl-1 on the other node)
nifi.state.management.embedded.zookeeper.start=true
[nifi#etl-2 zookeeper]$ cat /ssd/nifi-1.5.0/state/zookeeper/myid
2
[nifi#etl-1 logs]$ cat /ssd/nifi-1.5.0/state/zookeeper/myid
1
I've updated logback.xml to DEBUG, but there are so many message I can't seem to find out's what wrong. My best guess is that zookeeper in starting in local instead of cluster.
ls -l /ssd/nifi-1.5.0/state/
total 4
drwxrwxr-x. 18 nifi nifi 4096 Feb 23 18:49 local
drwxrwxr-x. 2 nifi nifi 18 Feb 23 15:26 zookeeper
I found the problem. I had nifi.cluster.is.node=yes instead of nifi.cluster.is.node=true.
Am trying to run Nifi as a 3 node cluster on Windows 10, with same properties set in all 3 conf files as mentioned above, but still its failing to start nifi as a 3 node cluster.
Below are the settings done on my files
state-management.xml file
<cluster-provider>
<id>zk-provider</id>
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
<property name="Connect String">node1:2181,node2:2181,node3:2181</property>
<property name="Root Node">/nifi</property>
<property name="Session Timeout">10 seconds</property>
<property name="Access Control">Open</property>
</cluster-provider>
zookeper properties
dataDir=./state/zookeeper
autopurge.snapRetainCount=30
server.1=node1:2888:3888
server.2=node2:2888:3888
server.3=node3:2888:3888
nifi properties:
nifi.web.http.host=node1
nifi.web.http.port=8080
nifi.cluster.is.node=true
nifi.cluster.node.address=node1
nifi.cluster.node.protocol.port=11122
nifi.zookeeper.connect.string=node1:2181,node2:2181,node3:2181
nifi.zookeeper.root.node=/nifi
In other 2 noes, the host name are placed respectively
But when i start the nodes, it displays the below error
C:\nifi-1.11.0-bin\Node1\bin>run-nifi.bat
2020-02-11 20:29:20,237 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi...
2020-02-11 20:29:20,238 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: C:\NIFI-1~1.0-B\Node1
2020-02-11 20:29:20,239 INFO [main] org.apache.nifi.bootstrap.Command Command: C:\Program Files\Java\jdk1.8.0_241\bin\java.exe -classpath C:\NIFI-1~1.0-B\Node1.\conf;C:\NIFI-1~1.0-B\Node1.\lib\javax.servlet-api-3.1.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\jcl-over-slf4j-1.7.26.jar;C:\NIFI-1~1.0-B\Node1.\lib\jetty-schemas-3.1.jar;C:\NIFI-1~1.0-B\Node1.\lib\jul-to-slf4j-1.7.26.jar;C:\NIFI-1~1.0-B\Node1.\lib\log4j-over-slf4j-1.7.26.jar;C:\NIFI-1~1.0-B\Node1.\lib\logback-classic-1.2.3.jar;C:\NIFI-1~1.0-B\Node1.\lib\logback-core-1.2.3.jar;C:\NIFI-1~1.0-B\Node1.\lib\nifi-api-1.11.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\nifi-framework-api-1.11.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\nifi-nar-utils-1.11.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\nifi-properties-1.11.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\nifi-runtime-1.11.0.jar;C:\NIFI-1~1.0-B\Node1.\lib\slf4j-api-1.7.26.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Djavax.security.auth.useSubjectCredsOnly=true -Djava.security.egd=file:/dev/urandom -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dzookeeper.admin.enableServer=false -Dnifi.properties.file.path=C:\NIFI-1~1.0-B\Node1.\conf\nifi.properties -Dnifi.bootstrap.listen.port=53535 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=C:\NIFI-1~1.0-B\Node1\bin..\logs org.apache.nifi.NiFi
2020-02-11 20:29:20,554 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read pid file C:\NIFI-1~1.0-B\Node1\bin..\run\nifi.pid; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2020-02-11 20:29:20,561 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read status file C:\NIFI-1~1.0-B\Node1\bin..\run\nifi.status; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2020-02-11 20:29:20,573 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 4284
C:\nifi-1.11.0-bin\Node1\bin>status-nifi.bat
20:31:57.265 [main] DEBUG org.apache.nifi.bootstrap.NotificationServiceManager - Found 0 service elements
20:31:57.271 [main] INFO org.apache.nifi.bootstrap.NotificationServiceManager - Successfully loaded the following 0 services: []
20:31:57.272 [main] INFO org.apache.nifi.bootstrap.RunNiFi - Registered no Notification Services for Notification Type NIFI_STARTED
20:31:57.273 [main] INFO org.apache.nifi.bootstrap.RunNiFi - Registered no Notification Services for Notification Type NIFI_STOPPED
20:31:57.274 [main] INFO org.apache.nifi.bootstrap.RunNiFi - Registered no Notification Services for Notification Type NIFI_DIED
20:31:57.277 [main] DEBUG org.apache.nifi.bootstrap.Command - Status File: C:\NIFI-1~1.0-B\Node1\bin..\run\nifi.status
20:31:57.278 [main] DEBUG org.apache.nifi.bootstrap.Command - Status File: C:\NIFI-1~1.0-B\Node1\bin..\run\nifi.status
20:31:57.279 [main] DEBUG org.apache.nifi.bootstrap.Command - Properties: {pid=4284, port=53536}
20:31:57.280 [main] DEBUG org.apache.nifi.bootstrap.Command - Pinging 53536
20:31:58.343 [main] DEBUG org.apache.nifi.bootstrap.Command - Process with PID 4284 is not running
20:31:58.345 [main] INFO org.apache.nifi.bootstrap.Command - Apache NiFi is not running
I installed the latest version of SonarQube 6.5 and have been able to get the SonarQube server up and running. I have my SQL Server database named ‘Sonar’ created with a user named ‘SonarUser’ and have given it admin rights. I have changed the collation to be case-sensitive (CS) and accent-sensitive (AS).
I have downloaded the jdbc driver and put it in the correct folders.
Followed the steps mentioned here - https://docs.sonarqube.org/display/SONAR/Installing+the+Server
However I am not able to make either Windows Authentication or SQL Server Authentication to work. The database is still empty, and do not see the tables/indexes in there.
I am making the below changes to the ‘sonar.properties’ file – 1 at a time – but it does not work
SQL Authentication
sonar.jdbc.username=SonarUser
sonar.jdbc.password=SonarUser
sonar.jdbc.url=jdbc:sqlserver://localhost;databaseName=Sonar
Windows Authentication
sonar.jdbc.url=jdbc:sqlserver://localhost;databaseName=Sonar;
integratedSecurity=true
When I make any change to the ‘sonar.properties’ file and then start the Sonar Server, it fails with the following error –
2017.10.03 16:59:09 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Sonarqube-6.5\temp
2017.10.03 16:59:09 INFO app[][o.s.a.p.JavaProcessLauncherImpl] Launch process[es]: C:\Program Files\Java\jre1.8.0_101\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=C:\Sonarqube-6.5\temp -cp ./lib/common/;./lib/search/ org.sonar.search.SearchServer
C:\Sonarqube-6.5\temp\sq-process1211130103830390174properties
2017.10.03 16:59:19 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2017.10.03 16:59:19 INFO app[][o.s.a.p.JavaProcessLauncherImpl] Launch process[web]: C:\Program Files\Java\jre1.8.0_101\bin\java
-Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Sonarqube-6.5\temp -cp ./lib/common/;./lib/server/;C:\Sonarqube-6.5\lib\jdbc\mssql\mssql-jdbc-6.1.0.jre8.jar
org.sonar.server.app.WebServer
C:\Sonarqube-6.5\temp\sq-process7396503632227644033properties
2017.10.03 16:59:23 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
2017.10.03 16:59:24 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
2017.10.03 16:59:24 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped <-- Wrapper Stopped
If I undo the changes in ‘sonar.properties’ file, and run the StartSonar.bat - the server runs fine.
Any help will be appreciated.
I was finally able to get through this error and was able to configure my SQL Database. In the web.log file, I saw the error message -
Unsupported mssql version: 10.0. Minimal supported version is 11.0.
Basically I was running an older version of SQL Server, which was causing this error. Once I created a database in SQL Server 2014 with this above steps, I was able to run the SonarQube instance without any issues. All the required tables got created in the database. I also confirmed that there are records inserted into the tables as you run SonarQube against my projects.
I have installed Neo4j 2.3.2 Community Edition on Mac OS 10.10. I can launch the application and connect to it from localhost:7474/browser/. So far, so good.
I would like to launch Neo4j 2.3.2 from a Terminal window, so that I don't have the overhead of a windowed application running at the same time. When I run the following command...
$ ~/neo4j/bin/neo4j console
... I get this output in the Terminal window:
WARNING: Max 256 open files allowed, minimum of 40 000 recommended. See the Neo4j manual.
Starting Neo4j Server console-mode...
Unable to find any JVMs matching version "1.7".
Using additional JVM arguments: -server -XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties -Djava.util.logging.config.file=conf/logging.properties -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -XX:hashCode=5 -Dneo4j.ext.udc.source=tarball
2016-02-25 14:03:18.755+0000 INFO [API] Setting startup timeout to: 120000ms based on 120000
2016-02-25 14:03:58.356+0000 INFO [API] Successfully started database
2016-02-25 14:04:04.220+0000 INFO [API] Starting HTTP on port :7474 with 2 threads available
2016-02-25 14:04:13.512+0000 INFO [API] Enabling HTTPS on port :7473
09:04:20.201 [main] INFO org.eclipse.jetty.util.log - Logging initialized #98517ms
2016-02-25 14:04:23.034+0000 INFO [API] Mounting static content at [/webadmin] from [webadmin-html]
2016-02-25 14:04:25.785+0000 INFO [API] Mounting static content at [/browser] from [browser]
09:04:25.993 [main] INFO org.eclipse.jetty.server.Server - jetty-9.2.4.v20141103
09:04:26.722 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.h.MovedContextHandler#1611ba2{/,null,AVAILABLE}
09:04:27.794 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /webadmin, did not find org.apache.jasper.servlet.JspServlet
09:04:27.981 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext#132ea25{/webadmin,jar:file:/Users/james/neo4j/system/lib/neo4j-server-2.2.5-static-web.jar!/webadmin-html,AVAILABLE}
09:04:38.841 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#60bfaa02{/db/manage,null,AVAILABLE}
09:04:39.326 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#28e2e149{/db/data,null,AVAILABLE}
09:04:39.353 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /browser, did not find org.apache.jasper.servlet.JspServlet
09:04:39.355 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext#78e6aa71{/browser,jar:file:/Users/james/neo4j/system/lib/neo4j-browser-2.2.5.jar!/browser,AVAILABLE}
09:04:39.536 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler#4994d9ab{/,null,AVAILABLE}
09:04:39.745 [main] INFO o.e.jetty.server.ServerConnector - Started ServerConnector#2d19cf20{HTTP/1.1}{localhost:7474}
09:04:40.576 [main] INFO o.e.jetty.server.ServerConnector - Started ServerConnector#43c742c{SSL-HTTP/1.1}{localhost:7473}
09:04:40.577 [main] INFO org.eclipse.jetty.server.Server - Started #119058ms
2016-02-25 14:04:40.577+0000 INFO [API] Server started on: http://localhost:7474/
2016-02-25 14:04:40.590+0000 INFO [API] Remote interface ready and available at [http://localhost:7474/]
I have Java version 8, update 74 installed (build 1.8.0_74-b02), so I assume that I can ignore the warning Unable to find any JVMs matching version "1.7".
However, when I visit http://localhost:7474/ in Chrome Version 45.0.2454.85 (64-bit), I see three errors in the Developer Console: two files that fail to load and a subsequent script error.
localhost/:28 GET http://localhost:7474/browser/styles/68eddd94.main.css
localhost/:466 GET http://localhost:7474/browser/scripts/ded362b3.scripts.js
Uncaught Error: [$injector:modulerr] Failed to instantiate module neo4jApp due to:
Error: [$injector:nomod] Module 'neo4jApp' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
As a result, the Neo4j interface does not appear in the browser window.
Is it possible to run Neo4j 2.3.2 from the Terminal, and if so, what do I need to do to get http://localhost:7474/ to load correctly?
Shift-reload, or test in an incognito window.
Looks like a JS file mismatch due to aggressive browser caching.