<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logs on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/tags/logs/</link><description>Recent content in Logs on Ghafoor's Personal Blog</description><generator>Hugo</generator><language>en</language><managingEditor>noreply@example.com (AG Sayyed)</managingEditor><webMaster>noreply@example.com (AG Sayyed)</webMaster><copyright>Copyright © 2024-2026 AG Sayyed. All Rights Reserved.</copyright><lastBuildDate>Fri, 15 May 2026 13:20:20 +0100</lastBuildDate><atom:link href="http://ghafoorsblog.com/tags/logs/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding Crash Application</title><link>http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/03-module/003-uderstanding-crash/</link><pubDate>Thu, 13 Nov 2025 11:06:11 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/03-module/003-uderstanding-crash/</guid><description>&lt;p class="lead text-primary"&gt;
This document explains how to investigate application crashes by examining logs, enabling diagnostic logging, tracing system calls, analysing recent changes, and building minimal reproduction cases to isolate root causes.
&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;When an application terminates unexpectedly, the investigation should start with all available evidence and proceed by systematically reducing the problem scope. Logs, tracing tools, and change history provide primary clues.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="logs-and-initial-evidence"&gt;Logs and Initial Evidence&lt;/h2&gt;
&lt;p&gt;Logs are the primary source of evidence. Relevant data includes timestamps and error messages around the crash time. Search logs for entries near the known crash time and for messages related to the failing component.&lt;/p&gt;</description></item><item><title>Managing Disk Space</title><link>http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/05-module/003-managing-disk-space/</link><pubDate>Tue, 11 Nov 2025 01:51:36 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/google/it-automation-content/it-automation-python-pcert/04-troubleshooting-debugging/05-module/003-managing-disk-space/</guid><description>&lt;p class="lead text-primary"&gt;
This document examines disk space management as a critical system resource, exploring how programs consume storage through binaries, data, caches, logs, and temporary files. It covers diagnostic approaches for identifying space usage patterns, understanding performance degradation as disks fill up, and implementing strategies to prevent disk exhaustion that can cause application crashes and potential data loss.
&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="understanding-disk-space-usage"&gt;Understanding Disk Space Usage&lt;/h2&gt;
&lt;h3 id="why-programs-need-disk-space"&gt;Why Programs Need Disk Space&lt;/h3&gt;
&lt;p&gt;Another resource that might need attention is the disk usage of computers. Programs may need disk space for lots of different reasons.&lt;/p&gt;</description></item></channel></rss>