Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if that was
the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

|11ú|03-|09Ä|01Ä· |15K|07¡|08dd |01ÖÄÄ|09ú-|03ú |11ú
|01Ó |15W|07¡ck|08ed |01Ó

--- Mystic BBS v1.12 A69 (Android)
* Origin: SH 2.0 (21:1/169)

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if that
was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

Yes, I have seen mine crash a few times. The way to get around that is run MIS
in a looping batch file.

MIS.BAT

:START
MIS
goto START

That keeps things stable over here.

- Mark
ÿÿÿ
--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (21:1/132.0)

On 09/18/16, Kidd Wicked said the following...

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if
that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

I did hear about that happening with MIS2 before A31. I rarely have any problems with A31 and MIS only. Do you run both for ssh or rlogin? As noted because the program is made to work for Windows/Linux/Mac it would tend to
have the same problems under all OS. I suspect g00r00 was making under
Windows with the other systems on VMs, so there's more troubleshooting
done under Windows, otherwise they'd be much the same. Did it leave mis.bsy in semaphore?

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

18 Sep 16 10:45, you wrote to all:

Anyone else having an issue on windows with MiS a31 shutting down
for no reason? I added a goodip.txt file and then I noticed it. wonder
if that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

This has also happened here with both mis and mis2 serveral times. I've always had a goodip.txt .. so do not think that has anything todo with the shutting down. Going on a long MIA hiatus of sometimes weeks, months ever years is the norn for mystic. History has proven that with a lot of bbs packages in the past

20+ years. In short, simi stable is is better then dropping the hobby altoghter. Hence, we see others move on 2 .. other software.

--- GoldED+/W32-MSVC 1.1.5-b20160201
* Origin: flupH * fluph.darktech.org (21:1/105)

On 09/18/16, Weatherman said the following...

Yes, I have seen mine crash a few times. The way to get around that is run MIS in a looping batch file.

Thanks, I will do that..

|11ú|03-|09Ä|01Ä· |15K|07¡|08dd |01ÖÄÄ|09ú-|03ú |11ú
|01Ó |15W|07¡ck|08ed |01Ó

--- Mystic BBS v1.12 A69 (Android)
* Origin: SH 2.0 (21:1/169)

On 09/18/16, bcw142 said the following...

troubleshooting done under Windows, otherwise they'd be much the same.
Did it leave mis.bsy in semaphore?

it looks like it happened after a telnet session was established but not
loggin on. I looked at all the timestamps on the logs and it didnt look like anything is going on. It happened with mis not mis2. Never happened with 1.10 a62 which ran for 6 months without crashing out.it hasnt crashed since i removed the goodip.txt file though. we will see..

|11ú|03-|09Ä|01Ä· |15K|07¡|08dd |01ÖÄÄ|09ú-|03ú |11ú
|01Ó |15W|07¡ck|08ed |01Ó

--- Mystic BBS v1.12 A69 (Android)
* Origin: SH 2.0 (21:1/169)

Sunday September 18 2016 10:45, you wrote to All:

Anyone else having an issue on windows with MiS a31 shutting down
for no reason? I added a goodip.txt file and then I noticed it. wonder
if that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

I almost always run ./mis -d and never see that. Once in a while when I've made
changes I run ./mis fullscreen so I can see that what I have done is working as I planned and I have noticed that mis will crash.

I don't know why that is but running ./mis -d seems more stable to me.

... This login session: $13.99, but for you $11.88
--- GoldED+/LNX 1.1.5-b20160322
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110)

On 09/18/16, Kidd Wicked said the following...

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if
that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

I haven't noticed anything but I run mine from a batch file that calls it
again just in case.

@ECHO OFF

:Mystic
C:
CD\Mystic
MIS

GOTO MYSTIC


That way if it crashes it will restart

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

Yes, I have seen mine crash a few times. The way to get around that is run MIS in a looping batch file.

LOL, you got it first.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

On 09/18/16, Al said the following...

Sunday September 18 2016 10:45, you wrote to All:

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonde if that was the problem. I looked at the telnet logs and all the othe ones also and it didnt show anything fishy..

I almost always run ./mis -d and never see that. Once in a while when
I've made changes I run ./mis fullscreen so I can see that what I have done is working as I planned and I have noticed that mis will crash.

I don't know why that is but running ./mis -d seems more stable to me.

ya but Kid is running Windows so ./mis -d does not work. :P only for us nix folks out there. :)

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

Sunday September 18 2016 15:40, you wrote to me:

I don't know why that is but running ./mis -d seems more stable
to me.

ya but Kid is running Windows so ./mis -d does not work. :P only for
us nix folks out there. :)

Oh, I thought that Android of his was on linux.. ;)

... What bug? That's a feature
--- GoldED+/LNX 1.1.5-b20160322
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110)

On 09/18/16, Al said the following...

Sunday September 18 2016 15:40, you wrote to me:

I don't know why that is but running ./mis -d seems more stable
to me.

ya but Kid is running Windows so ./mis -d does not work. :P only for us nix folks out there. :)

Oh, I thought that Android of his was on linux.. ;)

Nah hes running windows there is NO version for ANDROID. lol He just changed it so it would read Android.

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

Kidd Wicked wrote to All <=-

@MSGID: <57DEAAC9.443.fsx_mys@freeway.apana.org.au>
@TZ: 40f0
Anyone else having an issue on windows with MiS a31 shutting down
for no reason? I added a goodip.txt file and then I noticed it. wonder
if that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

I have had MIS die on rare occasions on my R-Pi setup. Seems to be an onncasional thing across all supported platforms. A looping batch file will sort it in Windows - after MIS terminates, delete the stale semaphore then restart MIS. :)

On my Pi Linux system, I've taken it a step further. The script that monitors MIS and MIS2 also checks an "upgrade" semaphore. If this is present, MIS/MIS2 are NOT restarted, to prevent corrupting an upgrade that may be in progress. This works in conjunction with 2 other scripts. One is a script that I use to start an upgrade. This terminates MIS/MIS2, sets the semaphore backs up the system, copies the new binaries into place, then issues a reminder to manually complete the rest of the upgrade (i.e. read the docs g00r00 provided).

The other script that is a part of this system is the script to manually start MIS/MIS2. This script also deletes the "upgrade" semaphore, enabling the auto restart system.

This way, upgrades are simplified and the automatic restart of the BBS is managed automatically through the upgrade process.

There's no reason this couldn't be done in Windows. In fact, it could be whittled down to 2 batch files, the main looping batch file that runs the BBS (clear the upgrade semaphore, before entering the main loop to start the BBS). The other batch file would be the upgrade/backup one. :)


... A man takes a drink, the drink takes another, and the drink takes the man. --- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

bcw142 wrote to Kidd Wicked <=-

I did hear about that happening with MIS2 before A31. I rarely have any problems with A31 and MIS only. Do you run both for ssh or rlogin? As

I run both MIS and MIS2. MIS2 crashes more frequently, but MIS has had the occasional crash as well. I had to extend my restart system to include MIS as a result. I run telnet/SSH/rlogin/binkp in MIS2, everything else in MIS. My BBS runs on a Banana Pi.

noted because the program is made to work for Windows/Linux/Mac it
would tend to have the same problems under all OS. I suspect g00r00 was making under Windows with the other systems on VMs, so there's more troubleshooting done under Windows, otherwise they'd be much the same.
Did it leave mis.bsy in semaphore?

I have seen this issue under Linux and seen reports of it under Windows. It's not frequent, and a looping batch file/shell script will sort it.


... (Tagline under construction)
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Al wrote to Kidd Wicked <=-

I don't know why that is but running ./mis -d seems more stable to me.

I still get the (very) occasional crash with ./mis -d


... It's only a hobby ... only a hobby ... only a
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Re: Re: Shutting down
By: Vk3jed to Al on Mon Sep 19 2016 10:00 am

I don't know why that is but running ./mis -d seems more stable to
me.

I still get the (very) occasional crash with ./mis -d

I have not seen mis crash when daemonized yet. We'll need to figure out what it is that causes that.

... Is fire supposed to shoot out of it like that!?
--- SBBSecho 3.00-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110.1)

On 09/18/16, Kidd Wicked said the following...

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if
that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

mine has only done it once. it could be a run time error.

|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 A31 (Windows)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

On 09/18/16, Kidd Wicked pondered and said...

Anyone else having an issue on windows with MiS a31 shutting down for no reason? I added a goodip.txt file and then I noticed it. wonder if
that was the problem. I looked at the telnet logs and all the other ones also and it didnt show anything fishy..

No and no... goodip.txt would not be the cause of that...

Best, Paul

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

Al wrote to Vk3jed <=-

I have not seen mis crash when daemonized yet. We'll need to figure out what it is that causes that.

It's not common (can take a month or more), but it happens. I didn't start seeing MIS crashes until g00r00 stopped issuing frequent updates. Prior to then, I suspect the upgrades were simply more frequent than the average time between MIS crashes. :)


... A skydiving school is one in which you MUST be a dropout to graduate.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 09/18/16, Pequito said the following...

Nah hes running windows there is NO version for ANDROID. lol He just changed it so it would read Android.

Did not. I have a super secret copy of mystic that even g00r00 has no
clue of.. Even mystic has no idea of its existence..:)

|11ú|03-|09Ä|01Ä· |15K|07¡|08dd |01ÖÄÄ|09ú-|03ú |11ú
|01Ó |15W|07¡ck|08ed |01Ó

--- Mystic BBS v1.12 A69 (Android)
* Origin: SH 2.0 (21:1/169)

I don't know why that is but running ./mis -d seems more stable to me.

Same here.
j

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: The Gatehouse BBS (bbs.digitaglatehouse.com) (21:1/159)