Slow Speeds


#1

I’ve been encountering slow speeds on my website, and while uploading to my site. It also seems to just randomly stop working all together. So, I was wondering If theres possibly something that I’m doing wrong or if there are other people out there experiencing this problem.


#2

You’re not the only one.

I believe it’s only the pages hosted on korben.dreamhost.com, because my friend’s site on another one of their servers is working perfectly.

I hope it gets better…


#3

You could ssh to the server and run “top” to see if anyone is hogging resources. It’s not going to show you their processes but it should show you how much of the cpu is being used up (percent value).

willscorner.net


#4

Alright, good to know I’m not the only one. And I’m on Korban too so I’m guessing thats where the problem lies…I’m hoping it gets fixed soon because it’s taken me about 20 minutes to install and login to my forum.


#5

No it’s also affecting me and I’m on korban. I just got my account today and I’m trying to transfer my site over from my old server…you can guess how not fun that is with the server behaving so badly :frowning:


#6

Well while I was in ssh and transferring files over, I got a broadcast message saying the server is rebooting now so hopefully they fixed the problem :slight_smile:


#7

Weird. Something is screwed up. I usually use Level3 to connect to dreamhost. Then it switched to Global Crossing.

My traceroutes are looking crazy right now.

Traceroute has started …

traceroute to happylittlethings.com (66.33.208.226), 30 hops max, 40 byte packets
1 192.168.123.254 (192.168.123.254) 36.499 ms 5.344 ms 9.505 ms
2 172.31.255.251 (172.31.255.251) 36.099 ms 27.398 ms 28.248 ms
3 192.168.22.57 (192.168.22.57) 28.979 ms 56.491 ms 34.831 ms
4 ge-5-1-189.ipcolo2.washington1.level3.net (63.210.31.9) 42.273 ms 31.438 ms 32.373 ms
5 ae-2-56.bbr2.washington1.level3.net (4.68.121.161) 88.805 ms 43.794 ms 42.639 ms
6 so-0-0-0.bbr1.losangeles1.level3.net (64.159.1.157) 121.187 ms so-0-2-0.bbr2.losangeles1.level3.net (64.159.0.246) 84.89 ms so-0-0-0.bbr1.losangeles1.level3.net (64.159.1.157) 129.02 ms
7 so-11-0.ipcolo1.losangeles1.level3.net (4.68.96.66) 118.083 ms so-10-0.ipcolo1.losangeles1.level3.net (4.68.113.154) 107.425 ms so-11-0.ipcolo1.losangeles1.level3.net (4.68.96.66) 87.358 ms
8 * ge-5-2.core2.newyork1.level3.net (4.68.97.169) 61.193 ms ge-2-0.core2.newyork1.level3.net (4.68.97.9) 88.626 ms
9 gblx-level3-oc12.newyork1.level3.net (63.211.54.74) 93.334 ms 87.775 ms 153.676 ms
10 so0-0-0-622m.ar1.lax3.gblx.net (67.17.73.38) 170.736 ms 175.786 ms 158.537 ms
11 ge1-gx.dreamhost.com (67.17.162.162) 146.331 ms 152.674 ms 136.184 ms
12 basic-ogle.neo.dreamhost.com (66.33.208.226) 148.212 ms 193.147 ms 147.703 ms

willscorner.net


#8

Well the reboot seemed to have fixed it for about 5 minutes, now it’s back to locking up again :-.

I hope this doesn’t become common with Dreamhost. I switched because I had heard some good things!


#9

schweb, looks like it could be something with the level3 uplink. All the traceroutes are fine using Mizma and Global Crossing.

Dreamhost doesn’t usually have network issues like this. The last time I can remember something like this was a DoS attack last year. As a result of that they upgraded the networking hardware.

Edit: Here is another traceroute that proves it is a network issue.

traceroute to happylittlethings.com (66.33.208.226), 30 hops max, 40 byte packets
1 192.168.123.254 (192.168.123.254) 4.789 ms 9.116 ms 8.689 ms
2 172.31.255.251 (172.31.255.251) 23.189 ms 54.916 ms 31.827 ms
3 192.168.22.57 (192.168.22.57) 55.465 ms 129.851 ms 43.277 ms
4 ge-5-1-189.ipcolo2.washington1.level3.net (63.210.31.9) 20.053 ms 28.992 ms 24.752 ms
5 ae-2-56.bbr2.washington1.level3.net (4.68.121.161) 56.407 ms 36.58 ms 40.888 ms
6 so-0-2-0.bbr2.losangeles1.level3.net (64.159.0.246) 84.46 ms so-0-0-0.bbr1.losangeles1.level3.net (64.159.1.157) 92.252 ms so-0-2-0.bbr2.losangeles1.level3.net (64.159.0.246) 87.876 ms
7 so-10-0.ipcolo1.losangeles1.level3.net (4.68.113.154) 103.604 ms so-11-0.ipcolo1.losangeles1.level3.net (4.68.96.66) 91.272 ms so-10-0.ipcolo1.losangeles1.level3.net (4.68.113.154) 104.873 ms
8 * * *
9 * * basic-ogle.neo.dreamhost.com (66.33.208.226) 362.262 ms

willscorner.net


#10

"Unfortunately, one of our routers had a hardware failure today at approximately 7:30pm PST.
This caused some traffic to be denied. Luckily, we have redundant networks and hardware, so
traffic was rerouted fairly quickly. If you did notice downtime, it should have been corrected
within minutes.

Currently, we’re in the process of replacing the bad hardware, and should have things back to
normal shortly! We apologize for the problems this may cause.

Happy dreamhost-sure-am-glad-I-got-my-clearance-card-for-our-data-center-today-team! "

willscorner.net


#11

I think the fact that these outages aren’t displayed in the “System Status” is hilarious, a real riot. It says the last downtime was 22 days ago, but 30 minutes ago I couldn’t get email, ftp, or http…

I see the disclaimer that says how it only measures like 5% of what can cause downtime, but come on…you guys should mark it “For Entertainment Purposes Only”.

New SUSE Linux Users


#12

Please note the rest of the disclaimer: “Note: System Status is not guaranteed accurate! It can not measure network failure downtime, system misconfiguration downtime, or some short downtimes. It is only a rough reporting of the historical uptime for your webserver’s hardware. If a service of yours is down and not marked as such here, please don’t be too surprised!”

What would you rather have them do? Focus on fixing the hardware issue, or spend time updating our System Status?


MacManX.com


#13

“I’ve been encountering slow speeds on my website, and while uploading to my site. It also seems to just randomly stop working all together. So, I was wondering If theres possibly something that I’m doing wrong or if there are other people out there experiencing this problem.”

Yeah, what’s the deal with this server timeout that keeps cutting off my upload only a few KB at a time?

PASV
227 Entering Passive Mode (xxx,xxx,xxx,xx,xxx,xxx).
Opening data connection IP: xxx,xxx,xxx,xx,xxx,xxx
PORT: 58577.
APPE file.zip
150 Opening BINARY mode data connection for file.zip
Connection closed. Server timeout.
226 Transfer complete.


#14

We had a problem with one of the modules on our primary router. This was causing one of our BGP sessions to “flap” (go up and down). Some customers may have experienced degredations and / or brief outages. An announcement was made.

We have moved the connection affected by this problem to a different module until we can determine whether the hardware is faulty.


#15

Well excuse my ignorance, but if you’re using a separate module now then shouldn’t the problem have rectified itself?

Maybe I’m doing something wrong, because I’m still getting the following:

PASV
227 Entering Passive Mode (xxx,xxx,xxx,xx,xxx,xxx).
Opening data connection IP: xxx,xxx,xxx,xx,xxx,xxx
PORT: 39870.
APPE file.zip
150 Opening BINARY mode data connection for file.zip
Connection closed. Server timeout.
Connection closed. Server timeout.
REST 2996224
Command aborted. Server timeout.
Connection closed. Server timeout.
226 Transfer complete.
350 Restarting at 2996224. Send STORE or RETRIEVE to initiate transfer.

Again, it’ll upload for around 20 seconds then stop. I don’t understand what’s going on. Help is appreciated.


#16

Muypill, I think the key is, “We had a problem with one of the modules on our primary router.”


MacManX.com


#17

May well be a totally unrelated error; though I replied to your message, I was mostly replying to the general thread. The problems we were having should now be rectified.

In regards to your more specific problem, I’d suggest opening a support ticket if you haven’t already. I don’t see any evidence of general network problems to your IP at the moment.


#18

Alright, thanks for the help.


#19

Thanks for the response will. I can confirm though that the speed issues and the random stopping of services is still going on this morning…


#20

Ive also been having some slow down problems

Not good as I only got my account yesterday.

So this will be fixed right?

Has it been fixed yet?

ALSO::::::

I have been getting an error message whilst in Frontpage
File>>publish Site >>FTP option
ERROR:

"Microsoft Front Page

500 ORT not understood

500 LPRT not understood"

Is anyone else getting this error