Jump to content

THIS SERVER **** SUCKS


reefnjunkie

Recommended Posts

just an update.... site is still faster than it has been in the past week... but I am starting to get some lag time when going from page to page...

 

--- pnwmas.org ping statistics ---

50 packets transmitted, 17 packets received, 66.0% packet loss

round-trip min/avg/max/stddev = 129.507/132.354/143.296/3.533 ms

 

 

Here is the traceroute.... i had to finally stop it, didn't seem to be getting where it needed to go.

traceroute to pnwmas.org (67.23.230.30), 64 hops max, 52 byte packets

1 10.0.0.1 (10.0.0.1) 4.775 ms 2.243 ms 2.310 ms

2 * * *

3 ge-7-1-ur01.troutdale.or.bverton.comcast.net (68.85.242.229) 12.196 ms 10.149 ms 18.059 ms

4 68.87.218.189 (68.87.218.189) 11.959 ms 10.037 ms 12.284 ms

5 pos-0-8-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.95.93) 15.203 ms

pos-0-9-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.95.97) 15.223 ms 18.055 ms

6 te-3-3.car1.seattle1.level3.net (4.79.104.109) 45.834 ms 16.799 ms 17.529 ms

7 ae-32-52.ebr2.seattle1.level3.net (4.68.105.62) 16.304 ms 15.215 ms 15.148 ms

8 ae-2-2.ebr2.denver1.level3.net (4.69.132.54) 52.275 ms 58.456 ms 55.393 ms

9 ae-1-100.ebr1.denver1.level3.net (4.69.132.37) 52.180 ms 52.508 ms 54.703 ms

10 ae-2-2.ebr2.dallas1.level3.net (4.69.132.106) 129.247 ms 134.472 ms 122.790 ms

11 ae-73-78.ebr3.dallas1.level3.net (4.69.146.76) 123.295 ms 131.418 ms 126.169 ms

12 ae-41-41.ebr3.atlanta2.level3.net (4.69.151.178) 124.514 ms 122.077 ms 122.929 ms

13 ae-63-63.csw1.atlanta2.level3.net (4.69.148.242) 123.317 ms

ae-73-73.csw2.atlanta2.level3.net (4.69.148.254) 120.201 ms

ae-63-63.csw1.atlanta2.level3.net (4.69.148.242) 120.703 ms

14 ae-72-72.ebr2.atlanta2.level3.net (4.69.148.249) 122.545 ms

ae-61-61.ebr1.atlanta2.level3.net (4.69.148.233) 122.780 ms 131.973 ms

15 ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 136.286 ms

ae-1-8.bar1.orlando1.level3.net (4.69.137.149) 128.899 ms

ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 134.566 ms

16 hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 134.482 ms

ae-3-5.bar2.orlando1.level3.net (4.69.148.210) 138.134 ms

hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 134.160 ms

17 67-23-230-2.static.dimenoc.com (67.23.230.2) 130.289 ms 131.224 ms

ae-0-11.bar1.orlando1.level3.net (4.69.137.145) 133.660 ms

18 hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 145.852 ms 139.971 ms *

19 * 67-23-230-2.static.dimenoc.com (67.23.230.2) 136.788 ms 134.509 ms

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *

29 * * *

Link to comment
Share on other sites

Things are getting better here

 

Ping statistics for 67.23.230.30:

Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 93ms, Maximum = 110ms, Average = 97ms

 

Tracing route to pnwmas.org [67.23.230.30]

over a maximum of 30 hops:

 

1 1 ms <1 ms 1 ms 192.168.1.1

2 9 ms 11 ms 9 ms 73.90.30.1

3 9 ms 10 ms 11 ms ge-1-19-ur02.vancouver.wa.bverton.comcast.net [6

8.87.219.109]

4 14 ms 9 ms 9 ms te-3-3-ar01.troutdale.or.bverton.comcast.net [68

.85.243.249]

5 15 ms 14 ms 15 ms pos-0-8-0-0-cr01.seattle.wa.ibone.comcast.net [6

8.86.95.93]

6 30 ms 29 ms 29 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]

7 39 ms 51 ms 37 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

 

8 66 ms 58 ms 66 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]

9 56 ms 70 ms 57 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 88 ms 89 ms 73 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 74 ms 88 ms 72 ms ae-63-68.ebr3.Dallas1.Level3.net [4.69.146.68]

12 85 ms 82 ms 85 ms ae-44-44.ebr3.Atlanta2.Level3.net [4.69.151.190]

 

13 83 ms 85 ms 83 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254]

 

14 86 ms 87 ms 90 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]

 

15 91 ms 92 ms 90 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149]

16 95 ms 96 ms 96 ms HostDime.com-10G-ethernet.core1.level3.net [67.3

0.140.2]

17 92 ms 91 ms 92 ms 67-23-230-2.static.dimenoc.com [67.23.230.2]

18 98 ms 94 ms 95 ms 67-23-230-30.static.dimenoc.com [67.23.230.30]

 

Trace complete.

Link to comment
Share on other sites

Well, I think the php execution time was part of the issue.

But we can probably make it run even better. I know that both Marc and Jay are working on some issues.

Let's see how it goes.

Please keep reporting speed tests and impressions. How about double posts?

Link to comment
Share on other sites

Pinging and tracing for the PNWMAS

 

Working well this morning!

 

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\kim Vigil>ping -n 50 pnwmas.org

 

Pinging pnwmas.org [67.23.230.30] with 32 bytes of data:

 

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=109ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=109ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=114ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=113ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=110ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=111ms TTL=45

Reply from 67.23.230.30: bytes=32 time=109ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

Reply from 67.23.230.30: bytes=32 time=109ms TTL=45

Reply from 67.23.230.30: bytes=32 time=109ms TTL=45

Reply from 67.23.230.30: bytes=32 time=112ms TTL=45

 

Ping statistics for 67.23.230.30:

Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 109ms, Maximum = 114ms, Average = 110ms

Control-C

^C

C:\Documents and Settings\kim Vigil>tracert pnwmas.org

 

Tracing route to pnwmas.org [67.23.230.30]

over a maximum of 30 hops:

 

1 3 ms 1 ms 1 ms 10.0.0.1

2 * * * Request timed out.

3 13 ms 9 ms 9 ms ge-7-1-ur01.troutdale.or.bverton.comcast.net [68

.85.242.229]

4 9 ms 9 ms 9 ms 68.87.218.189

5 15 ms 12 ms 13 ms pos-0-9-0-0-cr01.seattle.wa.ibone.comcast.net [6

8.86.95.97]

6 14 ms 14 ms 14 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]

7 15 ms 24 ms 13 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62]

 

8 46 ms 50 ms 54 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]

9 51 ms 52 ms 53 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 107 ms 109 ms 107 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 107 ms 108 ms 108 ms ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76]

12 98 ms 95 ms 96 ms ae-41-41.ebr3.Atlanta2.Level3.net [4.69.151.178]

 

13 97 ms 95 ms 95 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254]

 

14 106 ms 107 ms 108 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245]

 

15 106 ms 195 ms 105 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149]

16 112 ms 109 ms 117 ms HostDime.com-10G-ethernet.core1.level3.net [67.3

0.140.2]

17 106 ms 106 ms 105 ms 67-23-230-2.static.dimenoc.com [67.23.230.2]

18 111 ms 109 ms 110 ms 67-23-230-30.static.dimenoc.com [67.23.230.30]

 

Trace complete.

 

C:\Documents and Settings\kim Vigil>

Link to comment
Share on other sites

Thanks guys for all the effort. I do not expect everything to go swimmingly all the time especially on a free site, and when I saw PNWMAS having problems I thought of you guys scrambling to fix them with sympathy... Just watched my husband deal with calPOP server disasters for a week, I know it's hard work dealing with things like this for in many cases no pay. Thank you again,

Kate

Link to comment
Share on other sites

Yes thank you thank you thank you, its seems to be back to its good ol speed.

 

Just out of curiosity what was the sit

 

The max execution time and memory of php scripts.

I think the server could work faster than now. I still see it slowing down sometimes.

Link to comment
Share on other sites

The max execution time and memory of php scripts.

I think the server could work faster than now. I still see it slowing down sometimes.

 

So was the title of my post remotely accurate-the server was not liking the execution time just something with the word "server" in it so I can, well, tell a few certain individuals "zip it" (laugh)

 

Regardless, Thanks again to all those that took time to help this ol battered ship get its self righted

Link to comment
Share on other sites

So was the title of my post remotely accurate-the server was not liking the execution time just something with the word "server" in it so I can' date=' well, tell a few certain individuals "[b']zip it[/b]" (laugh)

 

Regardless, Thanks again to all those that took time to help this ol battered ship get its self righted

 

You are correct: the server was sucking too much gigabites :)

Thanks to all of you for your patience: we went through a server migration and software update in a few months and there were some issues

Link to comment
Share on other sites

i got this database error today (Feb 28th) when i try to access messages

Database error in vBulletin 4.1.0:

 

Invalid SQL:

 

SELECT contenttype.contenttypeid AS itemid

 

FROM contenttype AS contenttype

INNER JOIN package AS package

ON package.packageid = contenttype.packageid LEFT JOIN product AS product

ON product.productid = package.productid

WHERE

1 = 1 AND (product.active = '1' OR package.productid = 'vbulletin') AND contenttype.canattach = '1';

 

MySQL Error : Incorrect information in file: './pnwmas_pnwmas/contenttype.frm'

Error Number : 1033

Request Date : Monday, February 28th 2011 @ 07:39:04 AM

Error Date : Monday, February 28th 2011 @ 07:39:04 AM

Script : http://www.pnwmas.org/forums/private.php

Referrer : http://www.pnwmas.org/forums/index.php

IP Address : 75.164.155.226

Username : stylaster

Classname : vB_Database

MySQL Version : 5.0.91-community

Link to comment
Share on other sites

i got this database error today (Feb 28th) when i try to access messages

Database error in vBulletin 4.1.0:

 

Invalid SQL:

 

SELECT contenttype.contenttypeid AS itemid

 

FROM contenttype AS contenttype

INNER JOIN package AS package

ON package.packageid = contenttype.packageid LEFT JOIN product AS product

ON product.productid = package.productid

WHERE

1 = 1 AND (product.active = '1' OR package.productid = 'vbulletin') AND contenttype.canattach = '1';

 

MySQL Error : Incorrect information in file: './pnwmas_pnwmas/contenttype.frm'

Error Number : 1033

Request Date : Monday, February 28th 2011 @ 07:39:04 AM

Error Date : Monday, February 28th 2011 @ 07:39:04 AM

Script : http://www.pnwmas.org/forums/private.php

Referrer : http://www.pnwmas.org/forums/index.php

IP Address : 75.164.155.226

Username : stylaster

Classname : vB_Database

MySQL Version : 5.0.91-community

Link to comment
Share on other sites

Something wrong with vbulletin?

 

I am having error issues as well. When I tried to refresh to new posts I get this:

 

Database Error Database error

The PNWMAS database has encountered a problem.

Please try the following:

 

* Load the page again by clicking the Refresh button in your web browser.

* Open the www.pnwmas.org home page, then try to open another page.

* Click the Back button to try another link.

 

The www.pnwmas.org forum technical staff have been notified of the error, though you may contact them if the problem persists.

 

We apologise for any inconvenience.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...