New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while refreshing pending block on main: strconv.ParseUint: parsing "": invalid syntax #362

Open
iRespectrum opened this Issue Jul 26, 2018 · 11 comments

Comments

Projects
None yet
5 participants
@iRespectrum
Copy link

iRespectrum commented Jul 26, 2018

System information

Parity/v1.11.7-stable-085035f-20180717/x86_64-linux-gnu/rustc1.27.1

Redis version: Redis server v=4.0.10 sha=00000000:0 malloc=jemalloc-4.0.3 bits=64 build=861c87e1c67fd396

OS & Version: Ubuntu 16.04

Commit branch and hash: (master, ba60e1c)

2018/07/26 13:48:03 Can't parse pending block number
2018/07/26 13:48:03 Error while refreshing pending block on main: strconv.ParseUint: parsing "": invalid syntax

@mikeyb

This comment has been minimized.

Copy link

mikeyb commented Jul 26, 2018

Try searching issues before posting duplicates. This was already addressed months ago

@iRespectrum

This comment has been minimized.

Copy link
Author

iRespectrum commented Jul 26, 2018

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getWork","params":[],"id":1}' http://127.0.0.1:8545

{"jsonrpc":"2.0","result":["0x823a9bc4790d16337832ac72847b9abfb42ecbf157fd2b9f03fe9f8b5e625d25","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x00000000000014d2ca992a1d6a3a4b1b110715dc6590be94cec95da6f064c356","0x5c116c"],"id":1}

Parity work

Ethereum main net

But the pool can not connect to the RPC

@atlanticcrypto

This comment has been minimized.

Copy link

atlanticcrypto commented Jul 26, 2018

@iRespectrum you need to pull the develop branch - parity 1.11 changed their json rpc conventions (removing the response the pool used for pending block height). it was fixed in the develop branch to use the getwork function instead.

@mikeyb just stop.

@mikeyb

This comment has been minimized.

Copy link

mikeyb commented Jul 26, 2018

@atlanticcrypto just stop using logic? Let the world of idiocy take over? Nah, you do you, I will do me. Keep my name out your mouth

@iRespectrum

This comment has been minimized.

Copy link
Author

iRespectrum commented Jul 28, 2018

@atlanticcrypto use the branch to develop. There in the last commit the problem is solved

@mikeyb

This comment has been minimized.

Copy link

mikeyb commented Aug 12, 2018

close issue

@parkhanju

This comment has been minimized.

Copy link

parkhanju commented Aug 20, 2018

@atlanticcrypto @iRespectrum
I have the same problem.
What is the difference between master branch and develop branch?
The code is the same.

@stone212

This comment has been minimized.

Copy link

stone212 commented Aug 29, 2018

@iRespectrum @atlanticcrypto Did this work for you? I pulled the develop branch (with git pull origin develop) and I still have the same error. I am running Parity stable 1.11.8 on Ubuntu. Maybe I did not pull correctly? It seemed smooth so I did not try to debug the pull.

Maybe 1.11.8 has new problems?

My pull looked god:

``
$ git pull origin develop
From https://github.com/sammy007/open-ethereum-pool

  • branch develop -> FETCH_HEAD
    Updating bcfc0eb..154ebf0
    Fast-forward
    README.md | 28 +++++++++++++---------------
    payouts/unlocker.go | 4 ++--
    proxy/blocks.go | 44 ++++++++++++--------------------------------
    rpc/rpc.go | 4 ++--
    4 files changed, 29 insertions(+), 51 deletions(-)
@atlanticcrypto

This comment has been minimized.

Copy link

atlanticcrypto commented Aug 29, 2018

We run 1.11.8 on our OEP with no problems.

Shouldn't matter but try it with

git clone --branch develop

@stone212

This comment has been minimized.

Copy link

stone212 commented Aug 30, 2018

Yes a fresh pull worked. Strange.

@iRespectrum

This comment has been minimized.

Copy link
Author

iRespectrum commented Sep 5, 2018

@stone212 @atlanticcrypto
Parity 2 work with develop branch
Parity 1 work with master branch
Geth work with master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment