Venus: [bug]Cannot apply for FIL in Release v0.4.6

[diwufeiwen]

Describe the bug
http://user.kittyhawk.wtf:9797,Cannot apply for FIL.

curl -X POST -F "target=./go-filecoin address ls" "http://user.kittyhawk.wtf:9797/tap" | cut -d" " -f4
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 267 100 85 100 182 113 242 --:--:-- --:--:-- --:--:-- 242
bafy2bzacebeqrwbw4ip7ge4gjw6zcgy4ru5b6eplj7eqbydb63drxv2txt3mk
./go-filecoin wallet balance ./go-filecoin address ls
0

Version information
Release v0.4.6

[Lhehe]

After I retried the initialization node, I also encountered this problem.

[ckxaaa]

metoo

[ttt789]

这是真的 我也是

[steven004]

@pooja, I believe this is blocking the network trial. Could someone look into it?

[anorth]

Using the UI, I see the response is "failed to send funds"

[anorth]

The page reported a success for me just then, so it works sometimes. The balance has not yet reached my node's wallet though

I note that blocks have lots of messages like this. I initially discounted this as just an error in someone's forked implementation, but maybe it's affecting message throughput or something?

15:57:19.205  INFO consensus.: ApplyMessage failed: sector already committed at this ID SignedMessage cid=[bafy2bzacedfxgiok6zezlewceubi4bxhq67phigekdniodghd3redg5deb7u4]: {
  "meteredMessage": {
    "message": {
      "to": "t2l3mvbxn5vidkvzswyf3icl7bneuuyseau2kyvya",
      "from": "t1eqfffirfoyyjrdzlbmpghbd3yn4zaflqsm5a5lq",
      "nonce": "412",
      "value": "0",
      "method": "commitSector",
      "params": "hUKNAVggP2FRTKZ9dr+NQAbP+Yo461P62CaD0vgJH1dVldwV3ShYIPeINp7x11cmiYhKm+JDuvQLYyV4MIAH2PkPrcjxf5hZWCDi+9+GWswdF3feHxan6wU/Wl4ypprEPcR7oSbXzfPJPVkBgKDGv+zHFA2dpjZsnKo9a3KYW6t9k1m6Q0ro4zH96j34TFBeSX+ILu14b2hGlEfE9YChOatr1h9ekZv0R3MAHLhf5TF8Z/yy9YuzFE0Buec8LqYjVByvHY+5/3fGYfTmsg6er59Mrjfi8VQV75ZFskjx9BkwmFKyOT+4Qnt1RRHBwRdy09GG+PHtDMASe7ZFiIXzHBFG86Z8+f67Hm8fYSYas2O1I3cwmnl0GlodhqNkqUeCfQI1sI/V4OVhql7VFZfRy94pKL8GcXqxcQKMNXkzTlgNCHGlFK+ZLL+UH6du5nylzIftUSVUw09i4ytBF7H7DniNcmp+9SE4d5xD0Iocz4MmynEtNoRIOPgjqHqTwRUUJA6m4DuiYjlYTmvP1wSSjCap8W1BgabDPZ0fdj9Z5aab0Pt0m6jU9Hfc8ThL9ksuwq5Zoc12PnAuY7PBEaKiGZeVemcm1gC8qc/PsfBygAQIE4sYgdb60Z+hk9RNEfAnnjXHDWUqGTckRMPZoA=="
    },
    "gasPrice": "0.000000000000000001",
    "gasLimit": "300"
  },
  "signature": "vB9QPLg7uEv9fB97BjKcsMMk0vTc1XH+ZjwrwGZ0/M8ohVZmIdN8uXZYd7x6pEk35fcjCF98h4Q1fteaTncw5QA="
} processor.go:339

[jimpick]

Me too, but it eventually worked...

filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
failed to send funds
filecoin1@nuc:~$ curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap"
Success! Message CID: bafy2bzacealkhmyxafszejfe4jjcssoxeqqysb6nmivsumbnrl5axrdvrngac

[jimpick]

Update: Even though I got that Message CID 15 minutes ago, my wallet hasn't been credited with a balance yet. My chain appears to be synced. Might be a related issue maybe?

[birdmanscn]

Same problem here. I tried many times, sometimes it's Success! , sometimes it failed.
But no matter it's successful or not, my balance maintained 0.

Also, when I did

MESSAGE_CID=`curl -X POST -F "target=${WALLET_ADDR}" "http://user.kittyhawk.wtf:9797/tap" | cut -d" " -f4`

It returned like this differently everytime.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   203  100    21  100   182     20     175  0:00:01  0:00:01 --:--:--   176

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   267  100    85  100   182     104    224 --:--:-- --:--:-- --:--:--   224

Are the 21 and 85 in %Received is the percentage I received? So I never got 100% received, is it?
It seems this Total is the sum of Received and Xferd , but the total is over 100%?

And the %Received 85 case is a successful one, I got the Message CID, however it gave me this error while go-filecoin message wait ${MESSAGE_CID}

$ echo $MESSAGE_CID
bafy2bzacec6rtt6d7cueiqu2r7byrrrri7ivktjy2gev4o2kaco24ivey4z7e
$ go-filecoin message wait ${MESSAGE_CID}
Error: Post http://127.0.0.1:3453/api/message/wait?arg=bafy2bzacec6rtt6d7cueiqu2r7byrrrri7ivktjy2gev4o2kaco24ivey4z7e&encoding=json&message=true&receipt=true&return=false&stream-channels=true&timeout=10m: context deadline exceeded

And the balance is still 0

[swanduron]

The web page seems not stable in sometime. If someone gets error message likes "failed to send funds", another try is necessary in short times.

[sunhansong]

So is there a solution to it now? I've got the Success message, but my balance is still zero.

[jimpick]

I'm not on the Filecoin team, but my understanding is that there will be a new 0.4.7 release coming out soon that will fix this issue.

[zfogg]

+1

[ZenGround0]

We have some ideas about the root cause of this.

The faucet website/backing filecoin node sending messages seems to be working just fine. The issue appears to be caused by network partitions resulting from recent changes to the syncing code. Because of bugs in the syncing code block fetching occasionally stalls for one minute and prevents nodes from processing new blocks. Sometimes nodes behind this partition mine on their own chains which leads to forking. Geographically partitioned nodes (like the bootstrappers generating the messages) appear to be extra susceptible to being behind or on a fork rather than at the latest head.

It is still unclear to me why faucet messages are not propagated widely enough to make it onto all forks as they are not effectively partitioned by the syncing bugs.

devnet-staging-0.4.7 (currently on staging) fixes the worst fetch-blocking bugs, though we can't be sure how completely this addresses this bug until we have a more realistic network. We are still deciding whether we will deploy this patch to user this week, or wait for the upcoming 0.5.x release.

[wyblyf]

V0.5.6 Same problem +1

[OdysLam]

V0.5.6 Same problem +1

[OdysLam]

t1hieq4dc3y3tlptg3xy2nb4ruczlomcixak2we4a,
t1zssqje556qtduf6nh2mkbdza2acsrutqb3pnz2a

2 filecoin nodes

[OdysLam]

For some reason, FIL just disappeared and node fully synced (NAModysone)

[jimpick]

@OdysLam Same happened to me. I was informed that currently the devnet is partially broken due to a flaw / incomplete implemention that somebody was exploiting, which the team will be fixing after they get back from their planning week. Some context here:

https://github.com/filecoin-project/go-filecoin/issues/3502

[walkerxin]

V0.5.6 same problem and it's even not the return string.
And there is ubnormal my node height is bigger than that is shown in stats page.

So is the failed result reason?

[OdysLam]

@jimpick Thank you so much for this info, it saved me a ton of time from trying to figure out if I was doing something wrong.

Cheers :)