samba - Aug 2008 - High Cpu usage

Hello all.

I have a samba 3.0.31, compiled and running on a freebsd 6.3-p3 and he
work?s fine.

But in some situations ( situations not discovered yet ) the use o cpu is
very high, as you can
see in the top command above.

In my /var/log/messages i see this message, but i dont know what is, and
what i neet to do.

Enable log file on smb.conf i don't see anybody strange, i guess...

So, anybody can help me ?

Thanks

Alex.


-----/var/log/messages

34:16 propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/fault.c:fault_report(41)
Aug 11 16:34:16 propague smbd[55372]:
==============================================================Aug 11 16:34:16
propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/fault.c:fault_report(42)
Aug 11 16:34:16 propague smbd[55372]:   INTERNAL ERROR: Signal 11 in pid
55372 (3.0.31)
Aug 11 16:34:16 propague smbd[55372]:   Please read the Trouble-Shooting
section of the Samba3-HOWTO
Aug 11 16:34:16 propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/fault.c:fault_report(44)
Aug 11 16:34:16 propague smbd[55372]:
Aug 11 16:34:16 propague smbd[55372]:   From:
http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Aug 11 16:34:16 propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/fault.c:fault_report(45)
Aug 11 16:34:16 propague smbd[55372]:
==============================================================Aug 11 16:34:16
propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/util.c:smb_panic(1627)
Aug 11 16:34:16 propague smbd[55372]:   smb_panic: clobber_region() last
called from [check_cache(414)]
Aug 11 16:34:16 propague smbd[55372]: [2008/08/11 16:34:16, 0]
lib/util.c:smb_panic(1633)
Aug 11 16:34:16 propague smbd[55372]:   PANIC (pid 55372): internal error

-------



--------
CPU states: 18.3% user,  0.0% nice, 81.7% system,  0.0% interrupt,  0.0%
idle
Mem: 336M Active, 3109M Inact, 210M Wired, 163M Cache, 214M Buf, 16M Free
Swap: 10G Total, 8K Used, 10G Free

PID USERNAME       THR PRI NICE   SIZE    RES STATE  C   TIME   WCPU COMMAND
26348 criacao          1 139    0 40248K  8088K RUN    1  22:08 21.04% smbd
51011 junior           1 139    0 40588K  8112K RUN    1   1:57 18.75% smbd
50753 andrea           1 139    0 40244K  8060K CPU1   1  20:32 16.50% smbd
52143 criacao          1 139    0 40532K  8136K RUN    1   1:40 13.53% smbd
26798 adriano          1 139    0 40200K  8020K RUN    0  28:05 11.23% smbd
51120 root             1 139    0 40404K  8004K RUN    1  10:54 11.23% smbd
50727 criacao          1 139    0 40516K  8108K RUN    0   2:00 10.50% smbd
26337 criacao          1 139    0 40116K  7976K RUN    0  32:16  9.77% smbd
27184 studio           1 139    0 40364K  8080K RUN    0  14:11  9.77% smbd
12947 root             1 139    0 47560K 15196K RUN    0  11:44  8.98% smbd
52155 bianca           1 139    0 40548K  8140K RUN    0   1:11  8.98% smbd
50893 root             1 139    0 40356K  8060K RUN    1  15:32  6.01% smbd
50939 bianca           1 139    0 41404K  9016K RUN    1   1:27  5.22% smbd
52181 root             1  76    0   184M   145M select 0   0:18  0.00% smbd
16068 root             1  76    0 57376K 17136K select 0   0:07  0.00% smbd
51139 root             1  76    0 55916K 23448K select 0   0:05  0.00% smbd
------




*Alex Montoanelli*

Administra??o e Ger?ncia de Redes
Unetvale Conectividade <http://www.unetvale.net>
+55 48 3263 8700

Alex Montoanelli wrote:
> In my /var/log/messages i see this message, but i dont know what is, and
> what i neet to do.
This is not a high CPU use issue; it's a crash.

It's a segmentation fault, which means something crashed in samba.

You need to isolate the problem by tuning up your logs, isolating the 
problem, and removing it from the daemon's behavior.

Do you have a script of the install?  Or, do you have more logs?

1) How did you compile or install the program?
2) Provide your smb.conf.

Are you running Kerberos?  I don't know what cache is causing the 
problem, or why it's crashing from these logs, but I can tell you that 
you need to provide more information for the list to help you out. 
Someone may be able to explain it based on personal experience, but you 
can dig up more dirt.

-- 


Jason N