I’m having issues with Ignition 8.0.16 not Running after rebooting my windows (10) machine. I’ve tried the following fixes:
- Setting Ignition Service to Automatic (delayed start)
- Adding
wrapper.java.additional.4=-XX:UseAVX=0 to igntion.conf file as explained here: Ignition Gateway not starting after long time
- Changing Java path to match my Java exe path in igntition.conf file as explained here:
https://docs.inductiveautomation.com/display/DOC79/Changing+Gateway+Java+Version
Originally the Gateway status was “Started - Not Running” when i ran “gwcmd -i, --info”
After all of these changes it now says:
Error: could not open `C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\lib\jvm.cfg’
I’ve double checked and indeed, that jvm.cfg file does not exist.
I turned on “wrapper.debug=TRUE” in the ignition.conf file and received the following feedback:
Java Command Line (Query Java Version):
DEBUG | wrapper | 2020/11/13 08:30:25 | Command: "lib\runtime\jre-win\bin\java" -version
DEBUG | jvm ver. | 2020/11/13 08:30:25 | Error: could not open `C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\lib\jvm.cfg'
ERROR | wrapper | 2020/11/13 08:30:25 | Failed to parse the version of Java. Resolving to the lowest supported version (1.4).
then later:
INFO | jvm 4 | 2020/11/13 08:30:25 | Error: could not open `C:\Program Files\Inductive Automation\Ignition\lib\runtime\jre-win\lib\jvm.cfg'
Any help to remedy this situation and to create a permanent fix for future server reboots is much appreciated.
If you stop the gateway, delete the jre-win folder, then start it again - does it the new runtime that is unzipped include the jvm.cfg file?
If you then reboot is it gone? Do you you have any anti-virus software running?
Followed your steps of stopping gateway, deleting jre-win folder, starting again and it unzipped the jre-win.zip folder and indeed, the jvm.cfg file is now back and i can access the Ignition webserver again!
Going to reboot windows now to see what happens
Gateway service will not start after reboot. Tried manually starting in windows services as well as start-ignition.bat
log file gave me different information this time, something relating to stack size:
DEBUG | wrapper | 2020/11/13 09:17:50 | Magic number for file C:\ProgramData\Oracle\Java\javapath\java.exe: 0x4d5a9000
DEBUG | wrapper | 2020/11/13 09:17:50 | Java Command Line (Query Java Version):
DEBUG | wrapper | 2020/11/13 09:17:50 | Command: "C:\ProgramData\Oracle\Java\javapath\java.exe" -version
DEBUG | jvm ver. | 2020/11/13 09:17:50 | java version "1.8.0_131"
DEBUG | jvm ver. | 2020/11/13 09:17:50 | Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
DEBUG | jvm ver. | 2020/11/13 09:17:50 | Java HotSpot(TM) Client VM (build 25.131-b11, mixed mode)
DEBUG | wrapper | 2020/11/13 09:17:50 | Java version: 8.0.131
DEBUG | wrapper | 2020/11/13 09:17:50 | Java vendor: Oracle
DEBUG | wrapper | 2020/11/13 09:17:50 | Java bits: 64-Bit
DEBUG | wrapper | 2020/11/13 09:17:50 | Reading the JVM output using the encoding of the current locale (1252).
DEBUG | wrapper | 2020/11/13 09:17:50 | Magic number for file C:\ProgramData\Oracle\Java\javapath\java.exe: 0x4d5a9000
DEBUG | wrapper | 2020/11/13 09:17:50 | Startup Timeouts: wrapper.startup.timeout=30, wrapper.startup.delay.console=0, wrapper.startup.delay.service=0, wrapper.restart.delay=5
DEBUG | wrapper | 2020/11/13 09:17:50 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30, wrapper.ping.alert.threshold=7
DEBUG | wrapper | 2020/11/13 09:17:50 | Shutdown Timeouts: wrapper.shutdown.timeout=120, wrapper.jvm_exit.timeout=120, wrapper.jvm_cleanup.timeout=10, wrapper.jvm_terminate.timeout=10
STATUS | wrapper | 2020/11/13 09:17:50 | Launching a JVM...
DEBUG | wrapper | 2020/11/13 09:17:50 | Java Command Line:
DEBUG | wrapper | 2020/11/13 09:17:50 | Command: "C:\ProgramData\Oracle\Java\javapath\java.exe" -Ddata.dir=data -Xms1024m -Xmx2048m -Djava.library.path="lib" -classpath "lib/wrapper.jar;lib/core/common/annotations-13.0.jar;lib/core/common/barcode4j-2.1.jar;lib/core/common/bcpkix-jdk15on-1.64.jar;lib/core/common/bcprov-jdk15on-1.64.jar;lib/core/common/common.jar;lib/core/common/commons-cli-1.2.jar;lib/core/common/commons-codec-1.13.jar;lib/core/common/commons-collections4-4.4.jar;lib/core/common/commons-compress-1.19.jar;lib/core/common/commons-io-2.2.jar;lib/core/common/commons-lang3-3.9.jar;lib/core/common/commons-logging-1.2.jar;lib/core/common/commons-math3-3.6.1.jar;lib/core/common/core-java6-3.2.1.4.jar;lib/core/common/cron4j-2.2.3.jar;lib/core/common/curvesapi-1.06.jar;lib/core/common/guava-23.3-jre.jar;lib/core/common/httpclient-4.5.11.jar;lib/core/common/httpcore-4.4.13.jar;lib/core/common/ia-gson-2.8.5.jar;lib/core/common/java-cup-10k.jar;lib/core/common/jfreechart-min-1.0.0.jar;lib/core/common/jgrapht-core-1.4.0.jar;lib/core/common/jheaps-0.11.jar;lib/core/common/jide-common-3.7.4.jar;lib/core/common/joda-time-2.10.2.jar;lib/core/common/jose4j-0.7.0.jar;lib/core/common/jul-to-slf4j-1.7.26.jar;lib/core/common/jython-2.7.1-ia5.jar;lib/core/common/kotlin-stdlib-1.3.71.jar;lib/core/common/kotlin-stdlib-common-1.3.71.jar;lib/core/common/kotlin-stdlib-jdk7-1.3.71.jar;lib/core/common/kotlin-stdlib-jdk8-1.3.71.jar;lib/core/common/kotlinx-coroutines-core-1.3.5.jar;lib/core/common/log4j-over-slf4j-1.7.26.jar;lib/core/common/logback-classic-1.1.7.jar;lib/core/common/logback-core-1.1.7.jar;lib/core/common/metrics-core-3.1.0.jar;lib/core/common/poi-4.1.1.jar;lib/core/common/poi-ooxml-4.1.1.jar;lib/core/common/poi-ooxml-schemas-4.1.1.jar;lib/core/common/rsyntaxtextarea-3.0.3.jar;lib/core/common/slf4j-api-1.7.26.jar;lib/core/common/xmlbeans-3.1.0.jar;lib/core/gateway/FastInfoset-1.2.16.jar;lib/core/gateway/HASPJava.dll;lib/core/gateway/HASPJava_x64.dll;lib/core/gateway/TableLayout-20050920.jar;lib/core/gateway/commons-fileupload-1.4.jar;lib/core/gateway/gateway-8.0.16.jar;lib/core/gateway/gateway-api-8.0.16.jar;lib/core/gateway/hasp-srm-api-1.0.0.jar;lib/core/gateway/hsqldb-2.3.3.jar;lib/core/gateway/ignition32.dll;lib/core/gateway/ignition64.dll;lib/core/gateway/istack-commons-runtime-3.0.8.jar;lib/core/gateway/jSerialComm-2.5.1-ia2.jar;lib/core/gateway/jakarta.activation-1.2.1.jar;lib/core/gateway/jakarta.activation-api-1.2.1.jar;lib/core/gateway/jakarta.xml.bind-api-2.3.2.jar;lib/core/gateway/javax.mail-1.5.2.jar;lib/core/gateway/javax.mail-api-1.5.2.jar;lib/core/gateway/javax.servlet-api-3.1.0.jar;lib/core/gateway/jaxb-runtime-2.3.2.jar;lib/core/gateway/jetty-client-9.4.24.v20191120.jar;lib/core/gateway/jetty-http-9.4.24.v20191120.jar;lib/core/gateway/jetty-io-9.4.24.v20191120.jar;lib/core/gateway/jetty-rewrite-9.4.24.v20191120.jar;lib/core/gateway/jetty-security-9.4.24.v20191120.jar;lib/core/gateway/jetty-server-9.4.24.v20191120.jar;lib/core/gateway/jetty-servlet-9.4.24.v20191120.jar;lib/core/gateway/jetty-util-9.4.24.v20191120.jar;lib/core/gateway/jetty-webapp-9.4.24.v20191120.jar;lib/core/gateway/jetty-xml-9.4.24.v20191120.jar;lib/core/gateway/jquery-ui-core-6.1.1.jar;lib/core/gateway/metro-8.0.16.jar;lib/core/gateway/protobuf-java-3.8.0.jar;lib/core/gateway/simple-orm-8.0.16.jar;lib/core/gateway/sqlite-jdbc-3.23.1.jar;lib/core/gateway/stax2-api-3.1.4.jar;lib/core/gateway/stax-ex-1.8.1.jar;lib/core/gateway/tape-1.2.3.jar;lib/core/gateway/timingframework-1.0.jar;lib/core/gateway/txw2-2.3.2.jar;lib/core/gateway/websocket-api-9.4.24.v20191120.jar;lib/core/gateway/websocket-client-9.4.24.v20191120.jar;lib/core/gateway/websocket-common-9.4.24.v20191120.jar;lib/core/gateway/websocket-server-9.4.24.v20191120.jar;lib/core/gateway/websocket-servlet-9.4.24.v20191120.jar;lib/core/gateway/wicket-core-6.1.1.jar;lib/core/gateway/wicket-datetime-6.1.1.jar;lib/core/gateway/wicket-extensions-6.1.1.jar;lib/core/gateway/wicket-request-6.1.1.jar;lib/core/gateway/wicket-util-6.1.1.jar;lib/core/gateway/woodstox-core-5.0.3.jar;lib/core/gateway/xmlsec-2.1.4.jar" -Dwrapper.key="mQ3Bm6aiC8HxyryFOUrnazFiOqxQUvgs" -Dwrapper.port=32000 -Dwrapper.debug="TRUE" -Dwrapper.pid=6604 -Dwrapper.version="3.5.42-st" -Dwrapper.native_library="wrapper" -Dwrapper.arch="x86" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=5 -Dwrapper.lang.domain="wrapper" -Dwrapper.lang.folder="../lang" org.tanukisoftware.wrapper.WrapperSimpleApp com.inductiveautomation.catapult.Catapult
DEBUG | wrapper | 2020/11/13 09:17:50 | JVM started (PID=6460)
INFO | jvm 5 | 2020/11/13 09:17:50 | Error occurred during initialization of VM
INFO | jvm 5 | 2020/11/13 09:17:50 | Could not reserve enough space for 2097152KB object heap
DEBUG | wrapper | 2020/11/13 09:17:50 | JVM process exited with a code of 1, setting the Wrapper exit code to 1.
DEBUG | wrapper | 2020/11/13 09:17:50 | 1: STATUS_WAIT_1 (0x1)
ERROR | wrapper | 2020/11/13 09:17:50 | JVM exited while loading the application.
DEBUG | wrapper | 2020/11/13 09:17:50 | Preparing to restart with mode 2.
DEBUG | wrapper | 2020/11/13 09:17:50 | JVM was only running for 0 seconds leading to a failed restart count of 5.
FATAL | wrapper | 2020/11/13 09:17:50 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
My apologies, i still had the following line commented out in the ignition.conf file and that was preventing the starting of the gateway service:
wrapper.java.command=%JAVA_HOME%/bin/java
Still need to test the robustness of the gateway after reboots, as i had to manually start again.
1 Like