Stuart Berman

Look at the time stamps: Deal created 2022-08-05 06:43:40.209 Transfer started: 2022-08-05 06:44:54.876 (1 minute later) Deal failed: 2022-08-05 06:44:55.095 (1 second later)

That is not correct. I use boostd v1.2.0 and deals from bidbot work. Large deals from Estuary error out with commP error. Currently on lotus v1.16.1

Bidbot requires either Boost or Marketv1 as does Estuary.

I am unable to tell, most Estuary deals fail before they download for the last month.

FYI - I am still seeing this even after upgrading to `lotus-miner version` Daemon: 1.19.0-rc2+mainnet+git.2520b1644+api1.5.0 Local: lotus-miner version 1.19.0-rc2+mainnet+git.2520b1644 `boostd -version` boostd version 1.5.1-rc2+git.2c5604e

> Please let us know if you're still seeing this come up! How soon should we see this take effect? Do SPs need to do anything on our end to...

The most recent deal failed 1 hr 30 minutes ago: (time is local EST - UTC -5) 2022-11-28 15:20:22.701 | 8ms | deal failed err: data-transfer failed: could not finish...

I also got another failed deal about an hour ago: Deal 3ae043b9-cce0-42ed-a4f0-3d1758bf21df CreatedAt | 2022-11-28 21:13:06.846 (1h ago) -- | -- f3vnq2cmwig3qjisnx5hobxvsd4drn4f54xfxnv4tciw6vnjdsf5xipgafreprh5riwmgtcirpcdmi3urbg36a 12D3KooWCVXs8P7iq6ao4XhfAmKWrEeuKFWCJgqe9jGDMTqHYBjw bafyreieyllxrpqwww5sfym5owyqjbibzkwsvpubp3pt337bbnvacddkkqq bafy2bzaceapw2o3ptixrz4j7ilfte2uivybbp3xhdkrx77pvkabqbp5nw3zek Yes baga6ea4seaqkiwlcouzt6ishbbs6f5kj4y4vuoqp64hrkr7cfc5vdddjywxpwja 16 GiB (17,179,869,184 ...

Correct, I use the following IPs: - Boost/Yugabyte/Grafana/Docker/Prometheus/Bitswap = 192.168.1.98 - Lotus-miner & Lotus node = 192.168.1.95 - My Mac (browser) = 192.168.1.154 - Lotus-worker = 192.168.1.96

Using admin/admin - I now get a change password prompt After changing the default password, I get this screen: Navigating to dashboards, I see three options, all of which are...