Hello everyone…I’m getting these integrity and confit errors during startup. Nothing seems broken. Does anyone know a fix or should i just ignore? Thanks!

  • cbarrick@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    X.509 certs are commonly used in TLS/HTTPS.

    Why is one needed in your boot process?

    Is your drive encrypted?

    • 𝒍𝒆𝒎𝒂𝒏𝒏
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      X.509 certs are commonly used in TLS/HTTPS.

      Why is one needed in your boot process?

      Don’t know why but I found this funny

      • cbarrick@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        Did you try to set up that container to serve HTTPS?

        It sounds like you have some service configured to serve HTTPS, and it’s having trouble starting because the cert is broken.

        Only that particular service will be broken. The rest of the system is fine.

        Check systemctl status --failed for more info.

        Edit: I’m only talking about the X.509 error. The AMD error is probably related to your hardware.

        • Another_username@lemmy.worldOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I was setting up the containers to fix a problem when using wine, but found a different solution. I checked the system status. 0 units failed and x.509 isn’t mentioned