HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

h
hotplugd(1M) hotplugd(1M)
To start a new instance of
hotplugd with new values for logfile and mode, you can do so by stopping the
running instance of
hotplugd and manually starting it with the new values.
To have hotplugd always invoked on startup with the new values, change the values of the
HOTPLUGD_LOGFILE
and HOTPLUGD_MODE
variables in the configuration file,
/etc/rc.config.d/pci_olar
. At the next boot, hotplugd will be invoked with these new values.
DIAGNOSTICS
Messages in the System Log File
The following messages are logged in the system log file,
/var/adm/syslog/syslog.log
.Ifan
attention button event occurs after the daemon has been terminated following a successful start of the dae-
mon, the messages are logged in the system log file.
Could not allocate memory for PCI I/O Attention Button event
A chunk of memory, used for storing the attention button event information, could not be allocated.
The event is dropped after the power LED is set to
PWR_RAIL mode. That is, the power LED will be
set to ON if the power to the slot is ON, or the power LED will be set to OFF if the power to the slot is
OFF.
Could not add the event to the queue, dropping AB event
The queue has not been initialized (daemon not running) or the queue is under flow control. The
queue can go into flow control if the queue already has maximum number of events. Currently the
maximum is 128.
The event is dropped after setting the power LED to
PWR_RAIL mode (see previous message). Wait
till the attention button events are processed by the daemon.
Dropping AB event, slotId not found in the registered slotIds
The attention button event was received on a slot ID that has not been registered (during the system
bootup) with the kernel OLAR module.
The event is dropped after setting the power LED to PWR_RAIL mode (see previous message). Con-
tact your HP response center.
Could not get the slot information for PCI I/O Attention Button event :
slotId, olar_error_no =
olarErrMsg
The call to get the slot information failed. olarErrMsg gives the reason for the error.
This results in an invalid PCI OL* event to the daemon.
hotplugd daemon (pid= pid) is shutting down... dropping AB event : slotId
The system is clearing the attention button events in the queue due to the abnormal termination of
the daemon (for example, with the SIGKILL signal (see kill(1)) and there are pending attention but-
ton events in the queue.
While clearing the events from the queue, the system sets the power LED corresponding to the slotId,
to
PWR_RAIL mode (see previous message).
Setting the power led to PWR_RAIL mode failed : slotId, olar_error_no =
olarErrMsg
Setting the power LED to PWR_RAIL mode failed. The system sets the power LED to PWR_RAIL
mode while clearing attention button events from the queue, triggered by the abnormal termination of
the hotplugd daemon (for example, with the SIGKILL signal (see kill(1)).
Messages in the hotplugd Daemon Log File
The following messages are logged in the hotplugd daemon log file, defined by logfile.
ioctl(DEV_OLAR_GET_ABEVENT/WAIT) error : errno =
errMsg
An error has occurred on the
ioctl() call to get attention button events from the kernel in the
WAIT mode. errMsg gives the reason for the error.
ioctl(DEV_OLAR_GET_ABEVENT/NOWAIT) error : errno = errMsg
An error has occurred on the ioctl() call to get attention button events from the kernel in the
NOWAIT mode. errMsg gives the reason for the error.
Section 1M−−318 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005