Re: [ANN] Version 3.0.0-rc0

17 Jul 2013

      Hi again,

okay, that was quick. I started at the same virtual server which was
problematic earlier, and hit it immediately.

I now have one single virtual server in sites-enabled, and deleted most
modules to prevent them from instantiating in the first place.

The virtual server is EMPTY in all sections except for one custom SQL
query in post-auth. Config copy&pasted at the end of this mail. And here
is the result:

Signalled to terminate
Exiting normally.
rlm_sql (sql-webmailsso-users): Removing connection pool
rlm_sql (sql-webmailsso-users): Closing connection (4)
rlm_sql_mysql: Socket destructor called, closing socket
rlm_sql (sql-webmailsso-users): Closing connection (3)
rlm_sql_mysql: Socket destructor called, closing socket
rlm_sql (sql-webmailsso-users): Closing connection (2)
rlm_sql_mysql: Socket destructor called, closing socket
rlm_sql (sql-webmailsso-users): Closing connection (1)
rlm_sql_mysql: Socket destructor called, closing socket
rlm_sql (sql-webmailsso-users): Closing connection (0)
rlm_sql_mysql: Socket destructor called, closing socket

Program received signal SIGSEGV, Segmentation fault.
modcallable_free (pc=pc@entry=0x7fffffffe3c8) at src/main/modcall.c:2343
2343                            next = loop->next;
(gdb) print loop
$1 = (modcallable *) 0x2527285345554c41
(gdb)

SEUTLI is still there, and no sign of that in my minimal config.
Wherever the skewed Seattle comes from, I'm pretty certain I'm innocent.

And my config isn't weird! ;-) SQL custom statements are a supported
feature, right?

Of course I could create a "proper" sql module instance with this as its
post-auth query, but then we wouldn't have the joy of finding obscure
bugs in the source, right? :-)

Stefan

server AAI {

authorize {
        }

authenticate {
}

preacct {
}

accounting {
}

session {
}

post-auth {
                %{sql-webmailsso-users:INSERT INTO
check_webmailsso_users (user,token,timeout)
VALUES('%{User-Name}','notveryrandom',TIMESTAMPADD(hour, 12, NOW())) ON
DUPLICATE KEY UPDATE token='notveryrandom', timeout=TIMESTAMPADD(hour,
12, NOW())}
}

pre-proxy {
}

post-proxy {
}

}

On 17.07.2013 10:12, Stefan Winter wrote:
...
Hi,
...
I'll blame your configuration.  It's weird!
Can we settle for "complex"? ;-)
And it's SUETLI, right?
...
But realistically, it does need to be fixed.  If you could narrow it
down to a simple configuration (without depending on local config), that
would help a lot.
I'll reduce it to min later today...
Anyway:
raddb # grep -r -i seuli *
raddb # grep -r -i seutli *
raddb #
I do not use this word anywhere in my config. And I provoked the
segfault before anything was pulled from a database or anything... it
was a shutdown right after startup.
I even used my favourite search engine for "SEUTLI" and it asked back if
I maybe meant "Seattle". No, I didn't.
So, let me strip down the config and see where I end up.
Stefan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473