EON: smbd: dyndns: failed to get domainname

[Alan]

Running the snv_130 version of EON on a SuperMicro X7SPA-HF motherboard, I kept running into two error messages. The first one showed up during startup and described a failure to configure IPv4 interfaces. For example:


################################################################################

SunOS Release 5.11 Version snv_130 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Configuring devices.
Probing live-fs devices
Failed to configure IPv4 interface(s): e1000g0 e1000g1
Hostname: coltrane
Reading ZFS config: done.
Configuring network interface addresses:
e1000g0 configured
e1000g1 configured

################################################################################


I figure that since the confirmation of configuration came afterwords, it isn't a big deal. Plus, I'm able to connect to the machine so I don't really worry about it.

The second issue is that at a seemingly random interval I get a message like:

coltrane smbd[727]: dyndns: failed to get domainname

That would often appear shortly after a reboot, before I even logged into the machine. Of course, sometimes it wouldn't show up at all. While focused on the second issue, I came across this article (http://www.markwilson.co.uk/blog/2006/01/configuring-solaris-10-dhcp-client-to.htm) that described making updates to the /etc/hostname<interface> files. When I check those files from my install, they had:

coltrane

instead of:

inet coltrane


I changed the files to add the 'inet' string, cleared the dhcp cache as described (with "pkill dhcpagent" and "rm /etc/dhcp/<interface>.dhc"), ran updimg.sh and rebooted. When the machine spun back up, the first error had cleared and I got:


################################################################################

SunOS Release 5.11 Version snv_130 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Configuring devices.
Probing live-fs devices
Hostname: coltrane
Reading ZFS config: done.
Configuring network interface addresses:
e1000g0 configured
e1000g1 configured

################################################################################

I also noticed that my router was now showing the hostname (i.e. "coltrane") in it's DHCP client list. Prior to making the change, it only showed "*". So, that's a bonus.

The trick is that I'm still getting the 'coltrane smbd[727]: dyndns: failed to get domainname' messages from time to time.

So, three questions:

1) What is causing this?

2) Should I be worried about it?

3) Is there a way to make it go away?


Thanks,
-Alan

[Andre Lue]

Hi,

The "Failed to configure IPv4 interface(s): e1000g0 e1000g1" error is harmless.

The "coltrane smbd[727]: dyndns: failed to get domainname" error is most likely because /etc/nsswitch.conf contains mdns. It is fairly harmless but if you wish to fix, edit /etc/nsswitch.conf
hosts: files dns mdns
ipnodes: files dns mdns
change to
hosts: files dns
ipnodes: files dns

or enable /usr/lib/inet/mdnsd in /mnt/eon0/.exec

[Alan]

Thanks, I'll take a look at nsswitch.conf with I get home and report back here.

Also, the "Failed to configure IPv4" hasn't cropped back up since I changed the /etc/hostsname<interface> file to contain "inet <hostname>" instead of just "<hostname>".

-a

[Alan]

The '/etc/nsswitch.conf' file didn't have 'mdns' entries, but '/etc/nsswitch.dns' did. I removed those, added '/etc/nsswtich.dns' to '/mnt/eon0/.backup' so it would survive a reboot, but the error still shows up in dmesg.

I tried enabling the mdnsd daemon as well, but the message is still showing up after that.

I'm not really worried about it, but if there is somewhere I can look, I'd be happy to try to run it down. My next though is that there would be some way to disable it from smbd, but I haven't figured out where the config for that is in the CIFS install.

[Andre Lue]

Hi Al,

The nsswitch.dns is there as a template for going from host only to adding dns client capabilities. Changing that file does nothing. It is usually copied over nsswitch.conf etc.

Based on the error, I'm starting to thinking your dns server is failing on certain lookups for smbd. I'd say examine the smbd logs to see if there are any other tell tale messages. Where is your EON server pointed to for dns resolution?