Server on the fritz?

[Sittingduck]

Hi

Might be just me but the cc forum has been inaccessible for a fair few times today, especially during the past 3 hrs or so?

Has anybody else had the same problems?

 

[Shaun]

No problems with the server as far as I know. It's been up and running without any problems since the memory upgrade and if anything is responding a little faster now.

Have you tried rebooting your router?

Cheers,
Shaun

 

[potsy]

No problems in S Mancs

 

[Sittingduck]

No problems with the server as far as I know. It's been up and running without any problems since the memory upgrade and if anything is responding a little faster now.

Have you tried rebooting your router?

Cheers,
Shaun

Hi SHaun

Yup tried that a few hours back. The connection seems ok now but noticed it was sketchy with iphone and pc (even with iphone using 3G not wi-fi). ANyway its all good now - ta

 

[HaloJ]

Hi SHaun

Yup tried that a few hours back. The connection seems ok now but noticed it was sketchy with iphone and pc (even with iphone using 3G not wi-fi). ANyway its all good now - ta

Interesting. I experienced a few outages as well and just presumed that it was the memory upgrade taking place.

 

[Sittingduck]

I had thought it might be my ISP (.BE), as there were a few other sites behaving oddly too but not all. Seems fine and dandy this morning though

 

[Cheule]

I had thought it might be my ISP (.BE), as there were a few other sites behaving oddly too but not all. Seems fine and dandy this morning though

I'm also with Be* and nothing seems out of the ordinary. Either that or I was just lucky with the page refreshes going through at exactly the right moment

 

[Danny]

I fairly regularly (once every couple of days) find that the CC server has short periods where it does not respond. Usually the problem clears within minutes (or less), but it happens often enough to make me wonder whether there is some sort of connection problem.

NB I always check whether I can access other sites, so it is not a problem at my end.

 

[Shaun]

Did it happen before we moved to the new software?

 

[Danny]

Did it happen before we moved to the new software?

Sorry only just noticed your question. The answer is I am fairly sure that it did happen before, and it is still happening to me on a fairly regular basis.

 

[Shaun]

I'm planning some more work on the database back-end in the coming weeks which may make a difference. I'll post an announcement once I've completed the work.

Cheers,
Shaun

 

[Bman]

getting loads of timeouts from here...

got a friend to double check. Its not just me :

Pinging [url="http://www.cyclechat.net"]www.cyclechat.net[/url] [80.87.131.154] with 32 bytes of data:

Reply from 80.87.131.154: bytes=32 time=28ms TTL=56
Reply from 80.87.131.154: bytes=32 time=31ms TTL=56
{snip}
Request timed out.
Reply from 80.87.131.154: bytes=32 time=67ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Reply from 80.87.131.154: bytes=32 time=64ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=66ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=60ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=67ms TTL=56
Request timed out.
Reply from 80.87.131.154: bytes=32 time=67ms TTL=56
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.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=67ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.87.131.154: bytes=32 time=65ms TTL=56

Ping statistics for 80.87.131.154:
Packets: Sent = 96, Received = 62, Lost = 34 (35% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 83ms, Average = 42ms

 

[ColinJ]

CC has been a bit iffy for me too over the past few minutes, though it seems to be okay again now.

 

[Shaun]

I'll put a support ticket in to the datacentre in case there are any issues with switches/DNS etc.

Thanks,
Shaun

 

[Shaun]

The datacentre have reported back that a switch failed a few days ago and they've re-routed traffic.

They've asked if a few of you could run "tracert www.cyclechat.net" and post the results. To do this in Windows click START > Run ... > Type "cmd" and press enter.

In the command prompt window type "tracert www.cyclechat.net" (without the quotes) and wait for it to finish. Now right-click the command window and chose Select all then click CTRL+C to copy the info.

Now post here and use CTRL+V to paste it into your reply.

Sorry to ask, but it may help if there is a problem with routing to the server.

Thanks,
Shaun