RHEL8: Tang socket doesn't start at boot randomly

Solution Verified - Updated -

Issue

  • Even though tangd.socket is enabled, the socket is not initialized during boot

  • The console shows Ordering cycle found message when processing sockets.target unit

    [...] systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
    [...] systemd[1]: sockets.target: Found dependency on tangd-keygen.service/start
    [...] systemd[1]: sockets.target: Found dependency on basic.target/start
    [...] systemd[1]: sockets.target: Found dependency on sockets.target/start
    [...] systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
    [ SKIP ] Ordering cycle found, skipping Tang Server socket
    [...] systemd[1]: Stopped Switch Root.
    
  • The journal shows systemd broke an ordering cycle to be able to reach sockets.target unit

    # journalctl -b -p warning
    [...]
    [...] systemd[1]: sockets.target: Found ordering cycle on tangd.socket/start
    [...] systemd[1]: sockets.target: Found dependency on tangd-keygen.service/start
    [...] systemd[1]: sockets.target: Found dependency on basic.target/start
    [...] systemd[1]: sockets.target: Found dependency on sockets.target/start
    [...] systemd[1]: sockets.target: Job tangd.socket/start deleted to break ordering cycle starting with sockets.target/start
    [...]
    

Environment

  • Red Hat Enterprise Linux 8
    • tang

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content