skywire cli visor info shows dmsg server 0000.... after successful connection to dmsg

[0pcom]

[2024-03-07T09:56:25.598036393-06:00] WARN [dmsgC]: Failed to connect to the dmsg network, will try again later. timeout=20s
[2024-03-07T09:56:25.59823063-06:00] DEBUG [dmsg_ctrl]: Initialized.
[2024-03-07T09:56:25.598310372-06:00] DEBUG [transports]: Initialized.
[2024-03-07T09:56:25.598424921-06:00] DEBUG [sky_forward_conn]: Initialized.
[2024-03-07T09:56:25.598531568-06:00] DEBUG [sky_forward_conn]: Accepting sky forwarding conn...
[2024-03-07T09:56:25.598925673-06:00] DEBUG [ping]: Initialized.
[2024-03-07T09:56:25.599255886-06:00] DEBUG [visor]: Initialized.
[2024-03-07T09:56:25.599307832-06:00] INFO [visor:startup]: Startup complete.
[2024-03-07T09:56:25.599076056-06:00] DEBUG [ping]: Accepting sky ping conn...
[2024-03-07T09:58:18.675080409-06:00] WARN retrier [dmsgC]: Retrying... current_backoff=1.3s error="Get "http://dmsgd.skywire.skycoin.com/dmsg-discovery/available_servers": dial tcp 172.104.38.100:80: connect: connection timed out"
[2024-03-07T09:58:19.168138838-06:00] DEBUG [dmsgC]: Dialing session... remote_pk=0228af3fd99c8d86a882495c8e0202bdd4da78c69e013065d8634286dd4a0ac098
[2024-03-07T09:58:20.659689759-06:00] DEBUG [dmsgC]: Dialing session... remote_pk=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4
[2024-03-07T09:58:20.659840437-06:00] DEBUG [dmsgC]: Serving session. remote_pk=0228af3fd99c8d86a882495c8e0202bdd4da78c69e013065d8634286dd4a0ac098
[2024-03-07T09:58:20.659722513-06:00] DEBUG [dmsgC]: Connected to the dmsg network. timeout=20s
[2024-03-07T09:58:20.660038826-06:00] DEBUG [transport_manager]: Serving dmsg network
[2024-03-07T09:58:20.659736125-06:00] DEBUG [transport_setup]: Connected! local_pk=0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
[2024-03-07T09:58:20.660152414-06:00] DEBUG [transport_setup]: starting listener dmsg_port=47
[2024-03-07T09:58:20.660225853-06:00] DEBUG [transport_setup]: Accepting dmsg streams. dmsg_port=47
[2024-03-07T09:58:20.660072429-06:00] DEBUG [transport_manager]: listening on network: dmsg
[2024-03-07T09:58:21.431230986-06:00] DEBUG [dmsgC]: Updating entry. entry=	version: 0.0.1
	sequence: 0
	registered at: 1709827100172025892
	static public key: 0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c
	signature: da33e7ad0aeb7e4a0de8a26e3e853996d8aee721f862f7f9c6014fb65d79b950656817d4b81b36103f8ec998bb0883bdda0d221a2b13e37addeddf9b0e2e9d4400
	entry is registered as client. Related info: 
		delegated servers: 
			0228af3fd99c8d86a882495c8e0202bdd4da78c69e013065d8634286dd4a0ac098
			03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4


[2024-03-07T09:58:21.898473732-06:00] DEBUG [dmsgC]: Serving session. remote_pk=03717576ada5b1744e395c66c2bb11cea73b0e23d0dcd54422139b1a7f12e962c4

$ date ; skywire-cli visor info
Thu Mar  7 10:01:05 AM CST 2024
.:: Visor Summary ::.
Public key: "0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c"
Symmetric NAT: false
IP: 192.168.1.57
DMSG Server: "000000000000000000000000000000000000000000000000000000000000000000"
Ping: "0s"
Visor Version: unknown
Skybian Version: 
Uptime Tracker: connecting
Time Online: 300.935107 seconds
Build Tag: 

[0pcom]

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 the dmsg tracker client has started.