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.
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. :)
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.
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.
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.
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.
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.
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 :)
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
This is where if he ran Linux, he could fix it remotely with a SSH
login. ;)
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.
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)
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 28 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 146:48:08 |
| Calls: | 2,001 |
| Calls today: | 2 |
| Files: | 11,112 |
| Messages: | 943,405 |