Viewing 10 replies - 1 through 10 (of 10 total)
  • A url is much better that a video or picture.

    Thread Starter chrisncohen

    (@chrisncohen)

    Most of the time I cannot even get to your site. Sometimes I do but you need to check with your hosts or IT. This is a name-server or dns problem not a problem with wordpress AFAIK.

    500 Can’t connect to go.randolphcollege.edu:80 (Bad hostname ‘go.randolphcollege.edu’)

    Unable to fetch your robots.txt file.

    Your server was unable to respond to a HTTP HEAD request.

    The above a sample of errors reported in FF. In IE your site has been up for the last 45 minutes, links work, etc.

    Thread Starter chrisncohen

    (@chrisncohen)

    Don’t suppose you tried it in Chrome?

    Chrome = no workie.

    Thread Starter chrisncohen

    (@chrisncohen)

    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.

    Thread Starter chrisncohen

    (@chrisncohen)

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

    Thread Starter chrisncohen

    (@chrisncohen)

    DNS is fixed, still crashing Chrome

    Thread Starter chrisncohen

    (@chrisncohen)

    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

    Thread Starter chrisncohen

    (@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. ]

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Chrome v18 crashing on all wordpress sites’ is closed to new replies.