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)

On 04 Feb 2022, Chris Hizny said the following...

My intent was to run nightly maintenance:

/mystic/mutil maint.ini

Do you actually have a file called maint.ini in your Mystic directory?

--- Mystic BBS v1.12 A48 2022/01/28 (Raspberry Pi/32)
* Origin: Central Ontario BluesNET (1:229/307)

Do you actually have a file called maint.ini in your Mystic directory?

Absolutely. I can run this command manually at the command line and it works fine. Messages are packed, etc.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)

+ 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 will make a test to see if I can reproduce a similar issue on my Linux machine here, but the only thing that comes to mind is maybe something access related?

Your script isn't going to run properly if whatever runs it doesn't have access to echo to a log file in the logs directory. It seems Mystic is trying to run it based on the logs and the OS is returning a 0. That implies that it does actually run.

My question is, what would cause this? Also what is a BBS event type (these are not described in the Mystic Wiki).

There is no section for events written yet but I should probably put that on my TO-DO list. Instead they are listed in the WHATSNEW. I searched for "event type" on the Wiki and found this:

TYPE4: BBS
==========

This event type is not actually executed by MIS itself, and is similar to
what you might have found in old DOS-based BBS software. The purpose for
this event is to provide an option to force users to log off the BBS if
you want them to.

Like the scheduled Shell event, a BBS type event can be scheduled at a
certain hour/min and one or more days of the week. In addition to the
time/day scheduling there are some other options:

Node: This defines the node number for which the event will execute.
If you keep the node number at 0, it will be applied to all
users on all nodes.

Warning: This determins the time before the event to notify the user
of the upcoming event. This can be set to 0 to never warn them,
or (for example) 10 to give them a message that they will be
required to logoff in 10 minutes.

When this event time hits, the user will be logged off of the BBS if they
have not already logged off on their own.

... A SQL query walks into a bar and sees two tables. Asks: 'Can I join you?'

--- Mystic BBS v1.12 A48 2022/02/03 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

+ 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 will make a test to see if I can reproduce a similar issue on my Linux machine here, but the only thing that comes to mind is maybe something access related?

Your script isn't going to run properly if whatever runs it doesn't have access to echo to a log file in the logs directory. It seems Mystic is trying to run it based on the logs and the OS is returning a 0. That implies that it does actually run.

Well, in this case, you're looking at the hourly run, which *does* work. That's important. Hourly is fine. I can run anything hourly. The problem is if I change this from hourly to a shell or interval event type, it will not run, and will not create a log entry like the above.

That's why I am confused.

As for log permissions, they seem fine:

-rw-r--r-- 1 mystic mystic 46 Feb 5 11:10 errors.log
-rw-r--r-- 1 mystic mystic 376984 Feb 5 17:09 mis.log
-rw-r--r-- 1 mystic mystic 261005 Feb 4 23:20 mutil.20220204.log
-rw-r--r-- 1 mystic mystic 20434 Feb 5 01:30 mutil.20220205.log
-rw-r--r-- 1 mystic mystic 1830926 Feb 5 17:35 mutil.log
-rw-r--r-- 1 mystic mystic 6104 Feb 5 17:31 node1.log
-rw-r--r-- 1 mystic mystic 710 Feb 5 09:27 node2.log
-rw-r--r-- 1 mystic mystic 231 Feb 4 13:03 node3.log
-rw-r--r-- 1 mystic mystic 576488 Feb 5 17:35 poll.log
-rw-r--r-- 1 mystic mystic 52104 Feb 5 17:10 qwkpoll.log
drwxrwxr-x 2 mystic mystic 4096 Sep 28 03:18 tempmis

Thanks for the explanation of the BBS event type.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (1:218/860)