Go to file
Carsten Grohmann 674ea295a8 Line "Killed process" can contain the process UID
Newer Red Hat 7 releases changes the output of the OOM a little bit. The
last output line "Killed process" contains the process UID now.

Old:
    Killed process 6576 (java) total-vm:33914892kB, \
    anon-rss:20629004kB, file-rss:0kB, shmem-rss:0kB

New:
    Killed process 6576 (java), UID 12345, total-vm:33914892kB, \
    anon-rss:20629004kB, file-rss:0kB, shmem-rss:0kB
2020-11-19 14:58:39 +01:00
.build.yml Add build manifest 2020-10-29 21:23:54 +01:00
.gitignore Bundling multiple JS files into one single file 2020-10-29 14:32:42 +01:00
LICENSE.txt Update copyright years 2020-01-02 20:58:01 +01:00
Makefile Bundling multiple JS files into one single file 2020-10-29 14:32:42 +01:00
OOMAnalyser.html Line "Killed process" can contain the process UID 2020-11-19 14:58:39 +01:00
OOMAnalyser.py Line "Killed process" can contain the process UID 2020-11-19 14:58:39 +01:00
README.md Add bundler rollup.js to requirements 2020-11-19 09:45:46 +01:00
requirements.txt Update to Transcrypt 3.7 2020-10-29 14:14:37 +01:00

OOMAnalyser

builds.sr.ht status

Introduction

OOMAnalyser is a small project to transform the OOM message of a Linux kernel into a more user-friendly format.

OOMAnalyser consists of a web page into whose input field the OOM message is copied. JavaScript code extracts the data from it and displays the details. All processing takes place in the browser. No data is transferred to external servers. This makes it possible to use a locally stored copy of the website for analysis.

This project is written in Python and uses Transcrypt to translate Python code into JavaScript.

The current online version is available at https://www.carstengrohmann.de/oom/ .

Installation

Installing OOMAnalyser is quite easy since OOMAnalyser consists only of two files, a HTML file and a JavaScript file. Both can be stored locally to use OOMAnalyser without an Internet connection.

Installation steps

  1. Open https://www.carstengrohmann.de/oom/ in a browser
  2. Browse down to the paragraph “Local Installation” at the end of the document
  3. Download the HTML file and the JavaScript file to the main directory
  4. Open the file OOMAnalyser.html in your favourite browser

Building OOMAnalyser

Requirements

Prepare the build environment

  • Clone the repository:
# git clone https://git.sr.ht/~carstengrohmann/OOMAnalyser
  • Setup the Python virtual environment:
# virtualenv env
# . env/bin/activate
# env/bin/pip install -Ur requirements.txt

or

# make venv

Build OOMAnalyser

# . env/bin/activate
# transcrypt --build --map --nomin -e 6 OOMAnalyser.py
# rollup --format=umd --name OOMAnalyser --file=OOMAnalyser.js -- __target__/OOMAnalyser.js

or

# make build

Usage

  • Change into the source directory and start your own small web server.

  • Start Python built-in web server:

# python3 -m http.server 8080 --bind 127.0.0.1

 or

# make websrv

Resources

Known Bugs/Issues

Check the project issue tracker for current open bugs. New bugs can be reported there also.

License

This project is licensed under the MIT license.

Copyright (c) 2017-2020 Carsten Grohmann,  mail <add at here> carsten-grohmann.de

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Enjoy! Carsten Grohmann