log.nmbd huge

Status
Not open for further replies.

Ciphyx

Cadet
Joined
Jan 24, 2014
Messages
5
Anyone run into an issue with log.nmbd filling up /var/log/samba? It grows to the point of filling up the OS drive. It is populated with:
[2014/07/30 20:44:04, 0] nmbd/nmbd_packets.c:1515(process_nmb_request)
process_nmb_request: Multihomed registration request must be directed at a WINS server.
[2014/07/30 20:44:04, 0] nmbd/nmbd_packets.c:1515(process_nmb_request)
process_nmb_request: Multihomed registration request must be directed at a WINS server.
[2014/07/30 20:44:04, 0] nmbd/nmbd_packets.c:1515(process_nmb_request)
process_nmb_request: Multihomed registration request must be directed at a WINS server.
[2014/07/30 20:44:04, 0] nmbd/nmbd_incomingrequests.c:213(process_name_registration_request)
process_name_registration_request: unicast name registration request received for name XVNT<00> from IP 10.3.1.99 on subnet UNICAST_SUBNET. Error - should be sent to WINS server
[2014/07/30 20:44:04, 0] nmbd/nmbd_incomingrequests.c:213(process_name_registration_request)
process_name_registration_request: unicast name registration request received for name XVNT<1e> from IP 10.3.1.99 on subnet UNICAST_SUBNET. Error - should be sent to WINS server

I am running 8.0.4 at a datacenter several hundred miles away and can't get to it to upgrade it right now. Anyone know how to stop the errors or limit the size of the log file to stop filling up the OS drive?

Thanks
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
The logs won't "fill up the OS drive". The logs are stored on a ramdisk and are lost on a loss of power.

You definitely need to make it a priority to upgrade as many many security problems exist on a version that old. ;)
 

Ciphyx

Cadet
Joined
Jan 24, 2014
Messages
5
Thanks for your reply. I found that the active directory service was turned on causing the log.nmbd file to grow. Now that its turned off it is now working. I tried to upgrade through the gui from a remote computer across a VPN. I was able to perform step 1 and 2. The freenas then rebooted as it was supposed to and through ping I was able to see it come back up, but it booted right back into the same OS/version 8.0.4. Not sure why the upgrade didn't take.
 
Status
Not open for further replies.
Top