Error while fetching TX receipt

[jrischma]

System information

Geth version: Parity

Redis version: Redis server v=4.0.9 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=a646f7df284ad47

OS & Version: Linux 16.04.4

2018/05/24 00:08:58 Failed to unlock blocks: Error while fetching TX receipt: malformed used gas: 0x5258
2018/05/24 00:08:58 Unlocking suspended due to last critical error: Error while fetching TX receipt: malformed used gas: 0x5258

Hi, i receive that error on unlocker / payout

"unlocker": {
	"enabled": true,
	"poolFee": 0,
	"poolFeeAddress": "",
	"depth": 120,
	"immatureDepth": 20,
	"keepTxFees": false,
	"interval": "10m",
	"daemon": "http://127.0.0.1:8545",
	"timeout": "10s"
},

"payouts": {
	"enabled": true,
	"requirePeers": 5,
	"interval": "120m",
	"daemon": "http://127.0.0.1:8545",
	"timeout": "10s",
	"address": "0xef339dedeb0c.......",
	"gas": "21000",
	"gasPrice": "50000000000",
	"autoGas": true,
	"threshold": 500000000,
	"bgsave": false
},

2018/05/24 00:08:58 Failed to unlock blocks: Error while fetching TX receipt: malformed used gas: 0x5258
2018/05/24 00:08:58 Unlocking suspended due to last critical error: Error while fetching TX receipt: malformed used gas: 0x5258

thanks

[rlinxy]

I got the same problem, did you fix it?

[ruzmat]

Hi,
Have you fix the problem?

[mikeyb]

FIX: stop using parity on master branch

[ruzmat]

geth version v5.5.1-8a3bc2d

[ruzmat]

I cleaned the radis, and found a new block,
this block was successfully unlocked, but the second block is also not unlocked.

Unlocking suspended due to last critical error: Error while fetching TX receipt: malformed used gas: 0x5258

[13werwolf13]

we have the same problem, we cannot find solutions on our own

@ruzmat Did you manage to find a solution?

sorry for my english

[Devkon69]

Sorry but what version of parity geth should i use???

[hackmod]

parity is recommended by maintainer but the latest geth v1.8.17 also work

• geth above v1.8.17 (extended eth_getWork) for ethereum.
• recent stable parity

[Devkon69]

I use 5.5 geth from etc but i get gas error on unlocking?? Can you point me to link of working geth im on ubuntu 16.04 Many thanks on your fast reply You are great Il giorno ven 30 nov 2018, 14:09 HackyMiner <notifications@github.com> ha scritto:

…

parity is recommended by maintainer but the latest geth v1.8.17 also work - geth above v1.8.17 (extended eth_getWork) - recent stable parity — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#342 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArYS96ybDYvL3Fc4JeOZ3A4baG35A47xks5u0S4OgaJpZM4ULX48> .

[Devkon69]

I have to clean redis after update to parity or not??

[malefol7]

same problem:
Failed to unlock blocks: Error while fetching TX receipt: malformed used gas: 0x5208 (21000)
Unlocking suspended due to last critical error: Error while fetching TX receipt: malformed used gas: 0x5208

use:Parity-Ethereum/v2.1.10-stable and open-ethereumclassic-pool

the problem seems to be on the calculation of the gas used in the unlock.go file on the function
func (u *BlockUnlocker) getExtraRewardForTx(block *rpc.GetBlockReply) (*big.Int, error) {

I'm not an expert on go, but the result of the calculation of gasUsed seems to be wrong.

someone would know how to help!

[Devkon69]

I resolved just use the ethereum standard pool not classic and modify the block reward in payout/unlock file Il giorno dom 16 dic 2018, 12:00 malefol7 <notifications@github.com> ha scritto:

…

same problem: Failed to unlock blocks: Error while fetching TX receipt: malformed used gas: 0x5208 (21000) Unlocking suspended due to last critical error: Error while fetching TX receipt: malformed used gas: 0x5208 use:Parity-Ethereum/v2.1.10-stable and open-ethereumclassic-pool the problem seems to be on the calculation of the gas used in the unlock.go file on the function func (u *BlockUnlocker) getExtraRewardForTx(block *rpc.GetBlockReply) (*big.Int, error) { I'm not an expert on go, but the result of the calculation of gasUsed seems to be wrong. someone would know how to help! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#342 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArYS91RNeVdiGuUNFFiEzvuw9JD1Ul4Iks5u5ieygaJpZM4ULX48> .