Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • I posted this about a month ago.

    http://bt.steindorff.de/view.php?id=78

    We have been using the changes for a while and everything is going well.

    I’ve recently made a minor change to include code for the note and to stop updating the passowrd on SSO (because this was causing issues with verification of the wordpress_logged_in_* cookie when multiple browsers were being used.

    The minor change is here:
    else {
    $username=strtolower($_SERVER[‘REMOTE_USER’]);
    if (strpos($username, ‘@’) !== FALSE) {
    $account_suffix = substr($username, strpos($username, ‘@’));
    $username = substr($username, 0, strpos($username, ‘@’));
    }
    $password = wp_generate_password();
    $this->_auto_update_password = false;

    Hi Tim,

    I found the same issue.

    For me, it was cause by the way HyperDB checks for TCP responsiveness.

    I disabled the check and it went away.
    //$wpdb->check_tcp_responsiveness = true;
    $wpdb->check_tcp_responsiveness = false;

    For some reason, MySQL doesn’t like the TCP responsiveness chacks.

    When you look at the stats in MySQL, you can see that the handshake errors go up every time HyperDB does a check.

    mysql> select SUM_CONNECT_ERRORS, COUNT_HANDSHAKE_ERRORS from host_cache where host = ‘back-0’;
    +——————–+————————+
    | SUM_CONNECT_ERRORS | COUNT_HANDSHAKE_ERRORS |
    +——————–+————————+
    | 80 | 80 |
    +——————–+————————+
    1 row in set (0.00 sec)

    Can this issue be escalated to get it resolved?

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