boilermake not quite right still
hi, using latest GIT HEAD 3.x pull with boilermake , then install.... # service radiusd start Starting radiusd: /usr/sbin/radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory [FAILED] running from the build directory radiusd -fxx -l stdout - works. running whilst in another directory (eg top level or root home) # radiusd -fxx -l stdout radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory alan
On 6 Dec 2012, at 12:55, Alan Buxey <A.L.M.Buxey@LBORO.AC.UK> wrote:
hi,
using latest GIT HEAD 3.x pull
with boilermake , then install....
# service radiusd start Starting radiusd: /usr/sbin/radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory [FAILED]
running from the build directory radiusd -fxx -l stdout - works.
running whilst in another directory (eg top level or root home)
# radiusd -fxx -l stdout radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory
*sigh* Could you try editing this file: https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/radiusd... And removing "$(filter rlm_%,${ALL_TGTS})" -Arran
Hi, On Thu, Dec 06, 2012 at 05:27:04PM +0000, Arran Cudbard-Bell wrote:
On 6 Dec 2012, at 12:55, Alan Buxey <A.L.M.Buxey@LBORO.AC.UK> wrote:
# radiusd -fxx -l stdout radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory
Could you try editing this file: https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/radiusd...
And removing "$(filter rlm_%,${ALL_TGTS})"
That's great - it fixes the issue on Debian for installed files. However, to run it from the build/bin/ directory you still have to do $ LD_LIBRARY_PATH=build/lib/.libs/ build/bin/radiusd -X as libfreeradius-radius.so and libfreeradius-eap.so are not found. Not sure if that's fixable? Obviously when installed they will be in a known location, but not when in the build dir. Having written that, I've just noticed you can do $ build/bin/local/radiusd -X which *does* work fine - maybe that's the solution for now? Cheers Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
On Thu, Dec 06, 2012 at 07:48:12PM +0000, Matthew Newton wrote:
Could you try editing this file: https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/radiusd...
And removing "$(filter rlm_%,${ALL_TGTS})"
That's great - it fixes the issue on Debian for installed files.
Other good news - that also fixes the basic Debian package build/install/run :-) Thanks!! Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
On 6 Dec 2012, at 19:48, Matthew Newton <mcn4@LEICESTER.AC.UK> wrote:
Hi,
On Thu, Dec 06, 2012 at 05:27:04PM +0000, Arran Cudbard-Bell wrote:
On 6 Dec 2012, at 12:55, Alan Buxey <A.L.M.Buxey@LBORO.AC.UK> wrote:
# radiusd -fxx -l stdout radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory
Could you try editing this file: https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/radiusd...
And removing "$(filter rlm_%,${ALL_TGTS})"
That's great - it fixes the issue on Debian for installed files.
However, to run it from the build/bin/ directory you still have to do
$ LD_LIBRARY_PATH=build/lib/.libs/ build/bin/radiusd -X
That's why it also builds: build/bin/local/radiusd which is linked to libraries in the build tree :) -Arran
On 6 Dec 2012, at 19:48, Matthew Newton <mcn4@LEICESTER.AC.UK> wrote:
Hi,
On Thu, Dec 06, 2012 at 05:27:04PM +0000, Arran Cudbard-Bell wrote:
On 6 Dec 2012, at 12:55, Alan Buxey <A.L.M.Buxey@LBORO.AC.UK> wrote:
# radiusd -fxx -l stdout radiusd: error while loading shared libraries: build/lib/.libs/rlm_acctlog.so: cannot open shared object file: No such file or directory
Could you try editing this file: https://github.com/FreeRADIUS/freeradius-server/blob/master/src/main/radiusd...
And removing "$(filter rlm_%,${ALL_TGTS})"
That's great - it fixes the issue on Debian for installed files.
However, to run it from the build/bin/ directory you still have to do
$ LD_LIBRARY_PATH=build/lib/.libs/ build/bin/radiusd -X
as libfreeradius-radius.so and libfreeradius-eap.so are not found.
Not sure if that's fixable? Obviously when installed they will be in a known location, but not when in the build dir.
Having written that, I've just noticed you can do
$ build/bin/local/radiusd -X
which *does* work fine - maybe that's the solution for now?
Sorry, teaches me not to read to the end of emails. Yes that's by design, and that's the one you should be running if you don't want to install. -Arran
hi, still looking at issues with our FR3 that keeps dying. Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Opening additional connection (21) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing idle connection (14) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing connection (14) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing idle connection (13) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing connection (13) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing idle connection (12) Sat Dec 8 10:03:58 2012 : Info: rlm_sql (sql): Closing connection (12) Sat Dec 8 10:03:58 2012 : Error: TLS Alert read:fatal:unknown CA Sat Dec 8 10:03:58 2012 : Error: TLS_accept: failed in SSLv3 read client certificate A Sat Dec 8 10:03:58 2012 : Error: SSL error error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca Sat Dec 8 10:03:58 2012 : Error: SSL: SSL_read failed inside of TLS (-1), TLS session fails. Sat Dec 8 10:03:58 2012 : Auth: (1496) Login incorrect (TLS Alert read:fatal:unknown CA): [user] (from client wifi1 port 13 cli 30-00-00-00-00-00) Sat Dec 8 10:03:58 2012 : Auth: (1497) Login OK: [user] (from client wifi1 port 13 cli c0-00-00-02-0e-00 via TLS tunnel) Sat Dec 8 10:03:58 2012 : Auth: (1500) Login OK: [anonymous@lboro.ac.uk] (from client wifi1 port 13 cli c0-00-00-02-0e-00) Sat Dec 8 10:03:59 2012 : Info: rlm_sql (sql): Opening additional connection (22) ignoring the random user with incorrect settings causing the TLS part to fail..... the sql is opening up connection 22 but our config is pool { # Number of connections to start start = 10 # Minimum number of connections to keep open min = 2 # Maximum number of connections # # If these connections are all in use and a new one # is requested, the request will NOT get a connection. max = 20 # Spare connections to be left idle # # NOTE: Idle connections WILL be closed if "idle_timeout" # is set. spare = 10 # Number of uses before the connection is closed # # 0 means "infinite" uses = 0 # The lifetime (in seconds) of the connection lifetime = 0 # idle timeout (in seconds). A connection which is # unused for this length of time will be closed. idle_timeout = 60 # NOTE: All configuration settings are enforced. If a # connection is closed because of "idle_timeout", # "uses", or "lifetime", then the total number of # connections MAY fall below "min". When that # happens, it will open a new connection. It will # also log a WARNING message. # # The solution is to either lower the "min" connections, # or increase lifetime/idle_timeout. } ....so why is the connection SQL count going over 20 ? alan
....so why is the connection SQL count going over 20 ?
Because connection number identifies a unique connection, not a slot in the pool. Connection numbers are monotonically increasing. The resason why you're getting connection churn is because idle_timeout is set to 60, and one of your connections has been idle for more than 60 seconds, so it's closed. The 'spare' code then kicks in and opens a new connection to maintain the number of spare connections in the pool. You could set spare to 0 and then use a longer idle_timeout, then the pool would actually find the right number of connections to use instead of churning over the ones it's forced to keep open with spare. Course that might cause interesting issues on accounting spikes :) Anyway have you seen actual segfaults/crashy things, or were just concerned by the connection pool behaviour? -Arran
Hi, ah....hmmm, I'm sure I was seeing the same number eg (15) being used as the number of connections were closed/opened
Anyway have you seen actual segfaults/crashy things, or were just concerned by the connection pool behaviour?
no segfault in that area....still get the same segfault in the proxy part as per that crashlog sent over to pastebin earlier in the week.....even with latest GIT code. but good news, boilermake now works for me too! :-) alan
participants (3)
-
Alan Buxey -
Arran Cudbard-Bell -
Matthew Newton