SinDeus
Explorer
- Joined
- Sep 3, 2013
- Messages
- 65
Hi all,
After having updated to the latest version of FreeNAS (i.e. FreeNAS-9.3-STABLE-201512121950), my server started showing unprecedented issues.
It has occurred twice since then, and the symptoms are as follow:
The only way I can get around this is to manually reboot the system.
I tried to investigate, and I found that my /var/log/messages is overloaded with these lines:
The file itself is pretty large, I am currently putting it aside to avoid some unnecessary memory usage.
I'm a bit lost regarding the next step to take... Any advice ?
After having updated to the latest version of FreeNAS (i.e. FreeNAS-9.3-STABLE-201512121950), my server started showing unprecedented issues.
It has occurred twice since then, and the symptoms are as follow:
- Loss of the CIFS share.
- Unable to connect to the web interface.
- Unable to connect via SSH.
The only way I can get around this is to manually reboot the system.
I tried to investigate, and I found that my /var/log/messages is overloaded with these lines:
Code:
Dec 23 00:02:52 jotunheim nmbd[2385]: Error = Can't assign requested address Dec 23 00:02:52 jotunheim nmbd[2385]: [2015/12/23 00:02:52.632332, 0, pid=2385, effective(0, 0), real(0, 0)] ../source3/nmbd/nmbd_subnetdb.c:127(make_subnet) Dec 23 00:02:52 jotunheim nmbd[2385]: nmbd_subnetdb:make_subnet() Dec 23 00:02:52 jotunheim nmbd[2385]: Failed to open nmb bcast socket on interface 0.255.255.255 for port 137. Error was Can't assign requested address Dec 23 00:02:52 jotunheim nmbd[2385]: [2015/12/23 00:02:52.632888, 0, pid=2385, effective(0, 0), real(0, 0)] ../source3/lib/util_sock.c:485(open_socket_in) Dec 23 00:02:52 jotunheim nmbd[2385]: bind failed on port 137 socket_addr = 0.255.255.255.
The file itself is pretty large, I am currently putting it aside to avoid some unnecessary memory usage.
I'm a bit lost regarding the next step to take... Any advice ?