ryran / rebooty-inspector Goto Github PK

View Code? Open in Web Editor NEW

6.0 6.0 3.0 142 KB

Inspect recent startup events to see if they were preceded by clean shutdowns

Shell 100.00%

rebooty-inspector's People

Contributors

Stargazers

Watchers

Forkers

ftsiadimos pgarciaq

rebooty-inspector's Issues

Request compatibility with CentOS

Would like to request this to be modified to support CentOS please.

implement bash tab-completion

yep.

add -m/--minutes option to show arbitrary number of minutes worth of logs (before each startup event)

Good idea Jack.

report which file is being parsed for each reboot?

when using the glob option, it would be nice to know which file is being parsed for the specified reboot.

for example:

[jwaterwo@collab-shell ~]$ /git/Rebooty-inspector/Rebooty-inspector . -g -n1 -a
OS detected as RHEL 7

#[1] controller-a (3.10.0-229.1.2.el7.x86_64) startup at Apr 16 23:52:00 (most recent)
  ✘ NOT PRECEDED BY CLEAN SHUTDOWN!
  Relevant log(s):
    Apr 27 03:40:10 controller-a logrotate: ALERT exited abnormally with [1]
    Apr 16 23:52:00 controller-a rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="687" x-info="http://www.rsyslog.com"] start
    Apr 16 23:51:50 controller-a kernel: Linux version 3.10.0-229.1.2.el7.x86_64 ([email protected]) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Fri Mar 6 17:12:08 EST 2015

#[2] controller-a (3.10.0-229.1.2.el7.x86_64) startup at Apr 24 15:00:21
  ✔ Preceded by clean shutdown
  Relevant log(s):
    Apr 24 14:55:47 controller-a rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="10527" x-info="http://www.rsyslog.com"] exiting on signal 15.
    Apr 24 15:00:21 controller-a rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="700" x-info="http://www.rsyslog.com"] start
    Apr 24 15:00:10 controller-a kernel: Linux version 3.10.0-229.1.2.el7.x86_64 ([email protected]) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Fri Mar 6 17:12:08 EST 2015

After seeing these I then have to search the log files to determine WHICH file is actual contains this data.

Implement rebooty-inspector as citellus plugin

Citellus is being used on daily basis over lot of sosreport and could benefit of rebooty parsing.

Tracked in risuorg/risu#321

Include kernel version for each startup event

I like this idea.

Could either be something that is always included or only visible when using --verbose or --lines.

do qa with lots of sosreports

So far, I've only run this on RHEL 5.11 (with sysklogd, rsyslog3, rsyslog5), RHEL 6.6, and RHEL 7.1. Haven't taken the time to do serious testing yet. Need to.

Get rpm into yum repo

RHEL 5 rsyslog no work-y

So far, only parsing of RHEL 5 with standard sysklogd works. Need to implement rsyslog3 and rsyslog5.

Who knows, maybe even RHEL 6.0 and 6.1 might need special treatment (from what I remember it was rsyslog4).

Older dates considered "most recent"?

When looking at files with glob, the (most recent) tag was placedon an older reboot.

[jwaterwo@collab-shell ~]$ /git/Rebooty-inspector/Rebooty-inspector . -g -a
OS detected as RHEL 7

#[1] controller-a (3.10.0-229.1.2.el7.x86_64) startup at Apr 16 23:52:00 (most recent)
  ✘ NOT PRECEDED BY CLEAN SHUTDOWN!

#[2] controller-a (3.10.0-229.1.2.el7.x86_64) startup at Apr 24 15:00:21
  ✔ Preceded by clean shutdown

Get rid of -r/--root <SOSROOT> in favor of simply <SOSROOT>

That is to say, why do we require the -r option when we could just use the non-option-argument(s) as the sosroot, like xsos does.

ryran / rebooty-inspector Goto Github PK

rebooty-inspector's People

Contributors

Stargazers

Watchers

Forkers

rebooty-inspector's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs