<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Troubleshooting on Cloud Native &amp; Open Source: A Team Lead’s Working Journal</title>
    <link>https://www.msbiro.net/tags/troubleshooting/</link>
    <description>Recent content in Troubleshooting on Cloud Native &amp; Open Source: A Team Lead’s Working Journal</description>
    <image>
      <title>Cloud Native &amp; Open Source: A Team Lead’s Working Journal</title>
      <url>https://www.msbiro.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://www.msbiro.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.160.1</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Jan 2025 16:20:03 +0000</lastBuildDate>
    <atom:link href="https://www.msbiro.net/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resolving &#39;Operation Not Permitted&#39; for CyberArk Conjur Cloud CLI on macOS</title>
      <link>https://www.msbiro.net/posts/resolving-operation-not-permitted-cyberark-conjur-cloud-cli-macos/</link>
      <pubDate>Fri, 17 Jan 2025 16:20:03 +0000</pubDate>
      <guid>https://www.msbiro.net/posts/resolving-operation-not-permitted-cyberark-conjur-cloud-cli-macos/</guid>
      <description>This post details a troubleshooting journey resolving the &amp;#39;Operation Not Permitted&amp;#39; error when running the CyberArk Conjur Cloud CLI on macOS 15.2. The issue stems from macOS quarantining the binary, which can be fixed by removing the quarantine attribute via the xattr command. Follow this step-by-step guide to get your Conjur Cloud CLI up and running smoothly on macOS.</description>
    </item>
    <item>
      <title>macOS, Podman Desktop and the Podman Machine: Pay Close Attention to the Podman Version</title>
      <link>https://www.msbiro.net/posts/podman-desktop-and-podman-machine-on-macos-pay-attention-to-podman-version/</link>
      <pubDate>Fri, 10 Jan 2025 11:30:03 +0000</pubDate>
      <guid>https://www.msbiro.net/posts/podman-desktop-and-podman-machine-on-macos-pay-attention-to-podman-version/</guid>
      <description>This post explores compatibility issues when using Podman Desktop on macOS, particularly the Podman machine failing to start due to legacy Podman installations. It shares practical troubleshooting steps including identifying version conflicts, removing unsupported Podman machines, and successfully recreating them for smooth container management. Essential reading for developers managing container runtimes on macOS.</description>
    </item>
    <item>
      <title>Resolving Podman Log Rotation Issues in CyberArk Conjur Container 12.9 Deployments</title>
      <link>https://www.msbiro.net/posts/resolving-podman-log-rotation-issue-conjur-enterprise-129/</link>
      <pubDate>Wed, 24 May 2023 17:30:03 +0000</pubDate>
      <guid>https://www.msbiro.net/posts/resolving-podman-log-rotation-issue-conjur-enterprise-129/</guid>
      <description>This post addresses a log rotation issue seen in CyberArk Conjur 12.9 container deployments running on Podman. Unlike Docker, Podman requires the container to be recreated with the AUDIT_WRITE capability added and a specific permission set on the Nginx log directory for proper log rotation. The resolution was developed collaboratively with CyberArk support and is now documented for future updates. Essential guidance for operators using Podman with Conjur containers.</description>
    </item>
    <item>
      <title>Troubleshooting CyberArk Conjur Follower Setup and Postgres Connectivity</title>
      <link>https://www.msbiro.net/posts/troubleshooting-conjur-follower-setup-postgres-connectivity/</link>
      <pubDate>Mon, 21 Nov 2022 11:23:03 +0000</pubDate>
      <guid>https://www.msbiro.net/posts/troubleshooting-conjur-follower-setup-postgres-connectivity/</guid>
      <description>This post covers troubleshooting a CyberArk Conjur follower setup issue where the follower pod could connect to the Conjur API leader but failed to connect to the Postgres database, causing replication to stall and system errors. The solution involved verifying Postgres connectivity using openssl s_client with TLS, revealing a network load balancer misconfiguration that was subsequently corrected. Learn how to use this simple openssl command for effective container and network diagnostics.</description>
    </item>
    <item>
      <title>CyberArk Vault Synchronizer – CASVM035E Vault Name Is Missing: How to Fix It</title>
      <link>https://www.msbiro.net/posts/cyberark-vault-synchronizer-casvm035e-fix/</link>
      <pubDate>Fri, 30 Sep 2022 07:30:03 +0000</pubDate>
      <guid>https://www.msbiro.net/posts/cyberark-vault-synchronizer-casvm035e-fix/</guid>
      <description>This post addresses the CyberArk Vault Synchronizer error &amp;#39;CASVM035E Vault name is missing&amp;#39; encountered during upgrade from version 11.7 to 12.7. It guides users through the straightforward fix by updating the INTEGRATION_VAULT_NAME value in the VaultConjurSynchronizer.exe.config file, restoring secrets synchronization functionality on Windows.</description>
    </item>
  </channel>
</rss>
