How do I verify that a node is running correctly

[techmemes]

Thank you for putting together the scripts for creating a BlockDag node and running it. The set up is as simple as it can be at this stage of project development. Use of docker at the moment to run the node I believe made the set up much simpler so we did not have to worry much about the dependencies and env set up. Thank You!

I have been able to run the nodes successfully on a ubuntu machine. The node seems to be running ok currently.

Below is sample output from the running node. How can I determine that the node is healthy and functioning as expected.

2024-09-27|02:26:15.938 [INFO ] Start DAG REORGANIZE: Block ccb8aca1e5b8ae9cb8732174517c5d1af98173ff179e69ebe238135bc034eedf is causing a reorganize. module=CHAIN
2024-09-27|02:26:15.939 [INFO ] End DAG REORGANIZE: Old Len= 2;New Len= 3 module=CHAIN
2024-09-27|02:26:16.371 [INFO ] {6cf01a0ec807e7d2c327a5966747f425f0654323672812cdd69ffc76b8ca84c7 1a8ea74491bd0df5ac65638e4fcc592653711a8b5b33f0188e780f2eb2ae3083 1212262 829446 12000000000 CPU_Worker} module=miner     cost=157.976555ms txs=1
2024-09-27|02:26:17.695 [INFO ] Syncing graph state                 module=SYNC      cur=(1212262,829446,830096,1212888,3) target=(1212266,829445,830096,1213175,6) peer=16Uiu2HAmKr4kFun2dLwVZwjS3Q8VfkAcqFm4W94RyBYA3dQ4sn3n processID=349
2024-09-27|02:26:17.807 [INFO ] Start DAG REORGANIZE: Block a5c2441436f5b410481a66128bf321f32bede9e7661bf812962f2af2965f29c3 is causing a reorganize. module=CHAIN
2024-09-27|02:26:17.808 [INFO ] End DAG REORGANIZE: Old Len= 1;New Len= 3 module=CHAIN
2024-09-27|02:26:17.832 [INFO ] Start DAG REORGANIZE: Block 84ee8a4db3b5547d7ee22107f156c23664b3cf9729f462312d1918f1089e2eaa is causing a reorganize. module=CHAIN
2024-09-27|02:26:17.835 [INFO ] End DAG REORGANIZE: Old Len= 10;New Len= 12 module=CHAIN
2024-09-27|02:26:17.863 [INFO ] The sync of graph state has ended   module=SYNC      spend=0s    processID=349
2024-09-27|02:26:18.260 [INFO ] {3d37af54165f836e80826a731c42e88c506808a474908cdb65b4750cc24ec5ba b423e5a9e904cce337648144b9bf81ddfc84b42d92f70e35eb1397182c13656a uncertainty 829447 12000000000 CPU_Worker} module=miner     cost=889.50567ms  txs=1
2024-09-27|02:26:20.490 [INFO ] Start DAG REORGANIZE: Block 169f7bc571f4552f9a118fe65f68bd7e73e0aaa1d4978232c0d875fc6106148e is causing a reorganize. module=CHAIN
2024-09-27|02:26:20.492 [INFO ] End DAG REORGANIZE: Old Len= 7;New Len= 9 module=CHAIN
2024-09-27|02:26:20.496 [INFO ] {169f7bc571f4552f9a118fe65f68bd7e73e0aaa1d4978232c0d875fc6106148e 9c89b0b46617d0ac57abb945dd0e904a9d1d46b8b5bdbc1c38a38bf2989ccb4e 1212280 829447 12000000000 CPU_Worker} module=miner     cost=1.235153803s txs=1
2024-09-27|02:26:20.767 [INFO ] Syncing graph state                 module=SYNC      cur=(1212280,829447,830098,1212907,2) target=(1212283,829449,830100,1213186,3) peer=16Uiu2HAmKr4kFun2dLwVZwjS3Q8VfkAcqFm4W94RyBYA3dQ4sn3n processID=350
2024-09-27|02:26:20.814 [INFO ] Start DAG REORGANIZE: Block 9dff66e2c14b36b75b64a0d5437521b5c23a019a751a25eaef7aa872017940bd is causing a reorganize. module=CHAIN
2024-09-27|02:26:20.816 [INFO ] End DAG REORGANIZE: Old Len= 10;New Len= 12 module=CHAIN
2024-09-27|02:26:20.861 [INFO ] The sync of graph state has ended   module=SYNC      spend=0s    processID=350
2024-09-27|02:26:21.956 [INFO ] {091f0fe6be32912f68224d577d6deb4ac92f2a487c50edece11ae4f189c435a4 2ecd2b0c7796b628a7b5a6ca6b3a23556374a9c8ec409e4f273284b80a57b1bc uncertainty 829451 12000000000 CPU_Worker} module=miner     cost=458.652287ms txs=1
2024-09-27|02:26:24.610 [INFO ] Syncing graph state                 module=SYNC      cur=(1212290,829451,830103,1212919,3) target=(1212299,829452,830103,1213205,5) peer=16Uiu2HAmKr4kFun2dLwVZwjS3Q8VfkAcqFm4W94RyBYA3dQ4sn3n processID=351
2024-09-27|02:26:24.693 [INFO ] Start DAG REORGANIZE: Block b2c1f77a2728d5625d9e8cc84a29b30a527a1be57f2e41116620c6a606433fd4 is causing a reorganize. module=CHAIN
2024-09-27|02:26:24.695 [INFO ] End DAG REORGANIZE: Old Len= 1;New Len= 9 module=CHAIN
2024-09-27|02:26:24.718 [INFO ] The sync of graph state has ended   module=SYNC      spend=0s    processID=351
2024-09-27|02:26:25.254 [INFO ] Imported new chain segment           number=42508 hash=da8f68..af73b3 blocks=1 txs=1 mgas=0.021 elapsed=25.383ms  mgasps=0.827   snapdiffs=1.87MiB    triediffs=522.90KiB triedirty=791.39KiB
2024-09-27|02:26:25.258 [INFO ] Processed 46 blocks in the last 10.24s  module=CHAIN     transactions=47   order=1212305     time=2024-09-27T02:26:23+0000
2024-09-27|02:26:25.334 [INFO ] Start DAG REORGANIZE: Block 1ab96521c7ebd0a4de8d59e04c2dc7c3ff3f7f5eecfcab9d513f4b71b43f8ca6 is causing a reorganize. module=CHAIN
2024-09-27|02:26:25.335 [INFO ] Try to rewind                       module=BDAG      cur.number=42508 cur.hash=0xda8f68f6312d3adae9958734c5e52958f819b031ae4324be94ad74f7feaf73b3 target.evm.root=7186a7..6adc73 target.evm.number=42507 target.evm.hash=e3188b..7e68d8
2024-09-27|02:26:25.335 [WARN ] Rewinding blockchain to block        target=42507
2024-09-27|02:26:25.336 [INFO ] Rewound to block with state          number=42507 hash=e3188b..7e68d8
2024-09-27|02:26:25.341 [INFO ] Loaded most recent local block       number=42507 hash=e3188b..7e68d8 td=42507 age=33s
2024-09-27|02:26:25.342 [INFO ] Rewound                             module=BDAG      cur.number=42507 cur.hash=0xe3188bfbce5ce7be89fcdfc96e43d4894881304a1371724374936642ed7e68d8 target.evm.root=7186a7..6adc73 target.evm.number=42507 target.evm.hash=e3188b..7e68d8
2024-09-27|02:26:25.356 [INFO ] Imported new chain segment           number=42508 hash=6fc846..cb5350 blocks=1 txs=1 mgas=0.021 elapsed=10.789ms  mgasps=1.946   snapdiffs=1.87MiB    triediffs=526.98KiB triedirty=791.39KiB
2024-09-27|02:26:25.357 [INFO ] End DAG REORGANIZE: Old Len= 2;New Len= 4 module=CHAIN
2024-09-27|02:26:25.738 [INFO ] Start DAG REORGANIZE: Block 3863c9b0e2453a1979f148c7dbae1c3d9bed99df22e0f50dbffa059370268052 is causing a reorganize. module=CHAIN
2024-09-27|02:26:25.740 [INFO ] Try to rewind                       module=BDAG      cur.number=42508 cur.hash=0x6fc846ec2b0079f3fe9a4b8a671ab44a6feef04d7f1e3cd8aa5e94d8decb5350 target.evm.root=7186a7..6adc73 target.evm.number=42507 target.evm.hash=e3188b..7e68d8
2024-09-27|02:26:25.740 [WARN ] Rewinding blockchain to block        target=42507
2024-09-27|02:26:25.741 [INFO ] Rewound to block with state          number=42507 hash=e3188b..7e68d8
2024-09-27|02:26:25.745 [INFO ] Loaded most recent local block       number=42507 hash=e3188b..7e68d8 td=42507 age=33s
2024-09-27|02:26:25.746 [INFO ] Rewound                             module=BDAG      cur.number=42507 cur.hash=0xe3188bfbce5ce7be89fcdfc96e43d4894881304a1371724374936642ed7e68d8 target.evm.root=7186a7..6adc73 target.evm.number=42507 target.evm.hash=e3188b..7e68d8
2024-09-27|02:26:25.754 [INFO ] Imported new chain segment           number=42508 hash=da8f68..af73b3 blocks=1 txs=1 mgas=0.021 elapsed=6.340ms   mgasps=3.312   snapdiffs=1.87MiB    triediffs=526.98KiB triedirty=791.39KiB
2024-09-27|02:26:25.756 [INFO ] End DAG REORGANIZE: Old Len= 4;New Len= 5 module=CHAIN
2024-09-27|02:26:27.071 [ERROR] Failed to submit new block:b65c3a4c4875f0b7b5a0750d7ec90878c733c99fb5e5adb5b1b9f41b6cb32a19 ,The tips of block is expired:b65c3a4c4875f0b7b5a0750d7ec90878c733c99fb5e5adb5b1b9f41b6cb32a19 (error:main chain tip is overdue,submit main parent:fe0470a7d6c673cfb660635c3945374f899e0dcd2c1f4040cddb3ceabcfcf72c (829453), but main tip is :250591e59b2933bfa5f825335cbe976f2f4fdc05a0d02e63a436146f2e66ab57 (829456). Obsolete depth:3
)
 module=miner
2024-09-27|02:26:27.189 [INFO ] Start DAG REORGANIZE: Block 09dd69baaeec949e77612750fafc1e6192bdcc18e07739a70b3724f59815793d is causing a reorganize. module=CHAIN
2024-09-27|02:26:27.190 [INFO ] End DAG REORGANIZE: Old Len= 1;New Len= 1 module=CHAIN

[dev001101]

Hi @techmemes, If you'd like to check the details of your BlockDAG node, you can use the following curl command:

curl -s -k -u test:test -X POST -H 'Content-Type: application/json' --data '{"method":"getNodeInfo","params":[],"jsonrpc":"2.0","id":1}' http://127.0.0.1:38131

This command retrieves essential information about the node, such as its current status and configuration details. Ensure the username and password (test:test in this example) match your node's authentication settings, and update the IP and port if needed.