Bugzilla:FAQ: Difference between revisions

Bugzilla:FAQ (view source)

Revision as of 13:22, 19 March 2010

287 bytes added , 19 March 2010

→‎Troubleshooting: Update this section and add some new answers for common issues.

MaxKanatAlexander

canmove, Confirmed users

345

edits

@@ Line 203: / Line 203: @@
 =Troubleshooting=
+==Bugzilla can't connect to the database==
+Here's some things to check:
+# Make sure that the <tt>$db_user</tt> and <tt>$db_pass</tt> settings in the <tt>localconfig</tt> file are correct.
+# If you're using MySQL, make sure that DBD::mysql was compiled against the version of MySQL that you're using. For example, a DBD::mysql compiled against MySQL 4.0 won't work with MySQL 5.1. In versions of Bugzilla 3.2 or greater, you can re-install DBD::mysql by doing: <tt>./install-module.pl DBD::mysql</tt> in your Bugzilla directory.
+==I tried to move my Bugzilla from one machine to another, and now there's something wrong with the data.==
+Make sure that you followed the instructions on [[Bugzilla:Move Installation]]. In particular, when you import a database dump, your database has to be '''totally empty''', meaning that it must have no tables in it at all.
+==I get the error "MySQL server has gone away"==
+This usually means that the <tt>max_allowed_packet</tt> setting in your MySQL configuration is too small. It needs to be set larger than the largest piece of data you're trying to insert in to the database. (Usually, this means it has to be larger than your <tt>maxattachmentsize</tt> parameter.) The MySQL configuration is usually in <tt>/etc/my.cnf</tt>.
 ==My parameters don't update when using editparams.cgi, what am I doing wrong?==
-Bugzilla's parameters are being stored in the <tt>data/params</tt> file.
-So in order to update parameters, the user that your web server runs Bugzilla's scripts as needs permission to
+Bugzilla's parameters are stored in the <tt>data/params</tt> file.
+In order to update parameters, the '''user that your web server runs Bugzilla's scripts as''' needs permission to:
 * create, alter and delete files in Bugzilla's <tt>data/</tt> directory
 * alter and delete the <tt>params</tt> file in Bugzilla's <tt>data/</tt> directory
-Known quirks and things to think about:
+==Old Charts complain about "Unable to open the chart datafile ./data/mining/-All-"==
-* On Linux, check your SELinux settings, which may override common file permission settings.
-* It may be that your web server runs Bugzilla's script as a different user than you might think:
-** Using Apache, it may be that you have some SuexecUserGroup setting in effect. Check Apache's documentation on mod_suexec.
-** Using IIS, there appears to be some similar mechanics, too.
-==Old charts complain with "Unable to open the chart datafile ./data/mining/-All-"==
-Old charts are generated thanks to data being in data/mining/ (new charts store the data in the database directly). For both old and new charts to work, data must first be collected by the collectstats.pl script, which has to be run as root (or as the owner of data/mining/ in case you have a non-root installation). Data is only collected when collectstats.pl is run, so if you want to see stats on a daily basis, you have to run this script every day, e.g. by adding it to your cron jobs.
-See http://www.bugzilla.org/docs/tip/html/extraconfig.html for details.
+See http://www.bugzilla.org/docs/tip/html/extraconfig.html for information on how to set up the <tt>collectstats.pl</tt> script to enable the Old Charts and New Charts.
 ==My problem isn't listed here==
-There are several additional common problems listed in the [http://www.bugzilla.org/docs/tip/en/html/troubleshooting.html Troubleshooting section] of the Bugzilla Guide.
 If all else fails, check out places you can get [http://www.bugzilla.org/support/ support for Bugzilla].
 [[category:Bugzilla|F]]

Bugzilla:FAQ: Difference between revisions

Bugzilla:FAQ (view source)

Revision as of 13:22, 19 March 2010

Navigation menu

Search