Closed sachushaji closed 1 year ago
I unfortunately couldn't reproduce it, after having it run for several hours. More information would be needed:
I was running a single node with no neighbours connected. I was sending transactions to this node only
I was running a single node with no neighbours connected. I was sending transactions to this node only
Okay, I did the same :)
Can you remember that from a specific transaction/bundle on, this occurred?
I am not sure unfortunately, It was working when I left off and when I tried again the next day, the transactions where not confirming
you dont have access to the full log right?
@sachushaji Could you please attach the log-file with the exception?
you dont have access to the full log right?
Unfortunately yes
Expected Behaviour
Valid Transactions which are broadcasted to the network should get confirmed within some limited period of time
Current Behaviour
The Transactions are not confirming after a few hours of running the network with a single nominee. After a some hours of running the node, it also seems that the solid round is way far off from the current round.
Failure Information (for bugs)
Valid Broadcasted Transactions are not being confirmed even after a long period of time by checking the tail hashes using getInclusionState API.
Steps to Reproduce
Context
I ran the node in aws (t2 micro) with ubuntu 18.04. Unfortunately I am not sure exactly when the problem started. It should be within 12 hours running the node. Version:0.6.5 Operating System:ubuntu 18.04
Failure Logs
.