Each week we invite community members to help test RNode.
We would like your help using a new log aggregation tool for nodes running on the network. We will use time in this session to help you get started using RDoctor. Then we will join a test network and walk through a few scenarios.
Please read the RDoctor documentation. We will use this software and tools to support collecting logs from nodes participating in today's testing session.
Note If you used a previous version of RNode, please delete your existing .rnode directory. Most errors experienced using RNode relate to content in the directory from a previous version.
Today's version RChain Node 0.7.1 (8b27e1209b744e30e32dd2099ab5be307d0d5afd)
Binary packages (.deb, .rpm, and .tgz) https://repo.pyr8.io/rchain/downloads/testing/
Docker image
Docker pull rchain/rnode:testing |
Go to https://docs.google.com/spreadsheets/d/18merD3OzaDk7nmxQ78SUZBzWLbxA-aOnmcdxpXrp_U0/edit#gid=0
Pick out a an unclaimed row with a validator key pair
Specify your node if you want. You can wipe your information after testing
You best support the improvement and development of the RChain platform when you file a bug to report challenge you faced or unsuccessful outcomes. This will help us collect all relevant information to better understand your setup and experience.
Testing session summary
RNode Doctor
We did have success collecting logs from some participants. We know the aggregation works. We also observed difficulties running the tool on the user side. We will work to improve the configuration and operation of the tool for next week's testing.
Blockchain
We did have success bonding 2 node operators. Two other node operators were not successful. Ticket created to investigate why. We did not observe the UNKNOWN error during the session. We did observe the creation of 2 distinct DAGs and did not observe coming to consensus on one.