Your message dated Mon, 10 Feb 2025 22:17:19 +0100
with message-id <[email protected]>
and subject line Closing obsolete FreeRADIUS bugs
has caused the Debian Bug report #731223,
regarding freeradius-postgresql: segfaults on stop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
731223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731223
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: freeradius-postgresql
Version: 2.1.12+dfsg-1.2
Severity: normal
Dear Maintainer,
Stoping or restarting the daemon produces the following segfault:
freeradius[18371]: segfault at 7f7133dfa610 ip 00007f7133dfa610 sp
00007ffff5cefec8 error 14 in libfreeradius-eap-2.1.12.so[7f713460a000+a000]
If the core files are enabled I get the following report:
#0 0x00007f7133dfa610 in ?? ()
#1 0x00007f71364739d6 in int_free_ex_data (class_index=<optimized out>,
obj=0x10c9410, ad=0x10c9598)
at ex_data.c:522
#2 0x00007f7136818cdd in SSL_free (s=0x10c9410) at ssl_lib.c:528
#3 0x00007f71329b5027 in close_SSL (conn=conn@entry=0x10c0050)
at
/build/postgresql-9.1-wdcwzX/postgresql-9.1-9.1.9/build/../src/interfaces/libpq/fe-secure.c:1454
#4 0x00007f71329b50ef in pqsecure_close (conn=conn@entry=0x10c0050)
at
/build/postgresql-9.1-wdcwzX/postgresql-9.1-9.1.9/build/../src/interfaces/libpq/fe-secure.c:299
#5 0x00007f71329a4334 in closePGconn (conn=conn@entry=0x10c0050)
at
/build/postgresql-9.1-wdcwzX/postgresql-9.1-9.1.9/build/../src/interfaces/libpq/fe-connect.c:2873
#6 0x00007f71329a48be in PQfinish (conn=0x10c0050)
at
/build/postgresql-9.1-wdcwzX/postgresql-9.1-9.1.9/build/../src/interfaces/libpq/fe-connect.c:2953
#7 0x00007f7132bc8352 in sql_close (sqlsocket=<optimized out>,
config=<optimized out>)
at sql_postgresql.c:472
#8 0x00007f7132dd2cce in sql_close_socket (inst=inst@entry=0x10b7750,
sqlsocket=0x10bffb0)
at sql.c:172
#9 0x00007f7132dd2cf4 in sql_poolfree (inst=inst@entry=0x10b7750) at sql.c:153
#10 0x00007f7132dcff96 in rlm_sql_detach (instance=0x10b7750) at rlm_sql.c:809
#11 0x000000000041ac2e in module_instance_free (data=0x10b6c80) at modules.c:380
#12 0x00007f71374d8ffd in FreeWalker (tree=0xf65200, X=0x10dc560) at rbtree.c:63
#13 0x00007f71374d8fee in FreeWalker (tree=0xf65200, X=0x10b2c80) at rbtree.c:61
#14 0x00007f71374d8fee in FreeWalker (tree=0xf65200, X=0xf69410) at rbtree.c:61
#15 0x00007f71374d8fee in FreeWalker (tree=0xf65200, X=0xf682a0) at rbtree.c:61
#16 0x00007f71374d939e in rbtree_free (tree=0xf65200) at rbtree.c:74
#17 0x000000000041ba20 in detach_modules () at modules.c:428
#18 0x000000000040a0bd in main (argc=<optimized out>, argv=<optimized out>) at
radiusd.c:456
So it looks like a problem with PostgreSQL or OpenSSL libraries. In
fact if I switch to using Unix socket for the database connection the
segfault is gone:
sql some-block {
database = "postgresql"
driver = "rlm_sql_${database}"
server = ""
}
In other words it only affects TCP connections to the database:
sql some-block {
database = "postgresql"
driver = "rlm_sql_${database}"
server = "localhost"
}
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages freeradius-postgresql depends on:
ii freeradius 2.1.12+dfsg-1.2
ii libc6 2.13-38
ii libpq5 9.1.9-1
freeradius-postgresql recommends no packages.
freeradius-postgresql suggests no packages.
--- End Message ---
--- Begin Message ---
Dear submitter,
thanks for submitting a bug report against the Debian FreeRADIUS
package. Your bug has been filed for an ancient version of FreeRADIUS
(in Debian) that has not been supported anymore for years. I'm sorry we
could not take care of it in time.
If you can still reproduce this problem on a current version (at least
in 3.2.1 shipped with Debian 12 aka bookworm), please reopen this bug.
Bernhard
--- End Message ---
