Revolving around the core of technology
Syncrify V. 3.6 - Build 800 as download from Thecus App Repo works ok but web interface flashes that there is an update available. Following the procedure downloads patches into the (apparently) correct directory. Restarting Syncrify from the web page fails - restarting by disabling/enabling in the Thecus GUI brings it back up without a full system reboot. Syncrify remains unpatched and the patch files are still staged. Tried several times - same non-result (even with system reboot)!
What is the latest version for this system? Perhaps the patches don't update because they are the same or older version? I installed a copy from Synametrics on a Linux server and is V 3.5 - Build 778 update! Is there a way to update manually?
Running N4310 with OS6.0.867
Dear Brian,
Most likely, the problem is associated with "Restart", not upgrade. Do you know the script that starts and stop Syncrify on this package? If yes, you can specify that command in AppConfig.xml using the following steps:
Let us know if you still need help.
Imran
The ntServiceCommand value is null (""). The jvmPath is "java" - I tried changing to full path to java but no result so I reverted. There appears to be no stop script buth there is a start script in the Syncrify folder which functions but doesn't trigger an update. I don't know how the NAS OS is starting/stopping or enabling/disabling but it did drop a log.txt file in the install folder when I toggled it in the OS yesterday. I'm not expert enough with Linux to figure out where the OS is doing it's initialization of Sycrify.
I reviewed the step2.xml file in the patches folder and it appears that it might be a guide for a manual update using the CLI? What would be the caveats to doing it manually? I'm guessiong I could uninstall/reinstall through the OS if I hosed it up!
I've discovered something that might be causing your issue, Bryan. Watching the logs as I updated my own install of Syncrify Server, I noticed that the upgrade process is choking on a missing file: patches/AppLauncher.jar. I realized that not only is that file not downloaded, it isn't even specified in step1.xml with the other files. I was able to manually download the file using the URL noted in step1.xml (replacing the filename with AppLauncher.jar), and when I started the update process again it did find the file. Maybe that will help you as well.
BTW, I'm having this problem on a standard Ubuntu Server 16.04LTS install on a PC. Downloading AppLauncher.jar and making it available doesn't seem to have helped much; the service still stops, applauncher appears to execute, but the upgrade doesn't happen and the service itself is not started. I have to manually restart the service and it's still the old version.
Nelson,
AppLauncher.jar is a file that should have been copied during installation. If this file is missing, Syncrify will not be able to restart itself. Where did you download this file from?
Assuming you got the AppLauncher.jar from somewhere, it should create a couple of log files called starterOut.log and starterErr.log in the $INSTALL_DIR\logs folder. Do you see any errors in there?
One more update: The output in syncrify/logs/Syncrify.log indicates the command line used when trying to start AppLauncher.jar. So I changed to my main syncrify directory and ran that command line, and the update worked.
Nelson,
The command line to restart Syncrify is located in the ntServiceCommand parameter in AppConfig.xml file. Ensure this value is something like /etc/init.d/syncrify start .