Hi,
unfortunately the hole logfile is filled with:
[2009/11/25 15:59:20, 2] winbindd/winbindd.c:878(remove_client)
final write to client failed: Broken pipe
what is that??
our winbind-config:
idmap backend = rid:EVAN=10000-50000
idmap gid = 10000-50000
idmap uid = 10000-50000
winbind enum users = yes
winbind enum groups = yes
winbind trusted domains only = no
winbind use default domain = yes
allow trusted domains = no
strict locking = no
wide links = no
socket options = SO_SNDBUF=131072 SO_RCVBUF=131072 TCP_NODELAY
IPTOS_LOWDELAY SO_KEEPALIVE
use sendfile = yes
max xmit = 65535
read raw = no
write raw = no
large readwrite = yes
Best
Alex
Robert LeBlanc schrieb:
On Wed, Nov 25, 2009 at 6:15 AM, Alexander Födisch <[email protected]
<mailto:[email protected]>> wrote:
Does nobody have the same problem? Same behaviour w/ 3.4.3
It also takes a "long" time resolving names:
# date; id <user>; date
Mi Nov 25 14:08:55 CET 2009
uid=<...> Gruppen=<...>
Mi Nov 25 14:09:01 CET 2009
Sometimes it tooks more than 10 seconds...
Sometimes users get an error message "Access denied", even
filesystem permissions and samba settings are correct. I think samba
/winbind is running in a timout while resolving names and so samba
cannot grant access to files / folders.
Any ideas what we can do?
Can you find any hints in the log.winbindd log or the log.wb-<domain>
log. I had problems like that in the past, but they sem to be resolved
in 3.4.2. You may have a different problem.
Robert LeBlanc
Life Sciences & Undergraduate Education Computer Support
Brigham Young University
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
