Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

DAWN-238 ⁃ Connecting an external eosd to testnet does not work. #864

Closed
blockone-syncclient opened this issue Dec 4, 2017 · 2 comments
Assignees
Milestone

Comments

@blockone-syncclient
Copy link

blockone-syncclient commented Dec 4, 2017

Need the ability of an external eosd to connect to the testnet.

requires a fix to net_plugin.cpp to fix a segv when restarting synchronization after a connectivity break.

ATC - find config file in the attachment, copy it to ./data-dir
run programs/eosd/eosd --resync --data-dir ./data-dir
once it is caught up, disrupt its connection to its peer, either by pulling the ethernet wire or turning off wifi.
At some point, the console output shows an "operation timed out" message.
Reconnect the cable or turn on wifi.
Observe that the eosd will catch back up with the testnet without crashing.

┆Attachments: config.ini | genesis.json

@blockone-syncclient
Copy link
Author

➤ Phil Mesnier commented:

from Telegram:
Phil Mesnier, [Dec 5, 2017 at 5:49:11 PM]:
OK. So there is now a code change for the external p2p connectivity.

tuns out that when a connection closed, it was canceling and resetting the response_expected timer, but when the connection restarted, the timer was not re-initialized so the first time a timer was required, blamo.

heifner added a commit that referenced this issue Dec 6, 2017
#864 fix reconnection sync crash and bump the sync fetch span to 100 …
@blockone-syncclient
Copy link
Author

➤ Andrianto Lie commented:

Pass.

By the way, genesis.json that is the same as the one in testnet is required for this to pass. So, if public wants to connect to the testnet, the genesis.json in github will need to be updated. [^genesis.json]

@blockone-syncclient blockone-syncclient changed the title STAT-238 ⁃ Connecting an external eosd to testnet does not work. DAWN-238 ⁃ Connecting an external eosd to testnet does not work. Jan 16, 2018
@coreylederer coreylederer added this to the Q1, 2018 milestone Mar 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants