Services failing on startup

[Don Arnold_1]

Hello,

I have several services that fail when I reboot my server.

Software Distributor Agent Daemon
Configuring all unconfigured software filesets

Here's a display from the /etc/rc.log file:

ERROR: The 'swagentd' daemon started but the local hostname 'leo.iftc.net' cannot be resolved, therefore no SD commands will be able to contact it. The most likely solution is to define 'leo.iftc.net' in '/etc/hosts'.

"/sbin/rc2.d/S100swagentd start" FAILED
Configuring all unconfigured software filesets
Output from "/sbin/rc2.d/S120swconfig start":
----------------------------
ERROR: Cannot contact the 'swagentd' daemon because the local hostname 'leo.iftc.net' cannot be resolved, therefore no 'swconfig' or 'swremove' will be executed at this time'
The most likely solution is to define 'leo.iftc.net' in '/etc/hosts'.
"/sbin/rc2.d/S120swconfig start" FAILED

I've checked this file and it is configured correctly.

The box seems to be doing just fine. However, I'm concerned that a dark problem is awaiting and I'm unaware of it.

Any suggestions would be helpful.

Thank you,

Don

[melvyn burnard]

what does : nslookup leo.iftc.net
come back with? is this the correct ip address?
if so, what does: nslookup
return,? do they match? if not, that is your problem.

[Don Arnold_1]

Melvyn,

Thank you for responding to my question. I performed the nslookup for the host name and IP and return the same value.

[Steffi Jones_1]

Hello Don,

the software distributor is very sensitive to any network changes, issues.

Did you do any changes at all to the network? Do you use DNS?

I would go down all possible network routes first.

Do you have multiple IP addresses?

Steffi Jones

[Jeroen_D]

Hi,

a strange approach from me, but what the heck. Shutdown your server and try to ping its IP.
If you get reply, then it means someone else is using your server's IP.

The reason I propose this approach is because I've had a similar problem, couldn't find it, everything else appeared normal. DNS was working fine, but still there was an IP conflict with a Windows PC.

Good luck,
Jeroen.

[eran maor]

Hi Don

i will also check the /etc/nsswitch.conf to see how he is config .

i had a same problem , i think that in my case there was not nsswtich.conf and i create it and told him to go in hosts to file and that solve the problem .

but i dont know how your network ic config
but it is a network problem . i m sure

[Laurent Paumier]

Do you have your full hostname defined in /etc/hosts as stated in the error message ? swagentd is started before network is up, so you won't have access to the DNS.

[Shannon Petry]

It's not a network problem, but a host name resolution problem....

If you are using DNS, make sure that you have your domain defined in "/etc/resolv.conf" if your using fully quallified names....If your not using DNS, then go to SAM, and modify your network service switch!

Specify "hosts, DNS, NIS" and make sure that each is set to continue! instead of fail on bad lookups...

As for someone using your IP, the easiest way to test for this is ping from a neutral box. If two echo's come back, then you have a dup (or dual NIC's on that server badly misconfigured)....

Regards,
Shannon