Gateway went belly up

I installed an app that was running on a MS platform and installed it in a Linux machine. As a result, when running the app it crashed. I went back and extracted and restored a backup from the previous app that was running on the Linux machine but it still does not start the gateway. Errors are a result of a part of the Ignition program that points to a MS directory. What is the default directory for a Linux based system?

WrapperSimpleApp Error: Encountered an error running main:
INFO | jvm 1 | 2011/12/15 20:10:48 | WrapperSimpleApp Error: java.lang.IllegalStateException: Could not find C:\Program Files\Inductive Automation\Ignition/data/gateway.xml or C:\Program Files\Inductive Automation\Ignition/data/gateway.xml_clean.

Here is how you can fix this:
On your Linux box, open /var/lib/ignition/data/ignition.conf. Replace your properties with the ones listed below:
wrapper.java.classpath.1=/usr/local/bin/ignition/lib/wrapper.jar
wrapper.java.classpath.2=/usr/local/bin/ignition/lib/annotations-api.jar
wrapper.java.classpath.3=/usr/local/bin/ignition/lib/catalina.jar
wrapper.java.classpath.4=/usr/local/bin/ignition/lib/catapult.jar
wrapper.java.classpath.5=/usr/local/bin/ignition/lib/el-api.jar
wrapper.java.classpath.6=/usr/local/bin/ignition/lib/log4j-1.2.15-min.jar
wrapper.java.classpath.7=/usr/local/bin/ignition/lib/servlet-api.jar
wrapper.java.classpath.8=/usr/local/bin/ignition/lib/slf4j-api-1.5.3.jar
wrapper.java.classpath.9=/usr/local/bin/ignition/lib/slf4j-log4j12-1.5.3.jar
wrapper.java.classpath.10=/usr/local/bin/ignition/lib/tomcat-coyote.jar
wrapper.java.classpath.11=/usr/local/bin/ignition/lib/tomcat-juli.jar
wrapper.java.classpath.12=/usr/local/bin/ignition/lib/mail.jar

wrapper.java.library.path.1=/usr/local/bin/ignition/lib

wrapper.java.additional.6=-Ddata.dir=/var/lib/ignition/data

wrapper.logfile=/var/log/ignition/wrapper.log

This should get your gateway going again. BTW, we put in an update in 7.3.2 to use variables in the backed up ignition.conf instead of absolute paths, so this type of issue will no longer occur with Windows <-> Linux backups/restorations.

Up and running. :thumb_right: