Pings Enabled, now server chokes…

  • Streetwise

    (@streetwise)


    20 years, 8 months ago

    I’m running a server at home with several small sites on it. I building a blog for a client where I just imported about 130 articles from Blogger.

    Now today, I notice that the server hangs for periods of time (30sec +). Sometimes I get a ‘server timed out’ error. But then a few minutes later it’s fine…

    Do these hangs have anything to do with the fact that “ping” is enabled for all 130 articles? The blog is not ‘live’ yet in the sense that it’s being used yet, however I’m guessing that there’s massive pinging going on which is killing the server.

    I temporarily removed the link to ping-o-matic, so we’ll see if I notice any performance issues over the next day or two before I enable it again.

    Does anyone else have any words (kind) of wisdom to impart on this lost soul? I really don’t know where to start looking. I see that there could be some mysql tweaking that may need to be done.

    Thanks!

    Dave

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    20 years, 8 months ago

    This can be related to one of two issues, sometimes both.

    1. WordPress likes to send pingbacks to all of the links that you have included with your post. When it does this, it kindly waits for a response from the pinged host before proceeding. If it does not receive an immediate response, it will wait. Technically, this is not a problem with WordPress, but rather a problem with the remote host’s ability to quickly return a simple ping. Also, in some cases, the remote host may be down and completely unable to return the ping. In this case, WordPress will eventually give up and return you to your posting page, or your server may give up first and return a momentary “server stopped responding” error.

    2. WordPress also likes to ping whichever update services that you have listed in Options/Writing. Once again, WordPress will wait for a response before proceeding. Technically, this is also not a problem with WordPress, but rather a problem with the remote host’s ability to quickly return a simple ping. Also, in some cases, the remote host may be down and completely unable to return the ping. In this case, WordPress will eventually give up and return you to your posting page, or your server may give up first and return a momentary “server stopped responding” error. As a side note, the pinging mechanism of Pingomatic (a popular update service) has been having some serious issues as of late, which are currently affecting its availability.

    skippy

    (@skippy)

    20 years, 8 months ago

    Did you look for other posts regarding “ping”?

    Your blog should not be pinging all 130 of your posts. I don’t know, but I don’t imagine that importing generates pings.

    Thread Starter Streetwise

    (@streetwise)

    20 years, 8 months ago

    Yes, I did a search on ‘ping’ before I posted. The reason I ask is that I saw in some of the documentation where checking the ‘ping’ checkbox for each article will increase the load on the server. That’s why I was wondering exactly how it works. But if what you’re saying is true (all 130 posts shouldn’t be getting pinged), then I imagine it could be more of an issue with ping-o-matice being down.

    HOWEVER, when my server seems to hang, I can’t even hit a simple 3 page site on it that is pure html, not connected to mysql. Does that suggest something different?

    Thanks

    Dave

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Pings Enabled, now server chokes…’ is closed to new replies.