View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014151 | mantisbt | installation | public | 2012-04-12 13:27 | 2012-04-29 14:40 |
| Reporter | KonstB | Assigned To | dregad | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Product Version | 1.2.10 | ||||
| Summary | 0014151: Failed install on PostgreSQL | ||||
| Description | I have a hosting with PostgreSQL support. | ||||
| Tags | No tags attached. | ||||
|
To install Mantis, you need an account which has sufficient privileges on your database (see http://www.mantisbt.org/docs/master-1.2.x/en/administration_guide/admin.install.new.html) Alternatively, you might be able to generate the SQL from the install script and run that through your interface. As this is not a technical issue with MantisBT, but you are asking how to set it up, I am resolving this issue now. Please use the Forums for further support. |
|
|
Hmm, I think this is a technical issue, and you have to check installation on PostgreSQL, because I have found the reason. |
|
|
The 'register_globals' message is just a warning, so it's up to you to ignore it (or not). It is recommended to have it OFF for security reasons [1]. With regards to the main problem, can you please confirm which version of MantisBT you're working with, as the '$g_db->Connect' statement is actually at line 303 in 1.2.10. Anyway I believe that your proposed fix could potentially break the installation process for other RDBMS. To make sure I have a good understanding of your usage scenario, can you please clearly explain your DB setup (i.e. what input parameters you provide to install.php) Can you also have a look at 0009951 and tell me whether that is the same issue you are facing, and if information provided there is of any help. |
|
|
Maybe a better fix (not tested)
|
|
|
I use 1.2.10. May be I have shifted the line during my experiments with code. My setup scenario: The paramenters for install.php: Yes, I know, that my fix works only if DB already exists. But I have done some experiments and found that ADO command: 0009951 describes a little other problem with DB OWNER setting |
|
|
Thanks for feedback. I assume then that "mantisuser" has fullrights on ppp_mantis schema. Will try to make some tests later on as time allows. In the meanwhile, can you confirm if my suggested alternate fix works for you ? |
|
|
Where to find your alternate fix? In you comment it is not complete. |
|
|
Copy/paste error. Apologies. |
|
|
Hello, I made the following test on my local dev box.
The install script ran fine, and the schema was created successfully. I am therefore not able to reproduce your problem with the information provided Without additional details as to how your host has setup your DB and user account in terms of privileges, I'm afraid I will not be able to help you more. Can you provide the SQL scripts used to create your setup, or a configuration report ? |
|
|
It looks like this is a configuration option. |
|
|
My provider said, that this behaviour is managed by user configuration options in Postgress. I failed to get more information (( |
|
|
In that case, I am afraid that there is no chance for me to troubleshoot this problem. Since you were able to create your database in the end, then I am again resolving this issue. Feel free to reopen it (again) if you are able to get more info on the detailed PostgreSQL setup they are using. |
|
|
The only thing that they have said, was: each user have access to only one database (db name coincides with user login). |
|
|
Not really no, I'm sorry. |
|