Messages during boot

[Randy Brown_1]

We have a J5000 running HP-UX 11i. We are seeing some messages during the boot process. A couple are concerning and a couple are informational. We would like help with correcting the problems and eliminating the "muck" during boot if possible.

The first thing to solve is:
Enable auxiliary swap space................. FAIL

The weird thing is, after boot is complete, swapinfo -t later shows all 3 swap partitions active.

the rc.log file contains the following:
Enable auxiliary swap space
Output from "/sbin/rc1.d/S500swap_start start":
----------------------------
Enabling device paging on /dev/vg00/lvol9.
/usr/sbin/swapon: /dev/vg00/lvol9 is already enabled for paging.
Enabling device paging on /dev/vg00/lvol2.
Enabling device paging on /dev/vg00/lvol5.
Warning: swapon returned exit code: 1
"/sbin/rc1.d/S500swap_start start" FAILED

It appears that we redundantly trying to activate /dev/vg00/lvol9 but I can't figure out where this is happening.

Second, we are seeing the following:
Start NIS client subsystem .......................................... Oct
13 16:52:03 clifford syslog: ypbind: no entry in /var/yp/secureservers file
10.13 16:52:03 clifford pid=1242 /usr/lib/netsvc/yp/ypbind
ypbind will not use the servers list available in the file
/var/yp/binding//ypservers for binding purpose. Also if ypbind is
invoked with -broadcast option, then -broadcast option is ignored.
10.13 16:52:03 clifford pid=1243 /usr/lib/netsvc/yp/ypbind
ypbind -ypset: allowing ypset! (this is insecure)
OK

Our NIS server is an HP K220 (model 9000/859/K220) running 10.20. I was thinking this be the result of the older OS. Upgrading this machine is not an option for us so if it's something we'll just have to deal with we can until this machine is taken offline. But, is there a way to keep these messages from displaying?

Third: this is puzzling to me. NFS seems to be working fine once booted.
Oct13 16:53:05 clifford /usr/sbin/nfsd[2046]: Cannot get address for transport tcp
host \1 service nfsd
Oct 13 16:53:05 clifford /usr/sbin/nfsd[2046]: Cannot establish NFS service over
tcp: transport setup problem.

Finally, the following messages seem informational, but we would like to not have them appear during the boot if possible. If they do indeed exhibit a problem, please feel free to elaborate.

Oct13 16:52:02 clifford rpcbind: check_netconfig: Found CLTS loopback transport
Oct 13 16:52:02 clifford rpcbind: check_netconfig: Found COTS loopback
transportOct 13 16:52:02 clifford rpcbind: check_netconfig: Found COTS ORD loopback transport
Oct 13 16:52:02 clifford rpcbind: init_transport: check binding for udp
subsystem
Oct 13 16:52:02 clifford
rpcbind: init_transport: check binding for tcp
Oct 13 16:52:02 clifford rpcbind: init_transport: check binding for ticlts
Oct 13 16:52:02 clifford rpcbind: init_transport: check binding for ticotsord
Oct 13 16:52:02 clifford rpcbind: init_transport: check binding for ticots

Oct 13
16:52:21 clifford inetd[1345]: swat/tcp: Unknown service
Oct 13 16:52:21 clifford inetd[1345]: Thru with configuration

Thank you all in advance for any information that can help me. I will happy to provide additional information as needed.

Regards,
Randy

[Steven E. Protter]

I get the warning on swap space too.

It appears to be a scripting problem versus an actual problem.

Since all my swap areas also activate, I've chosen to ignore the issue with no ill effect.

I agree with you on the conclusion that the subsequent messages are informational.

The last one is an issue:
Oct 13
16:52:21 clifford inetd[1345]: swat/tcp: Unknown service
Oct 13 16:52:21 clifford inetd[1345]: Thru with configuration

swat is a utility that lets you configure and change your samba server via a web browser. If you are running CIFS/9000 you should not get this error. If you are not running the product you may have swat configured to run and in /etc/services with no configuration to run against.

Samba/CIFS is a two daemon service, one for client one for server. This I'd look into and correct.

SEP

[Robert-Jan Goossens · Accepted solution]

Hi Randy,

I'll start with number one of your questions.

You problaly have lvol2 in your /etc/fstab.

lvol2 is your default swap filesystem and is enabled at boot time. When you rc scripts are running the system tries to enable lvol2 agian resulting in the boot messages. Remove the line simular to the one below from your fstab file.

/dev/vg00/lvol2 swap pri=0 0 2

Best regards,
Robert-Jan

[Robert-Jan Goossens]

Number two,

Check this doc.

How to restrict NIS Client/Server bindings.
DocId: KBRC00004639

http://tinyurl.com/3p8pd

Regards,
Robert-Jan

***Moderator Edit: tinyurl'd link to clean thread formatting***

[Robert-Jan Goossens]

This is what I found about the rpcbind messages.

We get the following messages in /var/adm/syslog/syslog.log at bootup:
rpcbind: init_transport: check binding for ticlts
rpcbind: svc_tli_create: t_getname failed; T_IDLE
rpcbind: svc_dg_create: could not get transport information
rpcbind: init_transport: Could not create rmtcall fd for ticlts
rpcbind: init_transport: check binding for ticotsord
rpcbind: init_transport: check binding for ticots
We installed the latest ONC cumulative patch, but it did not help.

This is a known issue. The rpcbind messages in /var/adm/syslog/syslog.log are
informational messages that were in the pre-released version of HP-UX 11.0 for
debugging purposes. As long as there are no problems with rpcbind or NFS, then
these messages can be ignored.

Regards,
Robert-Jan

[Randy Brown_1]

Thanks for the quick responses! That will definitely give me some things to look into. The fstab entry was, in fact, there. I have commented it out and will check during our next reboot.

Regarding the swat/cifs message

The values in the cifsclient and samba files in /etc/rc.config.d are:
RUN_CIFSCLIENT=0
and
RUN_SAMBA=0
respectively. ps turns up nothing running currently for either of these.
I did find links in /etc/rc2.d for the startup scripts. I have moved them to _S900 to keep them from executing at boot time. I think that should stop those messages. Do you agree?

I will look at the NIS article shorlty.

Thanks again,
Randy

[Steven E. Protter]

unerscore

I generally change the capital S to a lower case s. That I know works.

Also, don't forget the K ill scripts. No reason to waste time on the way down for daemons that are not running.

SEP

[Randy Brown_1]

The underscore works. I will sometimes use a . too so that the file is not seen with a basic listing. I will get the kill scripts too. Thanks for the reminder!

Randy