dwinden on "[Plugin: iThemes Security (formerly Better WP Security)] Table 'wordpress-mu.wp_itsec_lockouts' doesn't exist"

hi there!
i use a WordPress Multisite installation.
ithemes Security created the tables for each site:
wp_32_itsec_lockouts
wp_32_itsec_log
wp_32_itsec_temp

for each site. But all tables are empty....
But in http.error.log I got these lines:

AH01071: Got error 'PHP message: WordPress-Datenbank-Fehler Table 'wordpress-mu.wp_itsec_lockouts' doesn't exist fxc3xbcr Abfrage SELECTlockout_hostFROMwp_itsec_lockoutsWHERElockout_active=1 ANDlockout_expire_gmt> '2016-06-22 15:57:51' ANDlockout_host`='xx.xx.xx.xx'; von require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), call_user_func_array, ITSEC_Lockout->check_lockoutn'

It seems lockout would write to the wrong tables...
`

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

Correction: not every site gets the created tables, but only one.
Every access to the website is checked against the table wp_itsec_lockouts, which doesnt exist.
the name of the table in a multisite WP is
wp_<nmber>_itsec_lockouts.

the wp_32_ ... tables were created, but the lookup table is wp_itsec_lockouts.
you see the difference?

@gandalfhh

Is this a new install of the iTSec plugin (> 5.4.x) or did you update the plugin from a pre 5.4.x version to the latest release ?

dwinden

It was an upgrade from 5.5
i deleted all tables.
Deinstall and reinstall dont help.
Should I delete the directory as well?

Maybe I solved this error by

rename table wp_32_itsec_lockouts to wp_itsec_lockouts.

Now it works.

I only get these error:

[Thu Jun 23 10:25:58.323164 2016] [core:error] [pid 7178] [client 66.249.65.121:49041] AH00124: Request exceeded the limit of 10 inteal redirects due to probable configuration error. Use 'LimitIntealRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

@gandalfhh

Yes, renaming the 3 iTSec plugin tables should resolve the issue.
I consider that to be a workaround, because we still don't know the cause of the issue. Why did the plugin create 3 wp_32_% tables ?

It's like site 32 was the current blog when the plugin was installed.
How many sites exist in the multi site env ? 32 ?

dwinden

Hm, maybe I was in the blog 32...
But my multisite WP has 42 tables/blog due to install and delete various blogs for testing purpose.
But: also wp_ tables exist without a number. Cant guess why the _32_ tables were created after deleting the log directory and the itsec tables.
Maybe an incorrect selection with multisite blogs?

Thank you for help.

@gandalfhh

The iTSec plugin can only be installed as a network plugin by a network administrator in multi site. It cannot be installed by the site 32 administrator.

So somehow the current blog was/is at 32 while installing the iTSec plugin as the network administrator. It's the only way to get 3 wp_32_itsec_% tables created...

Perhaps creating/deleting blogs for testing purposes causes some mixup.

Anyway renaming the 3 iTSec tables seems to resolve the issue for now.
If you agree please mark this topic as 'resolved'.

dwinden

solved by renaming the tables to the correct names.