• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Issue Management tool: Any available tool?

IT Head

New Pleskian
Hello ,
We were using Plesk(V: 12.5) on Linux to host our sites.
In that I had seen that Mantis issue management tool is available. I though did not use the tool
We tried to use Git to help us on deploying to the site.
Due to limited support and features in Plesk 12.5 for Git, we were advised to upgrade to Onyx 17.8.
We did that and set up Git repository with automatic/manual deployment for our sites.

We wanted to use Mantis tool. I searched in applications and found that Mantis exists in Plesk Onyx 17.8.
However after custom installation, it gave errors while adding new users.
Can the issue management tool like Mantix, trac be used on Plesk Onyx 17.8?
This issue management tool is to manage and trac issues raised by the teams and give visisbility of the same to the developers.

Thanks,
Srinivasa Pradeep
 
Mantis Bugtracker has been around for many years and works on basically all Linux servers thinkable. What exactly are the errors that you are experiencing, e.g. error code or message? Error log entries?
 
Mantis Bugtracker has been around for many years and works on basically all Linux servers thinkable. What exactly are the errors that you are experiencing, e.g. error code or message? Error log entries?
I am new to Plesk and know few things about linux. However I am not an expert in Linux either.

I have faced multiple issues.

1. Standard installation using Plesk Application page.
The Mantis installation overwrites the current deployment directory(mine is set to httpdocs).
Hence our index page was overwritten. The resolution was to go for Custom Install via Plesk Application panel in the Plesk tool
I have not created an admin user in mantis. I chose to use the Plesk admin user as the Mantis admin user too.

2. Launching Mantis
Launching Mantis through the URL (https://<your Domain>/mantis) brings up https://<Your domain>/mantis/login_page.php.
However I see following warning.

SYSTEM WARNING: 'session_start(): open(/var/www/vhosts/<your domain>/httpdocs/ei_session_log/sess_jl975rmcl9cfsubk08aajdhi62, O_RDWR) failed: No such file or directory (2)' in '/var/www/vhosts/<your domain>/httpdocs/mantis/core/session_api.php' line 121

Notice that it is trying to write to a sub directory under httpdocs.

This is a constant warning throughout navigation inside Mantis

3. Manage Users
I logged in as admin to Mantis and tried to create users using Manage Users option
It gives the following error:
------------------------------------------------------------------------------------------------------------
APPLICATION ERROR #401

Database query failed. Error received from database was #1690: BIGINT UNSIGNED value is out of range in '(1529642016 - `mantis_9`.`_user_table`.`date_created`)' for the query: SELECT *
FROM _user_table
WHERE ((1529642016 - date_created)<= 604800)
ORDER BY date_created DESC.

Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
---------------------------------------------------------------------------------------------------------------

Hence I could not resolve the issue. Hence I wanted to know if there is another issue management tool.
Please help me to resolve these issues and setup Mantis correctly.

Note: I have ssh connection to Plesk too.

Your help is much appreciated.

Thanks,
Srinivasa Pradeep
 
Last edited:
I forgot to mention some details about the web hosting scenario we have.
We have 5 domains hosted on the same server running plesk.
The issue I mentioned(#3) related to database occurs in all domains when I setup Mantis 1.2.19 and try to create users.

However in one domain, the issue (#2) related to the No such file or directory occurs.

I hope this helps you in identifying the issue

Thanks,
Srinivasa Pradeep
 
The warning that was creeping as described in Step 2. is fixed. The path was not exisitng. I reset the session save path in PHP settings for the site in Plesk.
I set it to default and then it worked as expected.
However the database error 401 when trying to open manage users still exists. I checked Mantis Bug tracker as well but to no avail
 
The changes worked. If anyone needs i can attach the list of files that i had to apply the patch and modify
 
Back
Top