XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Lock file is already being held

    Scheduled Pinned Locked Moved Xen Orchestra
    6 Posts 2 Posters 1.2k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • brodiecyberB Offline
      brodiecyber
      last edited by

      Hello

      I checked my delta and full backup jobs this morning and some of my vms failed the job and received the error in the title

      Lock file is already being held

      What does this error mean and how can dive further into the logs im currently looking through the XOA logs tab to see what i can find. Any guidance would be appreciated

      thanks

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        Without knowing which XO version are you using, it's a bit hard to tell. Are you using XO from the sources or XOA?

        brodiecyberB 1 Reply Last reply Reply Quote 0
        • brodiecyberB Offline
          brodiecyber @olivierlambert
          last edited by

          olivierlambert hello im using xen orchestra from source on xo-server 5.83.0 and xo-web 5.89.0 manageing 2 xc-png 8.2.0 hosts

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Please check you are on latest commit on master and rebuild please 🙂

            brodiecyberB 1 Reply Last reply Reply Quote 0
            • brodiecyberB Offline
              brodiecyber @olivierlambert
              last edited by

              olivierlambert sorry for the later reply ive been a just abit busy with a Kubernetes cluster
              will get on it tomorrow

              brodiecyberB 1 Reply Last reply Reply Quote 0
              • brodiecyberB Offline
                brodiecyber @brodiecyber
                last edited by

                brodiecyber Looks like it was some fluke with the way i scheduled the backup job as after i reorganized the times for the backup jobs im not encountering the error anymore.

                so entirely my fault was experimenting with incremental backups

                Thanks

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post