Failed to open nmb bcast socket on interface 0.255.255.255 for port 137

Status
Not open for further replies.
Joined
Sep 28, 2011
Messages
8
Hi

Today the /var/ partition ran full resulting in a very unstable system.
It turned out that the Samba log file had grown very big.

I removed the log.nmbd file and everything was back to normal.
Before deleting the file I took a copy so I had the possibility to determine the root cause.

The log file is spammed with messages like this:

[2012/04/07 22:11:23, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 0.255.255.255.
Error = Can't assign requested address
[2012/04/07 22:11:23, 0] nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
[2012/04/07 22:11:23, 0] nmbd/nmbd.c:331(reload_interfaces)
reload_interfaces: No subnets to listen to. Waiting..
[2012/04/07 22:11:23, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 0.255.255.255.
Error = Can't assign requested address
[2012/04/07 22:11:23, 0] nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
[2012/04/07 22:11:23, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 0.255.255.255.
Error = Can't assign requested address
[2012/04/07 22:11:23, 0] nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address
[2012/04/07 22:11:23, 0] lib/util_sock.c:667(open_socket_in)
bind failed on port 137 socket_addr = 0.255.255.255.
Error = Can't assign requested address
[2012/04/07 22:11:23, 0] nmbd/nmbd_subnetdb.c:127(make_subnet)
nmbd_subnetdb:make_subnet()
Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address

Any suggestions on how to fix whatever is not working so the log file will not grow big again?

Thank you :)



System Information

Hostname freenas.local
FreeNAS Build FreeNAS-8.0.4-RELEASE-x64 (10351)
Platform Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Memory 5964MB
System Time Sun Apr 8 10:38:39 2012
Uptime 10:38AM up 1 day, 12:28, 0 users
Load Average 0.00, 0.02, 0.24
OS Version FreeBSD 8.2-RELEASE-p6
 

dRuEFFECT

Cadet
Joined
Jun 10, 2015
Messages
2
I'm having the same issue.

After a couple days of my FreeNAS being up and running, I'll run into this issue where my CPU fan starts going crazy and things aren't responding well, while the screen (image attached) is spitting out like 100 lines per second. The only way I can get out of this is to reboot the system. Any help here? Can I prevent this?
 

Attachments

  • IMG_0885.JPG
    IMG_0885.JPG
    400.2 KB · Views: 371
Status
Not open for further replies.
Top