It is time to check that Endpoint Node is successfully installed and it is working as expected after installation.
It is possible to check the status of EN's process using the status commands
systemctl is installed along with the RPM, and the status of EN can be checked as follows.
$ systemctl status kend.service● kend.service - (null)Loaded: loaded (/etc/rc.d/init.d/kend; bad; vendor preset: disabled)Active: active (running) since Wed 2019-01-09 11:42:39 UTC; 1 months 4 days agoDocs: man:systemd-sysv-generator(8)Process: 29636 ExecStart=/etc/rc.d/init.d/kend start (code=exited, status=0/SUCCESS)Main PID: 29641 (ken)CGroup: /system.slice/kend.service└─29641 /usr/local/bin/ken --networkid 1000 --datadir /kend_home --port 32323 --srvtype fasthttp --metrics --prometheus --verbosity 3 --txpool.global...Jan 09 11:42:39 ip-10-11-2-101.ap-northeast-2.compute.internal systemd: Starting (null)...Jan 09 11:42:39 ip-10-11-2-101.ap-northeast-2.compute.internal kend: Starting kend: [ OK ]Jan 09 11:42:39 ip-10-11-2-101.ap-northeast-2.compute.internal systemd: Started (null).
You can check the current status such as
Active: active (running) in the example above.
kend is installed along with the package, and the status of EN can be checked as follows.
$ kend statuskend is running
The log is stored in
kend.out file located in the path defined in the
LOG_DIR field of the
kend.conf file. When the node works properly, you can see that each block is imported per second as follows.
$ tail kend.outINFO[02/13,07:02:24 Z]  Commit new mining work number=11572924 txs=0 elapsed=488.336µsINFO[02/13,07:02:25 Z]  Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.800ms mgasps=0.000 number=11572924 hash=f46d09…ffb2dc cache=1.59mBINFO[02/13,07:02:25 Z]  Commit new mining work number=11572925 txs=0 elapsed=460.485µsINFO[02/13,07:02:25 Z]  🔗 block reached canonical chain number=11572919 hash=01e889…524f02INFO[02/13,07:02:26 Z]  Committed address=0x1d4E05BB72677cB8fa576149c945b57d13F855e4 hash=1fabd3…af66fe number=11572925INFO[02/13,07:02:26 Z]  Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.777ms mgasps=0.000 number=11572925 hash=1fabd3…af66fe cache=1.59mBINFO[02/13,07:02:26 Z]  Commit new mining work number=11572926 txs=0 elapsed=458.665µsINFO[02/13,07:02:27 Z]  Committed address=0x1d4E05BB72677cB8fa576149c945b57d13F855e4 hash=60b9aa…94f648 number=11572926INFO[02/13,07:02:27 Z]  Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.783ms mgasps=0.000 number=11572926 hash=60b9aa…94f648 cache=1.59mBINFO[02/13,07:02:27 Z]  Commit new mining work
Klaytn provides a CLI client:
ken console. Another way of using the client is to connect to the process via IPC (inter-process communication). The IPC file
klay.ipc is located in the
data directory on an EN.
Please execute the following command and check out the result.
You can check the usable commands on API Document
The useful APIs to check the status of EN:
klay.blockNumber (to get the latest block number)
net.peerCount (to get the number of the connected Klaytn nodes currently)
You can get the latest block number to see if blocks are propagated properly.
The above command line returns the number of nodes that the EN connects to.