New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
What's wrong with BuyVM OVZ node7?
danielfeng
Member
Slow slow slow... Both disk & network I/O. Sometimes only ~150KB/s even for private network transfer. Something must be wrong!
Anyone else on node7 is suffering as well?
Comments
Have you logged a ticket?
From the looks of it there's a stuck kernel thread busying the kernel instead of allowing it to really handle requests. I'll have Anthony perfom an emergency reboot on it in the morning - don't worry, we'll be sure to spin everything down so there's no loss
Our new 2.6.32 kernel brings in a lot of speed improvements, it should bring cachefly/etc speeds back into the 70 - 90MB/sec range like it used to be.
Thanks,
Francisco
@DotVPS - 07 was rotated out to redo things with ext4. While it was removed from the normal IP it was on, there was no customers on the node
If you check you'll have spotted that on many of them. Infact, nodes 05/08/18 are all down as they're taking part in the trials.
Francisco
why do people post problems in the forum before creating a ticket?
Sometimes, the host is so good, you just have to question whether its just you or is everyone else facing difficulties?
Or fear of creating a ticket for the ridicule they'll face.
forum was open in a tab, too lazy to login to user portal for provider.
anyone want to add any other reasons?
There were also some comments on LEB about BuyVM VPS having routing issues afaik.
Mh, interesting. Didn't know about that but now that I found it I tried the same and I seem to have routing issues too on my BuyVM OVZ VPS. I can't reach anonymizer.com, too (as the guy from the post on LEB claimed)
I never heard/saw any tickets about funky routes or we'd have checked it out.
It's quite possible anonomizer blocked our ranges, but I'm thinking it's just something else (maybe a retarded black hole somewhere)
Francisco
Did not notice that until now. But after checking I also have routing issues.
1 205.185.112.136 (205.185.112.136) 0.056 ms 0.029 ms 0.026 ms
2 173.245.86.17 (173.245.86.17) 4.075 ms 4.218 ms 4.435 ms
3 v995.core1.sjc1.he.net (64.71.150.21) 0.459 ms 0.552 ms 0.547 ms
4 10gigabitethernet2-1.core1.sjc2.he.net (72.52.92.118) 3.458 ms 3.461 ms 3.411 ms
5 mpr1.sjc7.us (206.223.116.86) 1.608 ms 1.939 ms 1.779 ms
6 xe-4-1-0.er1.sjc2.us.above.net (64.125.27.90) 2.034 ms 1.813 ms 2.124 ms
7 xe-1-1-0.cr1.sjc2.us.above.net (64.125.26.197) 1.789 ms 2.691 ms 1.960 ms
8 xe-0-3-0.cr1.lax112.us.above.net (64.125.26.25) 10.033 ms 12.850 ms 12.722 ms
9 xe-1-0-0.cr2.lax112.us.above.net (64.125.30.238) 10.496 ms 10.428 ms 10.254 ms
10 xe-2-3-0.cr2.iah1.us.above.net (64.125.25.17) 45.817 ms 45.623 ms 46.454 ms
11 xe-2-3-0.cr2.dfw2.us.above.net (64.125.31.121) 45.973 ms 45.761 ms 45.770 ms
12 xe-0-1-0.er2.dfw2.us.above.net (64.125.27.82) 45.706 ms 45.604 ms 45.569 ms
13 64.124.178.146.allocated.above.net (64.124.178.146) 46.242 ms 45.572 ms 46.110 ms
14 * * *
15 * * *
16 * * *
1 205.185.112.136 (205.185.112.136) 0.099 ms 0.042 ms 0.039 ms
2 173.245.86.17 (173.245.86.17) 10.090 ms 10.113 ms 10.046 ms
3 208.178.63.113 (208.178.63.113) 1.352 ms 1.281 ms 1.212 ms
4 mojohost.port-channel100.ar3.mia2.gblx.net (64.213.78.98) 72.010 ms 71.886 ms 71.788 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
Seems like above.net and gblx.net have some issues in their network. I don't think that BuyVM can change something on this issue though.
C:\Documents and Settings\francisco>tracert 123bill.com
Tracing route to 123bill.com [64.59.93.245]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 205.185.112.1
2 <1 ms <1 ms <1 ms 173.245.86.17
3 16 ms 39 ms 2 ms 208.178.63.113
4 73 ms 73 ms 72 ms mojohost.port-channel100.ar3.mia2.gblx.net [64.2
13.78.98]
5 72 ms 71 ms 71 ms 64.59.93.245
Trace complete.
From a box on the LAN so maybe it's traceroute using a different packet type? I know one of the linux trace commands is TCP where as the other is ICMP
As for anonymizer.com, i get the same thing on a trace but it's possible it's some funky anycast setup or they simply get upstream filters. When visiting the site, though, it loads fully.
Francisco