Content-Type: multipart/alternative;
 boundary="------------2fptLz7uq6PazmuGRQFgFtdg"
Message-ID: <fa694cbb-fc32-46ee-8759-ac6d8084eab5@ebi.ac.uk>
Date: Thu, 20 Nov 2025 14:29:34 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Barman was hung after a Transport endpoint error
Content-Language: en-US
References: <a50e9505-b696-4717-b2c3-3a382456046d@ebi.ac.uk>
To: pgsql-admin@postgresql.org
From: Sri Mrudula Attili <sri@ebi.ac.uk>
In-Reply-To: <a50e9505-b696-4717-b2c3-3a382456046d@ebi.ac.uk>
Archived-At: 
 <https://www.postgresql.org/message-id/fa694cbb-fc32-46ee-8759-ac6d8084eab5%40ebi.ac.uk>
Precedence: bulk

This is a multi-part message in MIME format.
--------------2fptLz7uq6PazmuGRQFgFtdg
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Team,


  This is regarding our Barman backup host, which seems like hung for 5 
days with no backup, streaming, cron etc happening.

  We have checkmk monitoring that notifies us if any one of the 
parameters of Barman check fail, but we havent hot any events from 
checkmk as barman check was showing all OK and no FAILED.

What do you explain this situation in Barman.


*To provide further details about the issue:*

  * We user Data Domain as barman backup home for storage.
  * On 5th November data domain endpoints is not connect but the mount
    was still up on the host. We still dont know from the data domain
    side what caused this issue.
  * Barman log has errors*: [2800226] barman.cli ERROR: [Errno 107]
    Transport endpoint is not connected:
    '/nfs/DDbackup/pgsql-****-****/.active-model.auto'*
  * If the end point was missing barman should fail completely and the
    checks should fail as well, Which in turn would have helped us to
    identify the issue immediately.
  * The only way we figured out that there was an issue, on November
    11th one of barman backup maximum age parameter failed saying that
    weeks backup dint happen.
  * Upon checking why the backups failed etc, I went to barman logs and
    found out that all this time until the endpoint issue resolved
    barman was not doing the barman checks or barman check was hung at a
    state

*Below are the configuration details:*

  * Barman version : 3.10.0 Barman by EnterpriseDB (www.enterprisedb.com)
  * Postgresql version: (PostgreSQL) 16.9
  * Number of hosts configured: 26
  * Red Hat Enterprise Linux release 8.10

Thanks,

Sri


--------------2fptLz7uq6PazmuGRQFgFtdg
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-forward-container">
      <div class="moz-text-html" lang="x-unicode">
        <p>Hello Team,</p>
        <p><br>
        </p>
        <p> This is regarding our Barman backup host, which seems like
          hung for 5 days with no backup, streaming, cron etc happening.</p>
        <p> We have checkmk monitoring that notifies us if any one of
          the parameters of Barman check fail, but we havent hot any
          events from checkmk as barman check was showing all OK and no
          FAILED.</p>
        <p>What do you explain this situation in Barman.</p>
        <p><br>
        </p>
        <p><b>To provide further details about the issue:</b></p>
        <ul>
          <li>We user Data Domain as barman backup home for storage.</li>
          <li>On 5th November data domain endpoints is not connect but
            the mount was still up on the host. We still dont know from
            the data domain side what caused this issue.</li>
          <li>Barman log has errors<b> : [2800226] barman.cli ERROR:
              [Errno 107] Transport endpoint is not connected:
              '/nfs/DDbackup/pgsql-****-****/.active-model.auto'</b></li>
          <li>If the end point was missing barman should fail completely
            and the checks should fail as well, Which in turn would have
            helped us to identify the issue immediately.</li>
          <li>The only way we figured out that there was an issue, on
            November 11th one of barman backup maximum age parameter
            failed saying that weeks backup dint happen.</li>
          <li>Upon checking why the backups failed etc, I went to barman
            logs and found out that all this time until the endpoint
            issue resolved barman was not doing the barman checks or
            barman check was hung at a state</li>
        </ul>
        <p><b>Below are the configuration details:</b></p>
        <ul>
          <li>Barman version : 3.10.0 Barman by EnterpriseDB (<a
              class="moz-txt-link-abbreviated"
              href="http://www.enterprisedb.com" moz-do-not-send="true">www.enterprisedb.com</a>)</li>
          <li>Postgresql version: (PostgreSQL) 16.9</li>
          <li>Number of hosts configured: 26</li>
          <li>Red Hat Enterprise Linux release 8.10 </li>
        </ul>
        <p>Thanks,</p>
        <p>Sri</p>
        <p><br>
        </p>
      </div>
      <p><br>
      </p>
    </div>
  </body>
</html>

--------------2fptLz7uq6PazmuGRQFgFtdg--