smbd ports(139 and 445) are not listening on samba-4.4.9
shivappa Sangapur
ssangapur3 at gmail.com
Fri Mar 3 02:23:55 UTC 2017
Hi List,
samba version-4.4.9.
This looks very strange issue.
I have observed a issue where smbd ports are not listening after starting
samba.
"pgrep smbd" shows the process IDs but when accessed the fileshare
"connection refused" error is returned.
When checked the 'netstat -plan' for smbd no ports are listening on smbd
(139 and 445)
output of netstat -plan | grep smbd
unix 2 [ ] DGRAM 28684 6264/smbd
/samba/msg.sock/6264
unix 2 [ ] DGRAM 27698 6226/smbd
/samba/msg.sock/6226
unix 2 [ ] DGRAM 27631 6220/smbd
/samba/msg.sock/6220
unix 2 [ ] DGRAM 27638 6225/smbd
/samba/msg.sock/6225
but nmbd ports are listening (137,138)
Output of netstat -plan | grep nmbd
udp 0 0 172.16.255.255:137 0.0.0.0:*
6105/nmbd
udp 0 0 172.16.105.39:137 0.0.0.0:*
6105/nmbd
udp 0 0 0.0.0.0:137 0.0.0.0:*
6105/nmbd
udp 0 0 172.16.255.255:138 0.0.0.0:*
6105/nmbd
udp 0 0 172.16.105.39:138 0.0.0.0:*
6105/nmbd
udp 0 0 0.0.0.0:138 0.0.0.0:*
6105/nmbd
unix 2 [ ] DGRAM 26591 6105/nmbd
/samba/msg.sock/6105
unix 2 [ ACC ] STREAM LISTENING 26619 6105/nmbd
/samba/nmbd/unexpected
No errors are logged in log.smbd.
Only 'smbd version started... Copyright' log is logged.
After restarting samba service everything works fine from then.
This is not always reproducible.
(Observed only thrice)
Could you please suggest me what are the possible cases for this issue.
Is there any case where smbd is waiting for any events to start listening on
smbd ports after process is forked.
Your suggestions are highly appreciable.
Thanks & Regards,
Shivappa
--
View this message in context: http://samba.2283325.n4.nabble.com/smbd-ports-139-and-445-are-not-listening-on-samba-4-4-9-tp4715521.html
Sent from the Samba - samba-technical mailing list archive at Nabble.com.
More information about the samba-technical
mailing list