Server Related Posts

albert · June 05, 2018, 01:52:08 PM

I concur, it's got that I'm here, I'm gone thing going on again. Totally pointless even trying to play until it's reset, it'll end in tears.

OldBloke · June 05, 2018, 04:58:46 PM

Restarting it now ... brb

OldBloke · June 05, 2018, 05:13:58 PM

Quote from: OldBloke;431900Restarting it now ... brb

'tis done.

Pingy · June 05, 2018, 05:49:15 PM

It's still flaky! Just kicked me out again.

OldBloke · June 05, 2018, 05:55:40 PM

Quote from: Pingy;431905It's still flaky! Just kicked me out again.

I'm getting that too. It's a network issue at Brightstar I think.

Whitey · June 05, 2018, 06:33:48 PM

Quote from: OldBloke;431906I'm getting that too. It's a network issue at Brightstar I think.

Yes, both the server and iLO are timing out. Same symptoms we had before.

Penfold · June 07, 2018, 10:38:08 AM

I think it's down again.

OldBloke · June 07, 2018, 12:21:22 PM

Quote from: Penfold;431977I think it's down again.

Is it intermittent as it was a couple of days ago?

Penfold · June 07, 2018, 12:22:38 PM

Possibly. It's up again now.

Penfold · June 07, 2018, 12:38:29 PM

Yup, it appears to be cycling off and on.

OldBloke · June 07, 2018, 12:44:33 PM

Quote from: Penfold;431982Yup, it appears to be cycling off and on.

I've let Gandy know.

Penfold · June 07, 2018, 01:50:16 PM

Thanks.

albert · June 07, 2018, 01:58:10 PM

Has to be a local network issue, ARMA, Ark and Conan processes do not respond on their respective ports simultaneously. I setup basic tcp port monitoring on uptime.com for the 3 servers and all go down on the same test. There are no down detector or other alerts I can find for Brightstar as an ISP so either they don't disclose issues or only the part we connect to is impacted by this problem.

Maybe we could check the server logs for network port issues?

Whitey · June 07, 2018, 02:08:05 PM

Nothing reported at the server level.

albert · June 07, 2018, 02:13:56 PM

Well I say for sure it isn't a problem getting into or out of their BGP autonomous system...

When it fails:

C:\Users\greig\Downloads\tracetcp_v1.0.3>tracetcp.exe 77.108.135.2:7779

Tracing route to 77.108.135.2 [77-108-135-2.brightstar.limited] on port 7779
Over a maximum of 30 hops.
1 2 ms 1 ms 1 ms 192.168.0.1
2 12 ms 9 ms 11 ms 217.103.223.1 [ip-217-103-223-1.ip.prioritytelecom.net]
3 9 ms 9 ms 11 ms 212.142.51.229
4 12 ms 12 ms 12 ms 84.116.244.37 [asd-tr0021-cr101-bundle-ether112.aorta.net]
5 * * * Request timed out.
6 13 ms 10 ms 10 ms 84.116.130.97 [nl-ams04a-ri3-ae8-0.aorta.net]
7 11 ms 13 ms 11 ms 80.249.208.36 [ae-6.r25.amstnl02.nl.bb.gin.ntt.net]
8 17 ms 13 ms 16 ms 129.250.2.102 [ae-19.r24.amstnl02.nl.bb.gin.ntt.net]
9 20 ms 18 ms 21 ms 129.250.5.1 [ae-6.r25.londen12.uk.bb.gin.ntt.net]
10 18 ms 19 ms 24 ms 129.250.4.86 [ae-28.r02.londen03.uk.bb.gin.ntt.net]
11 17 ms 18 ms 19 ms 83.231.148.10
12 20 ms 17 ms 20 ms 77.108.131.7 [77-108-131-7.brightstar.limited]
13 * * * Request timed out.
14 * *
Terminate Event Occurred.

When it works:

C:\Users\greig\Downloads\tracetcp_v1.0.3>tracetcp.exe 77.108.135.2:7779

Tracing route to 77.108.135.2 [77-108-135-2.brightstar.limited] on port 7779
Over a maximum of 30 hops.
1 2 ms 2 ms 1 ms 192.168.0.1
2 15 ms 8 ms 9 ms 217.103.223.1 [ip-217-103-223-1.ip.prioritytelecom.net]
3 10 ms 10 ms 11 ms 212.142.51.229
4 10 ms 12 ms 11 ms 84.116.244.37 [asd-tr0021-cr101-bundle-ether112.aorta.net]
5 * * * Request timed out.
6 13 ms 23 ms 14 ms 84.116.130.97 [nl-ams04a-ri3-ae8-0.aorta.net]
7 13 ms 12 ms 12 ms 80.249.208.36 [ae-6.r25.amstnl02.nl.bb.gin.ntt.net]
8 13 ms 16 ms 12 ms 129.250.2.102 [ae-19.r24.amstnl02.nl.bb.gin.ntt.net]
9 20 ms 20 ms 19 ms 129.250.5.1 [ae-6.r25.londen12.uk.bb.gin.ntt.net]
10 21 ms 19 ms 21 ms 129.250.4.86 [ae-28.r02.londen03.uk.bb.gin.ntt.net]
11 21 ms 19 ms 19 ms 83.231.148.10
12 18 ms 20 ms 19 ms 77.108.131.7 [77-108-131-7.brightstar.limited]
13 20 ms 19 ms 19 ms 77.108.135.2 [77-108-135-2.brightstar.limited]
14 Destination Reached in 21 ms. Port closed on 77.108.135.2
Trace Complete.

So on failure the tcp trace is one ip hop from our server and that means you have LAN, server hardware or server software left to eliminate.

Interesting the "Terminate Event Occurs" error is, tracetcp says, is what happens when there are firewall ports blocking the connection.

Obviously we have a firewall on the server doing it's job properly, but could it be having some issues?

This is clearly difficult to troubleshoot without the hosting company talking to us.