search

Alethio / ethstats-cli

EthStats - CLI Client
https://ethstats.io
MIT License
45 stars 22 forks source link

Docker container crashes on Ubuntu 18.04 #16

Open jbroudou opened 5 years ago

jbroudou commented 5 years ago

Describe the bug

The ethstats-cli docker container crashes with an exit code of 1 after about 10 minutes of running the container.

Output from the last few lines of the log are as follows

2019-06-21 09:43:45.269 - INFO: Sending message on topic: "usage"
2019-06-21 09:43:45.270 - DEBUG: Sent message on "usage" with payload: {"hostCpuLoad":59.217877094972074,"hostMemTotal":16818675712,"hostMemUsed":16663748608,"hostNetRxSec":3429638.6336396323,"hostNetTxSec":74000.19976028765,"hostFsRxSec":0,"hostFsWxSec":0,"hostDiskRIOSec":0,"hostDiskWIOSec":0,"nodeCpuLoad":0,"nodeMemLoad":0,"clientCpuLoad":1.37,"clientMemLoad":0.2}
2019-06-21 09:43:45.282 - DEBUG: Data received for topic: "usageResponse"
2019-06-21 09:43:45.666 - DEBUG: Check connection
2019-06-21 09:43:48.410 - DEBUG: Check if receiving new blocks => last checked block: null, last received block: null
2019-06-21 09:43:48.410 - DEBUG: Check if receiving new sync blocks => last checked sync block: 0, last received block: 0
2019-06-21 09:43:48.410 - INFO: No new blocks received for more than 300 seconds.
2019-06-21 09:43:48.411 - INFO: Reinitializing app...
2019-06-21 09:43:48.411 - DEBUG: Stop client
2019-06-21 09:43:48.412 - WARNING: Connection closed with ethstats server
2019-06-21 09:43:48.412 - ERROR: Connection ended with ethstats server
2019-06-21 09:43:48.413 - INFO: Exited with code: 1, signal: undefined

The container was started with the command docker run -it --restart always --net host -v /opt/ethstats-cli/:/root/.config/configstore/ alethio/ethstats-cli --register --account-email system-support@OBSCURED --node-name eth1-node-inspectablock

Environment (please complete the following information):

baxy commented 5 years ago

Hi,

Based on your logs the app didn't received any new blocks from Parity. Because we had issues with the web3js package not receiving new blocks for various reasons we added a workaround to reinstatiate the connection to the node to fix the problem. But indeed it should not exit with the code error 1. Seems to be a bug. Will investigate more and fix it.

Thanks for your feedback.

hamid0785 commented 3 years ago

Thank you to all this community, you are very unique