Subj : Re: Fsxnet Hub Down.
To   : g00r00
From : Paul Hayton
Date : Sat Jan 20 2018 03:31 pm

On 01/19/18, g00r00 pondered and said...
 
 g0>  St> He had been having intermittent issues for the past couple weeks with
 g0>  St> hanging and no longer accepting incoming connections on the hub node 
 g0>  St> particular. The other nodes he has on the same system are still
 g0>  St> responding so this is probably related to that.
 g0> 
 g0> I think what he did was he moved back to an older version (A36?) that
 g0> was known to crash because he was having an issue where a port would
 g0> stop accepting connections.
 g0> 

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)

.