search

trexminer / T-Rex

T-Rex NVIDIA GPU miner with web control monitoring page
2.65k stars 439 forks source link

cannot unmarshal hex number with leading zero digits #1041

Open libertas-primordium opened 2 years ago

libertas-primordium commented 2 years ago

The miner isn't logging any errors to console, but it is triggering the following error in geth:

WARN [02-04|09:10:44.313] Served eth_submitHashrate conn=127.0.0.1:56886 reqid=9 duration=0s err="invalid argument 0: json: cannot unmarshal hex number with leading zero digits into Go value of type hexutil.Uint64"

trexminer commented 2 years ago

Could you post the message that's causing this issue?

libertas-primordium commented 2 years ago

Trying to capture loopback packets on windows with wireshark involves installing drivers that I really don't want on my PC.

trexminer commented 2 years ago

You can also run T-Rex with --protocol-dump parameter and it'll print out every message it sends and receives.

lodotek commented 2 years ago

I'm having this issue to when using ethminer against geth...

bfonnes commented 2 years ago

I am getting this warning, too, while using t-rex miner to solo mine. It is a little cryptic to me. Should I be concerned?

bandrewk commented 2 years ago

Same issue here. Note that it also occurs with phoenixminer.

To replicate, mine with T-Rex against a geth instance and view the geth output.

WARN [08-02|10:47:58.372] Served eth_submitHashrate conn=<redacted>:51724 reqid=9 duration="54.876µs" err="invalid argument 0: json: cannot unmarshal hex number with leading zero digits into Go value of type hexutil.Uint64"

Last message T-Rex sends:

{"id":9,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x00000000000000000000000005e64491","0x0d34a21d0c82bf14b6c749e05ed4e8c893b9fcd1f3e84f52ff40f894803d2484"],"worker":"<redacted>"}
20220802 12:51:51.955[135272.171] <redacted>:3334 asks job 0x2eae5d26d1d287f445efdac27147915764c615232b8aa841d00d6f5c36930f91 for block 15262662
20220802 12:51:51.956[135272.172] <-IN-300-302 {"jsonrpc":"2.0","id":9,"error":{"code":-32602,"message":"invalid argument 0: json: cannot unmarshal hex number with leading zero digits into Go value of type hexutil.Uint64"}}
20220802 12:51:51.956[135272.172] <redacted>:3334 asks job 0x2eae5d26d1d287f445efdac27147915764c615232b8aa841d00d6f5c36930f91 for block 15262662
20220802 12:51:52.153[135272.369] -OUT-> POST / HTTP/1.1
Host: <redacted>:3334
Accept: */*
Content-Type: application/json
charsets: utf-8
Content-Length: 48
Decidueye10 commented 2 years ago

Got the same. Trying to solo mine using T-rex to my own Geth node and got the same warning message on my Geth console.

Has this been fixed or this is a critical error? Or mining isn't affected?

EDIT: I figured it out: When I enabled --no-hashrate-report on T-rex the error disappears. So maybe there's some incompatibility between geth and miner hashrate report?