Closed tillkruss closed 3 years ago
Odd! Are you...:
Yes, running as root and log files are saved as well.
Is the output being logged properly? This is a bit out of my area of expertise but based on my Google searches, the "Interrupted (1)" status error while saving output to a text file can be indicative of a permissions issue for the log file location.
It would explain why the script is working, but still generating an error. I suppose a quick test would be to disable task logging and see if the status error still occurs.
Logs are written when no update occurred. This only happens when Plex is actually updated.
This only happens when Plex is actually updated.
Oh... Looking at this with fresh eyes I think I know what's going on. Synology DSM doesn't report on positive results for Tasks. So, to get a status message sent to you that reflects positive results (in this case a successful update of Plex), the script intentionally trips an exit status of 1. This causes the DSM to think that there was a problem involved with the script's execution and sends notifications. It otherwise would not send notifications with an exit status of 0.
I've updated the readme to reflect this. Thanks for bringing it up as an issue
When I go to "Task Scheduler > Run" I get the "Interrupted" status.
The update itself works flawless.