HP-UX 11i v3 Installation and Update Guide, March 2009 (Update 4 Release)

Table A-1 Known Install and Update Problems (continued)
Description/ActionProblem
During removal of HP-UX Software Assistant (SWA) from your
system, the unconfigure stage may generate a message in the
swagent.log that there was a problem with connecting to the HP
SIM server:
There was an error in CLIClientLogon constructor
There was a problem connecting to the HP Systems Insight
Manager server. Make sure that:
1. Your username has been added to HP Systems Insight Manager.
2. Your username and password, if specified, are correctly spelled.
3. HP Systems Insight Manager is running.
4. You used '--' for any long options and double quotes if your
username includes a domain.
Example: <commandname> --user "mydomain\myusername" --pass mypassword
What To Do
You can safely ignore this message. It is caused by a defect in the
unconfigure script and will appear on any system where HP SIM is
inactive or is not installed. If HP SIM is active, the message will not
appear.
Removal of SWA Generates
Harmless Message in
swagent.log
During update from HP-UX 11i v2 to HP-UX 11i v3 March 2009, the
currently running sfd daemon will be stopped and restarted. This
is done in order to start the sfd daemon freshly from the newly
delivered executable. Because the update is still going on and the
OS is still 11i v2, the starting of sfd out of the new binary delivered
for 11i v3 results in generation of a core file.
What To Do
There are no other known impacts because of this problem. No
workaround exists at this time. The sfd daemon will start without
any problem once the update is complete and the system reboots. If
required, the core file can be safely removed from the system.
Update from HP-UX 11i v2 to
HP-UX 11i v3 March 2009 Will
Result In Generation Of A Core
File From sfd
After cold installation, the pwgrd(1M) daemon creates the file /var/
spool/pwgr/status with zero size and initializes it with status
information. There is a small window between file creation and
initialization in which file size is zero. If any application calls
getpw*() or getgr*() APIs during this window, they will dump
core in libc.
What To Do
Install PHCO_37620 to fix this problem. For availability of the patch,
check the HP IT Resource Center site: http://itrc.hp.com. The other
workaround is to rerun the applications/daemons that have failed
by dumping core, or reboot the system.
After Installation, Applications
Calling getpw*() or getgr*()
Will Dump Core in libc During
a Certain Window
Known Install and Update Problems 107