Moses Narrow

#1758 is related

as noted in https://github.com/skycoin/skywire/issues/1804 the dmsghttp log server may become inaccessible even though the visor apparently maintains a connection to dmsg.

debug logging might be helpful on this ``` skywire-visor --loglvl debug ``` typically you'll see logging that says the app was started or not and the error

i have two transports shown on my local visor ``` $ skywire-cli visor pk 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c [user@linux ~]$ skywire-cli visor tp ls type id remote_pk mode label sudph 247984d4-4a1a-0eda-a67c-9e69bf0fb169 0382406ebecec832a1c27dece7cf58425a1c98753c7b3be8428d4414eada0986ac regular...

You have to deregister them by their ID, not by the port number view the IDs of the currently forwarded connections with `skywire-cli fwd -l` they should start at 1,...

What we really need for this is an endpoint on the transport discovery to show transports which have existed in the past day. Then the transport bandwidth logging may be...

I've just discovered that this is because the dmsg tracker client is only started when the hypervisor UI is accessed. `skywire cli visor info` shows the dmsg server correctly after...

3) was addressed in a previous PR. services-config is now included with the binary release and present on develop branch 1 & 2 are still outstanding

I attempted to test a local instance of the route-finder with a visor running locally - however, it did not return any routes at all. Apparently the route-finder does not...

Erson pointed out that **the route finder is supposed to use the same database as transport-discovery.** So that explains why it wasn't working on it's own. It's also wrongly documented...