• Hi,
    A few days ago, I noticed that within my WordPress dashboard, I see the following iThemes alert message:

    iThemes Security has noticed a change to some files in your WordPress site

    I realize that I can simply click on the Dismiss Warning button, but decided to run a Check Database within my Cpanel of my Godaddy account. These are the messages that appear specific to iThemes’ database tables:

    [wordpress_28.wp_itsec_lockouts] status: OK
    [wordpress_28.wp_itsec_log] warning: Table is marked as crashed and last repair failed
    [wordpress_28.wp_itsec_log] warning: 12 clients are using or haven’t closed the table properly
    [wordpress_28.wp_itsec_log] error: Invalid key block position: 284289726477762561 key block size: 1024 file_length: 715776
    [wordpress_28.wp_itsec_log] error: key delete-link-chain corrupted
    [wordpress_28.wp_itsec_log] error: Corrupt
    [wordpress_28.wp_itsec_temp] status: OK

    So as one can see, there’s an issue with the log table of iThemes. I thought about deactivating iThemes, deleting it, reinstalling it and reactivating it. Before doing so and losing all of my many configuration settings, I thought to raise this question in this support forum first to see if there’s a less painful workaround.

    Thanks in advance!

    https://wordpress.org/plugins/better-wp-security/

Viewing 4 replies - 1 through 4 (of 4 total)
  • @darrenchu

    First of all I don’t think there is any relation between the alert message and the fact that the wp_itsec_log table seems to be corrupt.

    The file change detection (FCD) warning alert is normally only displayed after a manual FCD scan … but there is a recent topic in this forum where this alert suddenly starts showing after a scheduled FCD scan completes…

    Would be interesting to get this change of behaviour confirmed from a second source.

    To fix the log table you can try and manually drop it from phpMyAdmin.
    Then use the following SQL command to recreate it: (The create_database_tables() method in the better-wp-security/core/class-itsec-lib.php file contains all 3 create table commands).

    CREATE TABLE wp_itsec_log (
    	log_id bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT,
    	log_type varchar(20) NOT NULL DEFAULT '',
    	log_function varchar(255) NOT NULL DEFAULT '',
    	log_priority int(2) NOT NULL DEFAULT 1,
    	log_date datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    	log_date_gmt datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    	log_host varchar(20),
    	log_username varchar(20),
    	log_user bigint(20) UNSIGNED,
    	log_url varchar(255),
    	log_referrer varchar(255),
    	log_data longtext NOT NULL,
    	PRIMARY KEY  (log_id),
    	KEY log_type (log_type),
    	KEY log_date_gmt (log_date_gmt)
    	) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

    Once executed you will probably need to refresh the phpMyAdmin left side navigation panel to actually see the new table listed\created.

    Use the above SQL command only if DB_CHARSET and DB_COLLATE are left untouched in the wp-config.php file:

    /** Database Charset to use in creating database tables. */
    define('DB_CHARSET', 'utf8');
    
    /** The Database Collate type. Don't change this if in doubt. */
    define('DB_COLLATE', '');

    To keep things in sync truncate(empty) the wp_itsec_lockouts and wp_itsec_temp tables.

    Needless to say you should follow the above instructions at your own risk.

    dwinden

    @darrenchu

    If you require no further assistance please mark this topic as ‘resolved’.

    dwinden

    @darrenchu

    If you require no further assistance please mark the topic as ‘resolved’.

    dwinden

    Thread Starter darrenchu

    (@darrenchu)

    Hi Dwinden
    Apologies for the late response. I didn’t receive the notification in my email for your previous responses.

    The warning message displayed in my WordPress dashboard and described in my original message disappeared after I rolled back my WordPress to the previous version. When I run a check database using my Cpanel the same error appears about the ithemes related database tables mentioned above.

    Either way, I’ve deactivated ithemes for now. I’ll try out your suggestions one day and report back on whether the database error messages disappear.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘iThemes Security has noticed a change to some files in your WordPress site’ is closed to new replies.