Closed zolia closed 4 years ago
2020-04-29T14:54:00.305 INF session/pingpong/accountant_promise_settler.go:159 > Loaded state for provider {“0x816c8cf15593824a772159541a9d67bd41a4ecc8”}: balance 0, available balance 0, unsettled balance 0
is the culprit. This should load proper info, like this: 2020-04-29T16:07:15.357 INF session/pingpong/accountant_promise_settler.go:159 > Loaded state for provider {“0xb8bbafc992fa207ac2877633a23dbb278b813a76”}: balance 6200000000, available balance 6200000000, unsettled balance 0
So this might happen after a fresh registration for provider. If the state fails to load from blockchain, the balance is assumed 0. This means that upon getting a payment from accountant, the provider will have a tiny bit of myst and detect that. However, the settler will also try to settle the promise, as he really needs the balance to be able to provide service.
There's 3 relevant todos in the node/session/pingpong/accountant_promise_settler.go
.
Search for:TODO: should we retry?
. Decide what to do with the initial state if we can't perform those actions. Do we quit? Do we stop service? Do we wait and retry fetching?
Dup #1422
imho there should be no such attempt at this phase. Also getting: "promise signed with wrong operator".
This happened for brand new provider, right after it registers its identity.
consumer log:
full log:
settle.log