topic Re: RC.LOG FILE ERROR in Operating System - HP-UX

RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:10:04 GMT

Hello All,

I am getting errors in my rc.log file upon startup of the system, which is an HP-UX 11 on a k580 with 4 240 mhz processors and 2 gig of ram. All patches are up to date and I am able to ping the host and nslookup comes back correctly. I am also able to start these agents manually. Does anyone have any Ideas of how I can get this corrected and not have the errors in the log rc.log file?

Start Software Distributor agent daemon
Output from "/sbin/rc2.d/S100swagentd start":
----------------------------
ERROR: The 'swagentd' daemon started but the local hostname 'mhzfast1' cannot be resolved, therefore no SD commands will be able to contact it. The most likely solution is to define 'mhzfast1' 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 'mhzfast1' cannot be resolved, therefore no 'swconfig' or 'swremove' will be executed at this time'
The most likely solution is to define 'mhzfast1'in '/etc/hosts'.
"/sbin/rc2.d/S120swconfig start" FAILED

Re: RC.LOG FILE ERROR

PVR — Thu, 13 Nov 2003 10:12:51 GMT

Hope localhost entry is there in /etc/hosts.

have u changed the hostname recently?

Re: RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:15:27 GMT

Yes the local host entry is in the /etc/hosts file. The host name has not changed.

Re: RC.LOG FILE ERROR

Stefan Farrelly — Thu, 13 Nov 2003 10:15:35 GMT

I think this is because swagent can start BEFORE things like lan cards or fibre drivers are loaded, so it cant resolve your hostname in dns. To get around this you should have an entry in your /etc/hosts file for your host, with its IP, and in /etc/nsswitch.conf the dns line should look like this;

hosts: files [NOTFOUND=continue] dns

This should fix your errors.

Re: RC.LOG FILE ERROR

doug mielke — Thu, 13 Nov 2003 10:16:22 GMT

try nslookup mhzfast1

If you post the results, we can tell you right where to go.

/etc/hosts od nsswitch, for instance.

Re: RC.LOG FILE ERROR

Bernhard Mueller — Thu, 13 Nov 2003 10:21:45 GMT

Joseph,

your /etc/hosts should also have a line stating:

127.0.0.1 localhost loopback

Regards,
Bernhard

Re: RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:28:45 GMT

I have my loopback and ip for loopback in the hosts file as well as the hostname and ip address as well.

If I buid an nsswitch.conf file what would need to be in that I currently do not have one of those in the /etc directory.

Re: RC.LOG FILE ERROR

doug mielke — Thu, 13 Nov 2003 10:32:40 GMT

do you have /etc/resolv.conf? Maybe you're not using DNS all.

Then you'd only have to worry about /etc/hosts.

Re: RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:35:33 GMT

I am using the resolv.conf file and there are DNS entries in the table so I am guessing it is starting up before the other items like stefan said and I need to somehow configure an nsswitch.conf file will I only need the one line entry in this file:

hosts: files [NOTFOUND=continue] dns

or is there more to it then just that one line?

Re: RC.LOG FILE ERROR

Robert-Jan Goossens — Thu, 13 Nov 2003 10:36:54 GMT

Hi Joseph,

There are examples in the /usr/newconfig/etc

# ls nsswitch.*
nsswitch.compat
nsswitch.hp_defaults
nsswitch.nisplus
nsswitch.files
nsswitch.nis

Hope this helps,
Robert-Jan.

Re: RC.LOG FILE ERROR

Bernhard Mueller — Thu, 13 Nov 2003 10:37:05 GMT

There are templates, e.g.
so make a copy
cp /etc/nsswitch.files /etc/nsswitch.conf
And edit the hosts line as per Stefan's reply.

Regards,
Bernhard

Re: RC.LOG FILE ERROR

Stefan Farrelly — Thu, 13 Nov 2003 10:37:28 GMT

Have a look in /usr/newconfig/etc for example of the nsswitch.conf file. We use this one;

#
# /etc/nsswitch.hp_defaults:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# uses NIS (YP) in conjunction with files.
#

passwd: files
group: files
hosts: files [NOTFOUND=continue] dns
automount: files
aliases: files

Re: RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:46:21 GMT

Once that file is in place and the line for hosts as been added do I then need to reboot the server in order to see if it fixed the problem?

Re: RC.LOG FILE ERROR

Bernhard Mueller — Thu, 13 Nov 2003 10:49:04 GMT

just run
swlist
see if it can "contact target" .... and list your sw

Regards,
Bernhard

Re: RC.LOG FILE ERROR

Robert-Jan Goossens — Thu, 13 Nov 2003 10:52:01 GMT

You can test it,

# /usr/sbin/swagentd -r
# swlist

Robert-Jan.

Re: RC.LOG FILE ERROR

Joseph A. Starkey — Thu, 13 Nov 2003 10:55:54 GMT

Robert

When Itested it I go this error in the /var/adm/sw/swagentd.log file:

WARNING: Failure registering as Remote Procedure Call server using
protocol sequence "ncacn_ip_tcp" with endpoint "2121". The
endpoint you have specified is in use by another process.
Either another copy of the SD daemon is running or there is a
conflict in choice of endpoints with another application.
Endpoints are specified within square brackets [] in the
"rpc_binding_info=" option.
WARNING: Failure registering as Remote Procedure Call server using
protocol sequence "ncadg_ip_udp" with endpoint "2121". The
endpoint you have specified is in use by another process.
Either another copy of the SD daemon is running or there is a
conflict in choice of endpoints with another application.
Endpoints are specified within square brackets [] in the
"rpc_binding_info=" option.
ERROR: Terminating prematurely - cannot serve RPC requests with any
binding.

======= 11/13/03 15:51:54 WET END swagentd (pid = 8348, startup
error).

Re: RC.LOG FILE ERROR

Stefan Farrelly — Thu, 13 Nov 2003 10:59:13 GMT

shutdown swagent first;

/sbin/init.d/swagentd stop

and check its died;
ps -ef|grep -i swagent

If you still see an swagentd process running kill it, then restart it;

/sbin/init.d/swagentd start

Re: RC.LOG FILE ERROR

Scott Larocque_1 — Wed, 10 Dec 2003 15:22:54 GMT

I just experienced the same problem and it turned out to be the nslookup version I had installed on the system.

When HPUX runs the /sbin/init.d/swagentd start, it uses nslookup to resolve the IP address of the host. The version of nslookup I had would never use the /etc/hosts file and always go to DNS, which is not running at that point in the boot process.

Verify that your nsswitch.conf has the
hosts: files [NOTFOUND=continue] dns

nslookup mhzfast1

If you do not see Using /etc/hosts, then your nslookup is probably the problem.