CryptiKit Update - Simple & easy Crypti node deployment and management.
Hello Everyone!
New release of CryptiKit today with some nice new features.
Please download here:
https://github.com/karmacoma/cryptikit/releases/tag/v1.4.0If you don't know about CryptiKit and what it can do already, please read here:
-
https://github.com/karmacoma/cryptikit/blob/master/README.mdChangelogNOTE: Config file update required. Please run the start_forging task on all of your nodes after downloading this release. This is due to an API key that needs to be added to the config, before forging statistics can be successfully retrieved.
Bug Fixes- Resolved issue when installing on servers where nodejs already installed
- Ensuring all existing processes are stopped before starting a node
- Checking crypti node is installed before executing certain tasks
- Removing blockchain.db.zip after decompressing it during tasks
Features / Improvements- Added forging information to "check_nodes" task including:
- Forged coins by each individual node
- Last forged block by each individual node
- Total forged for all selected nodes
- Graceful handling of common ssh connection errors
- Listing 'bad' nodes at end of "check_nodes" report summary
- More consistent, easier to read, colorized log messages
Check NodesBelow is some example output of the newly updated check_nodes task:
Checking nodes...
================================================================================
Node[1]: 111.11.11.111 (4956977736153893179C)
================================================================================
Loaded: true
Height: 33950
Blocks: 33829
Forging: true
Last Forged: Block -> 12886241379965779851 Amount -> 0.0
Forged: 2.92869137
Balance: 1002.92869137
Unconfirmed: 1002.92869137
Effective: 1002.92869137
When running the check_nodes task. CryptiKit now produces a detailed summary containing the total nodes checked, total forged, total balances, lowest / highest balances, followed by a breakdown of any nodes which are either not loaded properly, or not currently forging. Please see the below example:
================================================================================
Report Summary
================================================================================
Nodes Checked: 24 / 24 Configured
Total Forged: 1915.88691914
Total Balance: 26915.88691914
Total Unconfirmed: 26915.88691914
Total Effective: 26915.88691914
Lowest Balance: 1000.00168904 -> Node[15]
Highest Balance: 2421.74114445 -> Node[9]
--------------------------------------------------------------------------------
* 1 / 24 nodes are not loaded properly.
> Affected Nodes: 4
--------------------------------------------------------------------------------
* 2 / 24 nodes are not currently forging.
> Affected Nodes: 1,4
--------------------------------------------------------------------------------
Any connection / authentication errors encountered while running the check_nodes task, are automatically recorded by CryptiKit and subsequently reported back to you at the end of the Report Summary.
--------------------------------------------------------------------------------
* 3 nodes encountered errors and were not checked.
Error Messages:
* Node[13] => Connection closed by remote host.
* Node[14] => Connection refused.
* Node[15] => Authentication failed.
--------------------------------------------------------------------------------
Thanks for all the recent feedback, it really helped to motivate me.
