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

V12 Release

One of my vps reset itself, I guess due to memory shortage (768MB). Last seconds of cpu and disk usage

Y3QZhuu.jpg

Code:
(9a188722ec8085927a99b5afd9835c063ecac26bff2d4bc9f0902525570b3165, 1), scriptSig=) - 1440438560
2015-08-24 22:22:25 ResendWalletTransactions()
2015-08-24 22:23:36 peer=1928 using obsolete version 70051; disconnecting
2015-08-24 22:23:36 ProcessMessage(version, 105 bytes) FAILED peer=1928
2015-08-24 22:24:54 CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(63104594ab0ab1d2d34fb8ef0676c26f78812a372dcb08709ccf7e5763076194, 0), scriptSig=)
2015-08-24 22:25:12 receive version message: /darkcoinseeder:0.1.2/: version 70103, blocks=320000, us=123.456.78.9:9999, peer=1929
2015-08-24 22:25:39 CheckBlock() : skipping transaction locking checks
2015-08-24 22:25:39 CheckBlock() : skipping transaction locking checks
2015-08-24 22:25:39 CheckBlock() : skipping transaction locking checks
2015-08-24 22:25:39 UpdateTip: new best=000000000007ca137cc71dbd545a1cc939382041c817b05e85abbf911cd08fec  height=324909  log2_work=61.664479  tx=1310796  date=2015-08-24 22:19:51 progress=0.999982  cache=2440
2015-08-24 22:25:40 ProcessNewBlock : ACCEPTED
2015-08-24 22:26:03 receive version message: /darkcoinseeder:0.1.2/: version 70103, blocks=320000, us=123.456.78.9:9999, peer=1930
2015-08-24 22:27:54 receive version message: /darkcoinseeder:0.1.2/: version 70103, blocks=320000, us=123.456.78.9:9999, peer=1931
2015-08-24 22:30:02 CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(63104594ab0ab1d2d34fb8ef0676c26f78812a372dcb08709ccf7e5763076194, 0), scriptSig=)
2015-08-24 22:35:09 CActiveMasternode::SendMasternodePing() - Relay Masternode Ping vin = CTxIn(COutPoint(63104594ab0ab1d2d34fb8ef0676c26f78812a372dcb08709ccf7e5763076194, 0), scriptSig=)
2015-08-24 22:35:37 Timeout downloading block 00000000000a71cbc69a7c0d16d2ef26c97bf09a4dcda8beec7d8e8156c3e98d from peer=1181, disconnecting


Another one only deamon crashed. This one have 1gb of memory:

Code:
31.16.50.15:41532
2015-08-24 22:04:36 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:39 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:45 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:46 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:49 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:56 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:04:58 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:05:00 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:05:03 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:05:06 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:05:31 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
2015-08-24 22:05:32 CheckBlock() : skipping transaction locking checks
2015-08-24 22:05:32 CheckBlock() : skipping transaction locking checks
2015-08-24 22:05:32 CheckBlock() : skipping transaction locking checks
2015-08-24 22:05:33 UpdateTip: new best=00000000000d0c5140facc3d3852d571ae50cc03cf1cb0f3cb328b68e6922c0c  height=324901  log2_work=61.66444  tx=1310772  date=2015-08-24 22:04:59 progress=0.999998  cache=3105
2015-08-24 22:05:33 ProcessNewBlock : ACCEPTED
2015-08-24 22:05:41 dseg - Sent 1 Masternode entries to 31.16.50.15:41532
 
Last edited:
Entering the MN payment queue...

I shut down for a couple days and then turned them all back on, got them synced, and ran start-many on cold wallet...

Payments come in completely random spread out over about 72 hours... Two haven't been paid at all, some repeated... Sigtimes are identical...

I realize it wasn't going to be as perfectly ordered as when on the centralized monitor box, but wow, this is wacky... If it's working well, whatever, don't care. Just concerned it might not be right since variance is way, way more than anticipated...

OT: Wow, look at the market tank over this blocksize crapola... talk about dysfunction...
 
Maybe rpi can't handle v12 due to not enough memory?

It actually ran for 5 days - got paid - then died 12 hours later


it has 1GB of memory




I got it back up and running just now - see what happens



thinking about testing a new crontab setup
but
my cold side needed rebooted/restarted aslo
so
my crontab thoughts would not help if cold-side needs to re-boot

have to think about it
 
I didn't have to go far


https://bitcointalk.org/index.php?topic=421615.msg12233642#msg12233642


----------------------------------------
UdjinM6 Hero Member
star.gif
star.gif
star.gif
star.gif
star.gif



How to start dashd automatically again after it crashed.

run:
Code:
crontab -e

add line:
Code:
*/1 * * * * /home/dashuser/mn_watch.sh >/dev/null 2>&1

use any editor you like and save this as "mn_watch.sh" file in user "dashuser" home directory:
Code:
#!/bin/bash
if [ -z `pidof dashd` ]; then
/home/dashuser/dashd
fi

add executable flag:
Code:
chmod u+x mn_watch.sh


PS. Use appropriate username, not "dashuser" from my example
wink.gif

I also assumed that dashd is located in your user home directory, change path if needed.

PPS. not tested but should work
rolleyes.gif


EDIT: ooops, tested and fixed
smiley.gif
 
*********** v12.0.48 *************
- Fixed memory leak
- Fixed the bug that made masternodes hang sometimes (when waiting for remote activation)
Another super fast update by the team:grin:.
Am wondering for future reference, why was this missed in testnet and also does the memory leak cause database corruption ?
 
11 Days without a payment :sad:

"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service" : "[::]:0",
"pubKeyMasternode" : "XtEGzjn4HXeWpGZCMzafLy9mjUrNWyxmq6",
"status" : "Not capable masternode: Hot node, waiting for remote activation."



Sorry , My bad...

just needed to wait a little bit longer :

"vin" : "CTxIn(COutPoint(1c6e218ceca6f3aedf55e48a6d7e2d4295a5c40955f24c0fb3fc96ac315b6c1b, 1), scriptSig=)",
"service" : "37.142.217.238:9999",
"pubKeyMasternode" : "XtEGzjn4HXeWpGZCMzafLy9mjUrNWyxmq6",
"status" : "Masternode successfully started"
Is your pubKeyMasternode correct?
 
has the source code been updated??

I downloaded - 2 hours to compile and still on 47?? ugh

or maybe the Pi versions can also be released on dashpay.io/downloads ...??
 
THX Sir
Any chance of getting Pi added to Dashpay.io/download ??

I don't mind compiling from time to time but - why is the source code only 12.1.0?? :-(
Where did you get the source? 12.1.0 is the next development iteration - did you check out the correct branch/tag (12.0.48)?
 
The source link on dashpay.io links to github, there is no source bundle to download.

View attachment 1823


I clone <https://github.com/darkcoin/darkcoin>
and compile that
Worked before.....

??? ???



edit:
--------------------------------
taken from my Pi Guide:
--------------------------------
code:
cd
mkdir .dash
mkdir .ddl
cd .ddl
sudo apt-get install git
git clone https://github.com/darkcoin/darkcoin

You are now ready to Compile the DASH software, for use on the Pi2b

This Chapter will actually take the most time to complete. The process of Compiling the DASH software takes approximately two hours on the Pi2b, after you INPUT the ‘make’ command

code:
cd
cd ~/.ddl/darkcoin
./autogen.sh
./configure --with-incompatible-bdb
make clean
make
 
I clone <https://github.com/darkcoin/darkcoin>
and compile that
Worked before.....

??? ???
It should work like that, yes. If I do

Code:
$ git clone https://github.com/dashpay/dash.git

I get master, which is on 0.12.0.48

Code:
$ cat dash/configure.ac | grep VERS
define(_CLIENT_VERSION_MAJOR, 0)
define(_CLIENT_VERSION_MINOR, 12)
define(_CLIENT_VERSION_REVISION, 0)
define(_CLIENT_VERSION_BUILD, 48)

Maybe you switched to 0.12.1.x branch :)

Code:
$ git checkout v0.12.1.x

Code:
define(_CLIENT_VERSION_MAJOR, 0)
define(_CLIENT_VERSION_MINOR, 12)
define(_CLIENT_VERSION_REVISION, 1)
define(_CLIENT_VERSION_BUILD, 0)
 
Back
Top