HP Insight Management Agents 9.10 Managing ProLiant Servers with Linux HOW TO Whitepaper

stopped, dependent applications like the Rack Firmware Upgrade Utility terminate as well.
Table 15 (page 28)lists possible issues.
Table 15 cpqriisd messages
DetailsMessage Number
Could not setup server semaphoresMessage 1
Could not destroy server semaphores
Up sem: Ioctl Failure!
Down sem: Ioctl Failure!
Get sem: Ioctl Failure!
Set sem: Ioctl Failure!
These messages indicate that the synchronization objects called
semaphores, cannot be set up correctly. This issue most likely
occurs because the iLO driver is absent.
Description
Install the iLO driverRecommended action
Warning: Shared Memory Segment existsMessage 2
Killing process %s pid
%dpgid %d
These messages indicate that the daemon encountered a shared
memory segment that was not cleaned up properly.
Description
No action is required since this message in informational. This
warning will be removed in a later version of the Rack Infrastructure
Interface Service.
Recommended action
Multiple copies of this daemon may be running exiting…Message 3
This message indicates an issue with Rack Infrastructure Interface
Service Version 1.0.0 which disallows the starting of two copies
of the service.
Description
Only one copy of the daemon should be running at any time.Recommended action
Setup Shared Memory failed!Message 4
This message indicates that a common OS resource, shared
memory”, is not available. This issue could be due to high
Description
utilization; but most likely a memory segment from an earlier version
of this service was left behind erroneously.
Install the latest version of this service.Recommended action
Semaphore %s interrupted in %sMessage 5
Local Semaphore %s
interrupted in %s
This type of message will be logged if the service is terminated
abruptly, for example, through the “kill” command.
Description
No action is required, since this message is informational.Recommended action
Alert only seems to reach %d out of %d client applicationsMessage 6
The alerts coming from the infrastructure seem to be dispatched to
a subset of registered
Description
clients only. Most likely a client terminated suddenly without properly
deregistering itself.
This message does not indicate a problem with the Rack
Infrastructure Interface Service. However, there might be a problem
Recommended action
28 Error messages