Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
freeradius couldn't connect to postgresql server

Version-Release number of selected component (if applicable):
freeradius-3.0.0-4.el7

How reproducible:


Steps to Reproduce:
1.setup postgresql server, create data using 
2./etc/raddb/mods-config/sql/main/postgresql/setup.sql and chema.sql scripts
3.add users to database
4. set postgresql driver in sql config (driver = "rlm_sql_postgresql" in /etc/raddb/mods-available/sql file)
5. Enable sql module - ln -s /etc/raddb/mods-available/sql /etc/raddb/mods-enabled/sql

Actual results:
radiusd -X shows:
rlm_sql (sql): Opening additional connection (0)
rlm_sql_postgresql: Couldn't connect socket to PostgreSQL server @localhost:radius
rlm_sql_postgresql: Socket destructor called, closing socket
rlm_sql (sql): Opening connection failed (0)
rlm_sql (sql): Removing connection pool
/etc/raddb/mods-enabled/sql[19]: Instantiation failed for module "sql"


Expected results:
Successfull connect to postgresql server

Additional info:

Data in postgresql database:

su - postgres -c 'psql -c "SELECT * FROM radcheck" radius'
 id |   username   |     attribute      | op |   value    
----+--------------+--------------------+----+------------
  1 | paptestuser  | Cleartext-Password | := | mypassword
  2 | paptestuser  | Auth-Type          | := | PAP
  3 | chaptestuser | Cleartext-Password | := | mypassword
  4 | chaptestuser | Auth-Type          | := | CHAP
(4 rows)

This is not a bug in FreeRADIUS, it was a failure of the test to set the SQL login credentials for the postgres server in the FreeRADIUS SQL configuration file.

It's the exact same issue seen in the MySQL test.

I have updated the postgresql-auth-test/runtest.sh file with several fixes and will attach it to bug #1021541 which is the bug report being used to accumulate FreeRADIUS 3 test porting fixes.