I have Samba 3.0.4 joined to a Windows 2000 Active Directory domain
with about 16,000 users and 1,000 groups. I run FreeBSD 5.2.1 on a
Dell PowerEdge 1750, dual proc P4 Xeon with HTT and 1 gig of RAM.
Storage is RAID-5, three drives, 36G each. I use winbind to auth
users when accessing shares on the server. This is going to be our
new fileserver.
Check this:
# time ps auxwww | grep http
root 7904 0.0 0.3 4484 3212 ?? Ss 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7905 0.0 0.3 4884 3380 ?? S 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7906 0.0 0.3 4884 3380 ?? S 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7907 0.0 0.3 4884 3380 ?? S 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7908 0.0 0.3 4884 3380 ?? S 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7909 0.0 0.3 4596 3396 ?? S 2:58PM 0:00.01
/usr/local/sbin/httpd -k start
root 7913 0.0 0.1 1408 844 p1 S+ 2:58PM 0:00.00 grep http
real 1m42.312s
user 0m0.000s
sys 0m0.010s
That's just one example. It shouldn't take 1 minute 42 seconds to get a
ps
listing. Especially on a relatively idle server (soon to change, though).
The delay is even longer if I stop winbind for a few minutes and then load
it back up.
Some delays for things like ls or ps or top, or even logging in at the console
have been in excess of five minutes!!
If I stop winbindd, I NEVER get a delay on ANYTHING that looks up usernames
(ps, top, ls, etc.), even after a reboot (I ALWAYS get long delays right after
a reboot if I have winbind enabled).
Please help. What do I do to keep my system from haning up like this? This
is unacceptable.