<?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 Support Tools</title><link>https://support.tools/tags/logs/</link><description>Recent content in Logs on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/logs/index.xml" rel="self" type="application/rss+xml"/><item><title>Ollama Server Logs: Where to Find Them on Every OS</title><link>https://support.tools/ollama-server-logs-guide/</link><pubDate>Thu, 17 Apr 2025 00:00:00 -0500</pubDate><guid>https://support.tools/ollama-server-logs-guide/</guid><description>&lt;p&gt;When a model will not load, runs on the CPU instead of the GPU, or the API returns errors, the Ollama server log is the first place to look. This guide lists where the log lives on each platform, how to follow it live, and how to turn on debug logging.&lt;/p&gt;</description></item><item><title>Deploying a Syslog Server on Linux: A Comprehensive Guide</title><link>https://support.tools/deploy-syslog-server-linux/</link><pubDate>Fri, 20 Dec 2024 05:00:00 -0500</pubDate><guid>https://support.tools/deploy-syslog-server-linux/</guid><description>&lt;p&gt;Efficient log management is crucial for system administrators and security professionals. Centralizing logs from multiple machines simplifies troubleshooting and enhances security monitoring. In this comprehensive guide, we&amp;rsquo;ll walk you through deploying a syslog server on CentOS and configuring a Kali Linux client to send its logs to the syslog server.&lt;/p&gt;</description></item><item><title>Monitoring is a Pain (and We're All Doing it Wrong)</title><link>https://support.tools/monitoring-is-a-pain-and-were-all-doing-it-wrong/</link><pubDate>Thu, 19 Dec 2024 12:00:00 -0500</pubDate><guid>https://support.tools/monitoring-is-a-pain-and-were-all-doing-it-wrong/</guid><description>&lt;p&gt;&lt;strong&gt;And we&amp;rsquo;re all doing it wrong (including me).&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Monitoring is supposed to make life easier for developers and operators, but it often does the opposite. Despite our best intentions, observability tools frequently fall short, leaving us with brittle systems, ballooning costs, and frustration.&lt;/p&gt;</description></item><item><title>Viewing Logs from the Previous Container Instance When Your Container Is Crashing</title><link>https://support.tools/viewing-logs-previous-container-instance-crashing/</link><pubDate>Fri, 18 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/viewing-logs-previous-container-instance-crashing/</guid><description>&lt;p&gt;When a Kubernetes Pod enters a &lt;strong&gt;CrashLoopBackOff&lt;/strong&gt; state, it can be challenging to figure out what’s going wrong, especially since the container may be repeatedly crashing and restarting. In these cases, viewing the logs from the &lt;strong&gt;previous instance&lt;/strong&gt; of the container can provide critical insight into why the container is failing.&lt;/p&gt;&#10;&lt;p&gt;In this post, we’ll walk through how to view the logs from a previous container instance using the &lt;code&gt;kubectl logs&lt;/code&gt; command and provide troubleshooting tips for common issues.&lt;/p&gt;</description></item></channel></rss>