WordPress.org

Ready to get started?Download WordPress

Forums

Akismet
Akismet 2.5.0 server/connection problem (40 posts)

  1. Yui
    Member
    Posted 3 years ago #

    Joseph, with OpenSSL+IPv4 only curl there is no slowdown, its quite fast,

    traceroute isnt bad

    pings to rest.akismet.com:
    20 packets transmitted, 20 received, 0% packet loss,
    rtt min/avg/max/mdev = 21.956/23.088/26.736/0.948 ms

    at my look its only software configuration issue, libcurl.
    same server, same config, just different build config for libcurl.so.4.2.0

  2. Joseph Scott
    Member
    Plugin Author

    Posted 3 years ago #

    The previous versions of the plugin did two things differently:

    - It did not us the WordPress HTTP API for HTTP requests
    - It had a higher timeout value for HTTP requests that the current value used in version 2.5.1 of the plugin

    So far the common thread I've see with people reporting these issues involves the timeout setting. We can't rule out that switching to the WP HTTP API is having issues, but that requires more digging to determine if something odd is going on.

  3. mosco
    Member
    Posted 3 years ago #

    We have the same problem with 2.5.1 on wordpress 3.0.4 but only on one blog, all the other blogs on the same server (4 of them) don't have a problem. So that's weird because all these blogs are running the same wordpress and akismet plugin versions.

    It continually says "Akismet has detected a problem. A server or network problem prevented Akismet from checking 1 comment." the 4 other blogs are handling comments fine, and all these blogs including the one displaying the error are receiving comments.

    Is there a way to know which comment is creating the problem?

  4. Joseph Scott
    Member
    Plugin Author

    Posted 3 years ago #

    Could have been an brief issue where your server was unable to reach Akismet.com so only one comment on one of the sites was submitted during that window. Hard to tell without more data.

    A DB query of:

    SELECT comment_id
            FROM {$wpdb->prefix}commentmeta
            WHERE meta_key = 'akismet_error'
            LIMIT 100

    Should show you the comment_id of the comments that are scheduled to be re-checked.

  5. mosco
    Member
    Posted 3 years ago #

    Thanks! I found the problem comment, it had 4 entries in the wp_commentmeta table, two for the error and two that looked like normal akismet entries. I delete the two error entries and it seems good now.

  6. Yui
    Member
    Posted 3 years ago #

    cool, 2.5.2 is out, its the same as -dev version from svn, nothing new but increased timeouts ?

  7. Joseph Scott
    Member
    Plugin Author

    Posted 3 years ago #

    There were a couple of changes in the last few days to -dev that were included in 2.5.2. If you were to download the -dev files right now, they'd be the same as the 2.5.2 files.

  8. kirkmc
    Member
    Posted 3 years ago #

    The dev files from last week worked fine for me; the new update is doing the same thing as 2.5.1. And I didn't save copies of the older dev files. Any way to get them?

  9. Joseph Scott
    Member
    Plugin Author

    Posted 3 years ago #

    The 2.5.2 plugin was from the -dev files. It uses the same timeout value, the only changes beyond that were some minor CSS and text. You can see the timeline of changes for -dev at http://plugins.trac.wordpress.org/log/akismet/dev?rev=334317

  10. kirkmc
    Member
    Posted 3 years ago #

    Well, I've gone back to 2.4, from one of my sites I hadn't updated, and it seems to be working correctly. 2.5.2 was giving me the same problem I posted earlier about, with tons of spams getting through.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags