Revolving around the core of technology
Document ID: | 5299 |
---|---|
Subject: | Troubleshooting restarting problems with Syncrify |
Creation date: | 5/22/19 8:41 AM |
Last modified on: | 6/9/22 11:07 AM |
In order to patch Syncrify to a newer build, you must restart Syncrify from the web interface. Use the following tips to troubleshoot Syncrify if you're running into problems restarting Syncrify from the web interface.
AppLauncher.jar
must exists in $INSTALL_DIR\patches
folder.
ntServiceCommand
- This should refer to a script responsible for starting Syncrify. For example, on Windows
this is set to net start Syncrify
, which runs the service. On Linux, this could be something like:
/etc/init.d/syncrify start
<parameter name="ntServiceCommand" type="1" value="net start Syncrify"></parameter>
Parameters in this set matter if ntServiceCommand
(above) is left blank.
There are two parameters in this set:
vmParam
- Refers to additional VMParameters. You should not have to change this value. jvmPath
- Refers to the PATH where java is located.Example:
<parameter name="vmParam" type="1" value="-Xmx1024m -DLoggingConfigFile=logconfig.xml"></parameter> <parameter name="jvmPath" type="1" value="jre/bin/java"></parameter>The value for
jvmPath
could be absolute path to java.exe, related path to $INSTALL_DIR or simply java
,
provided the file is found on $PATH.
Do you have a helpful tip related to this document that you'd like to share with other users?