Kel Way
2005-Feb-02 16:11 UTC
[Samba] A smbd process pegging CPU at near 100% with v3.0.10-1 FC2 RPM
CPU 99.3%: 2170 root 25 0 11656 3228 10m R 99.3 0.5 0:07.42 smbd We're having the same problems as many others with print queues, client lock-ups, etc. I think maybe this CPU problem is related as we have two servers in two locations with the same versions, and both had the problem immediately after upgrading to 3.0.10. We use the YUM facility to upgrade Samba. To react to these problems without waiting for the .11 release, is it possible to use the FC3 RPM of RC1 on a Fedora Core 2 box? If not, a pointer to a FC2 binary would be appreciated. Many Thanks- Kel
Denis Vlasenko
2005-Feb-04 08:26 UTC
[Samba] A smbd process pegging CPU at near 100% with v3.0.10-1 FC2 RPM
On Wednesday 02 February 2005 18:11, Kel Way wrote:> CPU 99.3%: > 2170 root 25 0 11656 3228 10m R 99.3 0.5 0:07.42 smbd > > We're having the same problems as many others with print queues, client lock-ups, etc. I think > maybe this CPU problem is related as we have two servers in two locations with the same versions, > and both had the problem immediately after upgrading to 3.0.10. We use the YUM facility to > upgrade Samba. To react to these problems without waiting for the .11 release, is it possible to > use the FC3 RPM of RC1 on a Fedora Core 2 box? If not, a pointer to a FC2 binary would be > appreciated.strace -p <smbd_PID> ? -- vda
Kel Way
2005-Feb-04 17:06 UTC
[Samba] A smbd process pegging CPU at near 100% with v3.0.10-1 FC2 RPM
> strace -p <smbd_PID> ?2170 root 25 0 11656 3228 10m R 95.9 0.5 2805:07 smbd [root@nash-fs-01 root]# strace -p 2170 Process 2170 attached - interrupt to quit No output... just sits there until I quit. Thanks -
Jeremy Allison
2005-Feb-04 17:59 UTC
[Samba] A smbd process pegging CPU at near 100% with v3.0.10-1 FC2 RPM
On Fri, Feb 04, 2005 at 09:06:27AM -0800, Kel Way wrote:> > strace -p <smbd_PID> ? > > 2170 root 25 0 11656 3228 10m R 95.9 0.5 2805:07 smbd > > [root@nash-fs-01 root]# strace -p 2170 > Process 2170 attached - interrupt to quit > > > No output... just sits there until I quit. Thanks -Attach to it with gdb then get a backtrace. Jeremy