Skip to content
This repository has been archived by the owner on Nov 24, 2022. It is now read-only.

'invalid miner address or signature' in logs #109

Open
cerblue opened this issue Jun 21, 2022 · 1 comment
Open

'invalid miner address or signature' in logs #109

cerblue opened this issue Jun 21, 2022 · 1 comment

Comments

@cerblue
Copy link
Contributor

cerblue commented Jun 21, 2022

I'm seeing a lot of invalid miner address or signature error messages in logs, along with verifying miner address: calling full node state miner info: RPC client error: sendRequest failed: http status 503 Service Unavailable unmarshaling response: invalid character '<' looking for beginning of value. My miner (f010088) was able to get some deals recently, so the error may be happening intermittently. I've tried re-initializing the bidbot repo (signing a new verification message), and changing Lotus API gateway URL in the bidbot config, but this error persists.

@jsign
Copy link
Contributor

jsign commented Jun 21, 2022

invalid character '<' looking for the beginning of the value

Yeah, that's a signal that the GLIF API might have gone down temporarily.
I wouldn't worry much about it since that might happen once in a while (or longer if GLIF is having some particular longer downtime).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants