Verify that the newly deployed Replica nodes are operational and include the parameter values defined in the deployment descriptor.

Prerequisites

Verify that the VMware Blockchain nodes are deployed. See Deploy VMware Blockchain Nodes Using VMware Blockchain Orchestrator on AWS.

Procedure

  1. SSH into the Replica node.
  2. Enter the login credentials for the VMware Blockchain Orchestrator user account.
  3. To view all the running containers, run the sudo docker ps -a command
  4. Verify that the following containers are running.

    • Concord

    • daml_execution_engine

    • jaeger-agent

    • wavefront-proxy (optional)

      This container appears if you have set up metrics and enabled a Wavefront service account.

    • Fluentd

    • Agent

    • telegraf

  5. To view the Concord container logs, run the sudo docker logs –f concord command.

    Sample validation output to validate that Concord is running correctly.

    INFO ||concord.main||||main.cpp:976|int main(int, char **)|VMware Project concord starting|{"primary":"","path":""}|

INFO ||concord.main||||main.cpp:720|int run_service(concord::config::ConcordConfiguration &, concord::config::ConcordConfiguration &, logging::Logger &)|Successfully loaded D
AML genesis block|{"primary":"","path":""}|

INFO ||concord.tls||||TlsTCPCommunication.cpp:1216|int bft::communication::TlsTCPCommunication::TlsTcpImpl::Start()|Resolved 0.0.0.0:3501 to 0.0.0.0:3501|{"primary":"","path"
:""}|

INFO ||concord.bft||||ReplicaImp.cpp:3272|bftEngine::impl::ReplicaImp::ReplicaImp(bool, const bftEngine::ReplicaConfig &, bftEngine::IRequestsHandler *, bftEngine::IStateTran
sfer *, bftEngine::impl::SigManager *, bftEngine::impl::ReplicasInfo *, bftEngine::impl::ViewsManager *, shared_ptr<bftEngine::impl::MsgsCommunicator>, shared_ptr<bftEngine::impl::MsgHandlersRegistra
tor>, concordUtil::Timers &)|ReplicaConfig parameters isReadOnly=0, numReplicas=4, numRoReplicas=0, fVal=1, cVal=0, replicaId=2, numOfClientProxies=16, numOfExternalClients=30, statusReportTimerMilli
sec=3000, concurrencyLevel=3, viewChangeProtocolEnabled=1, viewChangeTimerMillisec=20000, autoPrimaryRotationEnabled=0, autoPrimaryRotationTimerMillisec=0, preExecReqStatusCheckTimerMillisec=1000, ma
xExternalMessageSize=33554432, maxReplyMessageSize=4096, maxNumOfReservedPages=8192, sizeOfReservedPage=4096, debugStatisticsEnabled=0, metricsDumpIntervalSeconds=600|{"primary":"","path":""}|
2020-09-30T23:21:11,956Z|INFO ||concord.bft||||ReplicaImp.cpp:3093|bftEngine::impl::ReplicaImp::ReplicaImp(const bftEngine::ReplicaConfig &, bftEngine::IRequestsHandler *, bftEngine::IStateTransfer *
, shared_ptr<bftEngine::impl::MsgsCommunicator>, shared_ptr<bftEngine::impl::PersistentStorage>, shared_ptr<bftEngine::impl::MsgHandlersRegistrator>, concordUtil::Timers &)|Starting internal replica
thread pool.  numThreads: 8|{"primary":"","path":""}|
  6. To verify that the Daml execution engine is communicating with Concord, run the sudo docker logs daml_execution_engine command.

    Sample validation output to validate that the Daml execution engine is communicating with Concord and is running correctly.

    INFO ||c.d.d.o.v.e.e.KVBCValidatorServer|main|||||Server started, port=55000||
INFO ||c.d.d.o.v.e.e.PipelinedValidator|pool-2-thread-2|||||Batch validation completed, correlationId=ec30d0cd-a17e-4e21-a87d-f2bd1dee06e7 participantId=p7cdf2f41_b449_4bb3_97a9_807d11597cc2 recordTime=2020-09-30T23:23:18.310Z readSetSize=2 writeSetSize=3||
  7. (Optional) Select a different Replica node IP address and repeat the validation steps.

What to do next

Verify that the Client node includes all the parameter values set in the deployment descriptor. See Validate a Client Node and Backup in VMware Blockchain Orchestrator for AWS.