Did you remove the /tmp/did_run.txt file before run schedule?
"Aborted" can be caused by schedule can't overwrite the file, if you run the script when logged in as some user other than fmserver.
Good suggestion - I have tried removing the file before running and the result is the same. I have also tried removing the old file as the first thing in the script.
rm -f /tmp/did_run.txt
All the scripts are running as fmserver and the file is created with read and write rights for fmserver. It seems fmserver is able to remove the file or overwrite it.
The problem also persists if I create a script that does not create a file, e.g. just echoes a bit of text.
Are there any best practices for debugging schedules? Besides logging from within the script which focuses on the script side of things and not FileMaker?
I'm currently trying to write a shell script to simply open a file and I'm getting the same 10022 error. I test the shell script file via terminal and it behaves as expected, but when its ran via FMS, It aborts unexpectedly.
I made sure permissions were fine on the file as well as tried adjusting the schedule to run with a particular user. Same error.
Here is my script:
Figured I would share a script I'm trying to run to see if we can narrow this down to an issue with FMS 15 or with our scripting. I tried a simple echo script as well. Same issue.
I also noticed that after my script schedule fails, I have to edit it and save it before I can attempt to run it again. Otherwise, if I try and run it, it never goes to a "running" state and stays as "Aborted Unexpectedly".
We had seen this problem in the past but it went away in FileMaker Server 15.0.1. It is back in FMS 15.0.3 running on Mac OS X 10.10.5 Yosemite.
I built a new test script:
and set it up as a FileMaker schedule with a time limit of 2 minutes and to terminate after the time limit. It should have run almost instantly but instead it ran out the clock and threw the same error 642 with Unexpected error 10022.