Conduit Firmware Version: 5.2.5
We have built automation to install our custom App both locally and remotely using the Putty’s plink.exe. For example here is a command we run and it runs without any issues and the custom app is installed successfully. In this case the app-manager command runs without any issues.
"echo "<pwd>" | sudo -S app-manager --command local --appfile testapp.tar.gz --appname "TestApp" --apptype CUSTOM
“
However we at times patch our custom app when needed and so we copy over the files to the custom app install folder and all that succeeds. But for the patch to take effect we restart the custom app and so we used app-manager to stop and start the custom app and an examples of the command is below.
"echo "<pwd>" | sudo -S /etc/init.d/customapp stop_apps
”
sleep 2.5s
"echo "<pwd>" | sudo -S /etc/init.d/customapp start_apps
”
And we get the following o/p with the errors below:
Password:
customapp.init: Stopping custom apps through app-manager (user request)…
customapp.init: Stopping custom app with ID [LOCAL]…
bash: AppCommand::executeStartScript:: command not found
Password:
customapp.init: Starting custom apps through app-manager (user request)…
customapp.init: Starting custom app with ID [LOCAL]…
AppCommand::executeStartScript:: command not found
However if I run it from the putty client it just works. Any ideas as to why from the plink.exe I get the error when just starting and stopping the app. Also the app-manager doesn’t throw the same error when installing the app.
Thanks,
Ajay