Search results

Well I think I like the new payment system. I receive a lot of payment this last 24 hours. :cool::grin: And really like the "fast upgrade" incentive. As lot of time people says : "will wait I should have a payment soon. Or will wait for stable version etc..etc.." EDIT : the column "Last Paid"...

Good morning. 2 more crash this morning and always with this last message in debug.log : Verifying mncache.dat format...

I don't think so because VULTR don't do this, I'm even mining of the VPS on VULTR and I'm using 100% of the cpu without problem. And even on VULTR my daemon crash. Edit : O.o, just saw a .46 on dashninja

Well we all agree that we have stability problem ;) 6 out of 15 offline tonight. As say before some movements on github were detected, we all know that it will take max 48h for the dev team to correct those glitch. We are with you.:smile: Edsit: If debug.log are needed I got a lot. Edit 2: One...

One of mine crashed at 19:02:31 (UTC). And not on VULTR neither on digitalOcean.

@UdjinM6, just another crash of one MN. This one is good, I saved the debug.log. Just told me where I can send it to you.

For memory usage, maybe I'll check to install nmon on 1 or 2 of my MN. Never did it for ubuntu but I'll check. EDIT: Ok found it, install the binary directly, and colecting data right now. ./nmon_x86_64_ubuntu1410 -f -s 120 -c 1000 Will post result later

Well the one that crashed has a crontab that restart it automatically (and log is already overwrited). And the other was not responding (have to kill it) and didn't save debug.log. Since then no crash for the moment ;) so I promise that next crash I'll save the debug.log (just for you ;).

Ok, will check what is the specification of my VPS (don't remember, I'm with 4 different provider lol). Also maybe the old versions made some noise that perturb the daemon.

Hi, I think the new version need more resource, what I'm seen is that my MN crashed more often, (not so much but 2 out of 15 last 24h). Maybe we'll need to have better VPS? But should be interesting to know of it's RAM that is needed (most probably), or cpu? Or Bandwidth? Also someone on BCT...

Maybe can I give an advice : yesterday I think I go too fast, made the masternode Start as they were already enabled with old version, and also face some details with some MN. I stop the daemon and wait that they were unlisted everywhere (my other daemon and dashninja), about 2 or 3 hours.. And...

Great no need to restart the already upgraded :grin:

Protocol bump? Or still 103?

lol... well ok.. That's true "wget" don't overite... TANTE... Maybe you are doing the same thing ;)

O.o I think 32 bit still have the problem. I hear Tante on BCT saying she still got 102 version for linux 32bits... Edit : One thing is sure, that your MN with fall offline if both are not on the same protocol version.

Ok Just did it and all OK : here my script for upgrading from v11 ==> v12: wget https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz --no-check-certificate tar zxvf dash-0.12.0.44-linux64.tar.gz cp dash-0.12.0/bin/dashd dashd2 cp dash-0.12.0/bin/dash-cli . ./dashd stop sleep 10 rm...

64 bits. With this link : wget https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz --no-check-certificate I still have some MN to upgrade (was waiting for .45 version but it take longer than I though). So I'll do it again and verify if still protocol version at 103

All my MN upgraded with protocol version 103 still online, after more than 10 hours. All good for me :)

Some of MN on linux updated to 103 protocol version. Start OK, detected and listed by all old and new version OK. So far so good. Anyway will wait for version 0.45 for the remaining MN.

Some more details about what I observed so far : When I start an upgrade MN, I got the message that it start ok. Himself detected it as Enable, other MN (upgraded in 12.0.44) did not detect it as enable and don't list it. MN with old version detect it correctly. And after sometimes it is...