The systemd from k8sp

systemd's People

Contributors

Stargazers

Watchers

systemd's Issues

systemd-analyze critical-chain flanneld.service 在不同的机器上，返回的结果不一样

在10.10.10.191上执行：

systemd-analyze critical-chain  flanneld.service

返回的结果如下：

core@coreos-191 ~ $ systemd-analyze critical-chain  flanneld.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

flanneld.service +483ms
└─system.slice
  └─-.slice
core@coreos-191 ~ $

在10.10.10.192/3上执行：

systemd-analyze critical-chain  flanneld.service

返回的结果如下：

core@coreos-192 ~ $ systemd-analyze critical-chain  flanneld.service
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

flanneld.service +842ms
└─etcd2.service @10.618s +2.467s
  └─basic.target @7.323s
    └─sockets.target @7.323s
      └─fleet.socket @13.100s +592us
        └─sysinit.target @7.261s
          └─audit-rules.service @6.792s +467ms
            └─systemd-tmpfiles-setup.service @6.491s +204ms
              └─systemd-journal-flush.service @5.427s +1.027s
                └─systemd-journald.service @1.359s +4.060s
                  └─systemd-journald-dev-log.socket
                    └─-.slice
core@coreos-192 ~ $

目前暂时不清楚具体的原因，三台机器上执行 systemctl show flanneld.service 的输出结果是基本一致的。
（193的Before属性比191/2 多了一个 multi-user.target）

Recommend Projects