On Tue, 2015-01-20 at 10:28 +0100, Carlo wrote:> Il 20/01/15 01:26, Andrew Bartlett ha scritto: > > On Sun, 2015-01-18 at 19:10 +0100, Carlo wrote: > > > >> With the latest stable release on 4.1.16 seems work well. > >> No more SID error > >> tomorrow i'll do some more accurate test > >> Thank you for your support Rowland > >> > >> testing the 4.2rc4 the problem still exist > >> do you reccomend me to write something of this behaviour at > >> https://bugzilla.samba.org/? > >> i still can reproduce the SID error with4.2rc2 /rc3 /rc4 > > Run 'net cache flush' to clear out the incorrect cache entry created by > > the previous versions of Samba 4.2rc that had this bug. > > Tested! > > this also resolve the problem if you have SID error, so the problem is on the > cache, but the Rowland suggestion also work well.Reverting to the built-in winbind should be a last-resort choice, as that code will soon go away.> because the problem appear only after some use or time, like 15-30 day of work > may be the cache. > > How to see what's stored in cache?net cache list> thanks Andrew > > > > Andrew Bartlett > > >-- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
On 20/01/15 09:42, Andrew Bartlett wrote:> Reverting to the built-in winbind should be a last-resort choice, as > that code will soon go away.I only suggested changing winbind as a test, if what he was doing didn't work and just changing 'winbindd' to 'winbind' made it work, then 'winbindd' would probably have been where the fault lied. However, as my own tests have proved, the fault is *not* in 'winbindd', I believe it was in the lack of settings to use it. Rowland
Il 20/01/15 10:49, Rowland Penny ha scritto:> On 20/01/15 09:42, Andrew Bartlett wrote: >> Reverting to the built-in winbind should be a last-resort choice, as that >> code will soon go away. > > I only suggested changing winbind as a test, if what he was doing didn't work > and just changing 'winbindd' to 'winbind' made it work, then 'winbindd' would > probably have been where the fault lied. > > However, as my own tests have proved, the fault is *not* in 'winbindd', I > believe it was in the lack of settings to use it.i believe too. thanks for support! Charles> > Rowland >
Il 20/01/15 10:49, Rowland Penny ha scritto:> On 20/01/15 09:42, Andrew Bartlett wrote: >> Reverting to the built-in winbind should be a last-resort choice, as that >> code will soon go away. > > I only suggested changing winbind as a test, if what he was doing didn't work > and just changing 'winbindd' to 'winbind' made it work, then 'winbindd' would > probably have been where the fault lied. > > However, as my own tests have proved, the fault is *not* in 'winbindd', I > believe it was in the lack of settings to use it. >This was the (my first) report bug https://bugzilla.samba.org/show_bug.cgi?id=11062#c0 I hope all needed information is here thanks again to all for support Charles> Rowland >