blacklist?

[Censseo]

Hello,
I have an issue with the miner, somehow I got disconnected from all peers after a few minutes, and all the blocks I find are never taken into account by the network.
This is one of the message I get:

And I got this message for every bloc I find.
I made like 1 xgt in 3 days with a 3900X
Is it possible that my ip got blocked by peers?

[liamnoroian]

I would make sure that your miner is in sync with the head. Your broadcasts may be ignored by other nodes if you’re running off a fork.

[Censseo]

This is what I thougth on the beginning, but I did the synchronisation from scratch two times since, how could I still be running off a fork?

[Censseo]

I just restarted from scratch, and I still have the same thing:
1226003ms witness_plugin.cpp:366 start_mining ] Miner working at block 7519741 rate: 48320197H/s
1226648ms witness_plugin.cpp:250 mine_rounds ] Miner found a solution with 5267560967526995112!
1226658ms witness_plugin.cpp:313 start_mining ] Broadcasting...
1226658ms witness_plugin.cpp:316 start_mining ] Mined block proceeding #7519741 with timestamp 2022-03-29T07:20:26 at time 2022-03-29T07:20:26
1226660ms database.cpp:1770 _apply_block ] Mining reward for XGT9pemKzHwt8h3dMhQjU54FiEu2BE3YdgHNM3NPeNe amount {"amount":"4166166","precision":8,"nai":"@@000000021"}
1226661ms p2p_plugin.cpp:774 broadcast_block ] Broadcasting block #7519742
1226661ms witness_plugin.cpp:347 start_mining ] Broadcasting Proof of Work for XGT9pemKzHwt8h3dMhQjU54FiEu2BE3YdgHNM3NPeNe
1226661ms witness_plugin.cpp:350 start_mining ] Broadcast succeeded!
1226671ms witness_plugin.cpp:263 start_mining ] Miner has started work XGT9pemKzHwt8h3dMhQjU54FiEu2BE3YdgHNM3NPeNe at block 7519742 target 3750584969
1230021ms witness_plugin.cpp:366 start_mining ] Miner working at block 7519742 rate: 52303425H/s
1233451ms peer_connection.cpp:261 connect_to ] established outbound connection to 95.216.69.92:2001
1233484ms peer_connection.cpp:261 connect_to ] established outbound connection to 116.202.114.157:2001
1233525ms peer_connection.cpp:261 connect_to ] established outbound connection to 95.217.88.154:2001
1233608ms peer_connection.cpp:261 connect_to ] established outbound connection to 45.56.83.92:2001
1233634ms peer_connection.cpp:261 connect_to ] established outbound connection to 95.216.71.199:2001
1233688ms peer_connection.cpp:261 connect_to ] established outbound connection to 195.201.167.19:2001
1233841ms peer_connection.cpp:261 connect_to ] established outbound connection to 73.158.49.251:2001
1233918ms peer_connection.cpp:261 connect_to ] established outbound connection to 198.74.48.55:2001
1233947ms peer_connection.cpp:261 connect_to ] established outbound connection to 73.15.145.219:2001
1234024ms witness_plugin.cpp:366 start_mining ] Miner working at block 7519742 rate: 49943826H/s
1236789ms database.cpp:759 _maybe_warn_multiple ] Encountered block num collision at block 7519742 due to a fork, witnesses are: [["XGT9pemKzHwt8h3dMhQjU54FiEu2BE3YdgHNM3NPeNe","2022-03-29T07:20:26"],["XGT3JrqjZAPiwQiw8uaCNiQhPHTuaby2qQQBUwCMmxc","2022-03-29T07:20:31"]]
1236790ms node.cpp:3121 send_sync_block_to_n ] Successfully pushed sync block 7519742 (id:0072bdfe855376c1433fadfc46eab8a9b24bcffb)
1236800ms database.cpp:783 _push_block ] Switching to fork: 0072bdffe87f40a27ccabd9259defc17f1777e45
1236800ms database.cpp:793 _push_block ] Pushing blocks from fork 7519742 0072bdfe855376c1433fadfc46eab8a9b24bcffb

[obskein]

I am looking into this issue. There are a couple of things going on.

Firstly, there is a distinction between the issue described and the trace provided.

@Censseo If your node is being disconnected from peers, then it is usually because the miner is producing bad blocks. The most common cause of bad blocks is associated with time, if blocks are not produced with good time stamps, other nodes will disconnect them.

I checked the wallet balance, and it appears to have had some success mining.

1. Is this a docker version of the miner?

2. Fork resolution is a normal part of the chain behaviour, it affects all the nodes. Increasing difficulty reduces block reorgs. I mention this because the pasted code indicates fork reconciliation, and is considered normal, intended behaviour.

[Censseo]

@obskein thanks for the response.
I understand that I'm producing bad blocks that got rejected by network. The thing is it started to do those bad blocks just like that, with no reason. I started to mine for 3/4 days without any issues, producing between 5 and 6 blocks average per 10 mins, and sudently I had like 1 or 2 blocks a day, and with each time a block was submitted, the log I posted above.
I tried many times to restart from scratch and still I got the same thing.
I use the same docker image since the beginning (rjungemann/xgt:1.4.8).
And I understand the resolution of forks, my problem is all my blocks are considered as forked by the network, and this cannot be normal, when I see my hashrate and how it was going for the first 3 days.

[Censseo]

So I tried to start again the mining.
Weirdly it worked for a couple of days, maybe because my ip changed. and again starting today the same issue reappeared.

What I can say is at some point, I got disconnected from all peers, and I don't know why. Sometime I just have 1 active connection, and it's not enought because when broadcasting my blocks, it is just beeing rejected by the network with the same message: Block collision. Even if my broadcast is a success, and wait like 10 seconds untill I receive the block collision message.

I have the feeling it is a network issue, it looks like I am somekind of blacklisted by almost all nodes.

[Censseo]

as you can see, for exemple:
2400876ms database.cpp:759 _maybe_warn_multiple ] Encountered block num collision at block 7667663 due to a fork, witnesses are: [["XGT9pemKzHwt8h3dMhQjU54FiEu2BE3YdgHNM3NPeNe","2022-04-05T15:39:49"],["XGT8hzFYWkk1KTzPEhKAsLii3GvvtoZy5ZdCa8SKQh4","2022-04-05T15:39:52"]]
My block has been broadcast at 15:39:49 but still it got rejected against the block broadcasted at 15:39:52.
And this happen a lot.
In my understanding, the first block found should be broadcasted to all peers, but it looks like it is not the case because this first block produced is not taken into account.