Bug 188124 - nmbd generates high load (cpu usage)
Summary: nmbd generates high load (cpu usage)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-06 09:10 UTC by Sorin Sbarnea
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 3.0.24-1.fc6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-15 16:15:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
my smb.conf (3.82 KB, text/plain)
2006-04-06 09:10 UTC, Sorin Sbarnea
no flags Details

Description Sorin Sbarnea 2006-04-06 09:10:10 UTC
Description of problem:
After upgrade from FC4 to FC5 nmbd generates high load (cpu usage).

Version-Release number of selected component (if applicable):
3.0.22-1

How reproducible:
smb as PDC

Steps to Reproduce:
1.
2.
3.
  
Actual results:
20-30% CPU usage at least on nmbd.

Expected results:
<1% cpu usage

Additional info:
on log level = 3 this is what i get in nmbd.log (repeated recusively ~5-6
times/second)

[2006/04/06 04:59:51, 3]
nmbd/nmbd_winsserver.c:wins_process_name_release_request(1641)
  wins_process_name_release_request: Unique name release for name SORIN<1f> IP
217.156.xx.xxx
[2006/04/06 04:59:51, 3]
nmbd/nmbd_winsserver.c:wins_process_multihomed_name_registration_request(1179)
  wins_process_multihomed_name_registration_request: name registration for name
SORIN<1f> IP 217.156.xx.xxx
[2006/04/06 04:59:51, 3] nmbd/nmbd_namelistdb.c:add_name_to_subnet(246)
  add_name_to_subnet: Added netbios name SORIN<1f> with first IP 217.156.xx.xxx
ttl=300000 nb_flags=60 to subnet WINS_SERVER_SUBNET

If more information is required

Comment 1 Sorin Sbarnea 2006-04-06 09:10:10 UTC
Created attachment 127399 [details]
my smb.conf

Comment 2 Christian Iseli 2007-01-20 00:07:54 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 3 Simo Sorce 2007-03-15 13:38:41 UTC
Do you still have this problem with later releases?
Can you reproduce this at will?
Does it happen only with that client registration (machine named SORIN), or does
it happen for all clients?

Comment 4 Sorin Sbarnea 2007-03-15 13:45:19 UTC
With the latest release I cannot confirm this bug anymore.

Comment 5 Simo Sorce 2007-03-15 16:15:40 UTC
then I close it as fixed with current release, thanks for helping.


Note You need to log in before you can comment on or make changes to this bug.