[WARN ] Side chain depth too large module=miner #19
Comments
|
I am having the same issue and seems like there is no body has a solution.. |
|
I believe what is happening is that the techs at BlockDAG are monitoring the Testnet blockchain and then picking up the errors and correcting them with specific programs written for the job. If the problem happens over a weekend, it takes longer for the correction to be made to all the affected blocks. Also, they may be updating the code that created the error in the first place which may be down to synchronisation issues etc. Because the Docker file is pulled each time the node is started the updated code will be automatically used by the node upon restart. I have experienced the problem several times now and in one case reconfigured the node from scratch but that may not have been needed, after all, this is a Testnet blockchain. |
|
Thanks for the reply
I am running several nodes on VM server
When I started 4 days ago with the first one,the same log was ongoing for
24 hours than after 48 hours the miner was mining and blocks started
processing.
Then I restarted the node and instead of continuing where it was
stoped,pulled another image from a different container,and the process
started all over again. In docker i see the the stopped container ( the one
that run with the miner ) Docker will allow the restart of the stoped
container and combines it with the new one. Do you think it will change
anything?
…On Fri, Jan 24, 2025 at 12:13 PM Alan John Hancock ***@***.***> wrote:
I believe what is happening is that the techs at BlockDAG are monitoring
the Testnet blockchain and then picking up the errors and correcting them
with specific programs written for the job. If the problem happens over a
weekend, it takes longer for the correction to be made to all the affected
blocks. Also, they may be updating the code that created the error in the
first place which may be down to synchronisation issues etc. Because the
Docker file is pulled each time the node is started the updated code will
be automatically used by the node upon restart. I have experienced the
problem several times now and in one case reconfigured the node from
scratch but that may not have been needed, after all, this is a Testnet
blockchain.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJDVVCU6LYSQDLBEIZEYHUL2MJYDFAVCNFSM6AAAAABTT7DEAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTGAYTMMZXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
You must of course stop the node the node first before restarting with:
The Network created as linux_default is required for Docker to run the container its ports etc are set in Docker config file: |
|
where do you put stop-node.sh into the comment line
I tried "docker stop-node.sh blockdag-testnet-network" and it does not work
…On Fri, Jan 24, 2025 at 4:45 PM Alan John Hancock ***@***.***> wrote:
You must of course stop the node the node first before restarting with:
docker stop blockdag-testnet-network ( I put this line into stop-node.sh )
If the above was not done or failed then it is possible to invoke another
instance of the Docker node image.
Below is the restart.sh actions that show that each Docker instance is
started with a fresh sha256 key the old instance being deleted.
restart.sh actions which calls node.sh that pulls the latest bdag image:
- pk_addr=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff.....
- export
MINNING_ADDRESS=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
- MINNING_ADDRESS=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
- docker-compose down
Removing blockdag-testnet-network ... done
Removing network linux_default
- docker rmi -f blockdagnetwork/bdag
Untagged: blockdagnetwork/bdag:latest
Untagged: ***@***.***
:22f97aef4e6206fa386eb89f64a8e2ca863b14e141186293b3c876bbd5b15839
Deleted:
sha256:2cba94ed21792d694af7735bbaad6ba256e5061d708d4a5fd2782e551b84c844
- bash node.sh Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
[+] Running 4/4
✔ bdag Pulled 1.8s
✔ 43c4264eed91 Already exists 0.0s
✔ 37dffb0e9d60 Already exists 0.0s
✔ e7f765945136 Already exists 0.0s
[+] Running 2/2
✔ Network linux_default Created 0.3s
✔ Container blockdag-testnet-network Started 1.6s
The Network created as linux_default is required for Docker to run the
container its ports etc are set in Docker config file:
docker-compose.yml
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJDVVCXLGI3P5ZDQMXVPMGT2MKX6FAVCNFSM6AAAAABTT7DEAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTGQZTAMZZHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
sorry disregard
Into the .sh file you adding the docker stop blockdag-testnet-network
On Fri, Jan 24, 2025 at 6:42 PM MyAshburn Dentist ***@***.***>
wrote:
… where do you put stop-node.sh into the comment line
I tried "docker stop-node.sh blockdag-testnet-network" and it does not work
On Fri, Jan 24, 2025 at 4:45 PM Alan John Hancock <
***@***.***> wrote:
> You must of course stop the node the node first before restarting with:
> docker stop blockdag-testnet-network ( I put this line into stop-node.sh )
> If the above was not done or failed then it is possible to invoke another
> instance of the Docker node image.
> Below is the restart.sh actions that show that each Docker instance is
> started with a fresh sha256 key the old instance being deleted.
> restart.sh actions which calls node.sh that pulls the latest bdag image:
>
> - pk_addr=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff.....
> - export
> MINNING_ADDRESS=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
> - MINNING_ADDRESS=Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
> - docker-compose down
> Removing blockdag-testnet-network ... done
> Removing network linux_default
> - docker rmi -f blockdagnetwork/bdag
> Untagged: blockdagnetwork/bdag:latest
> Untagged: ***@***.***
> :22f97aef4e6206fa386eb89f64a8e2ca863b14e141186293b3c876bbd5b15839
> Deleted:
> sha256:2cba94ed21792d694af7735bbaad6ba256e5061d708d4a5fd2782e551b84c844
> - bash node.sh Tk6uWKRd35mvjEqTCN9xA9wemH7FM3teBVv8atw7nAAhhff...
> [+] Running 4/4
> ✔ bdag Pulled 1.8s
> ✔ 43c4264eed91 Already exists 0.0s
> ✔ 37dffb0e9d60 Already exists 0.0s
> ✔ e7f765945136 Already exists 0.0s
> [+] Running 2/2
> ✔ Network linux_default Created 0.3s
> ✔ Container blockdag-testnet-network Started 1.6s
>
> The Network created as linux_default is required for Docker to run the
> container its ports etc are set in Docker config file:
> docker-compose.yml
>
> —
> Reply to this email directly, view it on GitHub
> <#19 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AJDVVCXLGI3P5ZDQMXVPMGT2MKX6FAVCNFSM6AAAAABTT7DEAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTGQZTAMZZHA>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
@AlanJHancock did you notice that the UTXO died in mid February :-) But I am looking forward to the updated node release next week. |
|
I attended the AMA yesterday, and the CEO mentioned UTXO briefly. I think he said they were going to remove it, which actually makes good sense, and go to an Account-Based Model. It looks like they already made that change in February, and they will be putting the new Explorer into action on the new Testnet, which will remove any UTXO data display. UTXO (Unspent Transaction Output) model isn't required for all blockchains; some use an account-based model instead, like Ethereum. UTXO Model: |
Uh oh!
There was an error while loading. Please reload this page.
log-node.txt
The miner is stuck continuously outputting the message:
[WARN ] Side chain depth too large module=miner
Tried script to restart with cleanup
./restartWithCleanup.sh
Also ran:
docker run blockdagnetwork/bdag:latest ./bdag --cleanup
I am not able to get the miner to run normally, what will fix it?
I have another node that seems to be working normally.
The text was updated successfully, but these errors were encountered: