|
From: Graham B. <gb...@po...> - 2003-03-26 18:56:24
|
Can you turn on debug at the start of the script, not just before
the ->add call. It may be the previous request that triggers
the problem.
Graham.
On Wed, Mar 26, 2003 at 11:47:42AM -0600, Daniel Davidson wrote:
> Debug gave me:
> Net::LDAP=HASH(0x804c00c) sending:
>
> substr outside of string at
> /usr/lib/perl5/site_perl/5.8.0/Convert/ASN1/Debug.pm line 33, <STDIN> line 5.
>
> I havent been able to find anything in the logs except for where I have
> stopped and restared slapd. It logs to /var/log somewhere, right?
>
> Dan
>
>
> On Wednesday 26 March 2003 11:09 am, Graham Barr wrote:
> > On Wed, Mar 26, 2003 at 10:52:50AM -0600, Daniel Davidson wrote:
> > > Following Grahm's advice, I received the following message.
> > >
> > > USR2 at /usr/lib/perl5/site_perl/5.8.0/Net/LDAP.pm line 661
> >
> > That line is the select on the socket. What do you see with a debug trace
> > on ? $ldap->debug(15);
> >
> > Also, do you have access to the server logs, if so do you see anything
> > there.
> >
> > Graham.
> >
> > > Know what I am doing wrong yet?
> > >
> > > Dan
> > >
> > > On Wednesday 26 March 2003 10:18 am, Graham Barr wrote:
> > > > On Wed, Mar 26, 2003 at 03:32:02PM +0000, Chris Ridd wrote:
> > > > > On 26/3/03 3:13 pm, Daniel Davidson <da...@li...> wrote:
> > > > > > When I remove the [$dn] and replace it with $dn then my origional
> > > > > > problem of the script hanging without an error happens again.
> > > > > >
> > > > > > I'm stumped,
> > > > > >
> > > > > > Dan
> > > > >
> > > > > Oops, to set the entry's DN just pass the DN as the first arg to add
> > > > > and not as dn => something.
> > > > >
> > > > > $ldap->add($dn,
> > > > > attrs => [ blah blah ]);
> > > >
> > > > There is no difference between $ldap->ad($dn,...) and $ldap->add(dn =>
> > > > $dn,...)
> > > >
> > > > It would be interesting to determine where it is hanging.
> > > >
> > > > Try adding this to your script.
> > > >
> > > > use Carp;
> > > > $SIG{USR2} = \&Carp::croak;
> > > >
> > > > Then when it hangs, find the pid and in another shell do
> > > >
> > > > kill -USR2 $pid
> > > >
> > > > You should see a stack trace on stderr.
> > > >
> > > > Although if you are on a windows box I am not sure this will work.
> > > >
> > > > Graham.
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.net email is sponsored by:
> > > > The Definitive IT and Networking Event. Be There!
> > > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by:
> > > The Definitive IT and Networking Event. Be There!
> > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
>
|