topic Re: unable to patch system in Operating System - HP-UX

unable to patch system

Rick Garland — Wed, 24 Jan 2007 13:44:48 GMT

Hi all:

HPUX 11.11 on rp3440
Testing a process to apply the DST patches and the tzupdater. I am working in single-user mode partly because the java needs to be "quiet" during the update process.

When I start swinstall, "Could not contact host "hpux0" because of an invaid protocol sequence. Prtocol sequences are specificed with the "-x rpc_binding_info" option. Make sure this option is specified correctly."

I have verified the /etc/hosts
I changed the nsswitch.conf to files only for the host.

When I restart swagentd -r, it exits out.

What up?

Re: unable to patch system

Steven E. Protter — Wed, 24 Jan 2007 13:49:02 GMT

Shalom,

swreg -l depot

Do that on the remote depot.

Make sure the /etc/exports configuration on the system serving up the NFS share permits access to this system, or copy the depot to local storage.

Until swagentd will run you'll never be able to get swinstall to work.

Check /var/adm/syslog/syslog.log for errors and act.

Work until swagentd is running and then you should be able to get the patch install working.

SEP

Re: unable to patch system

Geoff Wild — Wed, 24 Jan 2007 13:59:35 GMT

If you are in single user, then swagentd won't be running...

You will have to start it manually...

Rgds...Geoff

Re: unable to patch system

James R. Ferguson — Wed, 24 Jan 2007 14:01:14 GMT

Hi Rick:

You will need to start basic networking and the the 'swagentd' daemon via the appropriate '/sbin/init.d/' scripts if you have booted into single-user mode.

Regards!

...JRF...

Re: unable to patch system

John Payne_2 — Wed, 24 Jan 2007 14:02:44 GMT

Rick,

I assuming you are trying the interactive swinstall here. (Running 'swinstall' without any options.)

swinstall will always try to open up networking connections in that case. (ie to look for the depot locations you have previously used, although it doesn't actually make the connection, it tries to be ready to do so.)

I believe if you do non-interactive ('swinstall -s source LSOF') it will install for you, but honestly, I am never patching in single user mode.

Would runlevel 2 be sufficient for what you are trying to do?

John

lsof output from an interactive swinstall:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
swinstall 15100 root cwd DIR 64,0x3 8192 3262 /root
swinstall 15100 root txt REG 64,0x7 5388248 1445 /usr/sbin/swinstall
swinstall 15100 root mem REG 64,0x7 4754612 236 /usr/obam/lib/libIDMawrt.so.1
swinstall 15100 root mem REG 64,0x7 13197 1215 /usr/lib/tztab
swinstall 15100 root mem REG 64,0x7 132136 30341 /usr/lib/hpux32/libnss_files.so.1
swinstall 15100 root mem REG 64,0x7 2160832 31493 /usr/lib/hpux32/libm.so.1
swinstall 15100 root mem REG 64,0x7 2303896 31492 /usr/obam/lib/libobam.so.1
swinstall 15100 root mem REG 64,0x7 26552 122 /usr/lib/hpux32/libsin.so.1
swinstall 15100 root mem REG 64,0x7 4572596 30300 /usr/lib/hpux32/libc.so.1
swinstall 15100 root mem REG 64,0x7 13509976 30813 /usr/lib/hpux32/libdcekt.so.1
swinstall 15100 root mem REG 64,0x7 27932 31517 /usr/lib/hpux32/libdl.so.1
swinstall 15100 root mem REG 64,0x7 926384 30475 /usr/lib/hpux32/libpthread.so.1
swinstall 15100 root mem REG 64,0x7 745468 31516 /usr/lib/hpux32/dld.so
swinstall 15100 root mem REG 64,0x7 147140 31519 /usr/lib/hpux32/uld.so
swinstall 15100 root mem REG 64,0x8 532 2343 /var/spool/pwgr/status
swinstall 15100 root 0u STR 157,0 0t29344 1268 ldterm->ptem->pts
swinstall 15100 root 1u STR 157,0 0t29344 1268 ldterm->ptem->pts
swinstall 15100 root 2u STR 157,0 0t29344 1268 ldterm->ptem->pts
swinstall 15100 root 3u unix 64,0x8 0t0 7757 /var/spool/sockets/pwgr/client15100 (0x351ca200)
swinstall 15100 root 4rR REG 64,0x8 718524 39 /var/adm/sw/swinstall.log
swinstall 15100 root 5uR REG 64,0x8 718524 39 /var/adm/sw/swinstall.log
swinstall 15100 root 6u REG 64,0x8 65 1906 /var (/dev/vg00/lvol8)
swinstall 15100 root 7r CHR 207,0 0t0 71 /dev/tty
swinstall 15100 root 8u CHR 207,0 0t14759 71 /dev/tty
swinstall 15100 root 9u REG 64,0x8 47186 6273 /var (/dev/vg00/lvol8)
swinstall 15100 root 10u IPv6 0xe0000001345363c0 0t0 UDP *:* (Unbound)
swinstall 15100 root 11u unix 64,0x8 0t0 7629 /opt/dcelocal/var/rpc/local/15100/reaper (0x3cc99740)
swinstall 15100 root 13u unix 64,0x8 0t0 32166 /opt/dcelocal/var/rpc/local/15100/c-0/7001 (0x62ab9740->0x351ca580)
swinstall 15100 root 14u unix 64,0x8 0t0 8091 /opt/dcelocal/var/rpc/local/15100/c-0/7003 (0x63064ac0->0x347cbc80)

Re: unable to patch system

Rick Garland — Wed, 24 Jan 2007 14:06:54 GMT

It is probaby correct - have to have the basic networking and swagent running.

I do not install patches in single user mode either, but 1 of the requirements for the tzupdater is that no java be running or accessed during the update. With so many instances of java on the system, thought it be better idea to down the system and install in singe user. I am booting int is again and will try these options.

Thanks

Re: unable to patch system

Denver Osborn — Wed, 24 Jan 2007 14:15:03 GMT

Why not bring it down to a single user state from the default init -vs- booting it to single user?

shutdown -y 0
mount -a
swagentd -r

now isntall your patches...

-denver

Re: unable to patch system

Robert-Jan Goossens — Wed, 24 Jan 2007 14:30:25 GMT

Rick,

Ypu can configure your system as a stand alone system.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080029061

Title: SYS ADM: updating to HP-UX 11.0 with non-ethernet networking
Document ID: UNX1100059

Regards,
Robert-Jan

Re: unable to patch system

Rick Garland — Wed, 24 Jan 2007 15:54:00 GMT

All of these options worked to some degree - but not fully.
The client does not want to make the changes.

I can run the tzupdater in single-user mode and this takes care of the requirement that java be quiet during this time.

The patches can be installed normally.

Thanks

Re: unable to patch system

Steven E. Protter — Wed, 24 Jan 2007 17:32:35 GMT

Shalom,

I would suggest fixing networking by hand and taking other configuration files from working similar systems.

Normal patching can not take place in the absence of swagentd running. I'd also check permissions in /var/adm in case it needs to create a lock file of some kind.

SEP

Re: unable to patch system

Geoff Wild — Wed, 24 Jan 2007 19:43:33 GMT

We are going through the same thing now (as well as HP-UX patch bundles).

For Java, our plan is to shut down all applications on the server, punt any users, then run the Java tzupdater.

gds...Geoff