Litmus:InstallFAQ

This document is a compilation of install issues that have cropped up in non-Mozilla Litmus installations.

Where can I find installation instructions/a list of all the perl modules I need?

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.

Subsequent logins after initial account creation fail with the error "Username/Password incorrect. Please try again."

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.

Apache log shows errors like: "[error] [client *.*.*.*] prepare_cached(DESCRIBE test_results) statement handle DBIx::ContextualFetch::st=HASH(0x8b4eb80) still Active at /usr/share/perl5/Ima/DBI.pm"

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

"Litmus has suffered an internal error - file error - instructions/selecting_a_test_run.tmpl: not found"

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.

Use of uninitialized value in print at /opt/webtools/litmus/json.cgi line 138., referer: XXX

Make sure you have the JSON perl module installed.

While testing, Litmus logs me out when I try to access http://localhost/*.cgi

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.

ERROR: MochiKit.Async.XMLHttpRequestError("500: Request failed")

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.

process_test.cgi: Can't call method "name" on an undefined value at /var/www/litmus/process_test.cgi line 135., referer: XXX

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.

Apache error log contains: Can't locate Litmus.pm in @INC (@INC contains:...)

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.

Repeatedly logged out/login cookie not set (Litespeed/lsws)

One Litespeed user reported that Litmus was unable to set login cookie while running on his web server. He apparently worked around this by writing a php script to set the login cookie. To me, this sounds like he didn't have perl setup correctly. Check your modules.

"File does not exist: /xxx/Litmus.js, referer: xxx"

Did you follow the instructions in the INSTALL file? You need to run the 'make install' prior to accessing your Litmus install for the first time.

DBD::mysql::st execute failed: COLLATION 'utf8_unicode_ci' is not valid for CHARACTER SET 'latin1'

By default, new databases in MySQL are created with a charset of 'latin1,' but in order to display some international characters, the database needs to store data in 'utf8' format. You can change the charset of your database to utf8 (and the collation to utf8_unicode_ci while you're at it) by following the instructions in the MySQL documentation.