Reverse DNS lookup possibly causing connection refused after some time in some scenarios

[MDKAOD]

I'm hesitant to call this a FreeNAS problem, but would like another set of eyes to check out the messages here.

I have a couple of WinXP boxes working with my FreeNAS device with varying degrees of activity. The system has been throwing what I figured were benign DNS errors:

Code:

Mar 18 13:55:02 library smbd[9701]: [2014/03/18 13:55:02.570751,  0] ../source3/lib/util_sock.c:941(matchname)
Mar 18 13:55:02 library smbd[9701]:  matchname: host name/name mismatch: 192.168.1.114 != (NULL)
Mar 18 13:55:02 library smbd[9701]: [2014/03/18 13:55:02.570848,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 18 13:55:02 library smbd[9701]:  matchname failed on 192.168.1.114
Mar 18 13:55:08 library smbd[9704]: [2014/03/18 13:55:08.827033,  0] ../source3/lib/util_sock.c:941(matchname)
Mar 18 13:55:08 library smbd[9704]:  matchname: host name/name mismatch: 192.168.1.26 != (NULL)
Mar 18 13:55:08 library smbd[9704]: [2014/03/18 13:55:08.827170,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 18 13:55:08 library smbd[9704]:  matchname failed on 192.168.1.26
Mar 18 13:56:40 library smbd[10188]: [2014/03/18 13:56:40.448188,  0] ../source3/lib/util_sock.c:941(matchname)
Mar 18 13:56:40 library smbd[10188]:  matchname: host name/name mismatch: 192.168.1.19 != (NULL)
Mar 18 13:56:40 library smbd[10188]: [2014/03/18 13:56:40.448343,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 18 13:56:40 library smbd[10188]:  matchname failed on 192.168.1.19

Which, according to my research into the error, basically confirmed a minor DNS issue. No problem, I obviously began to sort out, but then I started getting reports of the entire FreeNAS system "locking up" and throwing the Windows clients the "device no longer accessible" error that has cropped up on the forum from time to time.

I was not able to interact with the console at all at this point. Touching the console locked up the entire system. However, I have been able to trigger a reboot of the system through the WebGUI. The system will not fully restart and hangs after "All disks synched". A manual restart brings the system back online with no problem.

So I started pulling logs. Messages log shows the following lines just as the system locks:

Code:

Mar 18 12:25:37 library smbd[4951]:  matchname failed on 192.168.1.114
Mar 18 12:32:28 library mDNSResponder: mDNSResponder (Engineering Build) (Mar 14 2014 22:59:16) stopping
Mar 18 12:32:28 library mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000800CC0D80 01  25 _smb._tcp.local. PTR library._smb._tcp.local.
Mar 18 12:32:28 library mDNSResponder: mDNS_FinalExit failed to send goodbye for: 0000000800CC2580 01  26 _http._tcp.local. PTR library._http._tcp.local.
Mar 18 12:32:28 library smbd[3169]: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Mar 18 12:32:29 library kernel: , 3178.
Mar 18 12:32:29 library winbindd[3172]: [2014/03/18 12:32:29.271123,  0] ../source3/winbindd/winbindd.c:234(winbindd_sig_term_handler)
Mar 18 12:32:29 library winbindd[3172]:  Got sig[15] terminate (is_parent=1)
Mar 18 12:32:29 library winbindd[3973]: [2014/03/18 12:32:29.400532,  0] ../source3/winbindd/winbindd.c:234(winbindd_sig_term_handler)
Mar 18 12:32:29 library winbindd[3176]: [2014/03/18 12:32:29.400532,  0] ../source3/winbindd/winbindd.c:234(winbindd_sig_term_handler)
Mar 18 12:32:29 library winbindd[3973]:  Got sig[15] terminate (is_parent=0)
Mar 18 12:32:29 library winbindd[3176]:  Got sig[15] terminate (is_parent=0)
Mar 18 12:32:29 library ntpd[2916]: ntpd exiting on signal 15
Mar 18 12:32:29 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:29 library kernel: .
Mar 18 12:32:30 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:31 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:32 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:33 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:34 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:35 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:36 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:38 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:38 library kernel: .
Mar 18 12:32:39 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:39 library kernel: , 2354.
Mar 18 12:32:40 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:41 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:42 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:43 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:44 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:45 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:46 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:47 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:48 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:49 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:51 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:52 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:53 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:54 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:55 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:32:56 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:32:57 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:32:58 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:32:59 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:33:00 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Mar 18 12:33:01 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Mar 18 12:33:02 library python: dnssd_clientstub ConnectToServer: connect() failed Socket:4 Err:-1 Errno:61 Connection refused
Mar 18 12:33:04 library python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Mar 18 12:34:49 library syslogd: kernel boot file is /boot/kernel/kernel

This lasted a couple of days intermittently, but I have narrowed down some commonalities.

The issue has always triggered while moving data within the FreeNAS system, using a CIFS share from WinXP clients who have this DNS error. It would appear that saving to the share, reading from the share, and other interactions are no problem, but moving the data from one directory within the share to another directory increases the chances of this scenario occurring.

Can another set of eyes help me with any insight as to whether the DNS error might have caused this issue to crop up? I have since fixed the DNS issues and am apparently just waiting to see if it happens again as this is an intermittent issue.

Thanks!

 

[Yatti420]

Are you on 9.2.1.2? 9.2.1.3 is going to fix any remaining CIFS issues I believe.. Do you have hostname lookups enabled freenas side or dns service enabled on windows xp side? Anything happen if you put your ip/hostname in the global hosts field in freenas network settings?

 

[MDKAOD]

9.2.1.3 Beta. This wasn't an issue on 9.2.1.1, but began at 9.2.1.2. Figured since I needed to try the FTP/syslog issue fix, I updated to 9.2.1.3-Beta yesterday, but this issue did not fix.

Hostname lookups are enabled on the freenas side, and the initial DNS errors obviously went away when I unticked that, but I didn't hang around long enough in that configuration to see if the issue resolved or not. On the XP side, the DNS clients on both systems are on.

I did not attempt the hosts file fix. If the issue presents itself again, after fixing the reverse DNS lookups, I will check.

 

[cyberjock]

9.2.1.3 Beta. This wasn't an issue on 9.2.1.1, but began at 9.2.1.2. Figured since I needed to try the FTP/syslog issue fix, I updated to 9.2.1.3-Beta yesterday, but this issue did not fix.

Hostname lookups are enabled on the freenas side, and the initial DNS errors obviously went away when I unticked that, but I didn't hang around long enough in that configuration to see if the issue resolved or not. On the XP side, the DNS clients on both systems are on.

I did not attempt the hosts file fix. If the issue presents itself again, after fixing the reverse DNS lookups, I will check.

And you put in a ticket, right?

 

[MDKAOD]

I haven't, no. As I figured this was more of my issue than a FreeNAS issue. I will head over there right now. Thanks.

 

[cyberjock]

Tickets are good.. they won't know about the problem if there isn't a ticket. ;)

 

[MDKAOD]

Good point. :) I was more going off of the forum suggestion of "Do you think you have found a bug in FreeNAS and want to discuss it before creating a support ticket?" haha

 

[MDKAOD]

Ticket #4591