iTHEME Log files size is 2.7 gb, HUGE ISSUE

Hi @hildansju,

… I see that the file that has the most size is the itheme file.

You mean, the biggest table is the [prefix_]itsec_logs table ? (where [prefix_] should be substituted with your own database table prefix).

If so, you should know that by default the logs table contains data for the past 60 days (which matches the 2 months you already found). However this is customizable from the plugin UI. Navigate to:

Security > Settings > CONFIGURE

Then scroll down to the Logging section where you should see the DAYS TO KEEP DATABASE LOGS setting.

That said it’s probably best to navigate to the plugin Settings > Logs page to see which feature is adding the most entries (Local Brute Force is a good candidate). Make sure you are on the All Events view and filter for every available module. Then let’s take things from there.

• This reply was modified 1 year, 3 months ago by nlpro.
• This reply was modified 1 year, 3 months ago by nlpro.

Hi @hildansju,

When installed (and activated) the iTSec plugin created a (WordPress) Cron job (purge-log-entries) which runs daily. So in worst case scenario it will take max 24 hours.

If you want to know exactly when the purge-log-entries cron job runs, enable the iTSec plugin Debug menu option as described in this iThemes Help Center article.

If the Local Brute Force module has the highest number of log entries AND those entries are indeed responsible for the majority of the logs table size, it’s probably best to enable the plugin features (if not already) that prevent these brute force attacks from happening. Like:

• Disable xmlrpc (Security > Settings > Advanced > WORDPRESS TWEAKS)
• Enable the Hide Backend feature (Security > Settings > Advanced > HIDE BACKEND).

In general don’t manually delete any data from the iTSec plugin tables. Use the DAYS TO KEEP DATABASE LOGS setting to control how much data is stored in the logs table and then let the plugin handle it. Other than that make sure to configure the iTSec plugin properly 😉

• This reply was modified 1 year, 3 months ago by nlpro.

Hi @hildansju,

No, though in future it will definately help have more control over the size of the logs table.

How to lower the (any) table size (after rows are deleted) is more a MySQL database management question. So I did some googling and found an interesting thread on this topic here.

Hi @hildansju,

Not 2.2 Gb, that’s for sure.

Yes, the thread I shared contains some actions that you can perform in MySQL (like running the optimize table command).

Personally I like the last method mentioned in the thread, that creates a new table using like and then copies the data from the old table into the new table. Then the old table is renamed and the new table renamed to the correct iTSec logs table name. Finally the old table is deleted.

Try (if not already) optimizing the table. If that does not have the desired effect, give the create-new-and-delete-old-table method a go.