https://lintech.uk/tags/troubleshooting/Recent content in Troubleshooting on Richard LinternHugo -- gohugo.ioen-GBCopyright © 2026 Richard LinternMon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/windows/bitlocker-suspension-investigation/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/windows/bitlocker-suspension-investigation/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Workflow for identifying why BitLocker protection is off or suspended and whether maintenance caused it. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.</p>https://lintech.uk/lab-notes/microsoft-365/exchange-recipient-investigation/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/microsoft-365/exchange-recipient-investigation/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Read-only checks for mailbox type, aliases, forwarding, permissions and delivery settings. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.</p>https://lintech.uk/lab-notes/gitops/flux-controller-health/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/flux-controller-health/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Basic controller health check: approximately 5 to 10 minutes</li> <li>Source or reconciliation investigation: approximately 15 to 30 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when Flux resources are not reconciling, a source is stale, or one of the controllers appears unhealthy.</p>https://lintech.uk/lab-notes/gitops/kustomization-troubleshooting/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/kustomization-troubleshooting/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial Kustomization checks: approximately 5 to 10 minutes</li> <li>Build or dependency investigation: approximately 15 to 30 minutes</li> <li>Render, dry-run and reconciliation validation: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when a Flux Kustomization is not ready, reports a build failure, waits on a dependency, or applies an unexpected revision.</p>https://lintech.uk/lab-notes/gitops/flux-reconciliation/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/gitops/flux-reconciliation/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Basic Flux health check: approximately 5 to 10 minutes</li> <li>Failed reconciliation investigation: approximately 10 to 30 minutes</li> <li>Render, dry-run, reconciliation and validation: approximately 15 to 45 minutes</li> </ul> <p>The actual duration depends on repository size, deployment dependencies, controller health and the cause of any reconciliation failure.</p>https://lintech.uk/lab-notes/kubernetes/node-health-resource-pressure/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/node-health-resource-pressure/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial node triage: approximately 5 to 10 minutes</li> <li>Resource-pressure investigation: approximately 15 to 30 minutes</li> <li>Host-level investigation: approximately 20 to 45 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry when a node is <code>NotReady</code>, workloads cannot schedule, resource pressure is suspected, or platform capacity needs review.</p>https://lintech.uk/lab-notes/kubernetes/pod-workload-troubleshooting/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/pod-workload-troubleshooting/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial pod triage: approximately 5 to 10 minutes</li> <li>Restart or scheduling investigation: approximately 15 to 30 minutes</li> <li>Dependency or storage investigation: approximately 30 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Use this entry to investigate pods in <code>Pending</code>, <code>Failed</code>, <code>Unknown</code>, <code>CrashLoopBackOff</code>, <code>ImagePullBackOff</code> or repeated restart states.</p>https://lintech.uk/lab-notes/linux/linux-system-health/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/linux/linux-system-health/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Review uptime, CPU, memory, storage, services, logs and network state on Linux.</p>https://lintech.uk/lab-notes/microsoft-365/service-health-checks/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/microsoft-365/service-health-checks/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Review tenant service health, advisories and workload-specific diagnostics. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.</p>https://lintech.uk/lab-notes/security/wazuh-agent-troubleshooting/Mon, 31 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/security/wazuh-agent-troubleshooting/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial checks: approximately 10 to 20 minutes</li> <li>Detailed investigation: approximately 20 to 60 minutes</li> </ul> </blockquote> <h2 class="relative group">Purpose <div id="purpose" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#purpose" aria-label="Anchor">#</a> </span> </h2> <p>Investigate Wazuh agent service state, connectivity, enrollment and telemetry flow.</p>https://lintech.uk/lab-notes/kubernetes/cluster-health-checks/Sun, 30 Aug 2026 00:00:00 +0000https://lintech.uk/lab-notes/kubernetes/cluster-health-checks/<blockquote><p><strong>Time guide</strong></p> <ul> <li>Initial cluster triage: approximately 10 to 20 minutes</li> <li>Standard health review: approximately 30 minutes</li> <li>Full platform, storage and host review: approximately 30 to 60 minutes</li> </ul> <p>The actual duration depends on cluster size, access availability and whether any checks identify faults that need further investigation.</p>