-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[PoA] Transactions are not propagated when adding a new node to the network #10040
Comments
Can you share the txqueue logs from your validator nodes? ( |
txqueue logs from
Same for the But if I try to view all transactions from my regular node, all pending transactions appear:
|
Yeah, you're certainly correct that the transactions don't seem to be being propagated in the first place. Your netstats also show your nodes are all in sync and on the same chain, that rules out connectivity issues. I'm seeing other users with similar issues elsewhere. It looks like you're running with --no-persistent-txqueue. Have the transactions (with lower nonces) before those on the txqueue been confirmed already? This is likely a case of nodes not accepting transactions because they don't have the dependencies of the transaction. |
No transactions from any
|
ie, transaction nonces |
No transactions confirmed from the |
|
1 - Logs for the
|
Using |
@fooock thank you so much for the logs and results, it seems thought that your transaction pool is now empty and you don't have any transactions from Would you mind reproducing the situation again and provide the same logs in the case where transactions are there? |
@joshua-mir, you have seen these symptoms in other installations. Could you kindly cross-reference Issues for those and similar, to compare configurations and logs? |
"I'm seeing other users with similar issues" usually refers to gitter. Unfortunately, I can't get everyone to share their logs or report/update issues here. Bumped priority, I'm still seeing this incidentally, but there has been improvements due to better transaction importing #10051 @wkarshat are you still seeing this yourself and are you willing to put in time to help investigate? |
@tomusdrw I can't reproduce the error... |
@joshua-mir I am running something like this
Any transaction that is submitted in the regular node are propagated to the network and included in the next block. |
@SidhMj does that imply that you aren't seeing this issue? |
@joshua-mir yes |
OP also mentioned they can't replicate so will close unless someone states otherwise |
Before filing a new issue, please provide the following information.
Parity-Ethereum/v2.1.8-stable-3eae1d3-20181130/x86_64-linux-gnu/rustc1.30.1
I'm trying the demo PoA tutorial. All seems to work, but when I add a new node to the network (this node isn't validator), the transactions from this node doesn't propagate to the other nodes in the network.
The initial network is composed of the nodes:
validator-01
validator-02
The updated network is with the node:
regular-02
All transactions related to this issue are from
regular-02
node.The genesis file for my network is:
The
.toml
configuration file from the regular node is:The
.toml
config file from one of the validator nodes is (the other one is the same config but with different identity and base path):When I send a new transaction from this node, a new transaction is created:
When I want to retrieve the transaction info from this node, I obtain this result:
From the Ethereum network status this is what I see:
I expect the transaction sent from the
regular-02
node has been mined, but this never occurs.What I'm missing?
Related?
#9329
The text was updated successfully, but these errors were encountered: