2.2. Configuration

2.2.2.1.1. Allow large attachments

By default, MySQL will only accept packets up to 64Kb in size. If you want to have attachments larger than this, you will need to modify your /etc/my.cnf as below.

If you are using MySQL 4.0 or newer, enter:

  [mysqld]
  # Allow packets up to 1M
  max_allowed_packet=1M

If you are using an older version of MySQL, enter:

  [mysqld]
  # Allow packets up to 1M
  set-variable = max_allowed_packet=1M

There is also a parameter in Bugzilla called 'maxattachmentsize' (default = 1000 Kb) that controls the maximum allowable attachment size. Attachments larger than either the 'max_allowed_packet' or 'maxattachmentsize' value will not be accepted by Bugzilla.

This does not affect Big Files, attachments that are stored directly on disk instead of in the database. Their maximum size is controlled using the 'maxlocalattachment' parameter.

2.2.2.1.2. Allow small words in full-text indexes

By default, words must be at least four characters in length in order to be indexed by MySQL's full-text indexes. This causes a lot of Bugzilla specific words to be missed, including "cc", "ftp" and "uri".

MySQL can be configured to index those words by setting the ft_min_word_len param to the minimum size of the words to index. This can be done by modifying the /etc/my.cnf according to the example below:

  [mysqld]
  # Allow small words in full-text indexes
  ft_min_word_len=2

Rebuilding the indexes can be done based on documentation found at http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html.

The ft_min_word_len parameter is only supported in MySQL v4 or higher.

2.2.2.1.3. Permit attachments table to grow beyond 4GB

By default, MySQL will limit the size of a table to 4GB. This limit is present even if the underlying filesystem has no such limit. To set a higher limit, follow these instructions.

Run the MySQL command-line client and enter:

  mysql> ALTER TABLE attachments 
            AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;
          

The above command will change the limit to 20GB. Mysql will have to make a temporary copy of your entire table to do this. Ideally, you should do this when your attachments table is still small.

This does not affect Big Files, attachments that are stored directly on disk instead of in the database.

2.2.2.1.4. Add a user to MySQL

You need to add a new MySQL user for Bugzilla to use. (It's not safe to have Bugzilla use the MySQL root account.) The following instructions assume the defaults in localconfig; if you changed those, you need to modify the SQL command appropriately. You will need the $db_pass password you set in localconfig in Section 2.2.1.

We use an SQL GRANT command to create a "bugs" user. This also restricts the "bugs"user to operations within a database called "bugs", and only allows the account to connect from "localhost". Modify it to reflect your setup if you will be connecting from another machine or as a different user.

Run the mysql command-line client.

If you are using MySQL 4.0 or newer, enter:

  mysql> GRANT SELECT, INSERT,
           UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,
           CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*
           TO bugs@localhost IDENTIFIED BY '$db_pass';
           mysql> FLUSH PRIVILEGES;

If you are using an older version of MySQL,the LOCK TABLES and CREATE TEMPORARY TABLES permissions will be unavailable and should be removed from the permissions list. In this case, the following command line can be used:

  mysql> GRANT SELECT, INSERT,
           UPDATE, DELETE, INDEX, ALTER, CREATE, DROP,
           REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
           '$db_pass';
           mysql> FLUSH PRIVILEGES;

2.2.2.2.1. Add a User to PostgreSQL

You need to add a new user to PostgreSQL for the Bugzilla application to use when accessing the database. The following instructions assume the defaults in localconfig; if you changed those, you need to modify the commands appropriately. You will need the $db_pass password you set in localconfig in Section 2.2.1.

On most systems, to create the user in PostgreSQL, you will need to login as the root user, and then

 bash# su - postgres

As the postgres user, you then need to create a new user:

 bash$ createuser -U postgres -dAP bugs

When asked for a password, provide the password which will be set as $db_pass in localconfig. The created user will have the ability to create databases and will not be able to create new users.

2.2.2.2.2. Configure PostgreSQL

Now, you will need to edit pg_hba.conf which is usually located in /var/lib/pgsql/data/. In this file, you will need to add a new line to it as follows:

host all bugs 127.0.0.1 255.255.255.255 md5

This means that for TCP/IP (host) connections, allow connections from '127.0.0.1' to 'all' databases on this server from the 'bugs' user, and use password authentication (md5) for that user.

If you are using versions of PostgreSQL before version 8, you may also need to edit postgresql.conf , also usually found in the /var/lib/pgsql/data/ folder. You will need to make a single line change, changing

# tcpip_socket = false

to

tcpip_socket = true

Now, you will need to restart PostgreSQL, but you will need to fully stop and start the server rather than just restarting due to the possibility of a change to postgresql.conf. After the server has restarted, you will need to edit localconfig, finding the $db_driver variable and setting it to Pg and changing the password in $db_pass to the one you picked previously, while setting up the account.