My witness nodes seems not working.
I saw the sync process before but now I only see this.
(I had to turn off the node to relocate the place and I had to run sh update.sh)
[root@cryptopie ~]# docker logs blurtd
347868ms chain_plugin.cpp:362 plugin_initialize ] Initializing chain_plugin
347868ms p2p_plugin.cpp:575 plugin_initialize ] Initializing p2p_plugin
347877ms rc_plugin.cpp:978 plugin_initialize ] Initializing resource credit plugin
347877ms rc_plugin.cpp:1042 plugin_initialize ] RC's will be computed starting at block 0
347877ms witness_plugin.cpp:479 plugin_initialize ] Initializing witness plugin
347877ms account_by_key_plugin.cpp:187 plugin_initialize ] Initializing account_by_key plugin
347877ms json_rpc_plugin.cpp:418 plugin_initialize ] Initializing json_rpc_plugin
347877ms account_by_key_api_plugin.cpp:14 plugin_initialize ] Initializing account_by_key_api_plugin
347877ms database_api_plugin.cpp:15 plugin_initialize ] Initializing database_api_plugin
347878ms condenser_api_plugin.cpp:19 plugin_initialize ] Initializing condenser_api_plugin
347879ms network_broadcast_api_plugin.cpp:13 plugin_initialize ] Initializing network_broadcast_api_plugin
347880ms transaction_status_plugin.cpp:263 plugin_initialize ] transaction_status: plugin_initialize() begin
347880ms transaction_status_plugin.cpp:290 plugin_initialize ] transaction status initializing
347880ms transaction_status_plugin.cpp:291 plugin_initialize ] -> nominal block depth: 64000
347880ms transaction_status_plugin.cpp:292 plugin_initialize ] -> actual block depth: 65200
347880ms transaction_status_plugin.cpp:293 plugin_initialize ] -> nominal track after block: 0
347880ms transaction_status_plugin.cpp:294 plugin_initialize ] -> actual track after block: 0
347880ms transaction_status_plugin.cpp:298 plugin_initialize ] Transaction status tracking activated
347880ms transaction_status_plugin.cpp:309 plugin_initialize ] transaction_status: plugin_initialize() end
347880ms transaction_status_api_plugin.cpp:13 plugin_initialize ] Initializing transaction_status_api_plugin
347880ms rc_api_plugin.cpp:14 plugin_initialize ] Initializing rc_api_plugin
347880ms webserver_plugin.cpp:309 plugin_initialize ] Initializing webserver_plugin
347880ms webserver_plugin.cpp:313 plugin_initialize ] configured with 32 thread pool size
347883ms webserver_plugin.cpp:322 plugin_initialize ] configured http to listen on 127.0.0.1:8091
347884ms webserver_plugin.cpp:331 plugin_initialize ] configured ws to listen on 127.0.0.1:8090
------------------------------------------------------
STARTING BLURT NETWORK
------------------------------------------------------
initminer public key: BLT5QRsKZp7TFNQdTj7VbpGHWxNL3Eq4zmfER4vJPBpK5VMbrprn8
chain id: cd8d90f29ae273abec3eaa7731e25934c63eb654d55080caff2ebb7f5df6381f
blockchain version: 0.7.0
------------------------------------------------------
347889ms chain_plugin.cpp:486 plugin_startup ] Starting chain with shared_file_size: 8589934592 bytes
347889ms chain_plugin.cpp:616 plugin_startup ] Opening shared memory from /blurtd/blockchain
347890ms block_log.cpp:142 open ] Log is nonempty
347890ms block_log.cpp:151 open ] Index is nonempty
I turned on the node for several hours but no new logs.
Can you help me?
@dotwin1981
@michelangelo3
Exactly what @michelangelo3 says!
Never, under any circumstances, disconnect the RasPi from power while the blockchain is running. This is equivalent to a power failure and everything is crashed.
So you can't get around a re-flash and re-setup. (I did today because of memory card change are also made 40 minutes).
If you have to take the RasPi (for whatever reason) from the power, you have to shut it down before, as @michelangelo3 has described.
The update.sh file is to be used exclusively with a HardFork.
Oh no. Before you disconnected the RasPi from the power supply, did you execute
docker stop blurtdand thenshutdown -h now? (update.sh is only necessary for HF's.)If you need to switch off the RasPi, then only enter the two commands above. Later, after you have switched it on again, start the chain with
docker start blurtd.How does your logbook look now, has anything changed? What are the last lines?
Congratulations, your post has been curated by @r2cornell-curate. Also, find us on Discord
Felicitaciones, su publication ha sido votado por @r2cornell. También, encuéntranos en Discord
Hi, @etainclub,
Thank you for your contribution to the Blurt ecosystem.
Please consider voting for the witness @symbionts.
Or delegate to @ecosynthesizer to earn a portion of the curation rewards!