Tracing route to 65-254-250-101.yourhostingaccount.com [65.254.250.101]
1 <1 ms <1 ms <1 ms wrt55ag [xx.x.x.xxx]
2 1 ms <1 ms <1 ms eq-660r [xx.x.x.xxx]
3 8 ms 8 ms 7 ms gateway [xx.x.xxx.xxx]
4 7 ms 8 ms 8 ms tn-76-5-159-229.sta.embarqhsd.net [76.5.159.229]
5 39 ms 38 ms 39 ms sl-gw21-atl-6-2.sprintlink.net [160.81.212.29]
6 39 ms 38 ms 39 ms sl-bb20-atl-5-0.sprintlink.net [144.232.12.109]
7 43 ms 43 ms 43 ms sl-bb25-rly-3-0.sprintlink.net [144.232.20.175]
8 43 ms 43 ms 44 ms sl-bb24-rly-12-0.sprintlink.net [144.232.14.149]
9 45 ms 44 ms 53 ms sl-st22-ash-6-0.sprintlink.net [144.232.20.189]
10 45 ms 46 ms 49 ms te-4-2.car4.Washington1.Level3.net [4.68.111.169]
11 52 ms 54 ms 53 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]
12 53 ms 52 ms 54 ms ae-84-84.ebr4.Washington1.Level3.net [4.69.134.185]
13 59 ms 51 ms 53 ms ae-3.ebr4.NewYork1.Level3.net [4.69.132.94]
14 55 ms 54 ms 52 ms ae-94-94.csw4.NewYork1.Level3.net [4.69.134.126]
15 57 ms 53 ms 52 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
16 54 ms * 54 ms ae-5-5.car2.Boston1.Level3.net [4.69.132.249]
17 59 ms 54 ms 55 ms RCN-CORPORA.car2.Boston1.Level3.net [4.79.2.94]
18 53 ms 58 ms 54 ms ge5-1.aggr2.sbo.ma.rcn.net [207.172.15.152]
19 55 ms 55 ms 55 ms 207.172.31.46
20 57 ms 58 ms 56 ms 3.225.148.207.static.yourhostingaccount.com [207.148.225.3]
21 55 ms 54 ms 54 ms 65-254-250-101.yourhostingaccount.com [65.254.250.101]
Trace complete.
Life's 3 rules: 1. Stuff happens 2. Stuff happens on a regular basis 3. Better get used to the first two... (not the actual saying but you get the drift)
It's still working a bit erratic but at least it doesn't seem to be totally non-resonsive like it's been the past couple of days. This definitely looks like a server-side hiccup.
"Experience is something you don't get until just after you need it"
I'm using pHpBB3 on my server dont have many users on it but ill look thru and see if I can find any cache settings
Life's 3 rules: 1. Stuff happens 2. Stuff happens on a regular basis 3. Better get used to the first two... (not the actual saying but you get the drift)
Never mind. It is an intermittent problem. Trying to get here from the email notification took a minute or so. This problem comes and goes. Clearing the cache might have helped, but it is not the problem.
"Experience is something you don't get until just after you need it"
Oh ok just trying to help if I can I ever set mine up to use a self-signed SSL.
Life's 3 rules: 1. Stuff happens 2. Stuff happens on a regular basis 3. Better get used to the first two... (not the actual saying but you get the drift)
Thats Powweb for you they stink. Its worse for me since I gotta go across country to get there. I get quite a few time outs myself, unfortunately its related to their server I don't think there is anything I can do about it.
I logged into SQL and trimmed the fat sorta speak out of the DB. Before it was 20mb+ now its a little over 12mb so that might help speed things along. I can tell its a little bit faster already. I also upped the amount of memory the scripts can use to 40mb a script and increased the time outs.
Lanik, on mine back when we first had those inital install issues i bumped mine upto 64mb if memory serves default was set at 16mb or 20mb, 64mb out of 2gb aint much to miss
Life's 3 rules: 1. Stuff happens 2. Stuff happens on a regular basis 3. Better get used to the first two... (not the actual saying but you get the drift)
Yes from what I can tell its limited in php.ini file, I can edit it and set the size to whatever I desire. I have no idea what the limit is and I'm afraid to set it too high and have something crash, so I guess we'll play it by ear and if it gets worse I'll up the memory limit per script to 64 the default is pitiful 16.
Thanks I've stumbled onto something interesting. Powweb uses phpMyAdmin 2.8.0 and its god damn slow POS. I was reading their forums and they are suggesting using MQA (MySQL Quick Admin) http://www.mysqlquickadmin.com I've installed it and it works very good so far I like it. Now I don't have to go through gazillion menus just to get the my DB.
It's back to being "on or off" here again. It seems to be a database problem more than a connection problem.
The way it seems to happen is that it DOES connect to the host ok .... it just freezes up when the database is trying to be called. I'm not sure what the problem would be as I am not an expert in this field by any means. It seems to be an intermittent problem in calling the db though ... not the site itself.
"Experience is something you don't get until just after you need it"
I used to run check, optimize and repair tables from right within phpMyAdmin. You can always give that a shot and see if it helps. For 2x I had the maintenance mod, I don't remember for sure but I thought phpBB3 has the maintenance mod built into the ACP.
Unrelated to the software changes, as this happens for a couple of days already:
Initial forum page loading times are very high for me, at around 20-30 seconds, sometimes even timeouting (is this even a word? ).
Subsequent pages come in a bit faster, but the whole forum still feels rather sluggish.
@Lanik:
The forum was hanging up so bad lately that I did maintenance in the ACP index. I did the normal, but I also ran the one thing that hadn't been done .... "Resynchronise dotted topics".
After I ran that, the forum was flying faster than it EVER has. Go figure.
Hope it wasn't just a coincidence ... but I guess we will see.
"Experience is something you don't get until just after you need it"
I narrowed it down with the slow database response. I have another database driven tool that access it and I see the same thing as well which leads me to believe something with the way they run their database server isn't right. I'm actually considering switching to another host. Not until some time in the first 2 months of next year and if I do decide to go that route I will take advantage of some of the free trials they have and play around with their tools and see how things are then. Probably going to put up another test board with a copy of what we have here and give it a go for a few weeks.
What it does is changes the indexes in the database from what I'm able to gather. Every little thing we do on this site has an affect on the database. Some times there are bunch of stale entries that are no longer needed by doing that little bit of "maintenance" you're forcing the database to dump its garbage. Once its done everything can be located promptly since the database doesn't have to parse any data that's been removed by now.
Also I tracked down the error message you sent me earlier about he max connections and again it has to do with the same thing poor garbage collection.