MySQL not using my.cnf settings

Author: Kellen Fields

Updated: June 2024

Audience: Everyone

Environmental details: Self-hosted, Replicated - KOTS

Summary

When installing Jama Connect®, you must create a my.cnf file with the appropriate settings in the Installation Guide. This will cause database connection issues if this file is ignored when setting up MySQL.

Solution

1. Open up my.cnf on the database server, located at /etc/mysql/
2.  Add [mysqld] to the top of the my.cnf file so the server reads it when starting.
3. The new file will look like this (all base settings recommended):
   

   #
   # The MySQL database server configuration file.
   #
   # You can copy this to one of:
   # - "/etc/mysql/my.cnf" to set global options,
   # - "~/.my.cnf" to set user-specific options.
   # 
   # One can use all long options that the program supports.
   # Run program with --help to get a list of available options and with
   # --print-defaults to see which it would actually understand and use.
   #
   # For explanations see
   # http://dev.mysql.com/doc/mysql/en/server-system-variables.html
   
   #
   # * IMPORTANT: Additional settings that can override those from this file!
   # The files must end with '.cnf', otherwise they'll be ignored.
   #
   
   !includedir /etc/mysql/conf.d/
   !includedir /etc/mysql/mysql.conf.d/
   [mysqld]
   bind-address=0.0.0.0
   key_buffer_size=16M
   max_allowed_packet=1G
   thread_stack=192K
   thread_cache_size=8
   tmp_table_size=2G
   max_heap_table_size=2G
   table_open_cache=512
   innodb_buffer_pool_size=12G
   innodb_log_file_size=256M
   innodb_log_buffer_size=12M
   innodb_thread_concurrency=16
   max_connections=351
   wait_timeout=259200

Cause

According to MySQL documentation. "You can place InnoDB options in the [mysqld] group of any option file your server reads when it starts.

Additional Resources

• INSTALL AND CONFIGURE MYSQL (KOTS)

• MySQL documentation

  
  Jama Software®'s recommended settings do include innodb options.