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

    non-zero exit, , File "/opt/xensource/sm/EXTSR", line 78 except util.CommandException, inst: ^ SyntaxError: invalid syntax

    Scheduled Pinned Locked Moved Backup
    6 Posts 4 Posters 36 Views 4 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.
    • F Offline
      FMOTrust
      last edited by olivierlambert

      Good day Community,

      I hope all is well.

      I just want to ask a little clarity as to the following error i am experiencing, Upon checking my Backup Status. I noticed the following.

      SR_BACKEND_FAILURE(non-zero exit, , File "/opt/xensource/sm/EXTSR", line 78 except util.CommandException, inst: ^ SyntaxError: invalid syntax )This is a XenServer/XCP-ng error
      

      Last weeks Backups were working fine, however this week we received the following

      Error on all VMSs within my Hosted Hypervisor. 
      SR_BACKEND_FAILURE(non-zero exit, , File "/opt/xensource/sm/EXTSR", line 78 except util.CommandException, inst: ^ SyntaxError: invalid syntax )This is a XenServer/XCP-ng error
      

      These are all occuring on a single Host running with its own pool. All other host and pools are successful.

      Where could i read up more on the above error as the only related comment i get to this is on Creation of a VM> And these are already existing VMS. Could this had been impacted by Patch installations?
      If so, which patches should i assess to determine the root.

      Kind regards

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

        Ping @Team-Storage

        1 Reply Last reply Reply Quote 0
        • dthenotD Offline
          dthenot Vates 🪐 XCP-ng Team @FMOTrust
          last edited by

          @FMOTrust Hello,

          Could you give us the output of yum info sm please?

          F 1 Reply Last reply Reply Quote 1
          • F Offline
            FMOTrust @dthenot
            last edited by

            @dthenot

            Thank you, Found the problem was related to the Version of Python that was adjusted by one of the sysadmins to configure mailing alerts via TLS as 2.7 did not support.

            This was impacting the creation of Snapshots and was a result of script difference, thus leading to the syntax error we discovered.

            We had reverted the Alternative to 2.7 and will now enforce on Script Level to identify path variable to make use of the python3.6.

            Thank you Very Much for the quick Response.

            dthenotD 1 Reply Last reply Reply Quote 0
            • dthenotD Offline
              dthenot Vates 🪐 XCP-ng Team @FMOTrust
              last edited by dthenot

              @FMOTrust Hello,

              Good news you found the problem.
              Yes, in XCP-ng 8.3 python should point to a 2.7.5 version while python3 will point to 3.6.8 at the moment.
              I imagine you are on 8.2.1 though since the smapi is running in python 3 in 8.3.
              While the smapi is python2 only on 8.2.1 and so will expect python to point to the 2.7.5 version.

              1 Reply Last reply Reply Quote 0
              • stormiS Offline
                stormi Vates 🪐 XCP-ng Team
                last edited by

                Changing python system wide on XCP-ng shows that the appliance nature of XCP-ng is really not well understood.

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