Might be the second oddest unsolveable glitch I've seen. First place goes to the scanner at work.

Latest response from my Host... who's talking to CPanel... who builds the software that this runs on:

Cpanel support said this:

"Hello

I've been examining how to change the timeout settings for the proxy_fcgi_module but there's not much documentation..."

Even CPanel doesn't understand this and can't find proper documentation. X_X

It seems to run hot and cold, so its hard to pin down. Far as I can tell, things have improved in some situations. The worst still seems to be when I send a PM. That almost always times out, sometimes sending the message successfully, and sometimes making it disappear.

Atm... I'm trying to get them to increase the "proxy timeout" in Apache. Which... I understand very little of. =|

But, I think it has to do with Apache's inner connection timeout for things like FCGI... which is what is handling these requests. It's so complicated.

I'm wondering if for some of you you send a request and because of a slower connection or whatever, maybe it takes 10 seconds to fully go through? However, it's hitting that inner connection timeout so Apache is like /nope. Then the FCGI process locks up because Apache pulled the plug. So you sit there waiting for the response, but it never comes. Eventually, Apache's global timeout of 180 seconds kicks in and is like, you've been here too long, go away.

That's... my best guess at this point lol.

But I can't figure out how to adjust this configuration setting, let alone how to even see what it's set at.

Our Host doesn't either. And apparently even CPanel themselves are having issues lol~

Well I certainly appreciate all of your efforts :)

CPanel spent quite a bit of time overnight adjusting our server.

Please let me know if you encounter any more issues today - starting now I suppose.

Cleared out my cache and tried sending a PM.... had the same three minute delay as before.

Sorry :(


Edit: Just had it happen while accepting non CoD trades, as well.

The errors seem to be happening much less frequently now. Definitely an improvement! Haven't gotten an error in at least a day.... perhaps it is fixed now?

Thank you :)

Here you go, Krin. The first two blocks of text are from the Traceroutes done during the lag. The third was done afterwards.


Traceroute has started

traceroute to sylestia.com (173.236.9.242), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 1.248 ms 0.916 ms 0.909 ms
2 lo0-100.clppva-vfttp-304.verizon-gni.net (72.86.37.1) 7.029 ms 7.110 ms 7.732 ms
3 b3304.clppva-lcr-22.verizon-gni.net (130.81.221.134) 9.745 ms 9.416 ms 7.583 ms
4 * * *
5 0.et-7-1-0.br1.iad8.alter.net (140.222.239.81) 8.323 ms 7.310 ms 7.314 ms
6 xe-2-1-0.er2.iad10.us.zip.zayo.com (64.125.13.173) 7.789 ms 7.055 ms 7.730 ms
7 ae1.cr2.dca2.us.zip.zayo.com (64.125.20.121) 9.854 ms 10.078 ms 11.893 ms
8 ae27.cs2.dca2.us.eth.zayo.com (64.125.30.248) 67.717 ms 66.305 ms 67.928 ms
9 ae3.cs2.iah1.us.eth.zayo.com (64.125.29.45) 97.156 ms 68.309 ms 74.192 ms
10 ae26.mpr4.phx2.us.zip.zayo.com (64.125.31.255) 67.615 ms 67.021 ms 67.575 ms
11 64.125.173.54.t00815-06.above.net (64.125.173.54) 142.237 ms 68.961 ms 67.523 ms
12 agg-c01c02.d03.s02.phx01.singlehop.net (108.178.63.246) 74.872 ms 70.106 ms 69.456 ms
13 aswg-c12.d03.s02.phx01.singlehop.net (108.178.63.218) 70.498 ms 71.903 ms 70.610 ms
14 server4.sylestia.com (173.236.9.242) 67.201 ms 66.983 ms 67.586 ms




Traceroute has started

traceroute to sylestia.com (173.236.9.242), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 2.386 ms 0.893 ms 0.849 ms
2 lo0-100.clppva-vfttp-304.verizon-gni.net (72.86.37.1) 6.199 ms 6.906 ms 7.394 ms
3 b3304.clppva-lcr-22.verizon-gni.net (130.81.221.134) 7.632 ms 7.156 ms 7.409 ms
4 * * *
5 0.et-7-1-0.br1.iad8.alter.net (140.222.239.81) 9.057 ms 7.649 ms 7.105 ms
6 xe-2-1-0.er2.iad10.us.zip.zayo.com (64.125.13.173) 7.493 ms 9.074 ms 7.314 ms
7 ae1.cr2.dca2.us.zip.zayo.com (64.125.20.121) 10.469 ms 8.951 ms 12.637 ms
8 ae27.cs2.dca2.us.eth.zayo.com (64.125.30.248) 70.379 ms 68.947 ms 70.182 ms
9 ae3.cs2.iah1.us.eth.zayo.com (64.125.29.45) 69.868 ms 68.982 ms 80.070 ms
10 ae26.mpr4.phx2.us.zip.zayo.com (64.125.31.255) 68.177 ms 68.202 ms 68.360 ms
11 64.125.173.54.t00815-06.above.net (64.125.173.54) 69.543 ms 70.963 ms 70.197 ms
12 agg-c01c02.d03.s02.phx01.singlehop.net (108.178.63.246) 70.448 ms 68.944 ms 69.804 ms
13 aswg-c12.d03.s02.phx01.singlehop.net (108.178.63.218) 70.155 ms 72.938 ms 73.600 ms
14 server4.sylestia.com (173.236.9.242) 67.770 ms 68.034 ms 67.571 ms





Traceroute has started

traceroute to sylestia.com (173.236.9.242), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 1.882 ms 0.903 ms 0.851 ms
2 lo0-100.clppva-vfttp-304.verizon-gni.net (72.86.37.1) 8.259 ms 9.566 ms 7.107 ms
3 b3304.clppva-lcr-22.verizon-gni.net (130.81.221.134) 7.477 ms 10.552 ms 11.005 ms
4 * * *
5 0.et-7-1-0.br1.iad8.alter.net (140.222.239.81) 8.373 ms 8.792 ms 7.307 ms
6 xe-2-1-0.er2.iad10.us.zip.zayo.com (64.125.13.173) 7.958 ms 5.885 ms 8.100 ms
7 ae1.cr2.dca2.us.zip.zayo.com (64.125.20.121) 11.927 ms 9.712 ms 9.510 ms
8 ae27.cs2.dca2.us.eth.zayo.com (64.125.30.248) 68.303 ms 68.649 ms 67.359 ms
9 ae3.cs2.iah1.us.eth.zayo.com (64.125.29.45) 67.882 ms 68.700 ms 67.409 ms
10 ae26.mpr4.phx2.us.zip.zayo.com (64.125.31.255) 67.568 ms 66.298 ms 69.726 ms
11 64.125.173.54.t00815-06.above.net (64.125.173.54) 72.207 ms 75.731 ms 99.696 ms
12 agg-c01c02.d03.s02.phx01.singlehop.net (108.178.63.246) 69.811 ms 69.376 ms 69.566 ms
13 aswg-c12.d03.s02.phx01.singlehop.net (108.178.63.218) 70.321 ms 71.286 ms 70.198 ms
14 server4.sylestia.com (173.236.9.242) 67.558 ms 66.387 ms 67.771 ms

Yep, as I expected.

Your connection is fine. Something is hanging on the server side of things.

Thank you!

I'll pass this info along and hopefully something can come of it.