Thought I'd have a look at MIS2 but when loading it displays ERROR: Missing MIS ANSI files in DATA What files does it require or is this simply an error displayed when Mystic can't bind to the IP?

Thanks

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

Thought I'd have a look at MIS2 but when loading it displays ERROR: Missing MIS ANSI files in DATA What files does it require or is this simply an error displayed when Mystic can't bind to the IP?

It means the ANSI files for MIS are not in the the data folder. The reason they aren't is unknown to me - maybe skipping steps in an upgrade instructions or I could have forgot the instructions, etc.

There should be mis*.ans files in the DATA folder. If you don't have them, MIS cannot run. To get them back you can install a fresh install of Mystic to a temp directory and then copy mis*.ans from its DATA directory into your DATA directory.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

It means the ANSI files for MIS are not in the the data folder. The instructions or I could have forgot the instructions, etc.

They appear to be there, in fact following the instructions for upgrade the same as previous versions. Not sure why MIS2 is not seeing them, MIS runs
fine otherwise. First time I've tried to run MIS2. Looked in the temp install folder and see no difference in mis*.ans files between the temp and the
online BBS versions, same files as far as I can tell.

cheers...

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

They appear to be there, in fact following the instructions for upgrade the same as previous versions. Not sure why MIS2 is not seeing them, MIS runs fine otherwise. First time I've tried to run MIS2. Looked in the

Okay, so you should have the following files in there:

mis_status1.ans
mis_status2.ans
mis_help.ans
mis_events.ans
mis_stats.ans

If you are in Unix you'll need to make sure the ownership is correct and also the casing of the filenames are correct.

In the next alpha I am going to give a more descriptive error message so
people will know exactly which file is missing should this happen to them.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

test

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

Okay, so you should have the following files in there:
mis_status1.ans
mis_status2.ans
mis_help.ans
mis_events.ans
mis_stats.ans

I am running Windows7. Since February I have been performing backups twice a month and have looked at the backups data folders as well as the new a34 install data folder. There is no mis_stats.ans file. There is a mis_stat.ans file. However, there is a mis_stats.bak file in all the data directories in backup and the new install folder. I renamed the .bak to .ans on the
mis_stats file and MIS2 worked.

I am not up on MIS2 or how it really works so forgive my dumb
questions but...when running MIS2 there are no events. Do we run MIS2 and MIS where MIS handles events, or is MIS2 events just not implemented yet forcing us to run MIS along with MIS2?

I did create a test message in MIS2, started up MIS and MIS seems to have
sent the test message created in MIS2.

Thanks..

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

questions but...when running MIS2 there are no events. Do we run MIS2
and MIS where MIS handles events, or is MIS2 events just not implemented yet forcing us to run MIS along with MIS2?

MIS2 doesn't have events yet its probably the last thing going to be added, otherwise MIS and MIS2 would be trying to kick off the same events all of the time.

You can use both if you need MIS events (for now), or you can use Windows Task Manager for events or crontab in Linux as an alternative that isn't dependent on Mystic.

MIS2 will have the event system eventually I just need to make sure its
stable, because when the events go in MIS goes away.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Thanks g00r00z

On 12:54 28/06 , g00r00 wrote:

questions but...when running MIS2 there are no events. Do we run MIS2
and MIS where MIS handles events, or is MIS2 events just not implemented yet forcing us to run MIS along with MIS2?

MIS2 doesn't have events yet its probably the last thing going to be added, >otherwise MIS and MIS2 would be trying to kick off the same events all of the >time.

You can use both if you need MIS events (for now), or you can use Windows Task >Manager for events or crontab in Linux as an alternative that isn't dependent >on Mystic.

MIS2 will have the event system eventually I just need to make sure its >stable, because when the events go in MIS goes away.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A34 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

MIS2 doesn't have events yet its probably the last thing going to be added, otherwise MIS and MIS2 would be trying to kick off the same
events all of the time.

Understood..

Thanks for the info and software...great job!

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

On 06/28/17, g00r00 pondered and said...

MIS2 doesn't have events yet its probably the last thing going to be added, otherwise MIS and MIS2 would be trying to kick off the same
events all of the time.

I reckon the day you add that is the day you write a short util to copy MIS events across to MIS2 and you kill off MIS :)

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I reckon the day you add that is the day you write a short util to copy MIS events across to MIS2 and you kill off MIS :)

Agreed....I think we all have quite a few events running and it sure would be appreciated to have that feature.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: ENCOM BBS : encom.cloudns.org (21:2/109)

Hi Paul,

Do you have MIS2 running in a similar batch file as you have for MIS? Here is what I have for my MIS batch:

snip<=-

@ECHO OFF
C:
CD \BBS\MYSTIC

:LOOP
IF EXIST \BBS\MYSTIC\SEMAPHORE\MIS.BSY (DEL \BBS\MYTSIC\SEMAPHORE\MIS.BSY)
MIS
if errorlevel 255 goto done
if errorlevel 10 goto done
if errorlevel 1 goto done
goto crash

:crash
TIMEOUT /T 5
set T=%time:~0,5%
set crash=%date:/=-% %T::=-%
echo CRBBS MIS restarted - %crash% > restartlog.txt

IF EXIST \BBS\MYSTIC\SEMAPHORE\FIDOPOLL.BSY (FIDOPOLL KILLBUSY)

GOTO LOOP

:done

snip<=-

I would think that this would also work for MIS2, as long as the error levels are the same.

Thanks,


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

MIS2 doesn't have events yet its probably the last thing going to be added, otherwise MIS and MIS2 would be trying to kick off the same events all of the time.

I reckon the day you add that is the day you write a short util to copy MIS events across to MIS2 and you kill off MIS :)

Yep that is the plan. :) One day MIS will be gone and MIS2 will magically
have events!

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

So I've moved over from the custom telnet to mis2. We'll see how this goes.
To get around the listing issue I found with launching mystic via sudo, I'm starting mis2 on a custom port that doesn't require sudo then redirecting
from my router to this custom port.

Looks like it's working. I'm also using a script that checks every 5 minutes
if mis2 goes down.

:) Hoping for better luck this time around.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

So I've moved over from the custom telnet to mis2. We'll see how this goes. To get around the listing issue I found with launching mystic via sudo, I'm starting mis2 on a custom port that doesn't require sudo then

What is the "listing issue" you speak of? Sorry if I missed it previously

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/07/17, g00r00 said the following...

So I've moved over from the custom telnet to mis2. We'll see how this goes. To get around the listing issue I found with launching mystic v sudo, I'm starting mis2 on a custom port that doesn't require sudo th

What is the "listing issue" you speak of? Sorry if I missed it
previously

load mis with sudo. then put a command im to launch bash from a menu. then do
a ls /root .

maybe im crazy..

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

load mis with sudo. then put a command im to launch bash from a menu.
then do a ls /root .

I just tested this on my Ubuntu 14 32-bit setup and I get this:

bash: cd: /root: Permission denied

Are you sure you had your BBS directory properly owned by your BBS user and group, and that the bbs user+group cannot already access /root? Are you sure your BBS is being started as the BBS user with a sudo to root?

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

load mis with sudo. then put a command im to launch bash from a menu. then do a ls /root .

I just tested this on my Ubuntu 14 32-bit setup and I get this:

bash: cd: /root: Permission denied

Are you sure you had your BBS directory properly owned by your BBS user and group, and that the bbs user+group cannot already access /root? Are you sure your BBS is being started as the BBS user with a sudo to root?

yes to all. i cannot access ls /root in a normal ssh/bash.

im running mis with sudo.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/07/17, niter3 said the following...

load mis with sudo. then put a command im to launch bash from a menu.
then do a ls /root .

maybe im crazy..

Not crazy this is normal behavior, /root is a protected directory. If you do ls /
it will work. There is another thing you can do to elevate your permissions: Open /bin/bash, do su - bbs_user (will ask password), sudo -i (will ask
again). That should make you root it the bbs user had sudo. If they didn't
try a user that does. It will take 3 exit commands to get back to the BBS.

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

Not crazy this is normal behavior, /root is a protected directory. If
you do ls /
it will work. There is another thing you can do to elevate your permissions: Open /bin/bash, do su - bbs_user (will ask password), sudo
-i (will ask again). That should make you root it the bbs user had sudo. If they didn't try a user that does. It will take 3 exit commands to get back to the BBS.

I'm not following what you're saying. I don't want to switch users....

if I login locally to the box I don't have permissions to do a ls /root. however if I sudo ./mis2 and telnet to the bbs, launch a command shell from a menu, I'm able to ls /root. It's carrying some permissions with it....

My work around, is loading mis2 on a non standard port, and using my router
to map from outside 23 to the internal port.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/12/17, niter3 said the following...

if I login locally to the box I don't have permissions to do a ls /root. however if I sudo ./mis2 and telnet to the bbs, launch a command shell from a menu, I'm able to ls /root. It's carrying some permissions with it....

Ya, I get it now. mis2 is really running as root to be able to do that, it never drops it's root permissions. You can elevate mis to root using users
with sudo, but you weren't trying to do that, mis2 kept root permissions
which it shouldn't really do.

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

Just tried /bin/bash on both the Pi & Ubuntu 16.04 x64 Linux and neither has root permissions, your starting mystic as full root user it sounds like
rather than sudo as a regular user with sudo permissions. On the Pi I start
it as Pi and it doesn't have root permissions, on Ubuntu I start it under bcw which is my regular user account and it doesn't have root permissions either. It's something to do with the way you started mystic which seems to be as
full root like sudo -i will do with a # prompt.

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

Ya, I get it now. mis2 is really running as root to be able to do that,
it never drops it's root permissions. You can elevate mis to root using users with sudo, but you weren't trying to do that, mis2 kept root permissions which it shouldn't really do.

Sort of... I can't do everything as if I was root..

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

Found MIS2 to cause ghost connections that wouldn't terminated over time.

I've switched back to xinited telnetd.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/15/17, niter3 said the following...

Found MIS2 to cause ghost connections that wouldn't terminated over time.

I've switched back to xinited telnetd.

I don't really think it's mis or mis2 causing the problems - I think it's the hackers/crackers doing some weird stuff that causes it. Any of the older methods should still work the same, but be careful of exploits in them. The Ghost connections will terminate either with nodespy kill ghost or kill -9 on the leftover task (in Linux, likely Task Manager will kill them in Windows). Need to figure out how to find them so cron/events/scheduler will be able to kill them.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: BCW Livingroom (21:1/145.5)

Had another experience where MIS2 was holding a lock on a compressed echomail packet so that despite MUTIL running and tossing the packet, the file
remained in the inbound afterwards. i.e. MUTIL could not delete it and MIS2 held it firm.

Then I saw repeated dupes in the HUB system as this processed looped each
time MUTIL was called.

Fix was to close MIS2 then run MUTIL and the file was processed and deleted from the echomail\in

Now the thing is the file came in via MIS2 BinkP server over IPv6..

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Does anyone have suggestions for MIS2?

I've already collected some feedback and some of it I do plan to implement, but I am wondering if anyone else has comments regarding the "messages" window now containing messages from all servers, etc. Or any suggestions on how to improve the UI?

No promises that I will do anything :) But I would love to hear any ideas if anyone has them.

--- Mystic BBS v1.12 A36 2017/11/08 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/09/17, g00r00 said the following...

implement, but I am wondering if anyone else has comments regarding the "messages" window now containing messages from all servers, etc. Or any

it does get a little confusing but the scroll helps but i can see the simple version in connections tab. ;)

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A36 2017/11/07 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 11/09/17, g00r00 pondered and said...

implement, but I am wondering if anyone else has comments regarding the "messages" window now containing messages from all servers, etc. Or any suggestions on how to improve the UI?

Can you please add a display of the servers primary (and ideally a toggle option for it's secondary) AKA's at the top of the display window.

If you run (like I do 3,4,5,6 instances of MIS2) it's gets really confusing
as to which is which :)

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/07 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Can you please add a display of the servers primary (and ideally a toggle option for it's secondary) AKA's at the top of the display window.

Would the BBS name work for you?

--- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/10/17, g00r00 pondered and said...

Can you please add a display of the servers primary (and ideally a to option for it's secondary) AKA's at the top of the display window.

Would the BBS name work for you?

Yep, just something to differentiate running copies is all I ask :)

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Would the BBS name work for you?

Yep, just something to differentiate running copies is all I ask :)

Okay for starters I put it on the Window title so it will read "Mystic Internet Server (BBS Name)" but I will try to work it into the screen somewhere too.

--- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/11/17, g00r00 pondered and said...

Okay for starters I put it on the Window title so it will read "Mystic Internet Server (BBS Name)" but I will try to work it into the screen somewhere too.

Thanks :)

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 11/12/17, g00r00 pondered and said...

Thank you very much. Unfortunately that didn't show anything that the other logs haven't already shown.

I made yet another round of mis2 and fidopoll .exe files in the same place. This one won't have as much logging as the last one, but there
are some new logging areas that might expose something.

I have not moved 1/100 to this 'latest' version yet... can do so if you wish when I get home tonight (8-9 hours time from when I wrote this).

I was going to say as far as I am aware everything is working fine at my end and can send you the large logs created by the MIS2 and Fidopoll .exe files
(if you wish) later tonight my time..

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I have not moved 1/100 to this 'latest' version yet... can do so if you wish when I get home tonight (8-9 hours time from when I wrote this).

Sure, if you aren't too afraid its going to fail go for it!

MIS2 and the new BINKP and socket code could certainly use the testing.

My main goal right now is to get that open issue with IREX resolved.

--- Mystic BBS v1.12 A36 2017/11/12 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Hi g00r00,

I've noticed an issue with running MIS2 on Linux 64bit.

After it runs for about a day or so, it will stop accepting both binkd and telnet connections.

The telnet connections, on the users end, will show connecting, then will disconnect.

The binkd connections, will show 'Cannot authenticate client'

+ 16:29:26 BINKP > Connect on slot 1/6
+ 16:29:26 BINKP 1-Address 219.89.83.33
+ 16:29:26 BINKP 1-HostName Unknown
+ 16:29:26 BINKP 1-No IP2Location DB
+ 16:29:26 BINKP 1-System fsxNet Games + Usenet Gateway
+ 16:29:26 BINKP 1-SysOp Paul Hayton
+ 16:29:26 BINKP 1-Location Dunedin, New Zealand
+ 16:29:26 BINKP 1-Info NDL 115200,TCP,BINKP
+ 16:29:26 BINKP 1-Info TIME Thu, 23 Nov 2017 12:29:20 +1300
+ 16:29:26 BINKP 1-Mailer binkd/1.1a-89/Win32 binkp/1.1
+ 16:29:27 BINKP 1-Info TRF 0 9119
+ 16:29:27 BINKP 1-Cannot authenticate client
+ 16:29:27 BINKP 1-Client thread shutting down

After restarting the MIS2 server, the connection is successful:

+ 16:44:57 BINKP 1-System fsxNet Games + Usenet Gateway
+ 16:44:57 BINKP 1-SysOp Paul Hayton
+ 16:44:57 BINKP 1-Location Dunedin, New Zealand
+ 16:44:57 BINKP 1-Info NDL 115200,TCP,BINKP
+ 16:44:57 BINKP 1-Info TIME Thu, 23 Nov 2017 12:44:51 +1300
+ 16:44:57 BINKP 1-Mailer binkd/1.1a-89/Win32 binkp/1.1
+ 16:44:58 BINKP 1-Info TRF 0 9633
+ 16:44:58 BINKP 1-Authenticating 21:1/10@fsxnet by CRAM-MD5
+ 16:44:58 BINKP 1-Queued 0 files for 21:1/10@fsxnet
+ 16:44:59 BINKP 1-Receiving: 88E60102.GAL (359 bytes)
+ 16:44:59 BINKP 1-Receiving: 021B0104.503 (257 bytes)

snip<=-

+ 16:44:59 BINKP 1-Receiving: 021B0104.470 (365 bytes)
+ 16:44:59 BINKP 1-Receiving: 021B0104.469 (257 bytes)
+ 16:45:00 BINKP 1-Session ended (0 sent, 36 rcvd, 0 skip)
+ 16:45:00 BINKP 1-Client thread shutting down
+ 16:45:00 BINKP 1-Removed BUSY file: /home/dan/mystic/echomail/out/fsxnet.015/0001000a.bsy

I can usually tell when MIS2 is doing this, as the WFC screen seems to scroll up, so that I can't see the Mystic logo. I wasn't able to capture log file evidence until the MIS2.LOG file was updated more often.


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A36 2017/11/20 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I've noticed an issue with running MIS2 on Linux 64bit.
After it runs for about a day or so, it will stop accepting both binkd
and telnet connections.

I have not had it stop accepting yet on ubuntu. But i have seen some high
CPU usage by MIS2, when there doesnt seem to be anything going on with the
bbs, no users connected, no connections etc.

12060 ? Ssl 2291:43 ./mis2 DAEMON

Scott Miller
---Quickshot
----Troybbs.com

--- Mystic BBS v1.12 A36 2017/11/19 (Linux/64)
* Origin: Troy's Den * troybbs.com (21:2/134)

I have not had it stop accepting yet on ubuntu. But i have seen some
high CPU usage by MIS2, when there doesnt seem to be anything going on with the bbs, no users connected, no connections etc.

Are you using the old prealpha that had a problem with high CPU usage? :p

--- Mystic BBS v1.12 A36 2017/11/22 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)