lukeshirnia / out-of-memory Goto Github PK

If there are loads of oom instances, you will only be able to show 3
Implement an option to view more or less, and data range

Fedora 28 (and soon RHEL 8) will require journalctl compatibility as they do not log to /var/log/messages as before.
Add this functionality

Dmesg reporting OOM issues but script reporting nothing

This is because dmesg is reporting very old oom incidents.
System has rotated and purged all logs since that report so there is nothing left in the log file.

Grab the oldest date (1st line in oldest compressed file) and print message to explain that its an old message, there are no incidents since $date

Doesnt provide information with there is an OOM incident with CentOS/RHEL 5

Although the system does not log in the same manner, more information can be provided.
Update script to provide a little bit more information

Need to add the ability to scan all logs, including compressed, with date and time (occurrences)

File "<stdin>", line 80
    with open("/proc/meminfo", "r") as meminfo:
            ^
SyntaxError: invalid syntax

Note: RHEL5 and python 2.4.x are EOL. I will not go out of my way to accommodate for EOL OS's and python versions.

When there are less than 3 oom occurrences, the script will either repeat a dates output or produce and error.

"Note: Only Showing: 3 of the 94 occurences
Showing the 1st, 2nd and last"

-q, --quick option doesn't report on the main log file

Need to add command line help to the script

Currently the script does not run when the file is larger than 300Mb.
Add an option like --override to allow to bypass this limit if the device has a significant amount of RAM.

Note: Limit was put in place for small devices. Maybe add a check for free RAM and base the size of the file on that.

Investigate implementing different return codes depending on what is returned by the script

Example:

Run script with the following output:

1. NO files have OOM issues - return code 1
2. OOM Found in 1 file - return code 2
3. Loads of OOM found (> 5) - return code 3

This allows automation tools to implement different "time saved" values depending on the scripts return code

Add functionality to report on the total number of processes recorded when the system ooms

Add a flag (such as --killed) that can be used to find and display oom incidents where a specific service was killed. Maybe accept a list for multiple killed services.

Fix date objects so the sort works correctly rather than the current sorting via alphabetical

Here's the output I'm getting on Fedora 25:

Python 2.7.13

~/out-of-memory $ python oom-investigate.py 
----------------------------------------
      _____ _____ _____ 
     |     |     |     |
     |  |  |  |  | | | |
     |_____|_____|_|_|_|
     Out Of Memory Analyser

Disclaimer:
If system OOMs too viciously, there may be nothing logged!
Do NOT take this script as FACT, investigate further
----------------------------------------
Unsupported OS

Error:
'NoneType' object has no attribute 'endswith'

----------------------------------------