Hello!

Here is the situation: apache listens 4 different IP, 3 are ok (170 kb/sec, my maximum), one is very slow - 15-20 Kb/sec. I just trying to download plain file 5 or 10 Mb size. What could be wrong?

The difference in Virtual host section is only log files and IPs, all other directives are identical.

Tried to disable firewall, no effect.

Help needed please

Hi again!

I figured out that this has nothing to do with apache. If I ping that ip I am getting a lof of packet loss.

174 packets transmitted, 106 received, 39% packet loss, time 174054ms
rtt min/avg/max/mdev = 58.518/62.669/142.495/9.560 ms, pipe 2

The other virtual IPs are just fine, 0% loss. Problem still not resolved, please help.

Firewall not supporting IP?

Brute force stopping your connection to the IP?

Originally posted by Stium
Firewall not supporting IP?

Brute force stopping your connection to the IP?

Thanks for reply.

With disabled firewall the same thing, I do not have brute force.

One more thing I found out is that this IP is fine from some locations. Have no idea why.

I have posted troubleshoting ticked to the hoster.

Can you do a trace to the IP?

This is a strange problem. Or PM me and I'll try tracing it.

IP is 67.19.42.105
This is from my side:
12 gig1-0-2.tp-car9-1.dllstx4.theplanet.com (67.18.116.85) 59.063 ms 85.898 ms 63.201 ms
13 www.russiantvonline.com (67.19.42.105) 67.386 ms 66.949 ms *

12 gig1-0-2.tp-car9-1.dllstx4.theplanet.com (67.18.116.85) 55.126 ms 52.194 ms 52.775 ms
13 * www.russiantvonline.com (67.19.42.105) 63.162 ms *


--- 67.19.42.105 ping statistics ---
162 packets transmitted, 119 received, 26% packet loss, time 162199ms
rtt min/avg/max/mdev = 58.943/64.766/165.957/10.946 ms, pipe 2


And this IP 67.19.42.106 is just fine:

--- 67.19.42.106 ping statistics ---
41 packets transmitted, 41 received, 0% packet loss, time 40396ms
rtt min/avg/max/mdev = 50.818/57.881/164.814/17.390 ms, pipe 2

I'd call the planet. They have good support system and they will help you figure it out.

First submit a ticket telling them all the data, IE pings and traces. Then when you call tell them you have submited a ticket and tell them the ticket number. That way you don't have to try explaining everything over the phone.

Good luck and let us know what the results are.

Stium,

Ticked has been submitted, waiting for reply...

Did you try to ping/trace that IP?

Trace worked but took awhile

I pinged it and it timed out 2/5 times.

do a ifconfig and see what settings you have for that IP, a bad netmask could cause pronlems, see how the others are setup then compare

Originally posted by sethgarnar
do a ifconfig and see what settings you have for that IP, a bad netmask could cause pronlems, see how the others are setup then compare

I did, it is absolutely identical. Machine is up for 71 days, I have not changed anything, tech support is looking for the problem too.

eth0 Link encap:Ethernet HWaddr 00:C0:9F:3B:91:06
inet addr:67.19.42.100 Bcast:67.19.42.111 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1804433361 errors:33584 dropped:0 overruns:0 frame:33584
TX packets:2700532 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2944899578 (2808.4 Mb) TX bytes:2995704794 (2856.9 Mb)
Base address:0xecc0 Memory:fe100000-fe120000

eth0:4 Link encap:Ethernet HWaddr 00:C0:9F:3B:91:06
inet addr:67.19.42.105 Bcast:67.19.42.111 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1804433361 errors:33584 dropped:0 overruns:0 frame:33584
TX packets:2700563 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2944899578 (2808.4 Mb) TX bytes:2995731884 (2856.9 Mb)
Base address:0xecc0 Memory:fe100000-fe120000

The issue has been resolved by provider.

Anyways I still do not understand why this happened and how to prevent it in the future. If this was a problem with the port - thet I would have problems on all IP's, but I had only on one alias.

Very strange.

Are you on Comcast?

I had the same issue a couple days ago. The HTTP IP on my box started showing massive, unusable packet loss. The rest of the IPs on that box, and the netblock as a whole, were fine. The IP was fine from anywhere else, even other Comcast customers. A couple days later, all was well again.

Originally posted by hiryuu
Are you on Comcast?


My traffic goes through verio.net, and that wasn't Apache issue. How come that I can ping/access IP without any problems, and an alias of this IP is having the packet loss?

And a part of my visitors noticed that the site is very slow. I tried to do a multiple traceroute, and half of the sources had packet loss, the other part was fine.