RE [Samba] panic actions on samba 3.2.2 (also)

[Stéphane PURNELLE]

Thanks Jeremy.

but how I use valgrind if the panic action reproduct ?

If think that's it's particular purpose because it's maybe due to failover 
ldap configuration.

127.0.01 is the ldap master
xx.xxx.x.xx is a ldap slave.

both smb.conf and ldap.conf contain theses address.

if ldap slave is not available (network load or slave server restart) then 
it cause nss_ldap problem.
Starting nscd can be workaround ?

thanks in advance

        Stéphane Purnelle

-----------------------------------
Stéphane PURNELLE                         stephane.purnelle at corman.be
Service Informatique       Corman S.A.           Tel : 00 32 087/342467

Jeremy Allison <jra at samba.org> a écrit sur 29/08/2008 23:32:55 :

> On Fri, Aug 29, 2008 at 04:57:32PM +0200, Stéphane PURNELLE wrote:
> > I think that's it's a bug in nss_ldap !
> > 
> > in ldap.conf I put local ldap server (127.0.0.1) and an adress for a 
slave 
> > ldap server (xx.xxx.x.x).
> > Each time I have a panic action, I have 
> > 
> > Aug 29 15:11:24 coradm01-node1 smbd: nss_ldap: reconnected to LDAP 
server 
> > ldap://xx.xxx.x.xx
> > or 
> > Aug 29 16:33:22 coradm01-node1 smbd: nss_ldap: reconnected to LDAP 
server 
> > ldap://127.0.0.1/ after 1 attempt
> > 
> > Coud anyone confirm that
> 
> Yes, looking at your backtraces it looks deep inside nss_ldap. Of
> course that's not 100% - you should probably run under valgrind
> to be sure.
> 
> Jeremy.