Prev: RHEL 5 compilation of Samba 3.5.2, termcap library problem, use '--no-as-needed'
Next: [Samba] Winbind is kill me!
From: Stan Hoeppner on 10 Apr 2010 18:30
Daniel Müller put forth on 4/10/2010 2:11 AM:
>
>
> Dear all, I have samba 3.2.15 PDC running with an openldap backend and
> smbd4wins on the same host. There is also a BDC the same as my PDC. After I
> did an update to 3.3.12 on my BDC this worked on the fly without problems.
> Then I went on doing the same update on my PDC with the result of chaos. No
> user was able to logon anymore , when I did a smbclient -L mypdc -N it was
> extremely slow, and my whole domain was down. After a few hours searching
> for the reasons, I only saw an error with the samba talking to my openldap
> on my PDC (this error was definitly not on my BDC with quiet the same
> configuration) that searching the ldap database. At the end the only way to
> solve this was to downgrade again to 3.2.15. Is there a way to upgrade a
> samba PDC to 3.3.12 without fail!? Greetings Daniel

It might help if you share that error message with the list. Just telling
us that you upgraded Samba and something broke doesn't give us much to go
on. Error messages, relevant log entries, and config files are always helpful.

--
Stan
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
 | 
Pages: 1
Prev: RHEL 5 compilation of Samba 3.5.2, termcap library problem, use '--no-as-needed'
Next: [Samba] Winbind is kill me!