You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: For security-related bugs/issues, please follow the security policy.
Describe the bug
While doing retrieval testing on Lotus built of the master branch, the retrieval stopped suddenly and it appears the API stopped listening on port 1234 - but the daemon kept running, and it appears the API comes back.
Here are my logs:
Mar 28 05:29:02 Retrieving f0157535 1639420 bafykbzacedoze6ckqa36rd7sxv7pcpjhugbbdnfssif2meiivcykvcvqup5h2
Mar 28 05:29:02 % Total % Received % Xferd Average Speed Time Time Time Current
Mar 28 05:29:02 Dload Upload Total Spent Left Speed
Mar 28 05:29:02 ^M 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0^M100 556 100 378 100 178 14000 6592 --:--:-- --:--:-- --:--:-- 20592
Mar 28 05:29:02 {"jsonrpc":"2.0","result":{"Err":"","Root":{"/":"bafykbzacedoze6ckqa36rd7sxv7pcpjhugbbdnfssif2meiivcykvcvqup5h2"},"Piece":null,"Size":34359738368,"MinPrice":"2","UnsealPrice":"2","PaymentInterval":1048576,"PaymentIntervalIncrease":1048576,"Miner":"f0157528","MinerPeer":{"Address":"f0157535","ID":"12D3KooWAypLydzLVAWD9aURXSvgxGdfAEuq7cUGVLkbmxK3cMLC","PieceCID":null}},"id":1}
Mar 28 05:29:02 > Recv: 0 B, Paid 0 FIL, ClientEventOpen (DealStatusNew)
Mar 28 05:29:02 > Recv: 0 B, Paid 0 FIL, ClientEventDealProposed (DealStatusWaitForAcceptance)
Mar 28 05:29:02 > Recv: 0 B, Paid 0 FIL, ClientEventUnsealPaymentRequested (DealStatusAccepted)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventPaymentChannelAddingFunds (DealStatusPaymentChannelAllocatingLane)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventLaneAllocated (DealStatusOngoing)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventPaymentRequested (DealStatusFundsNeeded)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventSendFunds (DealStatusSendFunds)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventVoucherShortfall (DealStatusCheckFunds)
Mar 28 05:29:03 > Recv: 0 B, Paid 0 FIL, ClientEventPaymentChannelAddingFunds (DealStatusPaymentChannelAddingFunds)
Mar 28 05:32:30 > Recv: 0 B, Paid 0 FIL, ClientEventPaymentChannelReady (DealStatusOngoing)
Mar 28 05:32:30 > Recv: 0 B, Paid 0 FIL, ClientEventPaymentRequested (DealStatusFundsNeeded)
Mar 28 05:32:30 > Recv: 0 B, Paid 0 FIL, ClientEventSendFunds (DealStatusSendFunds)
Mar 28 05:32:31 Success
Mar 28 05:32:31 0.36user 0.05system 3:29.18elapsed 0%CPU (0avgtext+0avgdata 72528maxresident)k
Mar 28 05:32:31 32inputs+0outputs (1major+11499minor)pagefaults 0swaps
Mar 28 05:32:31 ERROR: dial tcp 0.0.0.0:1234: connect: connection refused
Mar 28 05:32:31
I found an interesting panic in the Lotus node logs:
Describe the bug
While doing retrieval testing on Lotus built of the master branch, the retrieval stopped suddenly and it appears the API stopped listening on port 1234 - but the daemon kept running, and it appears the API comes back.
Here are my logs:
I found an interesting panic in the Lotus node logs:
Version (run
lotus version
):The text was updated successfully, but these errors were encountered: