|Main Archive Page > Month Archives > samba-users archives|
Am I the only one experiencing such breaking from winbind? I'm
suspicious of whether it actually works at all, and if I can't get it
working better "real soon now", I'm going to have to ditch it all
together. I really can't afford half of my cpu resources tied up in
logging messages, or my critical servers crashing once a week due to
winbind. I can't believe something this bad would be turned out by
the samba team; their stuff is usually top notch. Yet, I've followed
all the instructions on the webiste, I've tried a few different times,
I've reformatted and reinstalled my network a couple times, and I've
been seeking help, asking people to point out what I'm doing
wrong...and it still doesn't work.
Any more suggestions? Anyone actually using winbind successfully?
On Tue, May 11, 2010 at 9:10 AM, Jim Kusznir <email@example.com> wrote:
> Some more info:
> On my (working) Ubuntu 9.04 system, its often consistently at around
> 50% load, with winbind and syslogd using up that CPU. In
> /var/log/syslog, I get fairly continuous logging of:
> May 11 09:06:39 casas-thin-serv winbindd: rpc_api_pipe: host
> ad1.casas.wsu.edu, pipe \NETLOGON, fnum 0x400f returned critical
> error. Error was NT_STATUS_PIPE_DISCONNECTED
> May 11 09:06:39 casas-thin-serv winbindd: [2010/05/11 09:06:39,
> 0] rpc_client/cli_pipe.c:rpc_api_pipe(914)
> Authentication and other details work, but this is eating up a lot of
> CPU and disk space (logs) for nothing....and I'm suspicious that this
> might be connected to the issue.
> My AD controller (ad1.casas.wsu.edu) is a Win Serv 2008r2 box with the
> schema set to 2003 (IIRC...I know I did not set it to 2008, as I tried
> that first, and had lots of breakage). This system is around to serve
> mostly winbind clients, but 1-3 windows boxes...
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba