This document is a compilation of install issues that have cropped up in non-Mozilla Litmus installations.
When you checkout Litmus from CVS, there is a file INSTALL in the root directory that contains both installation instructions and a listing of all the required perl modules.
Your installation may be trying to connect to Bugzilla for authentication, but the bugzilla integration code has never been tested (to the best of my knowledge).
Check your localconfig file in your base litmus directory. Remove or comment out any variables with 'bugzilla' in the name. Setting 'our $bugzilla_auth_enabled = 0;' should also work. Try to login again.
These errors appear to be related to perl module version issues, but don't seem to actually affect the performance of Litmus aside from filling the logs with spurious garbage.
See: http://www.mail-archive.com/dbi-users@perl.org/msg28459.html
Make sure the template file is present. Templates live under litmus/template/en/default. You may need to perform a cvs update -dP to update your sources if you are missing files.
Make sure you have the JSON perl module installed.
Due to the way cookies are handled, testing a local install via http://localhost/ does not work. However, you should be able to successfully access and test your install using http://127.0.0.1/ instead.
Some webservers don't seem to return the correct status for AJAX calls, despite returning all the needed data from the request. You can work around this by applying the following patch to the js/MochiKit/MochiKit.js file.
Did you follow the instructions in the INSTALL file? You need to run the populatedb.pl script with the -r option when you first install.
Your httpd.conf needs to contain instructions for Apache on where to find the perl libs for Litmus. e.g.:
use lib '/opt/webtools/litmus';
You can see the above line in context in the example Apache domain config for Litmus .