Created attachment 1035 [details]
tlwebadm status section with all subcluster configuration commented out
Given non-existent subcluster configuration or one that does not declare any agents, you can start a session just fine, but tlwebadm and tlctl does not show any load information. A possible scenario where this would happen is if `agents=...' is mistyped as `agent=...'.
We fall back on an agent on 127.0.0.1 which is present in the load information sent to tlwebadm and tlctl but not presented. Error messages or warning is given by neither the services nor tlctl.
This has been observed in both 4.14.0 and 4.14.0post.