Closed Rasmusho12 closed 3 months ago
With DSN Server running what does the following command return?
sudo /usr/syno/bin/synopkg status DNSServer; echo $?
And the same command when DSN Server is stopped?
And for a package that is not installed:
sudo /usr/syno/bin/synopkg status foobar; echo $?
have the same issue: the problem is here:
RUNNING_
root@hive /volume1/scripts/Synology_app_mover-3.0.45 $ /usr/syno/bin/synopkg status MailServer; echo $?
{"aspect":{"active":{"status":"running","status_code":0,"status_description":"retrieve from status script"}},"description":"Status: [0], package is started","package":"MailServer","status":"running"}
0
STOPPED:
root@hive /volume1/scripts/Synology_app_mover-3.0.45 $ /usr/syno/bin/synopkg status MailServer; echo $?
{"aspect":{"active":{"status":"stop","status_description":"translate from systemd status"}},"description":"Status: [0], package is stopped","package":"MailServer","status":"stop"}
0
the return code is always 0
DSM Version: DSM 7.1.1-42962 Update 6
Probably better:
root@hive /volume1/scripts/Synology_app_mover-3.0.45 $ /usr/syno/bin/synopkg is_onoff MailServer; echo $?
package MailServer isn't turned on, status: [262]
1
root@hive /volume1/scripts/Synology_app_mover-3.0.45 $ /usr/syno/bin/synopkg is_onoff MailServer; echo $?
package MailServer is turned on
0
@dakky @Rasmusho12
I've released a new version that fixes this issue. https://github.com/007revad/Synology_app_mover/releases/tag/v3.0.46
After updating from 3.0.41 to 3.0.45 it doesn't want to stop the app. It fails to do so, however when checking directly on the synology, the app has stopped.![image](https://github.com/007revad/Synology_app_mover/assets/22321590/2f305c6e-b4a9-4908-86ce-ca089ddee927)
After downgrading there is no problem at all![image](https://github.com/007revad/Synology_app_mover/assets/22321590/a276e614-7e98-4788-816a-844b020aacd7)