Please note, I am NOT a Samba expert, but I saw this come across and this looks like it may be useful to many of you. This solution can be found in the
Red Hat Knowledgebase after logging in, at:
http://kbase.redhat.com/faq/FAQ_71_3603.shtm
Question:
After upgrading to Samba 3.0.4 in Red Hat Enterprise Linux 3, I receive errors similar to 'nsswitch/winbindd.c
rocess_loop(726) process_loop: Invalid request size from pid <pid>: 1568 bytes sent, should be 1824 This usually means that you are running old wbinfo, pam_winbind or libnss_winbind clients : 1 Time(s).' What can be done to resolve these errors?
Answer:
Release Found: Red Hat Enterprise Linux 3, Samba 3.0.4
Symptom:
When upgrading to the new Samba 3.0.4 packages from Samba 3.0.2 in an Active Directory environment with Winbind configured, commands such as wbinfo -u no longer work, and generate the following error messages:
Code:
nsswitch/winbindd.c:process_loop(726) process_loop: Invalid request size
from pid 27689: 1568 bytes sent, should be 1824 This usually means that you
are running old wbinfo, pam_winbind or libnss_winbind clients : 1 Time(s)
nsswitch/winbindd.c:process_loop(726) process_loop: Invalid request size
from pid 27692: 1568 bytes sent, should be 1824 This usually means that you
are running old wbinfo, pam_winbind or libnss_winbind clients : 1 Time(s)
nsswitch/winbindd.c:process_loop(726) process_loop: Invalid request size
from pid 27694: 1568 bytes sent, should be 1824 This usually means that you
are running old wbinfo, pam_winbind or libnss_winbind clients : 1 Time(s)
nsswitch/winbindd.c:process_loop(726) process_loop: Invalid request size
from pid 27699: 1568 bytes sent, should be 1824 This usually means that you
are running old wbinfo, pam_winbind or libnss_winbind clients : 1 Time(s)
Solution:
When running Samba 3.0.2 and doing an up2date samba the samba server and common packages are upgraded but not the samba-client package. You will end up with a version mismatch that appears to be responsible for the above mentioned problem.
Stopping Samba & Winbind, updating the samba-client package, re-joining the domain, and starting everything back up appears to resolve this. The following commands may help:
service smb stop (Stop the Samba service)
service winbind stop (Stop the Winbind service)
up2date samba-client (update/install the samba-client package)
net join ads -UAdminstrator (rejoin domain, Active Directory)
net rpc join -UAdminstrator (rejoin domain, NT Domain)
service winbind start (Start the Winbind service)
service smb start (Start the Samba service)
Note: You may have to downgrade your Samba version to 3.0.2 and upgrade all the Samba packages to 3.0.4 at the same time.
Samba 3.0.4 with winbind and active directory upgrade problem
