<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting on Samuel Matildes - Knowledge Base</title><link>https://docs.matildes.dev/tags/troubleshooting/</link><description>Recent content in Troubleshooting on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 14:15:13 +0100</lastBuildDate><atom:link href="https://docs.matildes.dev/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>How Antivirus Software Can Prevent Linux Boot: Troubleshooting Guide</title><link>https://docs.matildes.dev/linux/admin/antivirus-boot-issues/</link><pubDate>Fri, 31 Oct 2025 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/linux/admin/antivirus-boot-issues/</guid><description>&lt;h2 id="understanding-antivirus-boot-interference"&gt;Understanding Antivirus Boot Interference&lt;a class="td-heading-self-link" href="#understanding-antivirus-boot-interference" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Antivirus software, while crucial for system security, can sometimes interfere with the Linux boot process. This occurs when security modules become overly aggressive during system initialization, potentially causing boot failures, readonly filesystem mounts, or service startup issues.&lt;/p&gt;
&lt;h3 id="common-symptoms"&gt;Common Symptoms&lt;a class="td-heading-self-link" href="#common-symptoms" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;System fails to boot completely&lt;/li&gt;
&lt;li&gt;Filesystem mounts as readonly (&lt;code&gt;ro&lt;/code&gt;) instead of read-write (&lt;code&gt;rw&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Critical services fail to start&lt;/li&gt;
&lt;li&gt;Boot hangs at specific points&lt;/li&gt;
&lt;li&gt;SELinux/AppArmor policy violations during boot&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="filesystem-readonly-issues"&gt;Filesystem Readonly Issues&lt;a class="td-heading-self-link" href="#filesystem-readonly-issues" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;One of the most common problems occurs when antivirus software causes the root filesystem to mount readonly. This prevents the system from writing critical boot files and can halt the initialization process.&lt;/p&gt;</description></item><item><title>How to Enable Azure Serial Console and GRUB on Linux VMs</title><link>https://docs.matildes.dev/azure/vm/serial-console/</link><pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/azure/vm/serial-console/</guid><description>&lt;p&gt;Azure Serial Console is invaluable when SSH or the network is unavailable. This guide shows how to configure Linux distributions to expose the GRUB menu and kernel boot logs over the VM’s serial port on Azure, fixing cases where migrated images or some distros don’t show GRUB or any serial output.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;For proactive setup, follow Microsoft’s official guide: &lt;a href="https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/serial-console-grub-proactive-configuration"&gt;Proactive GRUB and serial console configuration for Linux on Azure&lt;/a&gt;. This article is intended for cases where you’re facing issues getting serial console and the GRUB menu to display and need troubleshooting-oriented configuration.&lt;/p&gt;</description></item><item><title>How to Troubleshoot Linux Performance — Field Playbook</title><link>https://docs.matildes.dev/linux/admin/linux-performance-playbook/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/linux/admin/linux-performance-playbook/</guid><description>&lt;p&gt;&lt;i class="fas fa-tachometer-alt" aria-hidden="true"&gt;&lt;/i&gt; A field-ready reference for Linux performance investigations — keep it open in a second terminal.&lt;/p&gt;
&lt;h2 id="how-to-use-this-playbook"&gt;How to use this playbook&lt;a class="td-heading-self-link" href="#how-to-use-this-playbook" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Linux performance problems split cleanly into &lt;strong&gt;two very different investigations&lt;/strong&gt;, and picking the wrong one wastes hours:&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Situation&lt;/th&gt;
 &lt;th&gt;Track&lt;/th&gt;
 &lt;th&gt;What you do&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;The problem is happening &lt;strong&gt;right now&lt;/strong&gt; (or you can reproduce it on demand)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Track A — Live Triage&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Interactive tools, sample at 1s intervals, follow the bottleneck&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;The problem is &lt;strong&gt;intermittent / random&lt;/strong&gt; (happens overnight, once a week, only under load you can&amp;rsquo;t reproduce)&lt;/td&gt;
 &lt;td&gt;&lt;strong&gt;Track B — Background Collection&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Arm continuous loggers &lt;em&gt;before&lt;/em&gt; the next occurrence, then mine the logs afterwards&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;div class="kb-callout kb-callout--rule"&gt;
 &lt;div class="kb-callout__title"&gt;
 &lt;i class="fas fa-bullseye" aria-hidden="true"&gt;&lt;/i&gt;
 &lt;span&gt;Rule of thumb&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="kb-callout__body"&gt;
 If you can&amp;rsquo;t reproduce it, &lt;strong&gt;do not&lt;/strong&gt; keep staring at &lt;code&gt;top&lt;/code&gt;. Stop, deploy collectors, walk away, and analyse later. Otherwise you&amp;rsquo;ll miss the event every single time.
 &lt;/div&gt;
&lt;/div&gt;

&lt;p&gt;&lt;img src="https://docs.matildes.dev/linux/admin/linux-performance-playbook/workflow.png" alt="Decision flow: live triage vs. background collection"&gt;&lt;/p&gt;</description></item><item><title>How to Analyze Linux sosreport and supportconfig with SOSParser</title><link>https://docs.matildes.dev/linux/admin/sosparser-analysis-tool/</link><pubDate>Tue, 06 Jan 2026 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/linux/admin/sosparser-analysis-tool/</guid><description>&lt;p&gt;
 &lt;a href="https://github.com/samatild/SOSParser" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-github" aria-hidden="true"&gt;&lt;/i&gt; GitHub
 &lt;/a&gt;
 &amp;nbsp;•&amp;nbsp;
 &lt;a href="https://hub.docker.com/r/samuelmatildes/sosparser" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-docker" aria-hidden="true"&gt;&lt;/i&gt; Docker Hub
 &lt;/a&gt;
 &amp;nbsp;•&amp;nbsp;
&lt;/p&gt;
&lt;p&gt;&lt;i class="fas fa-search" aria-hidden="true"&gt;&lt;/i&gt; Parse, analyze, and understand Linux diagnostic reports with automated intelligence.&lt;/p&gt;
&lt;h2 id="what-is-sosparser"&gt;What is SOSParser?&lt;a class="td-heading-self-link" href="#what-is-sosparser" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://github.com/samatild/SOSParser"&gt;&lt;code&gt;SOSParser&lt;/code&gt;&lt;/a&gt; is a powerful web application designed to automatically parse and analyze Linux &lt;code&gt;sosreport&lt;/code&gt; and &lt;code&gt;supportconfig&lt;/code&gt; diagnostic files, converting them into comprehensive, interactive HTML reports. Created to streamline the often tedious process of manually reviewing system diagnostic data, SOSParser transforms raw diagnostic archives into structured, searchable insights that accelerate troubleshooting and system analysis.&lt;/p&gt;</description></item></channel></rss>