Jump to content

THIS SERVER **** SUCKS


reefnjunkie

Recommended Posts

Beth, get a PC.. must be a MAC issue. :) just kidding.

 

What ISP is hosting the server or servers? I keep hearing ISP's the issue. That's like saying that coral is sting my other corals. Can you help? :D

 

I have a PC and I have issues every morning with the server being busy. Really? PNWMAS is that popular every morning at 9am? LOL

Link to comment
Share on other sites

Ping got this....

 

 

Ping has started…

 

PING pnwmas.org (67.23.230.30): 56 data bytes

Request timeout for icmp_seq 0

64 bytes from 67.23.230.30: icmp_seq=1 ttl=45 time=112.934 ms

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

64 bytes from 67.23.230.30: icmp_seq=6 ttl=45 time=111.699 ms

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

 

--- pnwmas.org ping statistics ---

10 packets transmitted, 2 packets received, 80.0% packet loss

round-trip min/avg/max/stddev = 111.699/112.316/112.934/0.618 ms

Link to comment
Share on other sites

Ping got this....

 

 

Ping has started…

 

PING pnwmas.org (67.23.230.30): 56 data bytes

Request timeout for icmp_seq 0

64 bytes from 67.23.230.30: icmp_seq=1 ttl=45 time=112.934 ms

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

64 bytes from 67.23.230.30: icmp_seq=6 ttl=45 time=111.699 ms

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

 

--- pnwmas.org ping statistics ---

10 packets transmitted, 2 packets received, 80.0% packet loss

round-trip min/avg/max/stddev = 111.699/112.316/112.934/0.618 ms

 

can you do that to one of my sites?

 

www.fycracing.com

www.reefhawaii.com

 

Both are forums. I also have 3 web stores on that server.

Link to comment
Share on other sites

Ping got this....

 

 

Ping has started…

 

PING pnwmas.org (67.23.230.30): 56 data bytes

Request timeout for icmp_seq 0

64 bytes from 67.23.230.30: icmp_seq=1 ttl=45 time=112.934 ms

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

64 bytes from 67.23.230.30: icmp_seq=6 ttl=45 time=111.699 ms

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

 

--- pnwmas.org ping statistics ---

10 packets transmitted, 2 packets received, 80.0% packet loss

round-trip min/avg/max/stddev = 111.699/112.316/112.934/0.618 ms

 

That packet loss is bad. Anyone else with slowness issues seeing similar packet loss?

Link to comment
Share on other sites

The tracert does not end because of the firewall I set up a few weeks ago.

I don't think we are under attack. I just performed some analysis and it looks clean. So it was for the ISP NOC.

It does not look like a server problem to me at this point. There are only 157 connections to Apache, 38 processes right now and

2 mysql processes. Even my grandma server could handle that lol

As for the IAP problem (Internet Access Provider, so we do not confuse it with the ISP), that could be the source of the problem.

Link to comment
Share on other sites

That packet loss is bad. Anyone else with slowness issues seeing similar packet loss?

 

Yes it is bad, so I did it again...

 

Ping has started…

 

PING pnwmas.org (67.23.230.30): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

64 bytes from 67.23.230.30: icmp_seq=2 ttl=45 time=120.045 ms

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

64 bytes from 67.23.230.30: icmp_seq=5 ttl=45 time=114.517 ms

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Request timeout for icmp_seq 11

64 bytes from 67.23.230.30: icmp_seq=12 ttl=45 time=115.328 ms

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

64 bytes from 67.23.230.30: icmp_seq=16 ttl=45 time=122.075 ms

Request timeout for icmp_seq 17

Request timeout for icmp_seq 18

 

--- pnwmas.org ping statistics ---

20 packets transmitted, 4 packets received, 80.0% packet loss

round-trip min/avg/max/stddev = 114.517/117.991/122.075/3.165 ms

 

then I tried another website I frequent that works fine, but is slow... my work website...

Ping has started…

 

PING www.westsidepediatrics.com (173.164.85.9): 56 data bytes

64 bytes from 173.164.85.9: icmp_seq=0 ttl=57 time=21.276 ms

64 bytes from 173.164.85.9: icmp_seq=1 ttl=57 time=22.929 ms

64 bytes from 173.164.85.9: icmp_seq=2 ttl=57 time=21.866 ms

64 bytes from 173.164.85.9: icmp_seq=3 ttl=57 time=31.590 ms

64 bytes from 173.164.85.9: icmp_seq=4 ttl=57 time=19.558 ms

64 bytes from 173.164.85.9: icmp_seq=5 ttl=57 time=19.648 ms

64 bytes from 173.164.85.9: icmp_seq=6 ttl=57 time=17.939 ms

64 bytes from 173.164.85.9: icmp_seq=7 ttl=57 time=22.769 ms

64 bytes from 173.164.85.9: icmp_seq=8 ttl=57 time=17.613 ms

64 bytes from 173.164.85.9: icmp_seq=9 ttl=57 time=21.225 ms

64 bytes from 173.164.85.9: icmp_seq=10 ttl=57 time=18.986 ms

64 bytes from 173.164.85.9: icmp_seq=11 ttl=57 time=18.700 ms

64 bytes from 173.164.85.9: icmp_seq=12 ttl=57 time=20.966 ms

64 bytes from 173.164.85.9: icmp_seq=13 ttl=57 time=21.220 ms

64 bytes from 173.164.85.9: icmp_seq=14 ttl=57 time=20.670 ms

64 bytes from 173.164.85.9: icmp_seq=15 ttl=57 time=19.370 ms

64 bytes from 173.164.85.9: icmp_seq=16 ttl=57 time=25.711 ms

64 bytes from 173.164.85.9: icmp_seq=17 ttl=57 time=27.236 ms

64 bytes from 173.164.85.9: icmp_seq=18 ttl=57 time=21.883 ms

64 bytes from 173.164.85.9: icmp_seq=19 ttl=57 time=21.712 ms

 

--- www.westsidepediatrics.com ping statistics ---

20 packets transmitted, 20 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 17.613/21.643/31.590/3.247 ms

Link to comment
Share on other sites

Qwest

 

PING pnwmas.org (67.23.230.30): 56 data bytes

64 bytes from 67.23.230.30: icmp_seq=0 ttl=48 time=142.551 ms

64 bytes from 67.23.230.30: icmp_seq=1 ttl=48 time=143.786 ms

64 bytes from 67.23.230.30: icmp_seq=2 ttl=48 time=142.250 ms

64 bytes from 67.23.230.30: icmp_seq=3 ttl=48 time=143.468 ms

64 bytes from 67.23.230.30: icmp_seq=4 ttl=48 time=144.168 ms

64 bytes from 67.23.230.30: icmp_seq=5 ttl=48 time=144.693 ms

64 bytes from 67.23.230.30: icmp_seq=6 ttl=48 time=140.854 ms

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Request timeout for icmp_seq 11

64 bytes from 67.23.230.30: icmp_seq=12 ttl=48 time=144.391 ms

64 bytes from 67.23.230.30: icmp_seq=13 ttl=48 time=144.848 ms

64 bytes from 67.23.230.30: icmp_seq=14 ttl=48 time=145.082 ms

64 bytes from 67.23.230.30: icmp_seq=15 ttl=48 time=141.831 ms

64 bytes from 67.23.230.30: icmp_seq=16 ttl=48 time=146.536 ms

64 bytes from 67.23.230.30: icmp_seq=17 ttl=48 time=145.433 ms

64 bytes from 67.23.230.30: icmp_seq=18 ttl=48 time=144.132 ms

64 bytes from 67.23.230.30: icmp_seq=19 ttl=48 time=142.706 ms

64 bytes from 67.23.230.30: icmp_seq=20 ttl=48 time=143.232 ms

Link to comment
Share on other sites

Here are the results from my tracert. I would have had a couple more lines but it just exited by itself before I could print screen again

 

 

and if you run a 'ping pnwmas.org' do you get lots of dropped packets like Beth?

 

You can type 'cmd' from the Run line and it will open a window and leave it open until you type 'exit'

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...