checksetup.pl ignores value in localconfig file
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
People
(Reporter: kupczyk.y, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
I have 2 servers running on Centos 7. The "uname -a" command returns the following : Linux ServerName 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.
The first server, called "sql", run a postgresql 9.2.24 database server.
The second server, called "bugzilla", have to run bugzilla 5.0.4 above an httpd Apache2/2.4.6. The "bugzilla" server is also running perl v5.16.3.
Issue happens when executing the checksetup.pl perl script.
Actual results:
When running checksetup.pl, the script triggers an error saying the following :
There was an error connecting to PostgreSQL :
FATAL : no entry in pg_hba.conf for host "<IP of sql server>", user "bugzilla", database "template1", inactive SSL
(Translated from my language so please understand that the displayed sentence might be different on an english system)
The IP address is good, the user is good but the database name is wrong.
checksetup.pl uses the database name find in the Bugzilla/DB/Pg.pm (template1).
The following command reports that the "template1" database name appears only in the Pg.pm file :
grep -R "template1" *
checksetup.pl ignores the database name find in the localconfig file (called bugs in my case).
The following command reports the correct database name "bugs" :
grep "$db_name" localconfig
Expected results:
checksetup.pl should use the database name written by the user in the localconfig file and not the one provided by the Pg.pm file.
![]() |
||
Updated•1 years ago
|
Description
•