V12 Release

Part 3:
Code: 
UpdateTip: new best=000000000007a32d6b6be30e2b0a28f4d5074f6b9ec70eb245513c1d038bb676  height=334441  log2_work=61.702449  tx=1341238  date=2015-09-11 07:28:26 progress=0.999999  cache=3215
ProcessNewBlock : ACCEPTED
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
UpdateTip: new best=000000000003fa370e04b77ecae2979575e238edb6613ee46aaa10f936579cc8  height=334442  log2_work=61.702453  tx=1341240  date=2015-09-11 07:28:51 progress=1.000000  cache=3217
ProcessNewBlock : ACCEPTED
mnb - Got NEW Masternode entry - af6ee4cfbca136de64cc0da4a1460cc068cfae889335c92af8e5168559a4e565 - 104.223.47.81:9999 - CTxIn(COutPoint(b8b3324cc2043d084a0bf50ad7adfe970e07d30ad3c70ea664933e5f19ea7fb5, 0), scriptSig=) - 1440862522
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
UpdateTip: new best=00000000000a433fd8614b2801b0536269ca2dec7e4d67b483c6e8c007b9ff83  height=334443  log2_work=61.702457  tx=1341241  date=2015-09-11 07:28:55 progress=0.999998  cache=3222
ProcessNewBlock : ACCEPTED
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
UpdateTip: new best=000000000010f9dde6ff51fb3a01fa8036db779a4ffb76c3baac3e425238b14a  height=334444  log2_work=61.702463  tx=1341247  date=2015-09-11 07:31:59 progress=0.999999  cache=3229
ProcessNewBlock : ACCEPTED
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
CheckBlock() : skipping transaction locking checks
UpdateTip: new best=00000000000c791ff4113772c67bd07aed3082b622fcb8669633995757337b7b  height=334445  log2_work=61.702468  tx=1341249  date=2015-09-11 07:32:30 progress=0.999999  cache=3231
ProcessNewBlock : ACCEPTED
CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(0fd39ca250015d6ed6bbb387d08c6d63e5d560956970275baa871e2f2d270efd, 0), scriptSig=)
receive version message: /Dash Core:0.12.0.53/Dash Ninja Port Checker:2.1.1.4/: version 70103, blocks=0, us=[::94.23.248.61]:50875, peer=160
dstx: Got Masternode transaction 582552c8687f0aa7ed104e3cbf9be7a0204d8d59ce06e8b7ac703cce1f07351f
PrioritiseTransaction: 582552c8687f0aa7ed104e3cbf9be7a0204d8d59ce06e8b7ac703cce1f07351f priority += 1000.000000, fee += 0.10
dstx: Got Masternode transaction 951290b6bbeff3bf12218475ad7acec820264331150066d2d6ad578587ee726f
PrioritiseTransaction: 951290b6bbeff3bf12218475ad7acec820264331150066d2d6ad578587ee726f priority += 1000.000000, fee += 0.10
mnb - Got NEW Masternode entry - f09244851e1aa8d85dcce87874d53c3df95537e5d9c406e4b502c060f26c8579 - 104.223.47.85:9999 - CTxIn(COutPoint(008248c1e7b60c7ff970060d873feb7bcb8966b9862acbbce46bee1324a898e2, 0), scriptSig=) - 1440003904
dstx: Got Masternode transaction 6e9f8c1a85901d2be05061bca79f6b4b2e1b1323d86bbb806dd14ae539b91ec8
PrioritiseTransaction: 6e9f8c1a85901d2be05061bca79f6b4b2e1b1323d86bbb806dd14ae539b91ec8 priority += 1000.000000, fee += 0.10
CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(0fd39ca250015d6ed6bbb387d08c6d63e5d560956970275baa871e2f2d270efd, 0), scriptSig=)
mnb - Got NEW Masternode entry - f09244851e1aa8d85dcce87874d53c3df95537e5d9c406e4b502c060f26c8579 - 104.223.47.85:9999 - CTxIn(COutPoint(008248c1e7b60c7ff970060d873feb7bcb8966b9862acbbce46bee1324a898e2, 0), scriptSig=) - 1440003904
mnb - Got NEW Masternode entry - 58699fb99eebaba0c7148f8beabbbbdafbe459dcdb7144fee7f9b2c97c1f1464 - 104.223.47.82:9999 - CTxIn(COutPoint(f8354d4986fb99c9f1ee9bf4508876c061597efec34339bb7cccfe6760329d7c, 0), scriptSig=) - 1440003901
peer=161 using obsolete version 70046; disconnecting
ProcessMessage(version, 105 bytes) FAILED peer=161
mnb - Got NEW Masternode entry - 0eab42cf482288337529c17aa1ad3ee5ffda3588b5694194a575d9b25a4e4aad - 104.223.47.83:9999 - CTxIn(COutPoint(27527bbbc56b8d0d9dd3b4760272895aceb827bbff3700f3da71fff6a1c6821c, 0), scriptSig=) - 1440003902
CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(0fd39ca250015d6ed6bbb387d08c6d63e5d560956970275baa871e2f2d270efd, 0), scriptSig=)
dumpaddr thread stop
msghand thread interrupt
opencon thread interrupt
addcon thread interrupt
net thread interrupt
PrepareShutdown: In progress...
StopNode()
Verifying mncache.dat format...
Loaded info from mncache.dat  380ms
  Masternodes: 3029, peers who asked us for Masternode list: 1, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 50798
Writting info to mncache.dat...
Written info to mncache.dat  242ms
  Masternodes: 3049, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 55132
Masternode dump finished  634ms
Verifying budget.dat format...
Loaded info from budget.dat  133ms
  Proposals: 4, Budgets: 1, Seen Budgets: 4, Seen Budget Votes: 5160, Seen Final Budgets: 1, Seen Final Budget Votes: 2975
Writting info to budget.dat...
Written info to budget.dat  52ms
Budget dump finished  187ms
Verifying mnpayments.dat format...
Loaded info from mnpayments.dat  271ms
  Votes: 37882, Blocks: 3795
Writting info to mnpayments.dat...
Written info to mnpayments.dat  144ms
Budget dump finished  421ms
Shutdown: done
 
GermanRed+ said:
I found something in the log messages:

Code: 
dumpaddr thread stop
msghand thread interrupt
opencon thread interrupt
addcon thread interrupt
net thread interrupt
PrepareShutdown: In progress...
StopNode()

So, why did dumpaddr stop? I will upload the last 300 lines of log messages later.
Click to expand...
Check /var/log/syslog
Are there any mentions of dashd?

RE part1-3: pastebin.com is a better way ;)
 
And now for the first ever automated block checking and restart script for your DASH daemons.
Code: 
#!/bin/bash
blockold=$(/home/dash/dash-cli getinfo | grep "blocks" | grep -Eo '[0-9]{6,100}')
while true
do
sleep 1000
blocknew=$(/home/dash/dash-cli getinfo | grep "blocks" | grep -Eo '[0-9]{6,100}')
if [ $blocknew -gt $blockold ]
then
blockold=$blocknew
else
tail -n 30 /home/dash/.dash/debug.log >> crash.log
/home/dash/dash-cli stop
sleep 30
pkill -9 dashd
sleep 10
/home/dash/dashd
sleep 60
blockold=$(/home/dash/dash-cli getinfo | grep "blocks" | grep -Eo '[0-9]{6,100}')
fi
done

This program grabs the current block. Then waits 16 minutes and checks that block. If the new block is bigger it stores the new block as the old and waits another 16 minutes. If the old block is not bigger we assume dashd is locked up. It first logs the last 30 lines of the debug.log and tries to shutdown nicely. And if that doesn't work it kills the process. Then restarts and finds blocks again. This should also restart the dashd if it doesn't get any output(like if it isn't running).

So for those with more than one masternode on a server, you should change dashd to dashd1, dashd2, etc. Then use pkill -9 dashd1, dashd2, etc. If you just use dashd it will shut anything down with dashd in it. If there is any interest, I could make a script for a set of nodes. Just send a donation of like .0001 Dash or something.
 
Last edited by a moderator:
UdjinM6 said:
Nice one Solarminer ! I (still) hope we'll find all bugs and make scripts like this obsolete though :smile:
Click to expand...
And, restart script can't prevent zombie processes filling up the process table thus crashing your machine. So, it should only be used as a temporary solution.
 
Last edited by a moderator:
UdjinM6

doc/guide-startmany.md
https://github.com/dashpay/dash/commit/02dfe6b23961a6d8d91617e2a123c902d2029c5d

138 136 ```dashd getinfo```

perhaps change to :

138 136 ```dash-cli getinfo```

I also have a question : just having masternode=0 in dash.conf will make it safe to sync my cold wallet ? and if there will be a protocol change i can put masternode=1 back in there and do a start from cold wallet ? (Instead of setting up a masternode.conf, i'm a bit hesitant to change my current setup).
 
Last edited by a moderator:
qwizzie said:
UdjinM6

doc/guide-startmany.md
https://github.com/dashpay/dash/commit/02dfe6b23961a6d8d91617e2a123c902d2029c5d

138 136 ```dashd getinfo```

perhaps change to :

138 136 ```dash-cli getinfo```

I also have a question : just having masternode=0 in dash.conf will make it safe to sync my cold wallet ? and if there will be a protocol change i can put masternode=1 back in there and do a start from cold wallet ? (Instead of setting up a masternode.conf, i'm a bit hesitant to change my current setup).
Click to expand...
Good eye! Yep, changing to "masternode=0" or commenting it out with "#" in the beginning of the line should be safe.
 
Are the developers working on v0.12.0.55,56,57...? I noticed there are MNs that were not paid even though the last payment time has been updated. Do you call it hijack without a trace? Dashninja.pl does not report it. It is like we were back to the days before enforcement with centralized control. The only difference is that you won't even see it on dashninja.pl.
 
fible1 said:
Just my two cents: My MN's have been running perfectly past few weeks.

Pablo.
Click to expand...
Something is wrong with dashnodes.com:

http://explorer.dashninja.pl/address/Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf
http://www.dashnodes.com/index/address/Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf
https://dashninja.pl/mndetails.html?mnpubkey=Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf

dashnodes.com is reporting this MN as expired but dashninja.pl is reporting this as active! Anyone want to comment on what this may mean?

EDIT: If someone controls half of the MN network, can he/she kick others off the MN list by reporting other MNs off the list?

EDIT2: This is not the only MN reported expired on dashnodes.com while it is reported active on dashninja.pl.
 
GermanRed+ said:
Something is wrong with dashnodes.com:

http://explorer.dashninja.pl/address/Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf
http://www.dashnodes.com/index/address/Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf
https://dashninja.pl/mndetails.html?mnpubkey=Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf

dashnodes.com is reporting this MN as expired but dashninja.pl is reporting this as active! Anyone want to comment on what this may mean?

EDIT: If someone controls half of the MN network, can he/she kick others off the MN list by reporting other MNs off the list?

EDIT2: This is not the only MN reported expired on dashnodes.com while it is reported active on dashninja.pl.
Click to expand...
It seems dashnodes.com is off. I am running a mirror of the dashninja code on http://dashninja.dashpay.io and it reports the given node as active.

http://dashninja.dashpay.io/?mnregexp=(Xqp8HaGaQS9MzJ78RBW8d9NkZAiP1FnqFf)#mnlistdetail
 
Guys, after 2 weeks without any major issue in the last 12 hours i had a CRAZY spike on my VPSs, one was even suspended (!) due to usage of more than 1,5TBs of datas (Please notice, TERA, not GIGA) and another one is close to be killed with 1,3TBs.

What the hell is going on?
 
Gi01 said:
Guys, after 2 weeks without any major issue in the last 12 hours i had a CRAZY spike on my VPSs, one was even suspended (!) due to usage of more than 1,5TBs of datas (Please notice, TERA, not GIGA) and another one is close to be killed with 1,3TBs.

What the hell is going on?
Click to expand...

Are you sure that the traffic is from the Masternodes and not from some system (OS-) update, or someone using your box illegally for file transfers?
 
What will happen if many MNs report that a MN is off the list when this is not true? Can a MN operator who controls a large amount of MNs kick other MNs off the list?
 
Wow a VPS got 6TB of traffic in 24h...

They charged me 150$

I think that I have a little problem about keeping my MNs up
 
You must log in or register to reply here.
Back
Top