Page MenuHomePhabricator

`bin/phd status` is misleading about local / remote daemons
Closed, ResolvedPublic

Description

bin/phd status attempts to synthesize pidfile and database records, but does so awkwardly in a way that isn't very explicit. In particular, it may produce output like this:

Log  Daemon  Host              Overseer ...
1    999:x   localhost         111      ...
2    888:x   host.company.com  222      ...

This is misleading. The "localhost" on the first line is because a matching daemon was found in local pidfiles. A more faithful and explicit output would be something like this:

Log  Daemon  Pidfile?   Host              Overseer ...
1    999:x   YES        host.company.com  111      ...
2    888:x   NO         host.company.com  222      ...

...although this isn't necessarily useful. Generally, this output could be significantly more useful and explicit in the modern era of autoscale pools.

The "Started" column is also pretty misleading.

Event Timeline

eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jun 1 2016, 10:37 PM
eadler moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jul 4 2016, 9:05 PM
epriestley moved this task from Backlog to vNext on the Daemons board.Feb 21 2017, 12:10 AM

I've marked D20604 as resolving this; it does so by making bin/phd status report local process status only. I strongly suspect that this is probably a better / less confusing behavior.