> > On a Linux machine, running Samba 2.2.4, we got this error message: > > > > Aug 7 01:47:01 node1-mgmt winbindd[7034]: [2002/08/07 01:47:01, 0] > > rpc_client/cli_pipe.c:rpc_api_pipe(359) > > Aug 7 01:47:01 node1-mgmt winbindd[7034]: cli_pipe: > return critical > > error. Error was SUCCESS - 0 > > > > Previous to that error message, winbindd ran without fault > for nearly 30 > > days. > > The DC 'went away'. (Which closed the pipe, and left 0 in the error > feild - yes we need a better way do handle this...).
I guessed something to that effect, but I don't believe something happened to the DC, that's what's bothering me. I'll need to check that out. So if hit this DEBUG statement DEBUG(0, ("cli_pipe: return critical error. Error was %s\n", cli_errstr(cli))); When the error is 0 I should: DEBUG(0, ("cli_pipe: Critical error - the pipe has closed. The DC has probably been disconnected") ) or something? need a patch? > It looks like the PDC has changed the machine account password on the > account, your local machine name has changed or the account on the DC > has been deleted. Could the DC have been restored from a backup, with > 'old' passwords? I believe not... As I said, I will have to check that out. > Anyway, try a rejoin and see if that helps. I was hoping to avoid a machine account reset, or a rejoin, but I assumed that's what I'll have to do anyway. Thanks! Nir. -- Nir Soffer -=- Software Engineer, Exanet Inc. -=- "Father, why are all the children weeping? / They are merely crying son O, are they merely crying, father? / Yes, true weeping is yet to come" -- Nick Cave and the Bad Seeds, The Weeping Song