Skip to content
This repository was archived by the owner on Oct 28, 2021. It is now read-only.
This repository was archived by the owner on Oct 28, 2021. It is now read-only.

Unable to connect aleth and geth node in private network #5263

@melhindi

Description

@melhindi

I am trying to create a private network with an aleth node and an geth node.
Both genesis config result in the same root block hash. Only the aleth node is mining. On the aleth node I used the flag --peerset requied:bb54f1d86ab216bec75b819af59bc941d76bcc0523c427599669fe3b040f094d0a19769f6a56d896354b0a5a9380e0f59a7f3a0b0f0fb0dda50ceeffd0da050f@127.0.0.1:30304 to add the geth peer and on the geth peer I used admin.addPeer("enode://6e7eab347f84cf6fb61e184b67ca2d947dc5fbbb53e1aa11c824f0fd996c2883e2d73fee94d265afc2a77dd9d96dffad434afabca8607e342e0a093a89c7fa15@127.0.0.1:30303")

The handshake between both nodes succeeds

2018-09-10 15:05:48 eth trace Generating seal on #c924987f… #60
2018-09-10 15:05:49 p2p net p2p.connect.ingress receiving auth from 127.0.0.1:65034
2018-09-10 15:05:49 p2p net Listening on local port 30303 (public: 0.0.0.0:0)
2018-09-10 15:05:49 p2p net p2p.connect.ingress receiving 460 bytes EIP-8 auth from 127.0.0.1:65034
2018-09-10 15:05:49 p2p net p2p.connect.ingress sending EIP-8 ack to 127.0.0.1:65034
2018-09-10 15:05:49 p2p net p2p.connect.ingress sending capabilities handshake
2018-09-10 15:05:49 p2p net p2p.connect.ingress recvd hello header
2018-09-10 15:05:49 p2p net p2p.connect.ingress hello frame: success. starting session.
2018-09-10 15:05:49 p2p net Hello: Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 V[5] ##3497871c… (eth,63) 0

however, I see the following message on the aleth node

2018-09-10 15:05:49 p2p net New session for capability eth; idOffset: 16
2018-09-10 15:05:49 p2p net <- [ 0x3F, 0x1B, 0x79743D, 0x8239FBEE011E49E936328A5768ECDAEF7A2060AC34E8F42E3FB56C9BA4ECA399, 0x1B8952088A122A5F3584AAB0B406E78A4F3F1EC92E2844385E543D0A0C828AD4 ]
2018-09-10 15:05:49 p2p net <- [ ]
2018-09-10 15:05:49 p2p net p2p.host.peer.register ##3497871c…
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 -> 16 [ 0x3F, 0x1B, 0x20000, 0x1B8952088A122A5F3584AAB0B406E78A4F3F1EC92E2844385E543D0A0C828AD4, 0x1B8952088A122A5F3584AAB0B406E78A4F3F1EC92E2844385E543D0A0C828AD4 ]
2018-09-10 15:05:49 p2p peer 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 Status: 63 / 27 / #1b895208…, TD: 131072 = #1b895208…
2018-09-10 15:05:49 p2p peer 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 Requesting 1 block headers starting from 4294967295
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 <- [ 0xFFFFFFFF, 0x1, 0x0, 0x0 ]
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 -> 3 [ ]
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 Latency: 0 ms
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 -> 20 [ ]
2018-09-10 15:05:49 p2p sync 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 BlocksHeaders (0 entries) : NoMoreHeaders
2018-09-10 15:05:49 p2p net 3497871c…|Geth/v1.7.2-stable-1db4ecdc/darwin-amd64/go1.9 DISABLE: Disabling capability 'eth'. Reason: Peer from another fork.
2018-09-10 15:05:49 eth client Rejigging seal engine...

and get the following error on the geth node:

INFO [09-10|15:02:31] Block synchronisation started
WARN [09-10|15:03:31] Synchronisation failed, dropping peer    peer=58dcddf9ad9a7896 err=timeout
WARN [09-10|15:04:37] Synchronisation failed, dropping peer    peer=58dcddf9ad9a7896 err=timeout

Any idea what is going wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions