Canmove, confirm
345
edits
Changes
Move in "Bugzilla Database"
If you are using an MTA other than sendmail
the sendmailnow param must be set to on or no mail will be sent.
=Database=
==I think my database might be corrupted, or contain invalid entries. What do I do?==
Run the "sanity check" utility (sanitycheck.cgi) from your web browser to see!
If it finishes without errors, you're probably OK.
If it doesn't come back OK (i.e. any red letters),
there are certain things Bugzilla can recover from and certain things it can't.
If it can't auto-recover, I hope you're familiar with mysqladmin commands
or have installed another way to manage your database.
Sanity Check, although it is a good basic check on your database integrity,
by no means is a substitute for competent database administration
and avoiding deletion of data.
It is not exhaustive, and was created to do a basic check
for the most common problems in Bugzilla databases.
==I want to manually edit some entries in my database. How?==
There is no facility in Bugzilla itself to do this.
It's also generally not a smart thing to do if you don't know exactly what you're doing.
If you understand SQL, though,
you can use the '''mysql''' command line utility to manually insert,
delete and modify table information.
There are also more intuitive GUI clients available.
Personal favorites of the Bugzilla team are
[http://www.phpmyadmin.net/ phpMyAdmin] and
[http://www.mysql.com/products/mysqlcc/ MySQL Control Center].
Remember, backups are your friend.
Everyone makes mistakes, and it's nice to have a safety net in case you mess something up.
Consider using '''mysqldump''' to make a duplicate of your database
before altering it manually.
==I think I've set up MySQL permissions correctly, but Bugzilla still can't connect.==
Try running MySQL from its binary: mysqld --skip-grant-tables.
This will allow you to completely rule out grant tables as the cause of your frustration.
If this Bugzilla is able to connect at this point then you need to check
that you have granted proper permission to the user password combo defined in localconfig.
*Running MySQL with this command line option is very insecure and should only be done when not connected to the external network as a troubleshooting step.
You may also be suffering from a client version mismatch:
MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to it with an older client may fail with the following message:
shell> mysql
Client does not support authentication protocol requested by server; consider upgrading MySQL client
To solve this problem, you should use one of the following approaches:
* Upgrade all client programs to use a 4.1.1 or newer client library.
* When connecting to the server with a pre-4.1 client program, use an account that still has a pre-4.1-style password.
* Reset the password to pre-4.1 style for each user that needs to use a pre-4.1 client program. This can be done using the SET PASSWORD statement and the OLD_PASSWORD() function:
mysql> SET PASSWORD FOR
-> ' some_user '@' some_host ' = OLD_PASSWORD(' newpwd ');
==How do I synchronize bug information among multiple different Bugzilla databases?==
Well, you can synchronize or you can move bugs.
Synchronization will only work one way --
you can create a read-only copy of the database at one site,
and have it regularly updated at intervals from the main database.
MySQL has some synchronization features built-in to the latest releases.
It would be great if someone looked into the possibilities there
and provided a report to the newsgroup on how to effectively synchronize two Bugzilla installations.
If you simply need to transfer bugs from one Bugzilla to another,
checkout the "move.pl" script in the Bugzilla distribution.
