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

    XCP-ng console unreadable because of error messages

    Scheduled Pinned Locked Moved Compute
    5 Posts 3 Posters 800 Views 2 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.
    • xerioX Offline
      xerio
      last edited by

      Running an XCP-ng host for a few hours results in the local console being unreadable and plastered with these errors:

      fcoe_driver CRITICAL: ['Traceback (most recent call last):\n', '  File "/opt/xensource/libexec/fcoe_driver", line 34, in execute\n    output = subprocess.check_output(cmd)\n', '  File "/usr/lib64/python2.7/subprocess.py", line 575, in check_output\n    raise CalledProcessError(retcode, cmd, output=output)\n', "CalledProcessError: Command '['fipvlan', '-c', '-s', 'eth1']' returned non-zero exit status 19\n"]
      

      I have actually two questions:

      • what or how can these above errors be prevented? ..not using any FCOE

      • is there a key combo or other simple way to re-draw the console menu so text becomes readable and the navigation usable again?

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        What version of XCP-ng are you running? FWIW, this same issue was discussed here, but should be fixed in v8.2.1.

        xerioX 1 Reply Last reply Reply Quote 0
        • xerioX Offline
          xerio @Danp
          last edited by

          @Danp these hosts are running:

          Version 8.2.1 ()
          Build number release/yangtze/master/58

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

            Actually, I don't think this is fixed yet in XCP-ng 8.2(.1). An update is being prepared that has a fix for it. XCP-ng 8.3 alpha already has the fix.

            xerioX 1 Reply Last reply Reply Quote 1
            • xerioX Offline
              xerio @stormi
              last edited by

              @stormi thanks, will look forward to try this out when the update drops.

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