cancel
Showing results for 
Search instead for 
Did you mean: 

CGI Server gone TU?

N/A

CGI Server gone TU?

After coming and going all day, I can't get any sites on the CGI server now, not even:
http://cgi.support.plus.com/status/plusnet/
I can ping it OK at the moment, but even that's been failing for periods of a few seconds each, all day.
A friend of mine reports the same, so how widespread is it?
15 REPLIES
csogilvie
Grafter
Posts: 5,852
Registered: 04-04-2007

CGI Server gone TU?

Yes, it was working 20 minutes ago as I was doing some test work on the support account but it seems to have gone totally. Although its now back....
N/A

CGI Server gone TU?

Thanks Colin, yes it's back here again now. Been bad all day and it's the weekend, I hope this is not how it's going to be till the replacement :x
Plusnet Staff
Plusnet Staff
Posts: 12,169
Thanks: 18
Fixes: 1
Registered: 04-04-2007

CGI Server gone TU?

Hi,

Didn't notice any problems with CGI here, we had a couple of calls but testing from here showed it being OK. I'll keep an eye on it though, let me know if the problem re-occurs.
N/A

CGI Server gone TU?

It's still playing around today, not only the initial connection problem anymore but it keeps dissappearing for periods of 20 seconds or more:
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249

Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Reply from 212.159.3.3: bytes=32 time=51ms TTL=249
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.159.3.3: bytes=32 time=22ms TTL=249
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Reply from 212.159.3.3: bytes=32 time=19ms TTL=249
Reply from 212.159.3.3: bytes=32 time=18ms TTL=249
N/A

CGI Server gone TU?

My website on the CGI server has only been accessible around 50% of the time I have tried to visit it both via PlusNet and from work (and has been for the past few weeks).

When it's not working for HTTP, it's generally been unable to return ping responses too.
lhorwath
Grafter
Posts: 1,248
Registered: 10-04-2007

CGI Server gone TU?

Hi there,

I can ping it both internally and externally with no porblems. I note you said "50% of the time", so I will monitor it to see if I can see an issue.

regards

Luke
N/A

CGI Server gone TU?

I'm getting really fed up with this. Just wrote a whole page of data to post to my database and quess what happened?
Reply from 212.159.3.3: bytes=32 time=20ms TTL=249
Reply from 212.159.3.3: bytes=32 time=21ms TTL=249
Reply from 212.159.3.3: bytes=32 time=21ms TTL=249
Reply from 212.159.3.3: bytes=32 time=20ms TTL=249
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.159.3.3: bytes=32 time=544ms TTL=249
Reply from 212.159.3.3: bytes=32 time=82ms TTL=249
Reply from 212.159.3.3: bytes=32 time=31ms TTL=249
Reply from 212.159.3.3: bytes=32 time=18ms TTL=249
lhorwath
Grafter
Posts: 1,248
Registered: 10-04-2007

CGI Server gone TU?

I'm getting an external ping of:

PING criticalmass.plus.net (212.159.3.3): 56 octets data
64 octets from 212.159.3.3: icmp_seq=0 ttl=245 time=48.5 ms
64 octets from 212.159.3.3: icmp_seq=1 ttl=245 time=52.8 ms
64 octets from 212.159.3.3: icmp_seq=2 ttl=245 time=81.2 ms
64 octets from 212.159.3.3: icmp_seq=3 ttl=245 time=22.8 ms
64 octets from 212.159.3.3: icmp_seq=4 ttl=245 time=25.5 ms
64 octets from 212.159.3.3: icmp_seq=5 ttl=245 time=25.1 ms
64 octets from 212.159.3.3: icmp_seq=6 ttl=245 time=23.7 ms
64 octets from 212.159.3.3: icmp_seq=7 ttl=245 time=29.1 ms
64 octets from 212.159.3.3: icmp_seq=8 ttl=245 time=58.9 ms
64 octets from 212.159.3.3: icmp_seq=9 ttl=245 time=25.0 ms
64 octets from 212.159.3.3: icmp_seq=10 ttl=245 time=26.4 ms
64 octets from 212.159.3.3: icmp_seq=11 ttl=245 time=38.8 ms
64 octets from 212.159.3.3: icmp_seq=12 ttl=245 time=25.5 ms
64 octets from 212.159.3.3: icmp_seq=13 ttl=245 time=24.8 ms
64 octets from 212.159.3.3: icmp_seq=14 ttl=245 time=24.2 ms
64 octets from 212.159.3.3: icmp_seq=15 ttl=245 time=25.2 ms
64 octets from 212.159.3.3: icmp_seq=16 ttl=245 time=25.3 ms
64 octets from 212.159.3.3: icmp_seq=17 ttl=245 time=30.2 ms
64 octets from 212.159.3.3: icmp_seq=18 ttl=245 time=40.7 ms
64 octets from 212.159.3.3: icmp_seq=19 ttl=245 time=24.7 ms
64 octets from 212.159.3.3: icmp_seq=20 ttl=245 time=25.1 ms
64 octets from 212.159.3.3: icmp_seq=21 ttl=245 time=25.0 ms
64 octets from 212.159.3.3: icmp_seq=22 ttl=245 time=28.0 ms
64 octets from 212.159.3.3: icmp_seq=23 ttl=245 time=27.8 ms
64 octets from 212.159.3.3: icmp_seq=24 ttl=245 time=29.4 ms
64 octets from 212.159.3.3: icmp_seq=25 ttl=245 time=40.7 ms
64 octets from 212.159.3.3: icmp_seq=26 ttl=245 time=49.4 ms
64 octets from 212.159.3.3: icmp_seq=27 ttl=245 time=37.7 ms
64 octets from 212.159.3.3: icmp_seq=28 ttl=245 time=65.4 ms
64 octets from 212.159.3.3: icmp_seq=29 ttl=245 time=24.1 ms
64 octets from 212.159.3.3: icmp_seq=30 ttl=245 time=45.4 ms
64 octets from 212.159.3.3: icmp_seq=31 ttl=245 time=56.6 ms
64 octets from 212.159.3.3: icmp_seq=32 ttl=245 time=24.1 ms
64 octets from 212.159.3.3: icmp_seq=33 ttl=245 time=23.6 ms
64 octets from 212.159.3.3: icmp_seq=34 ttl=245 time=27.9 ms
64 octets from 212.159.3.3: icmp_seq=35 ttl=245 time=45.2 ms
64 octets from 212.159.3.3: icmp_seq=36 ttl=245 time=26.0 ms

--- criticalmass.plus.net ping statistics ---
37 packets transmitted, 37 packets received, 0% packet loss
round-trip min/avg/max = 22.8/34.5/81.2 ms
N/A

CGI Server gone TU?

Currently no ping response whatsoever. Traceroute as per:

Quote
Tracing route to cgi.plus.net [212.159.3.3]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms my.router [192.168.10.1]
2 29 ms 28 ms 29 ms lo1.plusnet.pth-ag2.plus.net [195.166.128.6]
3 28 ms 27 ms 28 ms gi1-2.vlan3.pth-gw4.plus.net [212.159.1.3]
4 29 ms 28 ms 29 ms gi4-0-23.pth-gw1.plus.net [195.166.129.217]
5 66 ms 34 ms 56 ms atm0-1-0.ptb-gw1.plus.net [195.166.129.246]
6 33 ms 41 ms 40 ms vl4.sec.ptb-gw3.plus.net [195.166.129.227]
7 * * * Request timed out.
8 * * * Request timed out.


This has been frequently the case for serveral weeks - I am hoping/expecting that the upcoming upgrades will put an end to this?
lhorwath
Grafter
Posts: 1,248
Registered: 10-04-2007

CGI Server gone TU?

PING criticalmass.plus.net (212.159.3.3): 56 octets data
64 octets from 212.159.3.3: icmp_seq=0 ttl=245 time=30.6 ms
64 octets from 212.159.3.3: icmp_seq=1 ttl=245 time=24.1 ms
64 octets from 212.159.3.3: icmp_seq=2 ttl=245 time=23.2 ms
64 octets from 212.159.3.3: icmp_seq=3 ttl=245 time=47.7 ms
64 octets from 212.159.3.3: icmp_seq=4 ttl=245 time=25.4 ms
64 octets from 212.159.3.3: icmp_seq=5 ttl=245 time=69.9 ms
64 octets from 212.159.3.3: icmp_seq=6 ttl=245 time=25.1 ms
64 octets from 212.159.3.3: icmp_seq=7 ttl=245 time=25.9 ms
64 octets from 212.159.3.3: icmp_seq=8 ttl=245 time=24.0 ms
64 octets from 212.159.3.3: icmp_seq=9 ttl=245 time=24.8 ms
64 octets from 212.159.3.3: icmp_seq=10 ttl=245 time=98.3 ms
64 octets from 212.159.3.3: icmp_seq=11 ttl=245 time=84.5 ms
64 octets from 212.159.3.3: icmp_seq=12 ttl=245 time=25.9 ms
64 octets from 212.159.3.3: icmp_seq=13 ttl=245 time=23.8 ms
64 octets from 212.159.3.3: icmp_seq=14 ttl=245 time=25.1 ms
64 octets from 212.159.3.3: icmp_seq=15 ttl=245 time=26.5 ms

--- criticalmass.plus.net ping statistics ---
16 packets transmitted, 16 packets received, 0% packet loss
round-trip min/avg/max = 23.2/37.8/98.3 ms

Again, this is from an external connection. Is it just CGI you can't ping when this happens?
N/A

CGI Server gone TU?

Quote
PING criticalmass.plus.net (212.159.3.3): 56 octets data
... Is it just CGI you can't ping when this happens?

Well after watching this with two DOS windows side by side today, one pinging 3.1 and one pinging 3.3, I can report that the Plusnet cgi server times out for periods of around 20 seconds at a time whilst the Force9 cgi server stays rock solid at around 18ms round trip at the same time. I've never seen a failed ping from the Force9 server, but the PlusNet one has been dropping out all weekend and seems to be getting worse. Very strange when they are both virtual servers on the same physical server.
But then you know all this, we've been telling you so for a month now.
N/A

CGI Server gone TU?

so its not just me suffering then
csogilvie
Grafter
Posts: 5,852
Registered: 04-04-2007

CGI Server gone TU?

Its not surprising at all actually, although they are the same physical box, they have their own resources and such, so its perfectly possible that one is being used more than another. This has been explained numerous times by staff in the past.
N/A

CGI Server gone TU?

Quite so Colin, just wondering why they couldn't have moved some accounts from PN to F9 to balance the load. I would have preffered to move and have a working site than stay put and suffer the complaints I've been getting. I'm sure many others would have volunteered as well.