chrisncohen

BTW the TCP spike seems to only stay pegged with Chrome, the spike happens with IE briefly, then dies off, and NOT in with FireFox.

[ Stop bumping. ]

Dig what happens when I hit the home page of my site to the network traffic. It stays pegged like this ONLY on the wordpress site until I close the browser window (no clicking around). I’ve got other static stuff on that server that doesn’t spark this kind of traffic. tcpdump records HUGE number of outgoing TCP requests to the machine asking for the web page.

bwm-ng v0.6 (probing every 0.500s), press ‘h’ for help
input: libstatnet type: rate
| iface Rx Tx Total
==============================================================================
lo: 0.00 KB/s 0.00 KB/s 0.00 KB/s
eth0: 243.28 KB/s 11788.75 KB/s 12032.02 KB/s
——————————————————————————
total: 243.28 KB/s 11788.75 KB/s 12032.02 KB/s

DNS is fixed, still crashing Chrome

Just out of curiosity, how about this: https://art.go.randolphcollege.edu/

Okay,thanks. I’m getting some weird results doing nslookup from off-site, so something is definitely going on with DNS. Thanks for the assistance.

Don’t suppose you tried it in Chrome?

https://go.randolphcollege.edu

UPDATE: I take it back. The lag did not disappear. When I reactivated all the plugins and visited a DIFFERENT site (in my network of WP sites) than the ones I had visited previously, the lag was back. One interesting thing, after I removed define(‘ENABLE_CACHE’, true) from wp-config.php the lag that was on pages I already visited before had dissappeared.

UPDATE: turned off all of my plugins and took define(‘ENABLE_CACHE’, true); out of the wp-config.php and problem disappeared. Going back through and adding things one at a time to see what the culprit may have been.

update: I tore down the MU install today and put WordPress 3.0 in its place. I installed the Core Control plugin turned on the HTTP Logging Module and discovered that it was indeed cURL that was having trouble resolving the host names in those widgets and RSS feeds. Still haven’t figured out where the configuration glitch is.

Another little nugget: I ran the php/cURL script above from the command line since I have PHP installed as a cgi-binary as well and it worked when it doesn’t work from the browser…heh…

This is wordpressMU 2.9.2 BTW according to the dashboard footer.

The error was only as specific as what I put in quotes up there. It didn’t seem to show up in the apache access or error logs. I tried activating in in both the plugins and the mu-plugins folder as well.

The Core Control plugin died on me. It claimed “Plugin could not be activated because it triggered a fatal error.” when I tried to activate it in the control panel. I sense that this is a DNS problem as well. We had quite a time with getting our domain controller WIN2003 server to deal up a wildcard DNS entry to that server which seems to be working for everything except the application it was created for…I appreciate everyone’s suggestions. I’ll see what the folks at serverfault and superuser have to say.

It’s a fresh install of MU.