events
Display relevant miner events
events
Description
List the relevant miner events currently happening. This command may return one or more events (see details below), which most often than not represent an abnormal occurrence on the miner or one of its components.
More than one event can happen for a single component, but if the same event happens more than once, the timestamp is from the first occurrence. Once the underlying cause of the event is solved, the event disappears from the list.
Command
$ echo '{"command": "events"}' | nc $MINER_IP 4028 | jq
Currently, the following events are available:
Event code | Description |
---|---|
BOARD_ASIC_ENUMERATION_FAILURE | Board failure due to ASIC enumeration failure. |
BOARD_ASIC_INIT_FAILURE | Board failure due to ASIC initialization failure. |
BOARD_CRITICAL_PIC_FAILURE | Board failure due to critical PIC failure. |
BOARD_CRITICAL_SENSOR_FAILURE | Board failure due to a critical sensor failure. |
BOARD_HIGH_TEMPERATURE | Board temperature is above user-defined Hot Temperature. Consider activating ATM. |
BOARD_NOT_DETECTED | Board was removed or connection to control board is faulty. |
BOARD_NOT_ENOUGH_SENSORS_FAILURE | Board failure due to not enough working sensors. |
BOARD_OVERTEMP_SHUTDOWN | Board failure due to high temperature. |
FAN_FAILURE | Fan failure. |
FAN_PANIC | Fan panic. |
IDLE | Miner is in Idle mode. |
NO_ACTIVE_POOLS | No active pools available. |
NOPIC_PROTECTION | Miner shutdown due to NOPIC protection. |
NOPIC_SHUTDOWN | Board protection activated for this board. |
OVERTEMP_PROTECTION | Board overtemp protection triggered. |
PSU_PANIC | PSU panic. |
REBOOT_NOT_HASHING | Board reboot due to it not hashing. |
REBOOT_SYSINIT | Board reboot due to system initialization. This can take up to 5 minutes, depending on the model. |
REBOOT_USER | Board reboot due to user request. |
SHUTDOWN_USER | Board shutdown due to user request. |
SLEEP | Miner is in Sleep mode. |
Example
$ echo '{"command": "events"}' | nc $MINER_IP 4028 | jq
{
"EVENTS": [
{
"Code": "SHUTDOWN_USER",
"CreatedAt": "2018-03-09T12:51:53+00:00",
"Description": "Board shutdown due to user request.",
"DocUrl": "https://docs.luxor.tech/firmware/introduction-to-firmware",
"ID": 2,
"Target": "BOARD"
}
],
"STATUS": [
{
"Code": 357,
"Description": "LUXminer 2025.2.17.181707-ac0bd418",
"Msg": "Miner Events",
"STATUS": "S",
"When": 1520599918
}
],
"id": 1
}
Note that the meaning of the ID
field depends on the value of the Target
field. In the example above, this means that the shutdown event is happening to the third board (board 2).
Currently, the targets BOARD
, FAN
and MINER
can be returned; of those, only the MINER
target does not have an ID
because it is used to signal machine-wide occurrences.
Field details
Field | Notes |
---|---|
Code | The code that identifies the event. |
CreatedAt | When the event first happened. |
Description | A brief description of the event. |
DocUrl | Optional. A url pointing to official docummentation with more details about that specific event. |
ID | If present, the unique identifier of the component that triggered the event. |
Target | Can be MINER , BOARD or FAN . Together with the ID , this helps to identify the exact component that is having problems. |