GermanRed+
Active member
v0.12.0.53 still crashes. I can confirm this because I had one MN died today. Signal 10... Bus error?
V12 Release
- Thread starter eduffield
- Start date
Defacto
Member
yes... on two different hosts.
M
MangledBlue
Guest
running strong on V53 - Pi2b
camosoul
Well-known member
[up arrow] [home button] [type in new stuff]
Sometimes it's faster to edit a previous command. Feeding it backwards from bash history was easier... If I were writing a script, sure...
camosoul
Well-known member
I can't confirm any crashes... I set cron to attempt to launch dashd every 5 minutes from back in the day when dashd crashes were pretty much accepted... It might be crashing, but it's back up in 5 minutes at most...
I can confirm that .53 is unable to pull it's head out of it's butt and go hot.
The only way I got any of my nodes back online was to erase everything in ~/.dash/ except for the appropriate .conf files, launch dashd, when it get about halfway through the chain download (170000 block height by staring at tail -f debug.log) I then issue the start-alias. Absolutely nothing else works. If the node is already caught up, it self-excludes. If it's not even active, it'll take too long to pull the chain and will fall off the announce before managing to ping. Essentially, the announce has to go up BEFORE the node ever even checks itself, or else is self-excludes permanently. If the node doesn't find the announce on it's firt try, it does nothing but find any excuse it can to never ping. But, it has to pull chain and go active BEFORE ping window expires...
So, wait to be delisted. Launch dashd on masternode. Wait for chain to be halfway downloaded. Make announcement. Once the top of chain is reached, it goes "Enabled!" Nothing else works.
If it reaches the top of the chain, and the announce isn't live on the network from the Big Wallet, it'll lock itself out until delist and try again. If an announce is sent at this point it'll come up with any number of total bullshit excuses to not "Enable!"
Every. Single. Node. No. Exceptions. Nothing. Else. Works.
I can confirm that .53 is unable to pull it's head out of it's butt and go hot.
The only way I got any of my nodes back online was to erase everything in ~/.dash/ except for the appropriate .conf files, launch dashd, when it get about halfway through the chain download (170000 block height by staring at tail -f debug.log) I then issue the start-alias. Absolutely nothing else works. If the node is already caught up, it self-excludes. If it's not even active, it'll take too long to pull the chain and will fall off the announce before managing to ping. Essentially, the announce has to go up BEFORE the node ever even checks itself, or else is self-excludes permanently. If the node doesn't find the announce on it's firt try, it does nothing but find any excuse it can to never ping. But, it has to pull chain and go active BEFORE ping window expires...
So, wait to be delisted. Launch dashd on masternode. Wait for chain to be halfway downloaded. Make announcement. Once the top of chain is reached, it goes "Enabled!" Nothing else works.
If it reaches the top of the chain, and the announce isn't live on the network from the Big Wallet, it'll lock itself out until delist and try again. If an announce is sent at this point it'll come up with any number of total bullshit excuses to not "Enable!"
Every. Single. Node. No. Exceptions. Nothing. Else. Works.
Last edited by a moderator:
bertlebbert
Well-known member
Is it any concern that coinmine finding over 55% of blocks?
Edit: Where is everybody? Hello?
Edit: Where is everybody? Hello?
M
MangledBlue
Guest
Holiday weekend in the States
bertlebbert
Well-known member
Ahh, I see... said the blind man (as he picked up his hammer and saw) :grin:
Actually, same... long-weekend here in Canada also.
Actually, same... long-weekend here in Canada also.
moli
Well-known member
Everybody else is busy with their real life, silly... lol... Labor Day holiday weekend here... double pay and triple pay this weekend and no free labor.. :grin:
But someone else is "over" working...
https://www2.coinmine.pl/dash/index.php?page=statistics&action=pool
http://biersteker.tweakblogs.net/blog/11915/hidden-cryptominers-in-game-torrents
bertlebbert
Well-known member
moli
Well-known member
lmao....
nah.. i don't have any botnets to mine dash like this guy.. dash is his real life there .. rofl...
bertlebbert
Well-known member
It's just eerily quiet. I'd prefer if people would come here, and air any discontent... rather than over at Cryptsy 
moli
Well-known member
You said "over" ... you don't mean "overX" is "over" there to dump his dash, right?It's just eerily quiet. I'd prefer if people would come here, and air any discontent... rather than over at Cryptsy
:grin:
EDIT: https://i.imgur.com/K3Bq5DO.png
I'm wondering if he's also "anonymous" or something else..
maybe poiuty knows?
Last edited by a moderator:
GermanRed+
Active member
You can check the start time of your dashd from the ps command. If you remember roughly when you start your MNs, you know whether it crashed and restarted by cron or not.
Defacto
Member
it's a good idea to add one line sending email when MN is started by cron ;-)
echo "MN made boo boo" | mail -s "Dash Masternode started!" [email protected]
That explains those huge hashrates and I think those sells (at least cryptsy ) everyday. This guy is crashing DASH price.
GermanRed+
Active member
Could it be some central bankers funded operation? We should really take care of the >51% hash rate.
Congratulations all around,
we had just 3 Superblocks pass !
All budgets (as voted) got paid out,
MN payments were on hold while the Superblocks passed, we are back to normal !
This is the 1st time EVER in Blockchain history Superblocks were introduced and moved across the blockchain !!
Well well done to the Dev Team !
http://explorer.dashpay.io/block/000000000014702a849cddf3145c495086ef5235b8e1a08fbea8e9c17c7d149b
http://explorer.dashpay.io/block/000000000008ad3b2d5419b8206c02b3ec1abf10bd3039de15ce2e5ce0e13680
http://explorer.dashpay.io/block/000000000010ac0d276f4c44274274022b82769386f26926d6890903763721a5
Edit:
- Evan on Superblocks:
https://bitcointalk.org/index.php?topic=421615.msg12352921#msg12352921
- Evan on MN payments/delays
Each month masternode payments will be delayed by the amount of proposals that are paid. So for example this month, it means people will receive payments 3 blocks late. No payments are ever skipped from the budget system.
we had just 3 Superblocks pass !
All budgets (as voted) got paid out,
MN payments were on hold while the Superblocks passed, we are back to normal !
This is the 1st time EVER in Blockchain history Superblocks were introduced and moved across the blockchain !!
Well well done to the Dev Team !
http://explorer.dashpay.io/block/000000000014702a849cddf3145c495086ef5235b8e1a08fbea8e9c17c7d149b
http://explorer.dashpay.io/block/000000000008ad3b2d5419b8206c02b3ec1abf10bd3039de15ce2e5ce0e13680
http://explorer.dashpay.io/block/000000000010ac0d276f4c44274274022b82769386f26926d6890903763721a5
Edit:
- Evan on Superblocks:
https://bitcointalk.org/index.php?topic=421615.msg12352921#msg12352921
- Evan on MN payments/delays
Each month masternode payments will be delayed by the amount of proposals that are paid. So for example this month, it means people will receive payments 3 blocks late. No payments are ever skipped from the budget system.
Last edited by a moderator:
GermanRed+
Active member
That's great! Congratulation! But, let's not forget the >51%. We don't want to be the first to prove that >51% attack works in real life. BTW, has it been proven yet (i mean by other bitcoin clones)?