Alan DeKok al...@deployingradius.com writes:
Bjørn Mork wrote:
I am now seeing this very same problem, and strongly suspect it to be
related to dead proxy home servers. I was able to provoke the Exiting
normally on a server with *no* traffic at all, by doing a couple of
requests for a realm
Bjørn Mork wrote:
I don't have that symbol. Did you mean fr_event_loop_exit?
Sure.
Anyway, I ran the server (this time a lab-/test-server with some traffic
but nothing near any real load) using
Breakpoint 1, radius_signal_self (flag=2) at event.c:3733
3733event.c: No such file or
[0], buffer, sizeof(buffer));
(gdb)
Thanks,
-craig
- Original Message -
From: Alan DeKok al...@deployingradius.com
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Sent: Thursday, November 26, 2009 1:45 AM
Subject: Re: Unexpected Exiting normally 2.1.8?
Bjørn
mailing list freeradius-users@lists.freeradius.org
Sent: Thursday, November 26, 2009 7:36 AM
Subject: Re: Unexpected Exiting normally 2.1.8?
Bjørn Mork wrote:
I don't have that symbol. Did you mean fr_event_loop_exit?
Sure.
Anyway, I ran the server (this time a lab-/test-server with some
Craig Campbell wrote:
With the info you need (I hope)...
Breakpoint 2, radius_signal_self (flag=8) at event.c:3733
3733rcode = read(self_pipe[0], buffer, sizeof(buffer));
Hmm... that's with 'flag == 8', not 'flag == 2'. Why is it stopping?
It's *supposed* to call that
Alan DeKok al...@deployingradius.com writes:
Bjørn Mork wrote:
I don't have that symbol. Did you mean fr_event_loop_exit?
Sure.
Anyway, I ran the server (this time a lab-/test-server with some traffic
but nothing near any real load) using
Breakpoint 1, radius_signal_self (flag=2) at
Bjørn Mork wrote:
Yes. Just to be sure, I've repeated the process and the trace is the
same: Useless:
...
Which I guess tells us that there is some other path here than through
fr_event_loop_exit and radius_signal_self with flag==2?
For the life of me, I can't see another path through the
Alan DeKok al...@deployingradius.com writes:
Bjørn Mork wrote:
Yes. Just to be sure, I've repeated the process and the trace is the
same: Useless:
...
Which I guess tells us that there is some other path here than through
fr_event_loop_exit and radius_signal_self with flag==2?
For the
Bjørn Mork wrote:
However, I think I found one other possibility. This code in
fr_event_loop() will exit if the select() fails:
rcode = select(el-maxfd + 1, read_fds, NULL, NULL, wake);
if ((rcode 0) (errno != EINTR)) {
el-dispatch
: Unexpected Exiting normally 2.1.8?
Bjørn Mork wrote:
However, I think I found one other possibility. This code in
fr_event_loop() will exit if the select() fails:
rcode = select(el-maxfd + 1, read_fds, NULL, NULL,
wake);
if ((rcode 0) (errno != EINTR
could actually
verify it is good.
Thanks,
-craig
- Original Message -
From: Craig Campbell cr...@ccraft.ca
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Sent: Tuesday, November 24, 2009 7:28 AM
Subject: Re: Unexpected Exiting normally 2.1.8?
Thanks
Craig Campbell cr...@ccraft.ca writes:
can anyone identify a certain GOOD build to use for the git
bisect? (Say where 2.1.7 was released?)
I looked through the logs and have arbitrarily selected,
134f314c57d67b56bab93db4089c25e956ad6cf2] Lots of notes prior to 2.1.7
I do not know how to
Craig Campbell wrote:
Ok,
can anyone identify a certain GOOD build to use for the git bisect?
(Say where 2.1.7 was released?)
I looked through the logs and have arbitrarily selected,
134f314c57d67b56bab93db4089c25e956ad6cf2] Lots of notes prior to 2.1.7
I do not know how to force git
I am now seeing this very same problem, and strongly suspect it to be
related to dead proxy home servers. I was able to provoke the Exiting
normally on a server with *no* traffic at all, by doing a couple of
requests for a realm with dead home servers and then waiting:
Wed Nov 25 18:03:56 2009
Alan DeKok al...@deployingradius.com writes:
Bjørn Mork wrote:
I am now seeing this very same problem, and strongly suspect it to be
related to dead proxy home servers. I was able to provoke the Exiting
normally on a server with *no* traffic at all, by doing a couple of
requests for a realm
misleading info.
Thanks,
-craig
- Original Message -
From: Alexander Clouter a...@digriz.org.uk
To: freeradius-users@lists.freeradius.org
Sent: Monday, November 23, 2009 8:13 AM
Subject: Re: Unexpected Exiting normally 2.1.8?
Hi,
Craig Campbell cr...@ccraft.ca wrote:
I re
a version, I'll test again to ensure we got the bug we
were seeking.
Thanks,
-craig
- Original Message -
From: Alan DeKok al...@deployingradius.com
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Sent: Sunday, November 22, 2009 3:14 AM
Subject: Re: Unexpected Exiting
Craig Campbell wrote:
Thanks Alan,
I re -acquired the source, but there seems to be a (minor I think)
error.
$git clone git://git.freeradius.org/freeradius-server.git
$cd freeradius-server
$git fetch origin stable:stable
$git pull
No. See
Hi,
Craig Campbell cr...@ccraft.ca wrote:
I re -acquired the source, but there seems to be a (minor I think) error.
$git clone git://git.freeradius.org/freeradius-server.git
$cd freeradius-server
$git fetch origin stable:stable
$git pull - should be 'git
0x00424172 in main (argc=2, argv=0x7fff6246da68) at
radiusd.c:419
(gdb)
- Original Message -
From: Alan DeKok al...@deployingradius.com
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Sent: Monday, November 23, 2009 7:06 AM
Subject: Re: Unexpected Exiting normally
Craig Campbell wrote:
Once you have another version (reverted), I can test again...
I am really unfamiliar with git, so I may need a hint as to getting the
correct version for testing.
I've reverted the problem commit. It doesn't fix the PostgreSQL
issue, and it causes other problems.
: Re: Unexpected Exiting normally 2.1.8?
Craig Campbell wrote:
Still running tests with bisect.
successful runs take some time to identify (a day).
Please let me know if the bug is identified, otherwise I'll keep
plugging away.
Thanks. Once we know the commit, the fix should hopefully be easy
Craig Campbell wrote:
Ok,
I hope this is helpful. Below please find the git bisect log.
There were a number of iterations with make errors which I then
skipped. I suspect the errors were OS specific and were clearly fixed
in later iterations.
-bash-3.2$ git bisect log
git bisect
freeradius-users@lists.freeradius.org
Sent: Wednesday, November 18, 2009 12:31 PM
Subject: Re: Unexpected Exiting normally 2.1.8?
Craig Campbell wrote:
Ok,
I hope this is helpful. Below please find the git bisect log.
There were a number of iterations with make errors which I then
skipped. I
freeradius-users@lists.freeradius.org
Sent: Friday, November 06, 2009 5:04 PM
Subject: Re: Unexpected Exiting normally 2.1.8?
Craig Campbell wrote:
I was able to get some bisect runs (I think). However, I am
encountering a different error in these.
If radiusd is run in multithreaded mode
Craig Campbell wrote:
Still running tests with bisect.
successful runs take some time to identify (a day).
Please let me know if the bug is identified, otherwise I'll keep
plugging away.
Thanks. Once we know the commit, the fix should hopefully be easy.
Alan DeKok.
-
List
Craig Campbell cr...@ccraft.ca wrote:
I'm running an unreleased 'development? version of freeradius (2.1.8?).
me too, I get exactly what you are getting. If you are always
fiddling with FreeRADIUS I recommend you always run it in gdb as then
you can get things fixed easily.
I usually build
To: freeradius-users@lists.freeradius.org
Sent: Wednesday, November 04, 2009 11:43 AM
Subject: Re: Unexpected Exiting normally 2.1.8?
Craig Campbell cr...@ccraft.ca wrote:
I'm running an unreleased 'development? version of freeradius (2.1.8?).
me too, I get exactly what you are getting. If you
Alexander Clouter wrote:
It's when I add (I am pretty sure it's the in the first 8 or so
patches) the following I get the same problem with FreeRADIUS:
...
I guess at this point I am going to be told to be a good boy and run off
and use git bisect? :)
Pretty much, sorry.
Looking through
Craig Campbell cr...@ccraft.ca wrote:
Thanks for the update - I was concluding I'd have to wait for the release
of 2.1.8 to pursue this. I am currently in a situation where I can help
debug 2.1.8, since the 'new' systems aren't yet in production.
Well I can see no reason to run
Alan DeKok al...@deployingradius.com wrote:
Alexander Clouter wrote:
It's when I add (I am pretty sure it's the in the first 8 or so
patches) the following I get the same problem with FreeRADIUS:
...
I guess at this point I am going to be told to be a good boy and run off
and use git
Alexander Clouter wrote:
The problem is you *have* to
apply my listed cherry-picks, as if you add *any* of the TCP related
code Alan has been working on, it all stops compiling[1]
*Please* use the git stable branch. The master branch has a whole
whack of other changes in it which may or
I'm running an unreleased 'development? version of freeradius (2.1.8?).
So far it is working well, but it is terminating for reasons I cannot determine.
The log contains the following,
Mon Oct 26 15:48:57 2009 : Info: rlm_sql (sql): Driver rlm_sql_mysql (module
rlm_sql_mysql) loaded and linked
33 matches
Mail list logo
