Has anyone ever experienced where mystic does not seem to trigger on events? I've somehow recently corrected MAILOUT on semaphore trigger, but mailin has remained elusive.

OS: Linux
File Permissions on INI files: 777/chmod +x
ini files are in /mystic directory
Events are set for hourly and on !Toss event with:
MUTIL MAILIN.INI|MUTIL MAILOUT.INI
going to /mystic directory and running commands from prompt are successful. Weekdays are set to YES
Active flag - yes, it is YES.
if MUTIL works fine at command line, where else can I look?

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

*** Quoting Nuke from a message to All ***

Has anyone ever experienced where mystic does not seem to trigger on events? I've somehow recently corrected MAILOUT on semaphore trigger,
but mailin has remained elusive.

Yeah, I've been bitten by this. You have to restart mis each time you make a change to your events. I made a new event once to automatically post a message
using mutil and was baffeled that it wasn't working.

If you're running mis in daemon mode just do a sudo ./mis shutdown ; ./mis daemon and your event should just magically start working.


Jay

... My inferiority complexes aren't as good as yours.

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms | 289-424-5180 | bbs.nrbbs.net (21:3/110)

Yeah as has been said the mis running only appears to load it's configuration on startup so any changes to the telnet/ssh/other protocols as well as the events system will need a restart.

I'm having an odd problem at the moment where the filetoss works and places FSXNODE's FSXNET.Znn nodelist files into the right folder FSX_NODE but then
my bbs doesn't seem to process it and I cannot use the browse nodelist to
view whats in the network

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Tribe BBS (21:1/177)

Yeah, I've been bitten by this. You have to restart mis each time you make a change to your events. I made a new event once to automatically post a message

using mutil and was baffeled that it wasn't working.

If you're running mis in daemon mode just do a sudo ./mis shutdown ;
./mis daemon and your event should just magically start working.

but a computer reboot would have solved that, correct?
this has been going on now for two weeks.
I thought it might be permission problem with the INI files - but I've
modified those since.
~Nuke

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

Yeah, I've been bitten by this. You have to restart mis each time yo make a change to your events. I made a new event once to automatical post a message

using mutil and was baffeled that it wasn't working.

If you're running mis in daemon mode just do a sudo ./mis shutdown ; ./mis daemon and your event should just magically start working.

but a computer reboot would have solved that, correct?
this has been going on now for two weeks.
I thought it might be permission problem with the INI files - but I've modified those since.
~Nuke

OK - I think I figured it out though I don't know yet why.
I had to go into events and where I had "MUTIL MAILOUT.INI|MUTIL MAILIN.INI",
I had to add the working directory, so: "/MYSTIC/MUTIL /MYSTIC/MAILOUT.INI <etc>"
weird....

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

On 04 Mar 2021, 02:06a, Nuke said the following...

Events are set for hourly and on !Toss event with:
MUTIL MAILIN.INI|MUTIL MAILOUT.INI

Change this to:

./mutil mailin.ini|./mutil mailout.ini

The events need to know where the program is located, hence the ./ to run them.

Also, make sure the case is correct. Typically, the filenames are in lowercase, but double check on your system to make sure. :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/01/14 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

./mutil mailin.ini|./mutil mailout.ini

The events need to know where the program is located, hence the ./ to
run them.

You know, I know to do that in the command line, but I thought that would not be needed inside mystic config area! either way, it is workiing now!
thanks!!
~ Nuke

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

On 04 Mar 2021, 08:13p, Nuke said the following...

The events need to know where the program is located, hence the ./ to run them.

You know, I know to do that in the command line, but I thought that
would notbe needed inside mystic config area! either way, it is workiing now!thanks!!

You get so used to typing it in, without even thinking about it. :)

That is one that seems to get just about everyone, on the Linux side...


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2021/01/14 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 04 Mar 2021, Nuke said the following...

OK - I think I figured it out though I don't know yet why.
I had to go into events and where I had "MUTIL MAILOUT.INI|MUTIL MAILIN.INI", I had to add the working directory, so: "/MYSTIC/MUTIL /MYSTIC/MAILOUT.INI <etc>"
weird....

No, not weird, normal Linux. What you needed was ./mutil mailout.ini| and so on. The Events start in /mystic by default, so ./name to run something. Generally it can be safer to do the full path like /mystic/mutil mailout.ini but it's not needed. It just makes it easier to remember where things are.
It also works better when doing odd things like:
(DD) Exec external program ./mystic -ver
(GT) Display line of text |PA
which will show the mystic version to the BBS user. Sometimes you need a |CR
or two in front of the |PA (pause) for multi-line output to work. Sometimes
you need the full path to get it to work as well, I experiment with everything I can ;)

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

I had to go into events and where I had "MUTIL MAILOUT.INI|MUTIL MAILIN.INI", I had to add the working directory, so: "/MYSTIC/MUTIL /MYSTIC/MAILOUT.INI <etc>"

and if you are running under Linux (based upon you used / rather than \ in the paths) then you will need to add ./ to mutil, so

./mutil mailout.ini
and so on

You will also need to add a fidopoll ... else theres not much point doing the mailin

Avon's videos on the raspberry pi shows the following event line

./mutil mailout.ini|./fidopoll 21:1/100|./mutil mailin.ini

i.e. process outgoing email into files for fidopoll to send; send them;
import into the message databases any messages downloaded

the ./ is essential in linux as by default the current directory is NOT in
the PATH unlike windows. Without it you will see in the logs that mutil will
be tried to run by the events system but will fail

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Tribe BBS (21:1/177)

On 04 Mar 2021, hal said the following...

Avon's videos on the raspberry pi shows the following event line

./mutil mailout.ini|./fidopoll 21:1/100|./mutil mailin.ini

Remember that fidopoll goes away with A46 after that it's ./mis poll
it replaces ./fidopoll

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

./mutil mailout.ini|./fidopoll 21:1/100|./mutil mailin.ini

Remember that fidopoll goes away with A46 after that it's ./mis poll
it replaces ./fidopoll

Oooh hadn't seen that one

I've been too busy trying to get my Netmail, File Tossing and Nodelist
working.

I guess I'd better

./mutil mailout.ini|./mis poll 21:1/100|./mutil mailin.ini

instead then.

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Tribe BBS (21:1/177)

On 04 Mar 2021 at 02:06a, Nuke pondered and said...

MUTIL MAILIN.INI|MUTIL MAILOUT.INI
going to /mystic directory and running commands from prompt are successful. Weekdays are set to YES
Active flag - yes, it is YES.

What are you typing on the command line and is it any different? Your tag
line shows Linux/64. If so then the more common is:
./mutil mailout|./mis poll 21:1/100|mailin.ini
for a full poll. Remember commands need to come from somewhere (./=current directory). To setup you get the mail setup to go out, poll, then move the mailin from the poll. I have one that does ./mis poll forced but that seem
to error were 21:1/100 (FSXNET) doesn't. Any changes to ./mis commands take
a reboot of mis. For most sudo ./mis shutdown ; sudo ./mis daemon will work
on most. The Pi (at least Pi3) is slower so I find:
sudo /mystic/mis shutdown ; sleep 5 ; sudo /mystic/mis daemon
works from anywhere (not just mystic directory). I generally add commands to

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

MUTIL MAILIN.INI|MUTIL MAILOUT.INI
going to /mystic directory and running commands from prompt are successful. Weekdays are set to YES
Active flag - yes, it is YES.

What are you typing on the command line and is it any different? Your tag line shows Linux/64. If so then the more common is:
./mutil mailout|./mis poll 21:1/100|mailin.ini
for a full poll. Remember commands need to come from somewhere
(./=current directory). To setup you get the mail setup to go out, poll, then move the mailin from the poll. I have one that does ./mis poll
forced but that seem to error were 21:1/100 (FSXNET) doesn't. Any
changes to ./mis commands take a reboot of mis. For most sudo ./mis shutdown ; sudo ./mis daemon will work on most. The Pi (at least Pi3) is slower so I find: sudo /mystic/mis shutdown ; sleep 5 ; sudo /mystic/mis daemon works from anywhere (not just mystic directory). I generally add commands to

If I remember correctly, NUKE is on a46 - I hope I'm not speaking wrong, but I think fidopoll is still the a46 option, as opposed to ./mis poll.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/01/26 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

What are you typing on the command line and is it any different? Your line shows Linux/64. If so then the more common is:
./mutil mailout|./mis poll 21:1/100|mailin.ini
for a full poll. Remember commands need to come from somewhere (./=current directory). To setup you get the mail setup to go out, po then move the mailin from the poll. I have one that does ./mis poll forced but that seem to error were 21:1/100 (FSXNET) doesn't. Any changes to ./mis commands take a reboot of mis. For most sudo ./mis shutdown ; sudo ./mis daemon will work on most. The Pi (at least Pi3) slower so I find: sudo /mystic/mis shutdown ; sleep 5 ; sudo /mystic/ daemon works from anywhere (not just mystic directory). I generally a commands to

If I remember correctly, NUKE is on a46 - I hope I'm not speaking wrong, but I think fidopoll is still the a46 option, as opposed to ./mis poll.

Both avenues (MIS POLL or FIDOPOLL) work for me.
--Nuke--

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

Both avenues (MIS POLL or FIDOPOLL) work for me.
--Nuke--

Me too, because I made a Linux .sh script for 'fidopoll' just in case there was any old code that needed it/called it... it would still work because my script passes the data to ./mis poll. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/01/26 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)