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

Light client does not answer RPC calls #8996

Closed
Tbaut opened this issue Jun 27, 2018 · 3 comments
Closed

Light client does not answer RPC calls #8996

Tbaut opened this issue Jun 27, 2018 · 3 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Milestone

Comments

@Tbaut
Copy link
Contributor

Tbaut commented Jun 27, 2018

Before filing a new issue, please provide the following information.

I'm running:

  • Which Parity version?: Parity/v1.12.0-unstable-458afcd-20180620/x86_64-linux-gnu/rustc1.26.1
  • How installed?: from source
  • Are you fully synchronized?: yes
  • Which network are you connected to?: kovan / mainnet
  • Did you try to restart the node?: yes

When running Fether, the wallet sometimes seems not to get any answer from the node.
Any RPC such as getBalance don't get answered.
Here is a

  • gist of 1min of logs when it happens with -l pip,rpc,network
  • gist of the same 1min of logs when it happens with network filtered out for readability
  • gist of another time it happens with -l less,light_fetch,on_demand,pip_provider

Note that the last one, the problem seems to be the peer discovery.. oscillating between 1 and 0.

@Tbaut Tbaut added P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. labels Jun 27, 2018
@Tbaut Tbaut added this to the 1.12 milestone Jun 27, 2018
@Tbaut
Copy link
Contributor Author

Tbaut commented Jun 27, 2018

This seems to be a peer issue. In both cases, I end up having 1 or 2 peers, but they might not serve light clients as the logs do not show it. It could be related to #8974.

@Tbaut Tbaut changed the title Light client does not relay external calls Light client does not answer RPC calls Jul 3, 2018
@Tbaut
Copy link
Contributor Author

Tbaut commented Jul 3, 2018

This seems to not be bound to external calls as calling:
curl --data '{"method":"eth_estimateGas","params":[{"from":"0x004702bdcc3c7dbffd943136107e70b827028600", "gas":"0xcf08"}],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545 ^C
did not resolve (both while syncing or being synced)

@Tbaut Tbaut added the Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate. label Jul 3, 2018
@Tbaut
Copy link
Contributor Author

Tbaut commented Jul 3, 2018

Must be a duplicate: #8918

@Tbaut Tbaut closed this as completed Jul 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Projects
None yet
Development

No branches or pull requests

1 participant