Server on the fritz?

Page may contain affiliate links. Please see terms for details.
Bman

Bman

Guru
Location
Herts.
Lots of timouts right now :

(3rd post attempt)

Code: 
Pinging cyclechat.net [80.87.131.154] with 32 bytes of data:

Request timed out.
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=70ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=31ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=67ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=31ms TTL=56
Reply from 80.87.131.154: bytes=32 time=63ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=165ms TTL=56
Reply from 80.87.131.154: bytes=32 time=117ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=113ms TTL=56
Reply from 80.87.131.154: bytes=32 time=31ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=32ms TTL=56
Reply from 80.87.131.154: bytes=32 time=51ms TTL=56
Reply from 80.87.131.154: bytes=32 time=34ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=32ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=42ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=79ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=43ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Reply from 80.87.131.154: bytes=32 time=29ms TTL=56
Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=27ms TTL=56
Reply from 80.87.131.154: bytes=32 time=30ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=65ms TTL=56
Reply from 80.87.131.154: bytes=32 time=64ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=128ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=64ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=73ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=71ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=73ms TTL=56
Reply from 80.87.131.154: bytes=32 time=72ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=71ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=73ms TTL=56
Reply from 80.87.131.154: bytes=32 time=87ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=71ms TTL=56
Reply from 80.87.131.154: bytes=32 time=73ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=73ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=35ms TTL=56
Reply from 80.87.131.154: bytes=32 time=37ms TTL=56
Reply from 80.87.131.154: bytes=32 time=36ms TTL=56
Reply from 80.87.131.154: bytes=32 time=37ms TTL=56
Reply from 80.87.131.154: bytes=32 time=37ms TTL=56
Reply from 80.87.131.154: bytes=32 time=36ms TTL=56
Reply from 80.87.131.154: bytes=32 time=34ms TTL=56
Reply from 80.87.131.154: bytes=32 time=37ms TTL=56

Ping statistics for 80.87.131.154:
Packets: Sent = 129, Received = 98, Lost = 31 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 165ms, Average = 42ms
 
accountantpete

accountantpete

OAP
It's been a right pain over the last week - and is worse than ever this morning.

The site also seems a lot slower to load at the best of times.
 
Shaun

Shaun

Founder
Moderator
Thanks. I did some tests on the server last night and one point in the routing had a 5% packet loss so there's definitely a problem.

I expect the engineers will be on it tomorrow. :smile:

Cheers,
Shaun :biggrin:
 
Shaun

Shaun

Founder
Moderator
accountantpete said:
It's been a right pain over the last week - and is worse than ever this morning.

The site also seems a lot slower to load at the best of times.
Click to expand...

Ironically, I've spent the last four weeks working solidly into the early hours every night to optimise the server to work really fast at serving the new site pages.

Unfortunately this is a networking issue at the datacentre where the server is hosted.

I have an ongoing support ticket that I have used to document this weekend's outages, and hopefully they'll get it resolved as soon as possible.

Cheers,
Shaun :biggrin:
 
Shaun

Shaun

Founder
Moderator
The engineer found another server that was flooding the network causing the packet loss. That's been sorted now, so CC should be back up to speed.

Cheers,
Shaun :biggrin:
 
potsy

potsy

Rambler
Location
My Armchair
Lots of error messages for me too this evening
sad.gif
and what have you done to the hover Shaun? You numpty
whistling.gif
 
Panter

Panter

Just call me Chris...
Location
Sittingbourne, Kent
Can't get "new content" at the moment, I just get forwarded to a bright Green screen displaing this message:



"Server Error - 500

Sorry, there is a problem with the page or resource you requested.

You will automatically be returned to the CycleChat homepage.

If your browser does not refresh within 10 seconds, click here."




I'm not complaining, just saying... ;)
 
summerdays

summerdays

Cycling in the sun
Location
Bristol
potsy said:
Lots of error messages for me too this evening
sad.gif
and what have you done to the hover Shaun? You numpty
whistling.gif
Click to expand...

Yes - I've just seen a green error screen for my first time ever on new CC.

And I was wondering why the Hover had turned into "View Result".
 
Shaun

Shaun

Founder
Moderator
Yes, I've just finished reinstalling it, however it's only partially fixed as there are bits floating around in the back-end database that I still need to sort.

Ironically I can't test it from my iPhone :smile:

Are you still getting 500 (green screen) errors?

Cheers,
Shaun :biggrin:
 
You must log in or register to reply here.

Similar threads

classic33
Server Error
Replies
1
classic33
Server Error/Security Error
Replies
1
Top Bottom