| Author |
 Topic  |
|
|
allan
Starting Member
31 Posts |
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
|
RUlmer
Moderator
USA
417 Posts |
 Posted - 12/24/2012 : 10:11:31
|
P.S.
(This may be a double post, because I posted it once, and even though the page said it was posted the reply did not appear on the list. ????)
He (Allan) was not alone with the problem. I likewise could not access this support forum, nor could I load my own forum. This went on from the morning of the 21st till the evening of the 23rd. I tried to contact Admin, but was unable to login to send a message.
A few times, by waiting longer than 60 seconds the support forum would load, but I was unable to return to the logged in side of the program (the page just set there trying to navigate back to the forum's main page).
Something makes me suspect the problem was related to the sever in Tampa, Florida, but I don't know for sure that is where the problem related from.
Note:
another ForumCo forum that I'm a member of (SCHH Computer Club) did work these last few days, but somewhat slow. However, back when the storm "Sandy" was going on, and there was a cyber attack on Tampa's sever (from China) going on, that other forum (SCHH) was able to work then as well, even when I couldn't access my own forum or ForumCo's Support Forum at that time either.
I post this to let you know that the problem was wider spread than just what Allan experienced and posted about.
The previous similar incident I mentioned was back on Oct. 30, and posted about on Nov. 1. As with this last incident, some ForumCo forums in the Midwest of the U.S. were only partly working, but others not at all. This latest outage was very similar to that one back on Oct. 30.
See this topic for info about that incident;
You must be logged in to see this link.
I'm not sure how to "run a traceroute", or I'd do so for you; please advise |
Edited by - RUlmer on 12/24/2012 12:45:52 |
 |
|
|
RUlmer
Moderator
USA
417 Posts |
Posted - 12/24/2012 : 10:25:46
|
I now know how to run a traceroute, but because I'm not having the problem with the outage now, I don't know that I'll be able to see what happened back before at the time I couldn't access the forum(s)?
Next time it happens, I'll do a traceroute for you. 
|
|
|
|
allan
Starting Member
31 Posts |
Posted - 12/24/2012 : 18:58:03
|
Yes I do know how to run a traceroute but I don't think it was a routing problem. Members in the UK, Denmark, Greece, France Australia and the USA couldn't access the forum.
The server on this and at least two other forums was taking between 60 and 120 seconds to generate pages. This was fairly typical:
As RUlmer pointed out, it's happened before. |
http://symivisitor.forumco.com |
|
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
|
allan
Starting Member
31 Posts |
Posted - 12/28/2012 : 07:24:59
|
Err OK. I'm still puzzled about why routing problems should affect the time taken to generate pages. 
If it helps, page generation times varied between 60 and 120 seconds but the vast majority of the time it was either very close to 60 seconds or very close to 90 seconds as in the example I posted.
Also, there were Internal Server Error 500 messages at times and any attempt to post or send a PM timed out.
Traceroute:
quote:
Tracing route to forumco.com [68.233.244.203]
over a maximum of 30 hops:
1 11 ms 8 ms 18 ms cpc1-hali5-2-0-gw.barn.cable.virginmedia.com [94.171.164.1]
2 10 ms 13 ms 8 ms brad-core-2a-xe-021-605.network.virginmedia.net [81.97.81.49]
3 10 ms 14 ms 7 ms manc-bb-1c-ae7-0.network.virginmedia.net [81.97.80.117]
4 11 ms 11 ms 12 ms manc-bb-1b-ae6-0.network.virginmedia.net [213.105.159.89]
5 13 ms 19 ms 27 ms popl-bb-1a-as4-0.network.virginmedia.net [212.43.162.85]
6 25 ms 24 ms 15 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]
7 24 ms 24 ms 24 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
8 27 ms 21 ms 27 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.117.15.5]
9 39 ms 32 ms 37 ms te0-0-0-7.ccr22.ams03.atlas.cogentco.com [130.117.2.65]
10 28 ms 44 ms 27 ms te0-4-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.58.70]
11 95 ms 94 ms 92 ms te0-6-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.221]
12 105 ms 109 ms 105 ms te0-7-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.44.53]
13 103 ms 101 ms 124 ms te0-2-0-2.ccr22.dca01.atlas.cogentco.com [154.54.26.169]
14 121 ms 121 ms 119 ms te0-0-0-3.ccr22.atl01.atlas.cogentco.com [154.54.28.218]
15 234 ms 200 ms 204 ms te3-2.ccr01.jax01.atlas.cogentco.com [154.54.30.26]
16 129 ms 200 ms 226 ms te4-2.ccr01.mco01.atlas.cogentco.com [154.54.29.218]
17 298 ms 203 ms 203 ms te4-3.ccr01.tpa01.atlas.cogentco.com [154.54.47.186]
18 129 ms 130 ms 127 ms 38.104.150.70
19 129 ms 130 ms 132 ms ve225.fesxv26.tpa.hivelocity.net [206.51.235.210]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
|
http://symivisitor.forumco.com |
|
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
Posted - 12/31/2012 : 11:18:09
|
Thanks.
I have gone through the web server logs and identified some suspicious traffic from two isp's notorious for hosting spam bots. I have installed software designed to prevent them from taking up too much resources and also our ISP has installed a hardware solution to prevent denial of service traffic.
If you notice anything strange, as always post as much info as you can on these forums, or email it to me. |
Padraic,
ForumCo Support
www.forumco.com
Helpdesk Knowledgebase Rate ForumCo @ Hotscripts Rate ForumCo @ Cgi-Resources
Please provide:
* error messages * direct link to your forum * any possibly helpful information. |
|
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
|
allan
Starting Member
31 Posts |
Posted - 01/01/2013 : 09:58:41
|
Thanks for your efforts Padraic.
The forums were unusable again today, this time just for a couple of hours around 12.00UTC.
Traceroutes were similar whether the site is working or not:
Working:
Tracing route to mail.forumco.com [68.233.244.203]
over a maximum of 20 hops:
1 9 ms 16 ms 9 ms cpc1-hali5-2-0-gw.barn.cable.virginmedia.com [94.171.164.1]
2 8 ms 10 ms 10 ms brad-core-2a-xe-021-605.network.virginmedia.net [81.97.81.49]
3 20 ms 11 ms 8 ms manc-bb-1c-ae7-0.network.virginmedia.net [81.97.80.117]
4 11 ms 9 ms 8 ms manc-bb-1b-ae6-0.network.virginmedia.net [213.105.159.89]
5 16 ms 14 ms 15 ms popl-bb-1a-as4-0.network.virginmedia.net [212.43.162.85]
6 15 ms 15 ms 24 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]
7 22 ms 34 ms 21 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
8 23 ms 23 ms 24 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.117.15.5]
9 22 ms 24 ms 23 ms te0-5-0-6.ccr22.ams03.atlas.cogentco.com [154.54.73.193]
10 35 ms 36 ms 27 ms te0-4-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.58.70]
11 96 ms 95 ms 95 ms te0-6-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.221]
12 104 ms 104 ms 103 ms te0-7-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.44.53]
13 107 ms 100 ms 111 ms te0-4-0-2.ccr22.dca01.atlas.cogentco.com [154.54.42.25]
14 130 ms 119 ms 120 ms te0-0-0-3.ccr22.atl01.atlas.cogentco.com [154.54.28.218]
15 127 ms 127 ms 120 ms te3-2.ccr01.jax01.atlas.cogentco.com [154.54.30.26]
16 130 ms 131 ms 132 ms te4-2.ccr01.mco01.atlas.cogentco.com [154.54.29.218]
17 137 ms 123 ms 124 ms te4-3.ccr01.tpa01.atlas.cogentco.com [154.54.47.186]
18 127 ms 154 ms 129 ms 38.104.150.70
19 130 ms 132 ms 148 ms ve225.fesxv26.tpa.hivelocity.net [206.51.235.210]
20 * * * Request timed out.
Site down:
Tracing route to mail.forumco.com [68.233.244.203]
over a maximum of 20 hops:
1 11 ms 30 ms 15 ms cpc1-hali5-2-0-gw.barn.cable.virginmedia.com [94.171.164.1]
2 9 ms 7 ms 20 ms brad-core-2a-xe-021-605.network.virginmedia.net [81.97.81.49]
3 8 ms 7 ms 8 ms manc-bb-1c-ae7-0.network.virginmedia.net [81.97.80.117]
4 15 ms 7 ms 7 ms manc-bb-1b-ae6-0.network.virginmedia.net [213.105.159.89]
5 137 ms 61 ms 16 ms popl-bb-1a-as4-0.network.virginmedia.net [212.43.162.85]
6 14 ms 15 ms 16 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]
7 23 ms 21 ms 41 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
8 23 ms 23 ms 24 ms te0-7-0-10.ccr21.ams04.atlas.cogentco.com [130.117.15.5]
9 23 ms 31 ms 32 ms te0-0-0-7.ccr22.ams03.atlas.cogentco.com [130.117.2.65]
10 29 ms 28 ms 27 ms te0-0-0-7.ccr22.lpl01.atlas.cogentco.com [154.54.37.106]
11 102 ms 94 ms 93 ms te0-6-0-4.ccr22.bos01.atlas.cogentco.com [154.54.85.221]
12 114 ms 106 ms 101 ms te0-7-0-3.ccr22.jfk02.atlas.cogentco.com [154.54.44.53]
13 109 ms 116 ms 111 ms te0-2-0-2.ccr22.dca01.atlas.cogentco.com [154.54.26.169]
14 121 ms 128 ms 120 ms te0-0-0-3.ccr22.atl01.atlas.cogentco.com [154.54.28.218]
15 120 ms 120 ms 119 ms te3-2.ccr01.jax01.atlas.cogentco.com [154.54.30.26]
16 131 ms 131 ms 131 ms te4-2.ccr01.mco01.atlas.cogentco.com [154.54.29.218]
17 124 ms 124 ms 123 ms te4-3.ccr01.tpa01.atlas.cogentco.com [154.54.47.186]
18 129 ms 137 ms 143 ms 38.104.150.70
19 140 ms 134 ms 132 ms ve225.fesxv26.tpa.hivelocity.net [206.51.235.210]
20 * * * Request timed out.
One thing I did notice on this occasion was that for part of the time DNS lookups for forumco didn't work:
lookup failed 68.233.244.203
Could not find a domain name corresponding to this IP address.
lookup failed forumco.com
Could not find an IP address for this domain name.
I don't know if that helps you diagnose the problem. |
http://symivisitor.forumco.com |
|
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
|
allan
Starting Member
31 Posts |
|
|
allan
Starting Member
31 Posts |
Posted - 02/03/2013 : 09:49:14
|
....and the problems are back. For a few hours on January 20th when the forumco domain was unreachable again and now the best part of two days when the forums were unusable with 90 second page loads:
The problem lasted from sometime overnight (UTC) 1st - 2nd February until around 14.30 UTC 3rd February.
For most of the time it was taking 90 seconds to load our forum and 60 seconds for this one. The timings were fairly consistent. Perhaps the difference is to do with the relative sizes of two databases? Maybe that's a clue to what's going on?
I hope you can find the cause this time, our users are getting restive. |
http://symivisitor.forumco.com |
|
|
|
Admin
ForumCo Administrator
Éire
4092 Posts |
|
| |
Topic |
|
Very long outage
