Possibly. I wonder why no one has seen it before. It could be something special
to do with
the AIX implementation of the threads. Keep me informed. It certainly does no
harm to
move the lock
M
Matt Richards wrote:
> I think we may be onto something. The cf-serverd on the policy host seems to
I think we may be onto something. The cf-serverd on the policy host seems to
have ran through the night no problem. I wouldn't call it fixed yet, but it is
encouraging. I'll let it run a couple more days and see if that does it.
Does moving the ThreadUnlock make any sense or am I way off track?
Well, it is still doing it. I think it is the cf-server actually causing the
illegal cipher length in the client. I am using openSSL 0.9.8l. I don't have
the client side dialog, as it is very random on which host does it (and when).
I do have the server debug session from the core dump. Ooops, I
Your email is like the scene in Alice in Wonderland where she is walking down a
corridor
that gets smaller and smaller...the font size seems to disappear into oblivion
with each
line ;-)
Any chance you could capture one of these sessions in debug mode (cut out the
relevant
dialogue)?
My coll
Well some good news and some bad news. cf-serverd did core dump last night on
the policy host. I did get output from two clients at the same time.
one was from a regular cf-agent regular run (06:22:02 am):
Protocol transaction sent illegal cipher length
!! Authentication dialogue with x.xx.xx.
