samba - May 2008 - nmbd using 80-90% cpu for name reg from phantom

nmbd is using a lot of cpu:

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND 

22681 root      20   0 10080 1520 1084 R 99.0  0.3 146:30.78 nmbd

log.nmbd logs 30-40 messages per second::

[2008/05/17 12:56:41,  0] 
nmbd/nmbd_incomingrequests.c:process_name_registration_request(212)
   process_name_registration_request: unicast name registration request 
received for name SEC00159925E132<00> from IP 10.10.10.102 on subnet 
UNICAST_SUBNET. Error - should be sent to WINS server
[2008/05/17 12:56:41,  0] 
nmbd/nmbd_incomingrequests.c:process_name_registration_request(212)
   process_name_registration_request: unicast name registration request 
received for name SEC00159925E132<00> from IP 10.10.10.102 on subnet 
UNICAST_SUBNET. Error - should be sent to WINS server

nmbd is not set up as a WINS server.

The DHCP server only hands out addreses above 10.10.10.120, so .102 
should not exist, and, in fact, 10.10.10.102 can't be found:

  ping 10.10.10.102
PING 10.10.10.102 (10.10.10.102) 56(84) bytes of data.
 From 10.10.10.2 icmp_seq=2 Destination Host Unreachable

So, why does nmbd chew up so many cpu cycles dealing with this.

And, any clue where 10.10.10.102 is??

I don't need a WINS server.

sean

sean darcy wrote:
> nmbd is using a lot of cpu:
> 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 22681 root      20   0 10080 1520 1084 R 99.0  0.3 146:30.78 nmbd
> 
> log.nmbd logs 30-40 messages per second::
> 
> [2008/05/17 12:56:41,  0] 
> nmbd/nmbd_incomingrequests.c:process_name_registration_request(212)
>   process_name_registration_request: unicast name registration request 
> received for name SEC00159925E132<00> from IP 10.10.10.102 on subnet 
> UNICAST_SUBNET. Error - should be sent to WINS server
> [2008/05/17 12:56:41,  0] 
> nmbd/nmbd_incomingrequests.c:process_name_registration_request(212)
>   process_name_registration_request: unicast name registration request 
> received for name SEC00159925E132<00> from IP 10.10.10.102 on subnet 
> UNICAST_SUBNET. Error - should be sent to WINS server
> 
> nmbd is not set up as a WINS server.
> 
> The DHCP server only hands out addreses above 10.10.10.120, so .102 
> should not exist, and, in fact, 10.10.10.102 can't be found:
> 
>  ping 10.10.10.102
> PING 10.10.10.102 (10.10.10.102) 56(84) bytes of data.
>  From 10.10.10.2 icmp_seq=2 Destination Host Unreachable
> 
> So, why does nmbd chew up so many cpu cycles dealing with this.
> 
> And, any clue where 10.10.10.102 is??
> 
> I don't need a WINS server.
> 
> sean
> 
Well, turning on wins support solved it. So even if I don't need it, 
I'll have it. Odd that it's required.

No idea what it did with the phantom.

sean