Hi,
If everyone's in favor, I'll release 2.2.2 on Monday.
hold request
now its monday AM and the load has gone back to higher levels
the server is freaking out and freezing witht he last message in
the log being
Mon Oct 7 07:50:28 2013 : Error: [event.c:2318] Internal sanity check
a.l.m.bu...@lboro.ac.uk wrote:
now its monday AM and the load has gone back to higher levels
the server is freaking out and freezing witht he last message in
the log being
Mon Oct 7 07:50:28 2013 : Error: [event.c:2318] Internal sanity check failed
At least that's clearer.
It would
Hi,
clarification/agreement from Stefan or others?
tried the newest GIT this morning and the proxy issues were gone.
I haven't seen your Internal sanity check failed just yet (and am not
looking forward to it :-/ ).
Stefan
alan
-
List info/subscribe/unsubscribe? See
Hi,
More debug output would help. The last patch came from output sent by
Stefan. The patch seems to help. But there's an underlying issue which is
harder to debug. It looks like a Linux specific IPv6 problem. I don't see
any issue with v4.
interesting..the culprit may have been
a.l.m.bu...@lboro.ac.uk wrote:
interesting..the culprit may have been found. put HEAD onto server this
afternoon...
the logs had plenty of core messages but look
...
no 'bad logs' since that restart logged.
Good. It's the problem I thought it was, but the earlier fixes
weren't
On 4 Oct 2013, at 10:19, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hi,
Yesterday caught an email about the release of FR 2.2.2 on Monday to fix a
proxy problem. As I've just migrated 2 of my servers from 2.2.0 to 2.2.1 the
sudden release of 2.2.2 sounds important. What does 2.2.2 fix?
On 4 Oct 2013, at 10:37, Arran Cudbard-Bell a.cudba...@freeradius.org wrote:
On 4 Oct 2013, at 10:19, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hi,
Yesterday caught an email about the release of FR 2.2.2 on Monday to fix a
proxy problem. As I've just migrated 2 of my servers from 2.2.0
Hi,
a couple of logic issues that meant case/switch and if() worked different
to 2.x - thats been fixed. ..and an issue if your server does a lot of proxying
work - in which worker threads arent dealt with properly - your log file
will be full of core and module messages if you are being hit.
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request 17630 in com
ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request 17635 in com
ponent core module thread.
Fri Oct 4 11:24:14 2013 : Info: WARNING: Child is hung for
Yep, those are the ones. :-)
Stefan
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request
17630 in com ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request
17635 in com ponent core module thread.
Fri Oct 4
On 4 Oct 2013, at 12:00, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request 17630 in
com
ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request 17635 in
com
ponent
On 04/10/13 13:46, Arran Cudbard-Bell wrote:
If I asked particularly nicely, and promised you a beer at the next networkshop
we were both in attendance at, would you be willing to try git head?
I'll roll a v2.2.2_rc0 if it sweetens the deal any? It'd just be really good to
know that that
Hi,
If I asked particularly nicely, and promised you a beer at the next
networkshop
we were both in attendance at, would you be willing to try git head?
I'll take the beer - am running HEAD since last night on one server :-)
(as I said to Alan, i'll report at end of day)
alan
-
List
Woah! that's getting g to be lots of beer.
I'll run it on one of my outward facing servers. Point me at something I can
build and run
A
On 4 Oct 2013, at 14:33, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
If I asked particularly nicely, and promised you a beer at the next
networkshop
we were
Hi
early report :(
2.2.2 HEAD still showing:
Fri Oct 4 13:20:43 2013 : Info: WARNING: Child is hung for request 3767589 in
component core module thread.
Fri Oct 4 13:20:45 2013 : Info: WARNING: Child is hung for request 3767589 in
component core module thread.
Fri Oct 4 13:20:47 2013 :
On 10/04/2013 06:53 AM, a.l.m.bu...@lboro.ac.uk wrote:
a couple of logic issues that meant case/switch and if() worked different
to 2.x - thats been fixed.
I need a clarification. Do you mean worked differently ONLY IN 2.2.1?
But 2.2.2 is 100% logic consistent with all 2.x, except 2.2.1?
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Some things started acting differently in 2.2.1 compared to previous releases
of 2.x
2.2.2 should revert that so things behave the same - so far that seems to be
true but we are still seeing stalled module in core messages that we did not
see
On 4 Oct 2013, at 17:43, Alan Buxey a.l.m.bu...@lboro.ac.uk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Some things started acting differently in 2.2.1 compared to previous releases
of 2.x
2.2.2 should revert that so things behave the same - so far that seems to be
true
More debug output would help. The last patch came from output sent by
Stefan. The patch seems to help. But there's an underlying issue which is
harder to debug. It looks like a Linux specific IPv6 problem. I don't see any
issue with v4.
Alan DeKok.
On 2013-10-04, at 9:41 AM,
19 matches
Mail list logo