PM2 commands
On this page, you’ll find the most relevant PM2 commands for running a source-based Klayr Service installation. For more details about PM2, see PM2 docs.
Moreover, we’ll also talk about the steps to reset a Klayr Service node.
The process ID of each PM2-managed process can be seen by executing the List command. To learn more about PM2 log management please refer the PM2 logs documentation. |
Various PM2 commands
Start
Start Klayr Service.
pm2 start ecosystem.config.js
Response
[PM2] Applying action restartProcessId on app [klayr-service-gateway](ids: [ 0 ])
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-app-registry](ids: [ 1 ])
[PM2] [klayr-service-gateway](0) ✓
[PM2] [klayr-service-blockchain-app-registry](1) ✓
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-connector](ids: [ 2 ])
[PM2] [klayr-service-blockchain-connector](2) ✓
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-indexer](ids: [ 3 ])
[PM2] [klayr-service-blockchain-indexer](3) ✓
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-coordinator](ids: [ 4 ])
[PM2] [klayr-service-blockchain-coordinator](4) ✓
[PM2] Applying action restartProcessId on app [klayr-service-fee-estimator](ids: [ 5 ])
[PM2] [klayr-service-fee-estimator](5) ✓
[PM2] Applying action restartProcessId on app [klayr-service-transaction-statistics](ids: [ 6 ])
[PM2] [klayr-service-transaction-statistics](6) ✓
[PM2] Applying action restartProcessId on app [klayr-service-market](ids: [ 7 ])
[PM2] [klayr-service-market](7) ✓
[PM2] Applying action restartProcessId on app [klayr-service-export](ids: [ 8 ])
[PM2] [klayr-service-export](8) ✓
┌----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤
│ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 33328 │ 0s │ 16 │ online │ 0% │ 65.5mb │ XYZ │ disabled │
│ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 33331 │ 0s │ 0 │ online │ 0% │ 63.8mb │ XYZ │ disabled │
│ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 33341 │ 0s │ 0 │ online │ 0% │ 54.1mb │ XYZ │ disabled │
│ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 33338 │ 0s │ 16 │ online │ 0% │ 54.3mb │ XYZ │ disabled │
│ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 33355 │ 0s │ 15 │ online │ 0% │ 14.1mb │ XYZ │ disabled │
│ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 33346 │ 0s │ 15 │ online │ 0% │ 46.9mb │ XYZ │ disabled │
│ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 33326 │ 0s │ 15 │ online │ 0% │ 65.6mb │ XYZ │ disabled │
│ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 33351 │ 0s │ 15 │ online │ 0% │ 36.9mb │ XYZ │ disabled │
│ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 33348 │ 0s │ 15 │ online │ 0% │ 43.5mb │ XYZ │ disabled │
└----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
List
View the status of different microservices of Klayr Service in the list of PM2 processes:
pm2 list
Response
┌----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤
│ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 33328 │ 0s │ 16 │ online │ 0% │ 65.5mb │ XYZ │ disabled │
│ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 33331 │ 0s │ 0 │ online │ 0% │ 63.8mb │ XYZ │ disabled │
│ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 33341 │ 0s │ 0 │ online │ 0% │ 54.1mb │ XYZ │ disabled │
│ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 33338 │ 0s │ 16 │ online │ 0% │ 54.3mb │ XYZ │ disabled │
│ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 33355 │ 0s │ 15 │ online │ 0% │ 14.1mb │ XYZ │ disabled │
│ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 33346 │ 0s │ 15 │ online │ 0% │ 46.9mb │ XYZ │ disabled │
│ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 33326 │ 0s │ 15 │ online │ 0% │ 65.6mb │ XYZ │ disabled │
│ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 33351 │ 0s │ 15 │ online │ 0% │ 36.9mb │ XYZ │ disabled │
│ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 33348 │ 0s │ 15 │ online │ 0% │ 43.5mb │ XYZ │ disabled │
└----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
Logs
To check the logs for the different microservices of Klayr Service, use the command pm2 logs PROCESS_NAME
, where PROCESS_NAME
is the respective PM2-managed process that contains the logs you wish to view.
Alternatively, it is also possible to check the logs for a specific PM2 process based on its process ID.
For example, pm2 logs 0
can be used to check the Klayr Service Gateway logs.
The process ID of each PM2-managed process can be seen by executing the List command. To learn more about PM2 log management please refer the PM2 logs documentation. |
For example, to see the logs for the Gateway microservice, execute the following command:
pm2 logs klayr-service-gateway
Response
0|klayr-ser | 2023-07-19 17:53:08 503: 2023-07-19T17:53:08.503 INFO [TRANSIT] Connecting to the transporter...
0|klayr-ser | 2023-07-19 17:53:08 504: 2023-07-19T17:53:08.503 INFO [TRANSPORTER] Setting Redis transporter
0|klayr-ser | 2023-07-19 17:53:08 510: 2023-07-19T17:53:08.510 INFO [TRANSPORTER] Redis-sub client is connected.
0|klayr-ser | 2023-07-19 17:53:08 510: 2023-07-19T17:53:08.510 INFO [TRANSPORTER] Setting Redis transporter
0|klayr-ser | 2023-07-19 17:53:08 512: 2023-07-19T17:53:08.512 INFO [TRANSPORTER] Redis-pub client is connected.
0|klayr-ser | 2023-07-19 17:53:09 016: 2023-07-19T17:53:09.016 INFO [TEMP_SERVICE_GATEWAY] Waiting for service(s) 'indexer, connector'...
0|klayr-ser | 2023-07-19 17:53:09 018: 2023-07-19T17:53:09.018 INFO [REGISTRY] '$node' service is registered.
0|klayr-ser | 2023-07-19 17:53:09 018: 2023-07-19T17:53:09.018 INFO [$NODE] Service '$node' started.
0|klayr-ser | 2023-07-19 17:53:10 225: 2023-07-19T17:53:10.223 INFO [REGISTRY] Node 'XYZ.local-74790' connected.
0|klayr-ser | 2023-07-19 17:53:10 274: 2023-07-19T17:53:10.274 INFO [REGISTRY] Node 'XYZ.local-74787' connected.
0|klayr-ser | 2023-07-19 17:53:10 325: 2023-07-19T17:53:10.325 INFO [REGISTRY] Node 'XYZ.local-74798' connected.
0|klayr-ser | 2023-07-19 17:53:10 346: 2023-07-19T17:53:10.345 INFO [REGISTRY] Node 'XYZ.local-74772' connected.
0|klayr-ser | 2023-07-19 17:53:10 415: 2023-07-19T17:53:10.414 INFO [REGISTRY] Node 'XYZ.local-74804' connected.
0|klayr-ser | 2023-07-19 17:53:10 485: 2023-07-19T17:53:10.484 INFO [REGISTRY] Node 'XYZ.local-74795' connected.
0|klayr-ser | 2023-07-19 17:53:10 676: 2023-07-19T17:53:10.675 INFO [REGISTRY] Node 'XYZ.local-74779' connected.
Flush
Remove all the logs of the PM2-managed processes defined in the specified config file.
pm2 flush ecosystem.config.js
Response
[PM2] Logs flushed
Stop
Stop PM2 managed Klayr Service instance.
pm2 stop ecosystem.config.js
Response
[PM2] [klayr-service-blockchain-app-registry](1) ✓
[PM2] [klayr-service-gateway](0) ✓
[PM2] [klayr-service-blockchain-indexer](3) ✓
[PM2] [klayr-service-blockchain-connector](2) ✓
[PM2] [klayr-service-blockchain-coordinator](4) ✓
[PM2] [klayr-service-fee-estimator](5) ✓
[PM2] [klayr-service-transaction-statistics](6) ✓
[PM2] [klayr-service-market](7) ✓
[PM2] [klayr-service-export](8) ✓
┌------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤
│ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 0 │ 0 │ 32 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 0 │ 0 │ 0 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 0 │ 0 │ 0 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 0 │ 0 │ 32 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │
│ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │
└------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
Restart
Restart Klayr Service via PM2.
pm2 restart ecosystem.config.js
Response
[PM2] Applying action restartProcessId on app [klayr-service-gateway](ids: [ 0 ])
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-app-registry](ids: [ 1 ])
[PM2] [klayr-service-gateway](0) ✓
[PM2] [klayr-service-blockchain-app-registry](1) ✓
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-connector](ids: [ 2 ])
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-indexer](ids: [ 3 ])
[PM2] [klayr-service-blockchain-indexer](3) ✓
[PM2] Applying action restartProcessId on app [klayr-service-blockchain-coordinator](ids: [ 4 ])
[PM2] [klayr-service-blockchain-connector](2) ✓
[PM2] Applying action restartProcessId on app [klayr-service-fee-estimator](ids: [ 5 ])
[PM2] [klayr-service-blockchain-coordinator](4) ✓
[PM2] [klayr-service-fee-estimator](5) ✓
[PM2] Applying action restartProcessId on app [klayr-service-transaction-statistics](ids: [ 6 ])
[PM2] Applying action restartProcessId on app [klayr-service-market](ids: [ 7 ])
[PM2] [klayr-service-transaction-statistics](6) ✓
[PM2] [klayr-service-market](7) ✓
[PM2] Applying action restartProcessId on app [klayr-service-export](ids: [ 8 ])
[PM2] [klayr-service-export](8) ✓
┌----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤
│ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 33328 │ 0s │ 16 │ online │ 0% │ 65.5mb │ XYZ │ disabled │
│ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 33331 │ 0s │ 0 │ online │ 0% │ 63.8mb │ XYZ │ disabled │
│ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 33341 │ 0s │ 0 │ online │ 0% │ 54.1mb │ XYZ │ disabled │
│ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 33338 │ 0s │ 16 │ online │ 0% │ 54.3mb │ XYZ │ disabled │
│ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 33355 │ 0s │ 15 │ online │ 0% │ 14.1mb │ XYZ │ disabled │
│ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 33346 │ 0s │ 15 │ online │ 0% │ 46.9mb │ XYZ │ disabled │
│ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 33326 │ 0s │ 15 │ online │ 0% │ 65.6mb │ XYZ │ disabled │
│ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 33351 │ 0s │ 15 │ online │ 0% │ 36.9mb │ XYZ │ disabled │
│ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 33348 │ 0s │ 15 │ online │ 0% │ 43.5mb │ XYZ │ disabled │
└----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
Delete
Remove all processes from the PM2 list.
pm2 delete ecosystem.config.js
Response
[PM2] [klayr-service-gateway](0) ✓
[PM2] [klayr-service-blockchain-app-registry](1) ✓
[PM2] [klayr-service-blockchain-indexer](3) ✓
[PM2] [klayr-service-blockchain-connector](2) ✓
[PM2] [klayr-service-blockchain-coordinator](4) ✓
[PM2] [klayr-service-fee-estimator](5) ✓
[PM2] [klayr-service-transaction-statistics](6) ✓
[PM2] [klayr-service-market](7) ✓
[PM2] [klayr-service-export](8) ✓
┌----------------------------------------------------------------------------------------------------------------------------------------------┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
└----------------------------------------------------------------------------------------------------------------------------------------------┘
[PM2][WARN] Current process list is not synchronized with saved list. App klayr-service-gateway klayr-service-blockchain-app-registry klayr-service-blockchain-connector klayr-service-blockchain-indexer klayr-service-blockchain-coordinator klayr-service-fee-estimator klayr-service-transaction-statistics klayr-service-market klayr-service-export differs. Type 'pm2 save' to synchronize.
Taking Snapshots
If you wish to take a snapshot of your Source-based installation, the details can be found here on the Snapshots page.
Resetting Klayr Service
Clean all run-time files with dependencies
make clean-local
Response
rm -rf node_modules
cd ./framework && rm -rf node_modules
cd ./services/blockchain-app-registry && rm -rf node_modules
cd ./services/blockchain-connector && rm -rf node_modules
cd ./services/blockchain-coordinator && rm -rf node_modules
cd ./services/blockchain-indexer && rm -rf node_modules
cd ./services/transaction-statistics && rm -rf node_modules
cd ./services/fee-estimator && rm -rf node_modules
cd ./services/market && rm -rf node_modules
cd ./services/gateway && rm -rf node_modules
cd ./services/export && rm -rf node_modules
cd ./services/template && rm -rf node_modules
cd ./tests && rm -rf node_modules
Reset the Klayr Service database
To reset the database of Klayr Service, drop the respective MySQL and Redis databases.
Drop the MySQL database
-
Stop Klayr Service
yarn stop
-
Login to MySQL with the
klayr
user.mysql -u klayr -ppassword
-
Drop the database.
mysql> drop database klayr;
-
Create a fresh database.
mysql> create database klayr;
-
Quit MySQL.
mysql> quit;
The process to re-index all the data commences after Klayr Service starts again following a database reset. The process can be rather time-consuming and could take several hours, depending on the length of the chain. |
Flush Redis DB
Reset the databases for Redis after dropping the MySQL database:
redis-cli flushall
The
For more information, check the Redis documentation: FLUSHALL. To flush only a particular database in Redis, execute the following command instead:
|
You can start Klayr Service again with the Start command.
Upgrade Klayr Service
To upgrade Klayr Service to a desired version, please follow the steps listed below. To find all the tagged versions for Klayr Service, please check the available tags on GitHub.
-
Stop the existing running version of Klayr Service.
pm2 stop ecosystem.config.js
Response
Example output[PM2] [klayr-service-blockchain-app-registry](1) ✓ [PM2] [klayr-service-gateway](0) ✓ [PM2] [klayr-service-blockchain-indexer](3) ✓ [PM2] [klayr-service-blockchain-connector](2) ✓ [PM2] [klayr-service-blockchain-coordinator](4) ✓ [PM2] [klayr-service-fee-estimator](5) ✓ [PM2] [klayr-service-transaction-statistics](6) ✓ [PM2] [klayr-service-market](7) ✓ [PM2] [klayr-service-export](8) ✓ ┌------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐ │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤ │ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 0 │ 0 │ 32 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 0 │ 0 │ 0 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 0 │ 0 │ 0 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 0 │ 0 │ 32 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │ │ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 0 │ 0 │ 30 │ stopped │ 0% │ 0b │ XYZ │ disabled │ └------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
-
Checkout the version with
git checkout <tag>
.git checkout v0.7.8
-
Update the npm dependencies by executing the following command.
make build-local
-
Restart Klayr Service with the following command.
pm2 start ecosystem.config.js
Response
Example output[PM2] Applying action restartProcessId on app [klayr-service-gateway](ids: [ 0 ]) [PM2] Applying action restartProcessId on app [klayr-service-blockchain-app-registry](ids: [ 1 ]) [PM2] [klayr-service-gateway](0) ✓ [PM2] [klayr-service-blockchain-app-registry](1) ✓ [PM2] Applying action restartProcessId on app [klayr-service-blockchain-connector](ids: [ 2 ]) [PM2] [klayr-service-blockchain-connector](2) ✓ [PM2] Applying action restartProcessId on app [klayr-service-blockchain-indexer](ids: [ 3 ]) [PM2] [klayr-service-blockchain-indexer](3) ✓ [PM2] Applying action restartProcessId on app [klayr-service-blockchain-coordinator](ids: [ 4 ]) [PM2] [klayr-service-blockchain-coordinator](4) ✓ [PM2] Applying action restartProcessId on app [klayr-service-fee-estimator](ids: [ 5 ]) [PM2] [klayr-service-fee-estimator](5) ✓ [PM2] Applying action restartProcessId on app [klayr-service-transaction-statistics](ids: [ 6 ]) [PM2] [klayr-service-transaction-statistics](6) ✓ [PM2] Applying action restartProcessId on app [klayr-service-market](ids: [ 7 ]) [PM2] [klayr-service-market](7) ✓ [PM2] Applying action restartProcessId on app [klayr-service-export](ids: [ 8 ]) [PM2] [klayr-service-export](8) ✓ ┌----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┐ │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ ├----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┤ │ 1 │ klayr-service-blockchain-app-registry │ default │ 0.7.8 │ fork │ 33328 │ 0s │ 16 │ online │ 0% │ 65.5mb │ XYZ │ disabled │ │ 2 │ klayr-service-blockchain-connector │ default │ 0.7.8 │ fork │ 33331 │ 0s │ 0 │ online │ 0% │ 63.8mb │ XYZ │ disabled │ │ 4 │ klayr-service-blockchain-coordinator │ default │ 0.7.8 │ fork │ 33341 │ 0s │ 0 │ online │ 0% │ 54.1mb │ XYZ │ disabled │ │ 3 │ klayr-service-blockchain-indexer │ default │ 0.7.8 │ fork │ 33338 │ 0s │ 16 │ online │ 0% │ 54.3mb │ XYZ │ disabled │ │ 8 │ klayr-service-export │ default │ 0.7.8 │ fork │ 33355 │ 0s │ 15 │ online │ 0% │ 14.1mb │ XYZ │ disabled │ │ 5 │ klayr-service-fee-estimator │ default │ 0.7.8 │ fork │ 33346 │ 0s │ 15 │ online │ 0% │ 46.9mb │ XYZ │ disabled │ │ 0 │ klayr-service-gateway │ default │ 0.7.8 │ fork │ 33326 │ 0s │ 15 │ online │ 0% │ 65.6mb │ XYZ │ disabled │ │ 7 │ klayr-service-market │ default │ 0.7.8 │ fork │ 33351 │ 0s │ 15 │ online │ 0% │ 36.9mb │ XYZ │ disabled │ │ 6 │ klayr-service-transaction-statistics │ default │ 0.7.8 │ fork │ 33348 │ 0s │ 15 │ online │ 0% │ 43.5mb │ XYZ │ disabled │ └----------------------------------------------------------------------------------------------------------------------------------------------------------------------------┘
Please check the GitHub release notes for the relevant version to verify if the existing databases need to be flushed. |