search for: request_main_recv

...gin shell. I could also not log in on the console. Fortunately I still had an open session so I killed winbindd and immediately I could log in again. Errors in my winbindd log are as follows. winbindd Exceeding 200 client connections, no idle connection found and heaps of: nsswitch/winbindd.c:request_main_recv(556) malloc failed The "malloc failed" entries I also get under 3.0.22 which works OK Another thing that happened was that all of a sudden users had no write permissions on shares anymore they could write to a couple of minutes before. After logging in anew to the domain they could wr...

...time of almost 600 days. This is actually what grieves me most ;-) After poking around a bit I found in log.winbindd [2006/10/09 14:41:41, 0] nsswitch/winbindd.c:process_loop(832) winbindd: Exceeding 200 client connections, no idle connection found [2006/10/09 14:41:41, 0] nsswitch/winbindd.c:request_main_recv(556) malloc failed googling I found someone describing the same problem and also not being able to log into his box anymore. If I kill winbindd and fire it up again it works for about an hour or two before the message appears again. wbinfo -u then produces an error like "Cannot connect t...