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

Parity UI doesn't connect to my v1.11 node on linux #42

Closed
Tbaut opened this issue Apr 6, 2018 · 1 comment
Closed

Parity UI doesn't connect to my v1.11 node on linux #42

Tbaut opened this issue Apr 6, 2018 · 1 comment
Labels
F2-bug The client fails to follow expected behavior. P2-asap No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@Tbaut
Copy link
Contributor

Tbaut commented Apr 6, 2018

I'm running:

  • Which Parity version?: v1.11.0-unstable-811d165-20180404/x86_64-linux-gnu/rustc1.25.0
  • Which operating system?: Linux
  • How installed?: from source
  • Are you fully synchronized?: no
  • Which network are you connected to?: mainnet and ropsten
  • Did you try to restart the node?: yes

Launching my node with --light Parity UI shows :

Connecting to the Parity Node. If this informational message persists, please ensure that your Parity node is running and reachable on the network.

I works fine with v1.10

parity --chain foundation --light
2018-04-06 15:03:40  Starting Parity/v1.11.0-unstable-811d165-20180404/x86_64-linux-gnu/rustc1.25.0
2018-04-06 15:03:40  Keys path /home/thib/.local/share/io.parity.ethereum/keys/Foundation
2018-04-06 15:03:40  DB path /home/thib/.local/share/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2018-04-06 15:03:40  Path to dapps /home/thib/.local/share/io.parity.ethereum/dapps
2018-04-06 15:03:40  Running in experimental Light Client mode.
2018-04-06 15:03:45  Syncing #5387441 0x2ab8…8e36   286 hdr/s   3778+    0 Qed  #5387441    2/50 peers   929 KiB cache 3 MiB queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:03:45  Public node URL: enode://841015562d43c8037b127ee2a89f861d39beb468fecab72ad4bf369d3db8a01a5adeee0e0422cb021acea7ffeb0516db9e1211510ad353dc353b8c52165003d3@192.168.1.56:30303
2018-04-06 15:04:15     2/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:04:45     2/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:05:15     4/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:05:45     4/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs
2018-04-06 15:06:15     5/50 peers   3 MiB cache 0 bytes queue  RPC:  0 conn,  0 req/s,   0 µs

@Tbaut Tbaut added the bug label Apr 6, 2018
@amaury1093
Copy link
Contributor

Reproduced. Will investigate

@Tbaut Tbaut removed the bug label Apr 6, 2018
@Tbaut Tbaut closed this as completed Apr 8, 2018
@Tbaut Tbaut added F2-bug The client fails to follow expected behavior. P2-asap No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Apr 8, 2018
@Tbaut Tbaut added this to the 1.11 milestone Apr 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug The client fails to follow expected behavior. P2-asap No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

2 participants