I know I've posted this before, but is anyone else having issues with Mystic refusing telnet connections whenever MUTIL is being used?

This has only started happening with a39. Yes, I'm running MIS as admin, it happened with or without admin access. This is on Windows 7 x86, btw.

Here's a snippet of the log when it happens:

------------------- Node 1 (Mystic v1.12 A39 2018/04/21)
2018.06.21 20:52:44 Connect from 192.168.1.1 (WTFOMGLOLLERSKA)
2018.06.21 20:52:44 Unable to access users file
2018.06.21 20:52:44 Shutting down

Maybe coincidentally there was some weird issue with my users.dat file where
I had two entries, both at user index 1 after upgrading to a39, and just last week I tried to log on, only to find out the users.dat file was completely missing. Had to restore from a backup.

I'm really hoping it's not a corrupt user file, I'd hate to have to delete it and start fresh. I only keep backups from two months ago, and this has been going on for a while.

Anyone else with this issue?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

On 06/21/18, maskreet said the following...

I know I've posted this before, but is anyone else having issues with Mystic refusing telnet connections whenever MUTIL is being used?

It happens on my system as well, I never really noticed this before though.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)

On 06/22/18, Necromaster said the following...

On 06/21/18, maskreet said the following...

I know I've posted this before, but is anyone else having issues with Mystic refusing telnet connections whenever MUTIL is being used?

It happens on my system as well, I never really noticed this before

Okay, so I'm not going nuts, that's good to know. If it's happening to you as well, I'm guessing g00r00 did something with locking the users.dat file while MUTIL was running? Dunno why.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

Okay, so I'm not going nuts, that's good to know. If it's happening to
you as well, I'm guessing g00r00 did something with locking the
users.dat file while MUTIL was running? Dunno why.

It does not really bother me but may bother users thinking the system is down :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)

On 06/21/18, maskreet pondered and said...

I know I've posted this before, but is anyone else having issues with Mystic refusing telnet connections whenever MUTIL is being used?

Just tried to repro this with A39 under Windows 7 (32 bit) but could not.

I forced my nightly maint to run (takes about 3-5 mins) the logged in a few times and posted stuff without problem.

The only issue I saw was MUTIL borking with a RTE 1 which I take it was
because it could not run to export/import echomail I was posting / getting as it was currently busy with the nightly maint.

mis.txt

[snip]

+ 2018.06.23 21:16:31 EVENT Removing: c:\bbs\mystic\semaphor\echomail.out
+ 2018.06.23 21:16:31 EVENT Running event: Send Outgoing (Mystic)
+ 2018.06.23 21:16:31 EVENT Cmd: mutil mailout.ini
+ 2018.06.23 21:16:32 EVENT Res: 1
+ 2018.06.23 21:16:32 EVENT Cmd: fidopoll send
+ 2018.06.23 21:16:32 EVENT Res: 0

[snip]

errors.txt

[snip]

2018.23.06 21:15:09 MUTIL 000 Runtime error 1
2018.23.06 21:15:29 MUTIL 000 Runtime error 1
2018.23.06 21:16:32 MUTIL 000 Runtime error 1

[snip]

Best, Paul.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/21/18, maskreet pondered and said...

I know I've posted this before, but is anyone else having issues with Mystic refusing telnet connections whenever MUTIL is being used?

Logged this and will also pass to g00r00 when he's back :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/22/18, maskreet said the following...

Okay, so I'm not going nuts, that's good to know. If it's happening to
you as well, I'm guessing g00r00 did something with locking the
users.dat file while MUTIL was running? Dunno why.

I think it's the pack command for the users.dat so the deleted users get deleted. You can't be accessing while that is happening. I don't know if it's really locked the whole time mutil is running, but when packing users.dat it has to be locked.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: Workpoint (21:1/145.3)