Monday, August 25, 2014

New securityonion-setup package restarts MySQL to make config changes take effect

I noticed recently that the following issue didn't actually get resolved properly:

Issue 388: Configure MySQL to create an innodb file per table to prevent ibdata1 growing indefinitely

After troubleshooting the issue, I realized that Setup was only doing a MySQL reload and that's not picking up the new innodb_file_per_table setting, so we need to replace that with a MySQL restart.  I've updated Setup and the securityonion-setup package.  This new package has been tested by the following (thanks!):
David Zawdie
Heine Lysemose

Old version of Setup resulted in no per-table innodb files

New version of Setup results in an innodb file per table

Issues Resolved

Issue 576: Setup: restart MySQL to make config changes take effect

The new package is now available in our stable repo.  Please see the following page for full update instructions:

If you have any questions or problems, please use our security-onion mailing list:

Only 33 seats left for the Security Onion conference in Augusta GA! Reserve your seat today!

Commercial Support/Training
Need training and/or commercial support?  Please see:

Help Wanted
If you and/or your organization have found value in Security Onion, please consider giving back to the community by joining one of our teams:

We especially need help in answering support questions on the mailing list:

We also need help testing new packages:


1 comment:

Martin Paszkiewicz said...

Maybe I need to get outside more but this update has me very excited. Thank you Doug and everyone else for your hard work!

Search This Blog

Featured Post

Security Onion 2.4.70 now available including our new Detections interface and much more!

Security Onion 2.4.70 is now available! It includes some new features for our fellow defenders including our new Detections interface to hel...

Popular Posts

Blog Archive