Greetings,

Sorry to keep posting about this but the chaos continues, this time I
witnessed it happen. On MIS screen I watched it poll my fido hub then it returned RES:255, so I went into event manager and sure enough it wiped out
my entry for scinet and replaced it with duplicate fido event? Looking in
the MIS logs you can see that It only polls three networks instead of 4?
Mar 31 10:25:36 LINKS:
- Mar 31 10:25:36 Node 2 1:340/400@fidonet
- Mar 31 10:25:36 Node 1 21:1/100@fsxnet
- Mar 31 10:25:36 Node 3 46:1/156@agoranet
! Mar 31 10:25:36 Import from c:\mystic\echomail\in\
+ Mar 31 10:25:36 Extracting 837d4200.tu0
- Mar 31 10:25:36 unzip -oqqjC "c:\mystic\echomail\in\837d4200.tu0" "*.pkt" d c:\mystic\temputil\
+ Mar 31 10:25:36 Importing 837d4232.pkt (77:1/100 to 77:1/130)
+ Mar 31 10:25:36 Import #24 to SCIWAREZ
! Mar 31 10:25:36 Import from c:\mystic\echomail\in\unsecure\
+ Mar 31 10:25:36 Results: 1 echo, 0 net, 0 dupes, 0 tossed in 0.14s
+ Mar 31 10:25:36 Shutdown Normal (0)

Here is what it does again in events
From:
YES Hourly Poll FsxNetHub 00:05
Yes Hourly Poll Fidonet 00:09
Yes Hourly Poll Scinet 00:07
Yes Hourly Poll Agoranet 00:04

To:

YES Hourly Poll FsxNetHub 00:05
Yes Hourly Poll Fidonet 00:09
Yes Hourly Poll Fidonet 00:09
Yes Hourly Poll Agoranet 00:04

Driving me a little crazy over here

Nitro

--- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
* Origin: Abacus BBS (1:340/202)

Re: MIS errors continue
By: Rick Smith to All on Tue Mar 31 2020 10:37:20

Sorry to keep posting about this but the chaos
continues, this time I witnessed it happen. On MIS
screen I watched it poll my fido hub then it
returned RES:255, so I went into event manager and
sure enough it wiped out my entry for scinet and
replaced it with duplicate fido event? Looking in

this is smelling like possibly an off-by-one bug or similar... when the event records gets adjusted to show it has run, the rewrite writes to the wrong record... that's just an eWAG, though...

curious that no one else is reporting it here in fidonet but that could be because they're all reporting it on another FTN... if they're even noticing it at all...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

curious that no one else is reporting it here in fidonet but that could
be becau se they're all reporting it on another FTN... if they're even noticing it at all ...

I encountered something similar to this--specifically with the Event Editor--but I eventually chalked it up to my own user error (not saying thats the case here!) -- but in my case, I was making changes to shell events, but
i actually *think* I was hitting ESC to exit instead of hitting RETURN
first (ugh) to save, so it appeared that my edit was "undone" when I went
back into -cfg... At least that's what I think happened :)

|15 ÜÜÜ |15Alpha |14Þ
|15ÞßÛ|07ßÝ |07Card & Claw BBS |14ÜÝ
|15 ²ß|07Û |08cardandclaw.com:8888 |06Þ

--- Mystic BBS v1.12 A46 2020/03/26 (Windows/64)
* Origin: Card & Claw BBS | Berkeley, CA | Sysop: Alpha (1:218/410)

curious that no one else is reporting it here in fidonet but that could
be because they're all reporting it on another FTN... if they're even noticing it at all...

I'm not noticing this type of error at my location and I'm running Mystic a46 for Linux/x64.

--- Mystic BBS v1.12 A46 2020/03/18 (Linux/64)
* Origin: monterey bbs (1:218/820)

thats the case here!) -- but in my case, I was making changes to shell events, but i actually *think* I was hitting ESC to exit instead of hitting RETURN first (ugh) to save, so it appeared that my edit was

I thought the very same thing at first, then I started taking pictures of it each time I corrected it so cant be that... It is starting to drive me a
little nuts... I see in the prealpha directory there is an MIS2 should I
maybe give that a go?

Rick

--- Mystic BBS v1.12 A46 2020/03/26 (Windows/32)
* Origin: Abacus BBS (1:340/202)

On 2020-03-31 03:35:44 +0000, Ryan Fantus said:

curious that no one else is reporting it here in fidonet but that could be because they're all reporting it on another FTN... if they're even noticing it at all...

I'm not noticing this type of error at my location and I'm running Mystic a46 for Linux/x64.

Neither am I.
--
frank // netsurge
disksh0p!bbs % bbs.diskshop.ca % mystic goodness
SciNet ftn hq % https://scinet-ftn.org

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)