-
Notifications
You must be signed in to change notification settings - Fork 642
If node version is NOT 0.4.11 when restarting node #144
Comments
If I restart the client without saving the logs, what should I do? For 2 weeks I had an active node, and now I will not have time to complete the tasks OT4-B1 and OT4-B4. |
You should not restart your node without retrieving the logs first. Follow our instructions on the status page and the Medium post. |
logs were not saved, now I can leave tasks B1 - B4? |
This been many time adviced around support channels to restart node, which free lost transactions pool and improve baker functionality. Now apparently we loosing log files on restart ? This mean people who run bakers since the beggining and restarted they nodes lost main two challeges ? |
Logs are only reset if there is a new version upgrade on restart. This is why earlier restarts were fine. I agree it's unfortunate there is no prompt to preserve logs, we'll look at this. If you lost your logs due to precedence of earlier restarts, and you missed the log extraction instructions, then please:
|
I also could collect logs only after node upgrade( |
After looking in to may collected logs which I done before update ( pure luck ), it was clear. I think my logs are fine, thank you ! |
When restarting your node after our update, you should get something similar to
If the node version is not updated to
0.4.11
, please do the following from a terminal:docker ps -a
. This will provide you with yourCONTAINER ID
in the first column.docker rm <CONTAINER ID>
docker rmi concordium/opentestnet-client:0.4.8
The text was updated successfully, but these errors were encountered: