• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12.1 Testnet Launch Thread

Status
Not open for further replies.

Seems like all nodes kill the connection to you - maybe you are banned by the network :eek:

Or is a firewall not playing nice?


Code:
2016-05-26 07:54:40 CMasternodeSync::Process() - tick 175 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:54:40 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:44 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:46 CMasternodeSync::Process() - tick 181 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:54:46 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:48 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:50 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:52 CMasternodeSync::Process() - tick 187 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:54:53 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:55 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:54:58 CMasternodeSync::Process() - tick 193 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:00 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:03 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:05 CMasternodeSync::Process() - tick 199 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:08 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:11 CMasternodeSync::Process() - tick 205 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:13 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:17 CMasternodeSync::Process() - tick 211 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:24 CMasternodeSync::Process() - tick 217 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:24 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:27 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:28 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2016-05-26 07:55:30 CMasternodeSync::Process() - tick 223 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 2 nSyncProgress 0.250000
2016-05-26 07:55:33 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
 
Seems like all nodes kill the connection to you - maybe you are banned by the network :eek:

Or is a firewall not playing nice?
Tried with out firewall, no go.
Maybe i tested too much and got banned.

EDIT: Is there a way get out from ban list?
If not, i can reinitialize my 4G modem and get new ip.
 
@flare @UdjinM6

Speakin about banning,
what is the network parameters to ban and why, and when banned is released, or is it forever banned?
 
Maybe you can get your dialup a new IP?
Hmm, new IP and still no go, it must be some code broken.
Last 2 builds is broken to me, no block source and no masternodes.
In my end nothing is changed, but now new ip.

Edit: what if user have static ip?

EDIT2: its not dash-qt, because older version does not work also,
so its my network or providers network fault.
 
Last edited:
Fun tMN stats...

WFZslnQ.png
 
Hmm, new IP and still no go, it must be some code broken.
Last 2 builds is broken to me, no block source and no masternodes.
In my end nothing is changed, but now new ip.

Edit: what if user have static ip?

EDIT2: its not dash-qt, because older version does not work also,
so its my network or providers network fault.

Problem solved.
I wiped all folders, and i'm back to testing.
I figured i was forked yesterday because i was mining and there was no masternodes at that time.
 
@UdjinM6 @flare
Mixing test was failure.
New fresh wallet, all synced, 1000 / 2 rounds.
After one hour, it was stuck, first mixing tx:s unconfirmed and blockchain was not updated.
Restarted wallet and blockchain got synced again, and unconfirmed transactions confirmed.
:rolleyes:
 
My usb wifi on my windows machine is iffy, and I just noticed it was off again. Even so, Over the last ~10 hours at most, I have 2000 coins mixed 68%. Probably less time online :)

One of my masternodes has a cron job to keep it going if it should ever crash, however the other one does not. It crashed.

Shall I send my debug log to anyone? Ugh, got to go so I'm sending it to you Holger! You lucky guy!
 
Last edited:
I'm amazed... -privatesendmultisession has mixed 2 rounds (2000 tdash) in around 4 hours. I've never seen such fast mixing! Please let's incorporate some form of that on mainnet!!

On another note, I have 40 tDash that have been stuck in "Pending" for several days now. I have no idea why, unless it was a mixing session that never completed or something.
 
I'm amazed... -privatesendmultisession has mixed 2 rounds (2000 tdash) in around 4 hours. I've never seen such fast mixing! Please let's incorporate some form of that on mainnet!!

On another note, I have 40 tDash that have been stuck in "Pending" for several days now. I have no idea why, unless it was a mixing session that never completed or something.

OK disregard... -zapwallettxes worked.
 
Status
Not open for further replies.
Back
Top