~carstengrohmann

Germany

https://www.carstengrohmann.de

Trackers

~carstengrohmann/OOMAnalyser

Last active 2 years ago

~carstengrohmann/smm

Last active 4 years ago

#1 ERROR: Failed to extract kernel version from OOM text 10 months ago

Comment by ~carstengrohmann on ~carstengrohmann/OOMAnalyser

The OOM Analyser extracts the kernel version in a first step to choose the best fitting configuration for extracting all further values. The kernel version will be extracted based on the third OOM line:

[2003902.897143] CPU: 5 PID: 3000 Comm: salt-minion Kdump: loaded Tainted: G        W      ------------   3.10.0-1160.6.1.el7.x86_64 # 1

The line in your OOM contains the unexpected sequence ------------. Therefore, the extraction fails and the message ERROR: Failed to extract kernel version from OOM text should be shown. This bug is fixed in 8db40b50.

A second issue prevented a further memory analysis. Not all lines of the Mem-Info block contains a prefix:

[2003902.913102] Mem-Info:
[2003902.913815] active_anon:20439232 inactive_anon:11064761 isolated_anon:0
 active_file:2735 inactive_file:4097 isolated_file:0
 unevictable:0 dirty:4 writeback:198 unstable:0
 slab_reclaimable:205034 slab_unreclaimable:51897
 mapped:11464 shmem:14447592 pagetables:39090 bounce:0
 free:88803 free_pcp:33 free_cma:0

That's expected. But the code to handle this case, was broken and unfortunatelly the corresponding test also. The changeset e7bef145 solves this issue.

The current version now fully analyzes the example in this ticket.

The OOM analyzer uses complex regular expressions to extract all values from the input text. If one of these regular expressions does not match, then a message is displayed. This message contains a short description and not the regex, because it is too long and complex to be useful without much effort. Please contact me by mail or ticket if an error occurs.

REPORTED RESOLVED FIXED

#1 ERROR: Failed to extract kernel version from OOM text 11 months ago

~carstengrohmann assigned ~carstengrohmann to #1 on ~carstengrohmann/OOMAnalyser

#1 ERROR: Failed to extract kernel version from OOM text 11 months ago

Comment by ~carstengrohmann on ~carstengrohmann/OOMAnalyser

I am sorry that I am only now replying to the bug report.

The line with the kernel version contains garbage - this looks like an issue with the sourcehut software. I guess the right line would be (the space between # and 1 can be ignored):

[2003902.897143] CPU: 5 PID: 3000 Comm: salt-minion Kdump: loaded Tainted: G        W      ------------   3.10.0-1160.6.1.el7.x86_64 # 1

Is this line correct?

I changes the regular expression to detect the kernel version to match with your reported line. Please try the current version at https://www.carstengrohmann.de/oom/

There are two other issues with your OOM. I'll check both within the next days and update the bug report accordingly.

#335 Compare any two revisions in git/hg web interface 3 years ago

Ticket created by ~carstengrohmann on ~sircmpwn/git.sr.ht

Please implement a page to compare any two revisions in Git and Mercurial web interface.

Example: List any changes between tag "3.7.3" and master on GitHub: https://github.com/QQuick/Transcrypt/compare/3.7.3...master

#250 Enable markdown extensions 3 years ago

Ticket created by ~carstengrohmann on ~sircmpwn/sr.ht

[TOC]

#Desired request

please enable the markdown extensions for all places where markdown documents are formatted e.g. for readme, licenses, manpages.

#Additional notes

The extensions are part of the Python-Markdown package already and can be easily enabled.

Personally I would use the "Table of Contents" extension (https://python-markdown.github.io/extensions/toc/).

Please add additionally a note about the extensions to the sr.ht markdown documentation at https://man.sr.ht/markdown/.

Thank you,

Carsten