when performing a similar test as the one described in https://github.com/skycoin/skywire/issues/1803 ; it became apparent that the dmsghttp log server is not an accurate indicator of the visor being connected to dmsg.
All the public keys checked should be of the same version, v1.3.19 and all should respond over dmsghttp to /health checks. However, occasionally results were returned such as this
031f16af33f3674cc2830dce745f8c3213a124d1d1d4938d4558752c8939a8780d
Failed to connect to HTTP server
{
"ID": "b93fb0ef-0283-04af-b2ad-fac20d881ef8",
"Local": "031f16af33f3674cc2830dce745f8c3213a124d1d1d4938d4558752c8939a8780d",
"Remote": "0323272a60895f56aad82cb767fb5c413807adcf7c9fb0578b1b1c5807c7f29d4c",
"Type": "dmsg"
}
{
"Result": true
}
As should be apparent, that visor is connected to dmsg because it responded correctly to the transport setup and takedown request. The dmsghttp log server is, at the same time, unresponsive.
Another check of that visor's /health with dmsgcurl
[2024-04-09T08:58:00.843188591-05:00] ERROR [dmsgcurl]: error="failed to connect to HTTP server: Get "dmsg://031f16af33f3674cc2830dce745f8c3213a124d1d1d4938d4558752c8939a8780d:80/health": i/o deadline reached"
when performing a similar test as the one described in https://github.com/skycoin/skywire/issues/1803 ; it became apparent that the dmsghttp log server is not an accurate indicator of the visor being connected to dmsg.
Here is the test which was performed
All the public keys checked should be of the same version, v1.3.19 and all should respond over dmsghttp to
/health
checks. However, occasionally results were returned such as thisAs should be apparent, that visor is connected to dmsg because it responded correctly to the transport setup and takedown request. The dmsghttp log server is, at the same time, unresponsive.
Another check of that visor's
/health
withdmsgcurl
The error from above:
Is not an uncommon one to the transport bandwidth and survey collection process, many of such errors can be seen at https://fiber.skywire.dev/log-collection