Version 12.2 release

Status
Not open for further replies.

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
Don't remember exactly and don't have access right now, but it's ESXi with something like i7 4770.
For Dash VM - 1 core and 1Gb RAM.
Ok, but its more powerful than my 1 x 2.4 Ghz core and 1 Gb ram nodes.

My all nodes uses all the memory + some swap and 80% cpu at this moment,
wondering should i upgrade my nodes or wait if devs can tweak dashd more...
 
  • Like
Reactions: nnx3

qwizzie

Well-known Member
Aug 6, 2014
1,707
819
183
To @UdjinM6

So when i do getchaintips i see quite a few valid-forks (8x i think ?), will those forks disappear over time or can they become a threath
to the active chain ? And who is causing those forks ? are they miners ? or masternodes ? wallet users ?

I remember from the past with Evan we also had a lot of little forks popping up during an update, eventually (if i remembered correctly) we were all asked
to update immediately with an update that had some form of a block reference in it to guide us all to the correct chain. That does not seem necessary yet,
has something changed in our spork tech that got us a little more control over mini forks like these ? Or is this situation simply less severe then back then ?
 
Last edited:

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
Dashninja is in the wrong fork i think or its stuck: 38 minutes ago 769439
Wallet and explorer shows: 769456
 

Dusan

New Member
Oct 7, 2016
32
9
8
I did not do anything, had 12.2.1 and status ENABLED, bud now suddenly i have status NEW_START_REQUIRED.
I did not change anything.
 

Acedian

Member
Mar 17, 2017
243
71
88
Dash Address
XeMABbcebB5yeZH2HxsV7yLNJA9hbzMgpz
I did not do anything, had 12.2.1 and status ENABLED, bud now suddenly i have status NEW_START_REQUIRED.
I did not change anything.
That can sometimes be a bug, check elsewhere before issuing a new start or you may lose position in queue.
 
Apr 23, 2017
66
26
58
I would advice you to upgrade to at least a dual core server, I know it cost a bit more, but it's allot cheaper than missing a payment. At any-rate running 100% CPU power especially on a single core CPU, will most-likely result in your system failing one way or the other. In fact CPU usage around 70%, is much better upper limit to have. I only speak out of my experience as professional and overclocking as a hobby, both from what I have seen and heard. Take it or leave it either way you don't even have to spend 1% of your total profits of running a MN on a dual core or better.

Memory should never be full either, because once it's full you'll have to go the SSD for extra memory, rough estimate would be that is 10x slower.

But any rate I gladly take your spot in line to receive the next masternode payment first (joke)
 
Last edited:
  • Like
Reactions: nnx3

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
I would advice you to upgrade to at least a dual core server, I know it cost a bit more, but it's allot cheaper than missing a payment. At any-rate running 100% CPU power especially on a single core CPU, will most-likely result in your system failing one way or the other. In fact CPU usage around 70%, is much better upper limit to have. I only speak out of my experience as professional and overclocking as a hobby, both from what I have seen and heard. Take it or leave it either way you don't even have to spend 1% of your total profits of running a MN on a dual core or better.

Memory should never be full either, because once it's full you'll have to go the SSD for extra memory, rough estimate would be that is 10x slower.

But any rate I gladly take your spot in line to receive the next masternode payment first (joke)
Yes, i also have 25 years experience in the computer field + building and overclocking.
I agree what you said, but so far my nodes do not have any problems and i hope @UdjinM6 and
the team will tweak software little more efficient if possible, if not then i can upgrade my nodes.
 

qwizzie

Well-known Member
Aug 6, 2014
1,707
819
183
The protocol version changed with this update. You'll need to update your local cold wallet too and issue a start to make it work again.
Protocol version only bumped with v0.12.2.0
v0.12.2.1 is a hotfix for high cpu behaviour and does not contain a new protocol version on itself.

Edit : edit to show correct versions.
 

Figlmüller

Member
Sep 2, 2014
85
45
58
Vienna, Austria
Protocol version only bumped with v0.12.2.0
v0.12.2.1 is a hotfix for high cpu behaviour and does not contain a new protocol version on itself.

Edit : edit to show correct versions.
Yea, that's right. Mea culpa. At least I jumped directly to 12.2.1, skipping 12.2.0 - this may not be the case for all.
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
I would advice you to upgrade to at least a dual core server, I know it cost a bit more, but it's allot cheaper than missing a payment. At any-rate running 100% CPU power especially on a single core CPU, will most-likely result in your system failing one way or the other. In fact CPU usage around 70%, is much better upper limit to have. I only speak out of my experience as professional and overclocking as a hobby, both from what I have seen and heard. Take it or leave it either way you don't even have to spend 1% of your total profits of running a MN on a dual core or better.

Memory should never be full either, because once it's full you'll have to go the SSD for extra memory, rough estimate would be that is 10x slower.

But any rate I gladly take your spot in line to receive the next masternode payment first (joke)
Yes, i also have 25 years experience in the computer field + building and overclocking.
I agree what you said, but so far my nodes do not have any problems and i hope @UdjinM6 and
the team will tweak software little more efficient if possible, if not then i can upgrade my nodes.
Agree with both of you :) (though dual core cpu is probably still an overkill today). High CPU usage was a combination of a bug and a super extreme load due to migration process, there shouldn't be such issue during normal operation time.
 
  • Like
Reactions: AjM

Figlmüller

Member
Sep 2, 2014
85
45
58
Vienna, Austria
High CPU usage was a combination of a bug and a super extreme load due to migration process, there shouldn't be such issue during normal operation time.
What about high network traffic and connection count? I noticed an increase from usually ~18 connections to ~100 per node to dashd resulting in ~3.6 Mb/s. Traffic is also coming from weird hosts such as web and mailservers. Another DDoS wave?
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
What about high network traffic and connection count? I noticed an increase from usually ~18 connections to ~100 per node to dashd resulting in ~3.6 Mb/s. Traffic is also coming from weird hosts such as web and mailservers. Another DDoS wave?
Lot's of nodes come up and down during migration and they have to sync additional data (mnlist, winners, governance) from scratch first time after upgrade due to changes in cache data structure, so I guess this is also a temporary issue and should go away eventually. We'll see :) Traffic from web and mail servers could be because people use same servers for their masternodes, not sure about that though, never checked.
 

TRB

New Member
Aug 28, 2017
4
0
1
40
Cześć mam problem
Czekałem kilka godzin na transakcje, które nie korzystają
Wysokość bloku 769372
Jeszcze nie zrealizowane
co się dzieje
 

t0dd

Active Member
Mar 21, 2016
150
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
Dash Core packages for Fedora, CentOS and RHEL updated to 12.2 (and 1.1 for Sentinel)
If you don't know what I am talking about, this message likely doesn't apply to you.

WARNING (Masternode people): Ideally only update after your masternode has recently distributed a payment because you have to send a "start" from your wallet due to a protocol bump.

The github for these maintained packages of Dash Core is here: https://github.com/taw00/dashcore-rpm
If you are a current user of these packages, be aware that the 12.1 and 12.2 packages are actually housed in two different repositories so that you do not idly update your box accidentally.

When ready, read the "howto" in the documentation directory (folder) at that github link. I am probably too detailed in my description of the process, but the native packaging makes the whole process roughly a 3 minute exercise with maybe an hour of monitoring.

Enjoy. Stay dashy! :)
Okay Dash Masternode (or node) folks using my packages discussed in the quoted text (on Fedora, RHEL, or CentOS Linux)...
* If you have NOT already moved from 12.1 to 12.2... just follow the instructions in the quoted text and you are good.
* If you have already moved from 12.1 to 12.2 but are on 12.2.0, but not yet on 12.2.1 (rpm -qa|grep dashcore will tell you), then you should be able to simply do this...

sudo dnf upgrade -y --refresh
sudo systemctl restart dashd


...and you are done.

Note: If you are not running dashd like a sysadmin with systemd, contact me separately
and I will give you other instruction. A little more manual, but it is almost as easy.

* If you are just running the wallet, just do the dnf upgrade step above and you are golden.

Let me know if you have any issues. Thanks, and have a lovely day. -t
 
  • Like
Reactions: studioz

nnx3

New Member
Apr 30, 2017
22
2
3
40
Devs in my pinion U should correct last DASH. version, because ... CPU is still overheated : CPU is hot 50% about 40connections to other node... Im trying to test with other cryptocurency with results:
CPU Deamon usage fo currencies:

PIVX 3% (30nodes)
DECRED 1% (42nodes)
IOTA 26% (9nodes)
DASH 50% (40nodes)
MONERO 4% (13nodes)


Last time v. DASH have 6% cpu core usage
 

qwizzie

Well-known Member
Aug 6, 2014
1,707
819
183
Devs in my pinion U should correct last DASH. version, because ... CPU is still overheated : CPU is hot 50% about 40connections to other node... Im trying to test with other cryptocurency with results:
CPU Deamon usage fo currencies:

PIVX 3% (30nodes)
DECRED 1% (42nodes)
IOTA 26% (9nodes)
DASH 50% (40nodes)
MONERO 4% (13nodes)


Last time v. DASH have 6% cpu core usage
1 : you can put a limit on the number of connections in your dash.conf (maxconnections=XX)
2 : because of a restructure with v0.12.2.0 and a overlooked bug, a lot of pressure was set on the CPU side.
v0.12.2.1 fixes the bug part.

Try to do another check on your CPU after you upgraded to v0.12.2.1 and after you limited your connections to 10 (maxconnections=10)
How fast is your CPU by the way ? And what kind of processor do you have ?
 
Last edited:

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
1 : you can put a limit on the number of connections in your dash.conf (maxconnections=XX)
I checked my maxconnections, and it was 128, so i changed that to 32, lets see how it affects to my mnodes cpu usage.
 
  • Like
Reactions: qwizzie

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
I checked my maxconnections, and it was 128, so i changed that to 32, lets see how it affects to my mnodes cpu usage.
@UdjinM6 @qwizzie
Maxconnections reduction results from 128 ==> 32, nice drop from 80% cpu usage to 45%.
Also memory usage dropped about 150 MB.

EDIT: Server specs: 1x 2.4 Ghz CPU, 1 GB Memory + 512 MB Swap.

maxconn.png
 
Last edited:

demo

Well-known Member
Apr 23, 2016
3,113
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
The stupid Masternodes should write 100 times the below sentence, for punishment:
The market doesn't care about conferences, flying jets, rain ponchos, mma fighters, meet-ups. The market cares about technology, progress, updates.
The market doesn't care about conferences, flying jets, rain ponchos, mma fighters, meet-ups. The market cares about technology, progress, updates.
The market doesn't care about conferences, flying jets, rain ponchos, mma fighters, meet-ups. The market cares about technology, progress, updates.
And you can clearly see in the below chart how the market reacted, after the 12.2 update.
Maybe the stupid Masternodes should write for punishment the above sentence not only 100 times, but 1000 times, in order to finally understand it.

chart.jpeg


And especially for @Macrochip (who rated the above truth as troll) he should write it 10000 times.
 
Last edited:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
I would like to try out the experimental HD wallet. Is it dashd only? How do we access it? Thanks :D
 

qwizzie

Well-known Member
Aug 6, 2014
1,707
819
183
I would like to try out the experimental HD wallet. Is it dashd only? How do we access it? Thanks :D
From Testnet v12.2 thread :

- Experimental BIP39/BIP44 complaint HD wallet (disabled by default, should be fully functional but there is no GUI yet)

The official release note should have mentioned the "disabled by default because missing GUI" part too.
Also i remember reading awhile back that the HD wallet should not be activated, it had an unsafe element that needed to be worked on (could possibly be fixed by now).
It had something to do with the seed creation i think.
 
Last edited:

jimbursch

Well-known Member
Mar 5, 2017
837
501
163
57
WARNING: The way it's currently implemented is NOT safe and is NOT recommended to use on mainnet. Wallet is created unencrypted with mnemonic stored inside, so even if you encrypt it later there will be a short period of time when mnemonic is stored in plain text. This issue will be addressed in future releases.
Just curious, given the above, why was this HD functionality included in this release? As a matter of principle, it seems unwise to release code that requires this type of warning.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Thank you guys. I'm curious, once you create the wallet and encrypt it, is the mnemonic passphrase encrypted, and thus safe after the wallet is encrypted? I can see creating the wallet offline on a temporary OS the way we do paper wallets, no? I'm not going to use this until it's released, except in testnet. :) So don't worry :D
 

t0dd

Active Member
Mar 21, 2016
150
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
I dont know what is default, but 32 works nice.
@UdjinM6 can you comment on this?
Mine have been set at 8 for over a year. I get paid, but... is my Masternode properly servicing the network? Yeah, if it needs to be set to something else, I would love @UdjinM6 or someone to comment. Especially since I write documentation that others follow.
 
Status
Not open for further replies.