Hello There,

Just an FYI.

It seems that the Fsxnet hub (21:1/100) is down as I haven't been able to connect in the last 18 hours. I have informed Paul and he suspects that the hub
has crashed. He is out of town for three days and isn't able to restart it till
he returns.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The Ouija Board (1:282/1031)

On 01/18/18, Jeff Smith said the following...

It seems that the Fsxnet hub (21:1/100) is down as I haven't been able to connect in the last 18 hours. I have informed Paul and he suspects that the hub has crashed. He is out of town for three days and isn't able to restart it till he returns.

He had been having intermittent issues for the past couple weeks with MIS hanging and no longer accepting incoming connections on the hub node in particular. The other nodes he has on the same system are still responding so this is probably related to that.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

He had been having intermittent issues for the past couple weeks with MIS hanging and no longer accepting incoming connections on the hub node in particular. The other nodes he has on the same system are still
responding so this is probably related to that.

I think what he did was he moved back to an older version (A36?) that was known to crash because he was having an issue where a port would stop accepting connections.

--- Mystic BBS v1.12 A39 2018/01/18 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Hello Static!

19 Jan 18 01:16, you wrote to me:

It seems that the Fsxnet hub (21:1/100) is down as I haven't been
able to connect in the last 18 hours. I have informed Paul and he
suspects that the hub has crashed. He is out of town for three
days and isn't able to restart it till he returns.

He had been having intermittent issues for the past couple weeks with
MIS hanging and no longer accepting incoming connections on the hub
node in particular. The other nodes he has on the same system are
still responding so this is probably related to that.

I was aware that Paul ran several installs of Mystic on the same PC. I did check
and was able to connect to the other Mystic nodes. Which indicated that only the
(21:1/100) install of Mystic seems to be affected. Hopefully when A39 is released
it will deal with the MIS issues that Paul has been having.


Jeff


--- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: The Ouijaboard II - Anoka, MN (1:282/1032)

Jeff Smith wrote to All <=-

Hello There,

Just an FYI.

It seems that the Fsxnet hub (21:1/100) is down as I haven't been able
to connect in the last 18 hours. I have informed Paul and he suspects
that the hub has crashed. He is out of town for three days and isn't
able to restart it till he returns.

Bummer, Murphy strikes again. Yeah, I will have to setup a cross link to another net. :)


... I don't do drugs. I get the same effect just standing up fast.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Static wrote to Jeff Smith <=-

He had been having intermittent issues for the past couple weeks with
MIS hanging and no longer accepting incoming connections on the hub
node in particular. The other nodes he has on the same system are still responding so this is probably related to that.

This is where if he ran Linux, he could fix it remotely with a SSH login. ;)


... DISK ERROR: DISK ERROR: DISK ERROR: @$%#&%!! *WHACK* C:\>
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Hello Tony,

It seems that the Fsxnet hub (21:1/100) is down as I haven't been able
to connect in the last 18 hours.

Bummer, Murphy strikes again. Yeah, I will have to setup a cross link to another net. :)

I have contemplated a similar thought myself.


Jeff


--- BBBS/Li6 v4.10 Toy-3
* Origin: The Ouija Board (1:282/1031)

On 01/19/18, g00r00 pondered and said...

He had been having intermittent issues for the past couple weeks with hanging and no longer accepting incoming connections on the hub node particular. The other nodes he has on the same system are still responding so this is probably related to that.

I think what he did was he moved back to an older version (A36?) that
was known to crash because he was having an issue where a port would
stop accepting connections.

Managed to remote in and restart 1/100 (I am still on the road for another 36 hours) 1/101 was fine and is running the ver as per tearline. 1/100 is
running A38 :( Have zipped up some logs for you for next poll :)

Thanks everyone and sorry for the hassles... Murphy's law indeed!

We will need to look at some further interlinking of systems etc. to reduce single point dependency. More in the coming days... will chat about this in fsx_gen

Best, Paul

Best, Paul


`I'm not expendable, I'm not stupid, and I'm not going' - Kerr Avon, Blake's 7

--- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Jeff Smith wrote to Tony Langdon <=-

Bummer, Murphy strikes again. Yeah, I will have to setup a cross link to another net. :)

I have contemplated a similar thought myself.

Well, I could open a link with both of my systems. I believe Synchronet handles dupes well, Mystic does, at least for small to moderate traffic flows.


... NO CARRIER? How are we gonna land this modem?
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Paul Hayton wrote to g00r00 <=-

Managed to remote in and restart 1/100 (I am still on the road for
another 36 hours) 1/101 was fine and is running the ver as per
tearline. 1/100 is running A38 :( Have zipped up some logs for you for next poll :)

Nice work. :)

Thanks everyone and sorry for the hassles... Murphy's law indeed!

Stuff happens, that's half the fun. :)

We will need to look at some further interlinking of systems etc. to reduce single point dependency. More in the coming days... will chat about this in fsx_gen

Now tht I'm back up and running, count me in. I have both Mystic and Synchronet at the ready.


... THE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

This is where if he ran Linux, he could fix it remotely with a SSH
login. ;)

You could always SSH in or RDP in with Windows too.

--- Mystic BBS v1.12 A39 2018/01/18 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

g00r00 wrote to Tony Langdon <=-

This is where if he ran Linux, he could fix it remotely with a SSH
login. ;)

You could always SSH in or RDP in with Windows too.

True, though I found SSH to be of limited use on Windows, and GUI protocols have a lot more overhead, but yes it can work.


... Say pistachios ... it's impolite to say nuts.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

He had been having intermittent issues for the past couple weeks with MIS hanging and no longer accepting incoming connections on the hub node in particular. The other nodes he has on the same system are still
responding so this is probably related to that.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)

I've noticed in 1.12 A38 if a user drops out of the system improperly the
node will not recycle like it should causing a ghost user.
Hopefully this issue will be resolved soon.

outwestbbs.com - door games - files -running on a raspberry PI 2

--- Mystic BBS v1.11 (Raspberry Pi)
* Origin: Dogtown BBS -= bbs.kiwi.net =- (1:218/520)