Howto: Mantis bug tracker step-by-step installation instructions

This step-by-step document records the installation of Mantis by yourself. As a Bug Tracking System, Bugzilla is also good, that is, it is a bit difficult to install. Install this document first.

Installation environment: PhP 5.3.8-2ubuntu1 MySQL ver14.14 distrib 5.17 Apache/2.2.21 (UBUNTU) Ubuntu 12.04

1. Install
Please refer to the following documents (click to open the link) and do not repeat them any more. Respect others' labor achievements. This document is just as good as it is.

TIPS:

A. The document contains

mysql> create database mantis defaultcharacter set utf8 collate utf8_general_ci;

This default character is separated... Sorry, please do not simply copy and paste it. To tell the truth, I started to do the same. I found a syntax error.
My version is mantisbt-1.2.8 stable version.
B. When modifying the Apache configuration document, for Ubuntu, the main configuration document is apache2.conf and httpd. conf is the user configuration document. Unlike the RedHat series, the main configuration in the Rh series is httpd. conf. It does not seem to be in the form of an additional configuration file.
C. Pay attention to the path problem. The installation environment varies for each person. Therefore, the website directory and mantisbt directory are different. Pay attention to the path when setting the alias.
D, according to localhost/mantisbt/admin/instal. PHP installation. Note that admin username and password are the administrator accounts of the MySQL database. Print SQL queries instead of writing to the Datebase should be checked. If you do not create a database, you only need to output SQL statements.
E. The document prompts you to delete system warning: invalid argument supplied for foreach (). I did not receive this warning during installation.

2. Several possible errors and Solutions
2.1 checking PHP support for Database Type
Bad-database is not supported by PHP. Check that it has been compiled into your server.
This problem mainly occurs because MySQL is a binary installation, so no PHP connection driver package is configured.
Solution: sudo apt-Get install php-mdb2-driver-mysql php5-mysql
Of course, you can use the software center to install related packages.
After installation, restart the system and use the phpinfo () function to output the environment to check whether the installation is successful.

2.2 attempting to connect to database as admin
Bad
Does administrative user have access to the database? (Can't connect to local MySQL server through socket '/var/run/mysqld. Sock' (2 ))
This problem occurs, and the binary installation kills the victim. Obviously, the sock interface of the database cannot be found. In fact, MySQL is already running. View/etc/My. position of sock under INI, my path in/tmp/mysqld. sock; you will find that their paths are inconsistent. This is the reason. You can change the database interface location or modify PHP parameters in two methods. We recommend that you modify the PHP configuration to avoid any problems.
Vim/etc/PhP5/apache2/PHP. ini
Modify mysql. default_socket =/tmp/MySQL. Sock under [MySQL ].
(Note: The php. ini file in centos seems to be in/etc/PHP. ini)
Restart Apache and MySQL
Use the phpinfo () function to view the environment parameters. The default_socket has been modified, but the above mysql_socket is still the default configuration. Please kindly remind me of any modification methods. But it does work, huh, huh.

2.3 After installation is complete, the logon page prompts system warning: session_start (): cannot find save handler 'memecache'-session startup failed.

Problem description: Because I installed memcache (view the previous document), I modified the session_handler value of PHP. The default value is files.
At first, I thought it was wrong. I checked the install document and found that it was correct. So I searched the internet and found that there was very little information. Later I checked it carefully, how is memecache ??? Shit: memcache is clearly written in the document. It is normal after modification,

2.4 I succeeded. I changed the management password and sent the email but did not receive the email.
Problem description: this problem is a headache, especially when you change the administrator password. After sending the email, you find that you did not receive it, and the account is locked. It hurts a lot. I am so miserable, let me help you with it.
This is still due to the mail configuration problem. php and mantis both have mail configuration. You need to confirm by email to change the password and add an account.
　　　　　
You can refer to the information on the Internet to find out what protocol your email address uses, pop or SMTP.

If the setting is successful in the future, the document will be supplemented at any time.

Supplemental Error 1

Attempting to connect to database as user === possible problem Database User doesn' t have access to the database ()

Checking database server version running MySQL version === bad MySQL 4.1.0 or later is required for installation.

Analysis: These two problems occur together. The database is completely normal and the version is as high as 5.5. The above error should not occur. Check the first error. The user has not logged on to the database, what's going on?

Method: The reason is the password you set when you enter the user name and password for creating the database for you. If the input is incorrect, the above error will be prompted and you will be notified of the mysql version error. Re-run the installation page. The password is the password used to create the database.

Supplemental Error 2

Out of date --- a lot of English. We cannot identify your database architecture version, but you can log on to it. In management, you can see a #100 error, I cannot remember a scheam error.

Analysis: I did not find a solution after searching for a long time on the Internet. Later, I found that there may be a problem with the script for creating the Mantis database, and a statement for version creation was missing. The solution is to re-delete the database mantis and reinstall the database. Generally, the problem can be solved.