v1.12 A47 (2021/12/24), but this also was problematic on A46.
Hourly jobs (mainly polls) run fine.
Semaphore-based events run fine.
Shell and Interval do not.
My intent was to run nightly maintenance:
/mystic/mutil maint.ini
This command works fine if I run it manually from the command line. My logs show nothing, other than no indication that this event ran. There are no error messages of any sort.
Some helpful folks on fsxNet suggested I play with the paths some. This did not make any difference. I thought, okay, maybe restart mis after a change, as I don't know when that is read and compiled into event file (event.dat) but that made no difference either.
I tried the following:
./mutil maint.ini
./mutil ./maint.ini
/mystic/mutil /mystic/maint.ini
/mystic/mutil maint.ini
Same behavior. Tried switching to interval, then back to shell for each.
So then I said, forget mutil for now. I created a shell script which simply does this:
#!/bin/bash
rightnow=$(date)
echo "${rightnow}" >> /mystic/logs/MAINT_IS_RUNNING_HUZZAH
Which runs fine from the command line.
Same issue. So it wasn't anything with mutil so far as I can tell.
What I did learn was that if I schedule this to run hourly, it runs fine. But that is the only event type that runs. Since I know this runs fine, I know this command/path works:
/mystic/proof.sh
But this will not run as a shell or interval event.
My question is, what would cause this? Also what is a BBS event type (these are not described in the Mystic Wiki).
The hourly events show up in the logs. If I set it to shell, it does not. I have the logging level set to MAX currently.
+ 2022.02.04 19:42:08 EVENT Running event: Nightly Maintenance
+ 2022.02.04 19:42:08 EVENT Cmd: /mystic/proof.sh
+ 2022.02.04 19:42:08 EVENT Res: 0
I have taken a screenshot of the event configuration here just in case I am doing something obviously wrong:
https://i.imgur.com/IRRuyOq.png
--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)