Bugzilla:FAQ:Bugzilla Database: Difference between revisions

m (category:Bugzilla; ~nav)
Line 33: Line 33:
If this Bugzilla is able to connect at this point then you need to check
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.
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.  
*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?==
==How do I synchronize bug information among multiple different Bugzilla databases?==
1

edit