Cannot pull from miner available balance using lotus wallet

[jamerduhgamer]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

• lotus daemon - chain sync
• lotus miner - mining and block production
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt)
• lotus miner/market - storage deal
• lotus miner/market - retrieval deal
• lotus miner/market - data transfer
• lotus client
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Lotus Version

lotus version
Daemon:  1.18.0+mainnet+git.4154e9652+api1.5.0
Local: lotus version 1.18.0+mainnet+git.4154e9652

lotus-miner version
Daemon:  1.18.0+mainnet+git.4154e9652+api1.5.0
Local: lotus-miner version 1.18.0+mainnet+git.4154e9652

lotus-wallet --version
lotus-wallet version 1.18.0+mainnet+git.bd10bdf99

Describe the Bug

The Lotus miner cannot pull from the available balance using lotus-miner actor withdraw if the owner wallet is on a remote lotus wallet server. However, you can run lotus wallet list | grep <owner address> from the lotus-miner and are able to see the owner wallet which means you have connectivity to the remote lotus wallet server and that the correct FULLNODE_API_INFO is exported as well.

Logging Information

On the lotus miner server:

lotus-miner actor control list --verbose
name       ID         key                                          use        balance
owner      f0763314   f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq               22.816796733938610151 FIL

Also on the lotus miner server that does not have the owner key locally:

lotus wallet list | grep f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq
f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq                                 22.816796733938610151 FIL   61

On the lotus miner server:

lotus-miner actor withdraw 19.89
ERROR: failed to sign message: key not found

Repo Steps

1. Have the owner wallet for a miner sit on a remote server running lotus wallet.
2. Set the lotus wallet API info on your lotus daemon server in the config.toml file under "RemoteBackEnd"
3. Have your lotus miner connected to the lotus daemon server that is also connected to the lotus wallet server.
4. Run lotus wallet list | grep <owner address> to see your connectivity to the lotus daemon and from the lotus daemon to the lotus wallet.
5. Attempt to withdraw FIL from the available balance of the SP

[geoff-vball]

@jamerduhgamer Do you have a beneficiary set for your miner?

[jamerduhgamer]

Hi @geoff-vball, no beneficiary has been set!

[jamerduhgamer]

I tried another test today, where I moved the wallet private key from the lotus wallet server onto the lotus daemon server itself and still ran into the same issue!

lotus-miner actor control list --verbose | grep f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq
owner f0763314 f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq 22.816796733938610151 FIL

lotus wallet list | grep f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq
f1mddpc4i2hayggkdfwskezcfqlb6u3ymnklazsvq 22.816796733938610151 FIL 61

lotus-miner actor withdraw 119.8998
ERROR: failed to sign message: key not found

[geoff-vball]

Does your miner have an sign/admin token for the node?

[jamerduhgamer]

Hi @geoff-vball, figured it out!

What happened was we are running two identical lotus daemons (daemon1 and daemon2) however the lotus wallet server was only connected to daemon1 and not daemon2 however the lotus miner server was connected to the daemon2.

Even though we had exported the FULLNODE_API_INFO for the correct lotus daemon (daemon1), since the miner itself was connected to the other lotus daemon (daemon2), it wasn't able to see the key with the lotus-miner actor withdraw command but could see if with the lotus wallet list command. This method has worked in the past on previous versions where we would have the lotus wallet connected to not main daemon so not sure why this is only showing up now but at least its resolved.