Building from source with postgres support
Hi list, I am a reasonable long-time user of Freeradius on a single monolithic host but I'm setting up a new server and putting my services in containers. I have postgres in a Docker container running nicely, fully configured with my old user base migrated from MySQL. I am compiling Freeradius 3.0.15 on a separate container and hoping to use Postgres as the store. radtest with bob/hello works fine. However I realised when I tried to set up Postgres support that it fails with rlm_sql_postgresql.so not found. I'm guessing that the compile process detects database support and only builds in binding libraries if it finds that database on the same system? Can you tell me what the requirements are that Freeradius' build process builds rlm_sql_postgresql.so for me? One that is hopefully compatible with driving Freeradius on that end but independent of Postgres on the other container? Freeradius is on a Centos 7.4 container, Postgres 10 is on Debian container. Thanks
On Mon, 2017-11-06 at 14:42 +0000, Toby Walsh wrote:
I am compiling Freeradius 3.0.15 on a separate container and hoping to use Postgres as the store. radtest with bob/hello works fine. However I realised when I tried to set up Postgres support that it fails with rlm_sql_postgresql.so not found. I'm guessing that the compile process detects database support and only builds in binding libraries if it finds that database on the same system?
It builds if the dev libraries for the database are available. It doesn't look for the database itself. See the output of the configure script.
Freeradius is on a Centos 7.4 container, Postgres 10 is on Debian container.
There are Dockerfiles in the FreeRADIUS source which will build a fully-featured FreeRADIUS. You could try them? See the v4.0.x branch on github in scripts/docker. -- Matthew
On Nov 6, 2017, at 9:42 AM, Toby Walsh <walshtj@gmail.com> wrote:
I am a reasonable long-time user of Freeradius on a single monolithic host but I'm setting up a new server and putting my services in containers. I have postgres in a Docker container running nicely, fully configured with my old user base migrated from MySQL. I am compiling Freeradius 3.0.15 on a separate container and hoping to use Postgres as the store. radtest with bob/hello works fine. However I realised when I tried to set up Postgres support that it fails with rlm_sql_postgresql.so not found. I'm guessing that the compile process detects database support and only builds in binding libraries if it finds that database on the same system?
It requires the PostgreSQL client libraries. See the output of "configure" for details.
Can you tell me what the requirements are that Freeradius' build process builds rlm_sql_postgresql.so for me? One that is hopefully compatible with driving Freeradius on that end but independent of Postgres on the other container? Freeradius is on a Centos 7.4 container, Postgres 10 is on Debian container.
You don't need the database on the FreeRADIUS machine. You need the postgresql client libraries: libpq Search the RPM repositories for the right package for your system. Alan DeKok.
Thanks Matthew and Alan. I didn't know there were dockerfiles in v4.0. That's nice! I might have a look. On top of Docker, just to make it more complicated, I'm running the build process from Python and the parts that build the Docker images and run the containers is through Ansible, so that hides stdout and stderr by default. As a result I don't see the output of configure unless I run "docker build" against my dockerfile manually. I probably should have in this circumstance but as I hoped you guys pointed me in the right direction. Alan, I'm building from source and don't really want to resort to RPMs. I could I guess, but I'm used to getting messages from the mailing list about compiling from source and staying up to date rather than rely on outdated distributions roadmaps. On Mon, 6 Nov 2017 at 22:47 Alan DeKok <aland@deployingradius.com> wrote:
On Nov 6, 2017, at 9:42 AM, Toby Walsh <walshtj@gmail.com> wrote:
I am a reasonable long-time user of Freeradius on a single monolithic
host
but I'm setting up a new server and putting my services in containers. I have postgres in a Docker container running nicely, fully configured with my old user base migrated from MySQL. I am compiling Freeradius 3.0.15 on a separate container and hoping to use Postgres as the store. radtest with bob/hello works fine. However I realised when I tried to set up Postgres support that it fails with rlm_sql_postgresql.so not found. I'm guessing that the compile process detects database support and only builds in binding libraries if it finds that database on the same system?
It requires the PostgreSQL client libraries. See the output of "configure" for details.
Can you tell me what the requirements are that Freeradius' build process builds rlm_sql_postgresql.so for me? One that is hopefully compatible with driving Freeradius on that end but independent of Postgres on the other container? Freeradius is on a Centos 7.4 container, Postgres 10 is on Debian container.
You don't need the database on the FreeRADIUS machine. You need the postgresql client libraries: libpq
Search the RPM repositories for the right package for your system.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon, 2017-11-06 at 15:24 +0000, Toby Walsh wrote:
Alan, I'm building from source and don't really want to resort to RPMs. I could I guess, but I'm used to getting messages from the mailing list about compiling from source and staying up to date rather than rely on outdated distributions roadmaps.
The package for the libpq library, not for FreeRADIUS... -- Matthew
Oh. Of course. Thanks, both of you. On Mon, 6 Nov 2017 at 23:30 Matthew Newton <mcn@freeradius.org> wrote:
On Mon, 2017-11-06 at 15:24 +0000, Toby Walsh wrote:
Alan, I'm building from source and don't really want to resort to RPMs. I could I guess, but I'm used to getting messages from the mailing list about compiling from source and staying up to date rather than rely on outdated distributions roadmaps.
The package for the libpq library, not for FreeRADIUS...
-- Matthew
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
Matthew Newton -
Toby Walsh