HP-UX 11i v3 Installation and Update Guide, September 2009 (Update 5 Release)

Table A-2 Known install and update problems (continued)
Description/actionProblem
The fsdaemon and the swagentd daemons are left running if drd
runcmd is sent an interrupt signal that stops the process before it has
had a chance to clean up. If you have interrupted the execution of this
command with an interrupt signal, you may check for these two processes
on the system using ps –ef:
What to do
ps -ef | grep -e swagentd -e fsdaemon
root 189 10 May 4 ?
0:00 /sbin/fs/fsdaemon -f 0
root 11701 10 06:39:39 ?
0:00 /sbin/fs/fsdaemon -f 1
root 1851 10 May 4 ?
0:23 /usr/sbin/swagentd -r
root 11694 10 06:39:39 ?
0:00 /usr/sbin/swagentd –r
What to do
Kill the two extra running processes on the system that were started
during the time that you ran the drd runcmd. In this case it would be
Process 11701 and 11694.
fsdaemon and the swagentd
daemons are left running if
drd runcmd is sent an
interrupt signal
After generating a large number of events in a short time (which does
not occur in a customer environment unless there is a catastrophic failure),
the memory footprint of SFMProviderModule cimprovagt process
increases. The increase may be in the order of 100 to 200 MB. Typically,
this may happen over a long period of time (several months to years), if
server is not rebooted during this time.
What to do
If memory footprint has increased, the solution is to disable and enable
the SFMProviderModule:
# cimprovider –dm SFMProviderModule
# cimprovider –em SFMProviderModule
SFMProviderModule
(SysFaultMgmt product)
cimprovagt process may
show increased memory
usage
During HP-UX update from HP-UX 11.31 September 2008 to HP-UX
11.31 September 2009 on PA-RISC systems, the p_client binary can
fail and dump core. The binary is restarted after the update is complete.
This problem occurs only during update and hence is temporary. The
failure of p_client does not affect any functionality, and does not cause
any loss of data.
What to do
There are no known impacts because of this problem. No workaround
exists at this time. If required, the core file can be safely removed from
the system after the update is complete.
Update from HP-UX 11.31
September 2008 to HP-UX
11.31 September 2009 on
PA-RISC systems may result
in core dump
94 Known install and update problems