ERROR: [Errno 5] Input/output error

[Boyan Botev]

I have just installed barman 1.6 and trying to troubleshoot an issue I have. I see constant "ERROR: [Errno 5] Input/output error" in the log file. I get the same error when trying to run "barman backup". I am not sure how to proceed from here and was hoping someone would be able to tell me if they have seen this issue before.  

barman diagnose

{

    "global": {

        "config": {

            "barman_home": "/var/lib/barman",

            "barman_user": "barman",

            "errors_list": [],

            "log_file": "/var/log/barman/barman.log"

        },

        "system_info": {

            "barman_ver": "1.6.0",

            "kernel_ver": "Linux c3dupgbarman1 2.6.32-573.12.1.el6.x86_64 #1 SMP Mon Nov 23 12:55:32 EST 2015 x86_64 x86_64 x86_64 GNU/Linux",

            "python_ver": "Python 2.6.6",

            "release": "RedHat Linux Red Hat Enterprise Linux Server release 6.7 (Santiago)",

            "rsync_ver": "rsync  version 3.0.6  protocol version 30",

            "ssh_ver": "OpenSSH_6.7p1 (CentrifyDC build 5.2.3-425) , OpenSSL 0.9.8zf-fips 19 Mar 2015"

        }

    },

    "servers": {}

}

Thanks,

Boyan

[Boyan Botev]

I was able to track down the issue to a problem with flock on a new NFS mount. I was also able to reproduce the problem using the flock command at the OS level. So it appears this is an environment issue and has nothing to do with barman. I am working with our Unix team to resolve the issue.  

  File "/usr/lib/python2.6/site-packages/barman/lockfile.py", line 153, in acquire

    fcntl.flock(fd, flags)

This is the OS error when trying to lock a file using flock:

flock: 200: Input/output error  

 

Thanks,

Boyan

[Boyan Botev]

I noticed that version 1.5 and above of barman has a way to redirect the lock files to a different directory than the barman home via the barman_lock_directory. Following the documentation I redirected the lock files to /var/run/barman and now my issues related to flock are resolved. Just wanted to update the thread in case someone else had the same issue.