mirror of
https://github.com/xcat2/confluent.git
synced 2026-09-02 07:26:04 +00:00
Markus Hilger
c13a434246
An ipmi node named no source at all, so -s dropped every event, and a log with no entries can never be named by one.
82 lines
3.4 KiB
Markdown
82 lines
3.4 KiB
Markdown
nodeeventlog(8) -- Pull eventlog from confluent nodes
|
|
============================================================
|
|
|
|
## SYNOPSIS
|
|
|
|
`nodeeventlog [options] [-s <sources>] <noderange> [clear]`
|
|
|
|
## DESCRIPTION
|
|
|
|
`nodeeventlog` pulls and optionally clears the event log from the requested
|
|
noderange.
|
|
|
|
A platform may keep its events in more than one log, and some of those are
|
|
noisier than others. Reading gathers every log the platform describes as an
|
|
event log, wherever it keeps them, and `-s` narrows the output to the ones
|
|
asked for. `-s list` names the logs a node offers rather than showing entries.
|
|
|
|
A source is named by the entries that come from it, so a log that holds no
|
|
entries is not among them, and a node whose logs are all empty names none. An
|
|
ipmi managed node keeps its events in the one log the spec gives it, which is
|
|
reported as `SEL`.
|
|
|
|
Clearing is deliberately narrower than reading: it only touches the logs the
|
|
platform's own manager publishes, so a log that only a read reaches is never
|
|
destroyed by one. A selection cannot be cleared, so `-s` and `clear` are
|
|
refused together.
|
|
|
|
## OPTIONS
|
|
|
|
* `-m MAXNODES`, `--maxnodes=MAXNODES`:
|
|
Specify a maximum number of nodes to clear if clearing log, prompting if
|
|
over the threshold
|
|
|
|
* `-l LINES`, `--lines=LINES`:
|
|
return the last <n> entries for each node in the eventlog.
|
|
|
|
* `-t TIMEFRAME`, `--timeframe=TIMEFRAME`:
|
|
return entries within a specified timeframe for each node's event log.
|
|
This will return entries from the last <n> hours or days. 1h would be
|
|
entries from within the last one hour.
|
|
|
|
|
|
* `-s SOURCES`, `--source=SOURCES`:
|
|
only show entries from the named logs, comma delimited and matched without
|
|
regard to case. `-s list` names the logs the node offers instead of showing
|
|
entries. A platform that named a log "list" would be shadowed by that.
|
|
Asking for a log the node named nothing from is reported on stderr and
|
|
exits non-zero, rather than looking like an empty log.
|
|
|
|
* `-h`, `--help`:
|
|
Show help message and exit
|
|
|
|
## EXAMPLES
|
|
* Ask which logs a node keeps:
|
|
`# nodeeventlog n2 -s list`
|
|
`n2: AuditLog,EventLog,Logs,SEL`
|
|
|
|
* Pull only the sel and the chassis log, leaving the audit noise out:
|
|
`# nodeeventlog n2 -s SEL,Logs`
|
|
`n2: 07/23/2026 13:03:12 SEL: Processor - Thermal Trip`
|
|
`n2: 08/05/2026 04:30:26 Logs: PowerUnit - Power Off`
|
|
|
|
* Pull the event log from n2 and n3:
|
|
`# nodeeventlog n2,n3`
|
|
`n2: 05/03/2017 11:44:25 Event Log Disabled - SEL Fullness - Log clear`
|
|
`n2: 05/03/2017 11:44:56 System Firmware - Progress - Unspecified`
|
|
`n3: 05/03/2017 11:44:39 Event Log Disabled - SEL Fullness - Log clear`
|
|
`n3: 05/03/2017 11:45:00 System Firmware - Progress - Unspecified`
|
|
`n3: 05/03/2017 11:47:22 System Firmware - Progress - Starting OS boot`
|
|
|
|
* Pull and clear the event log from n2 and n3:
|
|
`# nodeeventlog n2,n3 clear`
|
|
`n2: 05/03/2017 11:44:25 Event Log Disabled - SEL Fullness - Log clear`
|
|
`n2: 05/03/2017 11:44:56 System Firmware - Progress - Unspecified`
|
|
`n2: 05/03/2017 11:48:29 System Firmware - Progress - Starting OS boot`
|
|
`n3: 05/03/2017 11:44:39 Event Log Disabled - SEL Fullness - Log clear`
|
|
`n3: 05/03/2017 11:45:00 System Firmware - Progress - Unspecified`
|
|
`n3: 05/03/2017 11:47:22 System Firmware - Progress - Starting OS boot`
|
|
`# nodeeventlog n2,n3`
|
|
`n2: 05/03/2017 11:48:48 Event Log Disabled - SEL Fullness - Log clear`
|
|
`n3: 05/03/2017 11:48:52 Event Log Disabled - SEL Fullness - Log clear`
|