Bobcares

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*The maximum is $4000 in credits, Offer valid till November 30th, 2024, New Customers Only, Credit will be applied after purchase and expires after six (6) months

For every $500 you spend, we will provide you with a $500 credit on your account*

BLACK FRIDAY SPECIAL

*The maximum is $4000 in credits, Offer valid till November 30th, 2024, New Customers Only, Credit will be applied after purchase and expires after six (6) months

Change the innodb_log_file_size value in MySQL/MariaDB

by | Dec 30, 2021

Change the innodb_log_file_size value in MySQL/MariaDB with assistance from our in-house experts.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped out a customer with changing the innodb_log_file_size value in MySQL/MariaDB.

How to change the innodb_log_file_size value in MySQL/MariaDB

If you are looking for a way to change the innodb_log_file_size value in MySQL/MariaDB like a pro, we have your back. Our Support Engineers are here with two sets of solutions based on the server you are using.

How to change the innodb_log_file_size value in MySQL/MariaDB on Linux

  1. First, we have to connect to the Plesk server via SSH.
  2. Then we will stop the MySQL service. The command we use will depend on the OS and the MySQL version:
    # service mariadb stop
    
    # service mysql stop
  3. Next, we will open the MySQL configuration file via any text editor. For instance, here we use the vi editor:
    • On Debian.Ubuntu-based distributions:
      # vi /etc/mysql/my.cnf
    • On CentOS/RHEL-based distributions:
      # vi /etc/my.cnf
  4. Then, we have to head to the [mysqld] section and modify the innodb_log_file_size according to our preference. In case the innodb_log_file_size directive is not present, our Support Team recommends adding it manually under the [mysqld] section.
    [mysqld]
    <...>
    innodb_log_file_size=128M
    <...>
  5. After that, we have to move ib_logfile0 and ib_logfile1 files to another directory. For instance, here we move them to the /root:
    # mv /var/lib/mysql/ib_log* /root
  6. Finally, we start the MySQL service with these commands:
    # service mariadb start
    
    # service mysql start

How to change the innodb_log_file_size value in MySQL/MariaDB on Windows server

Before we begin, our Support Techs would like to point out that there are two MySQL instances with their own configuration in Plesk for Windows:

  • MySQL server for customers’ databases can be found at %plesk_dir%Databases\MySQL\
  • Plesk SQL server for Plesk system databases can be found at %plesk_dir%MySQL\
  1. First, we will connect to the Plesk server via RDP.
  2. Then, we have to open the MySQL configuration file via any text editor as seen below:
    • For MySQL server:
      C:\>%plesk_dir%Databases\MySQL\my.ini
    • For Plesk SQL server:
      C:\>%plesk_dir%MySQL\my.ini
  3. Next, we will head to the [mysqld] section and modify the innodb_log_file_size according to our preference.
    innodb_log_file_size=128M
  4. After that, we have to remove the redo log files as seen below:
    • For MySQL server:

      We have to navigate to the  %plesk_dir%Databases\MySQL\data  folder and delete the  ib_logfile0 and ib_logfile1 files.

    • For Plesk SQL server:

      We have to navigate to the %plesk_dir%MySQL\Data folder and delete the ib_logfile0 and ib_logfile1 files.

  5. Finally, we have to start the Plesk SQL Server or MySQL57 service through Windows Services or Plesk Services Monitor.

[Seeking a solution to another query? We have your back.]

Conclusion

In brief, the skilled Support Engineers at Bobcares demonstrated how to change the innodb_log_file_size value in MySQL/MariaDB.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF