Hello Bruno -
I have copied this mail to Mike, as there have been some significant changes
in Radiator 2.18 and this problem may be one that we missed.
thanks for letting us know
Hugh
Mike -
Bruno has upgraded to Radiator 2.18, and now after a HUP signal his
PostAuthHook no longer works because the code fragment shown below no longer
has a valid reference in "$authby->{ld}". As a work around I have suggested
he call the "reconnect" routine explicitly, which does work.
thanks
Hugh
On Tuesday 20 March 2001 00:24, Bruno Tiago Rodrigues wrote:
> hello again
>
> > I don't have exactly the same setup here, so could you try something for
>
> me
>
> > please? In your code (shown below), I would like to know which line is
> > causing the problem:
> >
> > if ($code eq 'Access-Request') {
> >
> > my $authby=Radius::AuthGeneric::find ('ldap_auth_id');
> > my $ldap_c=$authby->{ld};
> >
> > Ie. - is the Radius::AuthGeneric::find not returning the correct value?
> > or is the $authby->{ld} not returning anything (or returning "undef")?
>
> i've tried dumping the structures before and after sending the HUP signal,
> at the time the hook is called. after the signal is sent,
> Radius::AuthGeneric::find returns a valid hash with similar contents than
> it did before but without any "ld" array on it. so I guess "find" is
> returning everything OK and the possible problem comes from beyond.
>
> > In general, the AuthBy LDAP* clauses open and close the connection to the
> > LDAP server for every request, so I suspect that is your problem.
> >
> > You can either use the "HoldServerConnection" parameter in the AuthBy
>
> LDAP2
>
> > clause (which I see you are doing), or you can explicitly call
> > $authby->reconnect(); in your code.
>
> as of now, my setup is using (as requested) something like
>
> my $ldap_c=$authby->{ld};
> if (!$ldap_c) {$authby->reconnect();$ldap_c=$authby->{ld};}
>
> it works fine, recconnect is called the first time the hook is called after
> a HUP signal is sent... but wasn't this supposed to be implicit by
> "HoldServerConnection" and the HUP signal processing?
>
> > This behaviour did change some time ago, so if you were using an earlier
> > version of Radiator previously that may be why you are seeing different
> > behaviour. There could also be a problem with -HUP processing of course.
> >
> > Could you also let me know what LDAP server version you are using? And
> > can you tell me what you did prior to sending the -HUP (ie. what
> > changed?)?
>
> I first noticed this after changing a file i'm including and which contains
> <client> clauses (and then killing -HUP radiator) but I got to the
> conclusion that I could replicate it everytime I sent a HUP signal. Our
> directory server is Netscape DS 4.12 running on Solaris (radiator host is
> RedHat linux running perl 5.6.0. Net::LDAP version is 0.15.
>
> any comments? do you want me to send you the full set of configuration
> files ?
>
> -Bruno
>
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
