Browsed by
Tag: bind

Samba error: bind failed on port 137

Samba error: bind failed on port 137

Problem Samba will not start and is showing the following errors in the log files. Feb 6 15:27:02 server nmbd[22392]: [2013/02/06 15:27:02, 0] lib/util_sock.c:open_socket_in(822) Feb 6 15:27:02 server nmbd[22392]: bind failed on port 137 socket_addr = 172.16.203.142. Feb 6 15:27:02 server nmbd[22392]: Error = Cannot assign requested address Feb 6 15:27:02 server nmbd[22392]: [2013/02/06 15:27:02, 0] nmbd/nmbd_subnetdb.c:make_subnet(97) Feb 6 15:27:02 server nmbd[22392]: nmbd_subnetdb:make_subnet() Feb 6 15:27:02 server nmbd[22392]: Failed to open nmb socket on interface 172.16.203.142 Feb 6 15:27:02 server…

Read More Read More

Named error: couldn’t open pid file ‘/var/run/named/named.pid’: File exists

Named error: couldn’t open pid file ‘/var/run/named/named.pid’: File exists

The following error causes named/bind to become unusable and fail. Mar 25 14:10:09 station1 named[27449]: couldn’t open pid file ‘/var/run/named/named.pid’: File exists Mar 25 14:10:09 station1 named[27449]: exiting (due to early fatal error) I noticed the problem when working on RHEL servers. The user is root and the group is named. I’m assumed that the server could no longer do anything with the named.pid file because the group named does not have permission to change anything in the directory. I…

Read More Read More