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

dashman - linux masternode mangement made mootastic

moocowmoo

moocowmoo

Bovine Bit-flipper
Foundation Member
martinf said:
Thanks! That worked!
Click to expand...

Glad to hear it! I just had to peek at the code to remember the dash.conf processing.

martinf said:
Also, man you are quick with updates. Noticed dashman trew an error as the Dash download page changed. Not many minutes before you fixed it. Thumbs up!
Click to expand...

It was luck tonight. I went to vote with dashman and saw the failure.
But, you can count on me fixing things quickly once I'm aware of them. I know a lot of people rely on dashman. :)

Over the next year, I'll be creating dash.org api's for dashman to rely on instead of web scraping.
 
Last edited:
Balych

Balych

New member
Code: 
dashman version 0.1.19 (15-g13a09d6) - Tue Jun 21 17:27:32 UTC 2016
gathering info, please wait... DONE!

*** a newer version of dash is available. ***

  current version:  0.12.0.57
   latest version:  0.12.0.58

download https://www.dash.org/binaries/dash-0.12.0.58-linux64.tar.gz.asc
and install to /home/imp/.dash? [y/N] y

 --> Downloading https://www.dash.org/binaries/dash-0.12.0.58-linux64.tar.gz.asc...DONE!
 --> Checksumming dash-0.12.0.58-linux64.tar.gz.asc...  SHA256 checksum FAILED! Try again later. Exiting.
 
splawik21

splawik21

Yeah, it's me....
Staff member
Dash Core Group
Foundation Member
Dash Support Group
MOO indeed I get the same error as above.
 
555007

555007

New member
Hello! completely newbie question:
trying to install dashman in accordance with
https://github.com/moocowmoo/dashman
but it fails somehow. Linux 16.04.

[email protected]:~/dashman# ./dashman install
missing dependency: curl netcat
--> sudo apt-get install curl netcat
***
Update:
sudo apt-get install curl netcat
with success
sudo apt-get update
success
But if try to install dashman then new message:
missing dependency: netcat6
--> sudo apt-get install netcat6

Trying to:
sudo apt-get install netcat6
results in fail:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package netcat6

***

Any idea why?
 
Last edited:
D

DYGYs

New member
Hi,

Since about a week ago, running the (latest?)
dashman version 0.1.19 (15-g13a09d6-dirty)
always returns "No JSON object could be decoded"

so, launching it in debug mode (btw, could a --verbose be added to just turn it on through "set -x" ?)
bash -x dashman/dashman status

it turns out that the command
timeout 7 curl -s 'httpx://dashninja.pl/api/masternodes?ips=\["x.x.x.x:9999"\]&portcheck=1&balance=1'

gets a redirection into "www." + the old link

which... isn't followed because we're not telling it to do so.

How to fix this?
a) fix the url path (which may break again on the next dashninja website update), and/or
b) explicitly tell curl to follow the redirection, by passing it "-L" (I had gone with this one - for now)

so,
nano dashman/lib/dashman_functions.sh

and on about line 27

change:
curl_cmd='timeout 7 curl -s'

into:
curl_cmd='timeout 7 curl -s -L'

Save it (Ctrl+x, Enter)

Done! It's now fixed until moocowmoo comes back from vacations and updates the dashman tool :)

Cheers

[Edit: second attempt, first got stuck on the moderation approval queue]
 
UdjinM6

UdjinM6

Official Dash Dev
Dash Core Group
DYGYs said:
Hi,

Since about a week ago, running the (latest?)
dashman version 0.1.19 (15-g13a09d6-dirty)
always returns "No JSON object could be decoded"

so, launching it in debug mode (btw, could a --verbose be added to just turn it on through "set -x" ?)
bash -x dashman/dashman status

it turns out that the command
timeout 7 curl -s 'httpx://dashninja.pl/api/masternodes?ips=\["x.x.x.x:9999"\]&portcheck=1&balance=1'

gets a redirection into "www." + the old link

which... isn't followed because we're not telling it to do so.

How to fix this?
a) fix the url path (which may break again on the next dashninja website update), and/or
b) explicitly tell curl to follow the redirection, by passing it "-L" (I had gone with this one - for now)

so,
nano dashman/lib/dashman_functions.sh

and on about line 27

change:
curl_cmd='timeout 7 curl -s'

into:
curl_cmd='timeout 7 curl -s -L'

Save it (Ctrl+x, Enter)

Done! It's now fixed until moocowmoo comes back from vacations and updates the dashman tool :)

Cheers

[Edit: second attempt, first got stuck on the moderation approval queue]
Click to expand...
Fixed 6 days ago, pull the latest version ;)
https://github.com/moocowmoo/dashman/commit/18e1a15b1bc998ea55972b37602b83eee8028bfc
 
D

DYGYs

New member
UdjinM6 said:
Fixed 6 days ago, pull the latest version ;)
Click to expand...

Thanks. Should have checked there first :)

I guess that I've just grown spoiled by the auto-update
notifications of the dashman, which didn't quite trigger (yet).

On a tangentially related (to me only, but granted... way off
topic to dashman): I've just got my first node payment skipped.

The info from 'httpx://dashninja.pl/mndetails.html?mnpubkey=XkqrtwtcK3e9Jsc4CZjnjgH5yWR3woyL94' says:
Last Paid (from dashd) - 8/10/2016, 5:10:58 PM (1 day 13 hours 48 minutes 41 seconds ago)
Last Paid (from blocks) - 8/3/2016, 11:46:19 AM (1 week 1 day 19 hours 13 minutes 20 seconds ago) on block 513838

What means "from dashd" above? Was it the expected date from the node's daemon itself?

Any clue on what can have been wrong, or it's just something
that do happens sometimes?
 
UdjinM6

UdjinM6

Official Dash Dev
Dash Core Group
DYGYs said:
Thanks. Should have checked there first :)

I guess that I've just grown spoiled by the auto-update
notifications of the dashman, which didn't quite trigger (yet).

On a tangentially related (to me only, but granted... way off
topic to dashman): I've just got my first node payment skipped.

The info from 'httpx://dashninja.pl/mndetails.html?mnpubkey=XkqrtwtcK3e9Jsc4CZjnjgH5yWR3woyL94' says:
Last Paid (from dashd) - 8/10/2016, 5:10:58 PM (1 day 13 hours 48 minutes 41 seconds ago)
Last Paid (from blocks) - 8/3/2016, 11:46:19 AM (1 week 1 day 19 hours 13 minutes 20 seconds ago) on block 513838

What means "from dashd" above? Was it the expected date from the node's daemon itself?

Any clue on what can have been wrong, or it's just something
that do happens sometimes?
Click to expand...
Yeah, this happens sometimes... The reason is that network sometimes has hard times to decide which masternode is the winner and we are not good enough to detect this yet, so we count that for every mn which received high number of votes, not only for the one which was actually paid later. I'm working on improving this logic but there are some difficulties - we need to find the balance between accuracy and speed (you don't want your mn/wallet to hick up for a few seconds scanning blocks every 2,5 minutes). Hopefully in 12.1 this will be much rare event if it would happen at all.
 
D

DYGYs

New member
UdjinM6 said:
Yeah, this happens sometimes (...). Hopefully in 12.1 this will be much rare event if it would happen at all.
Click to expand...

Thanks, I'll wait then :cool:

Regarding 12.1, public release is on queue for the next few days or still a couple of weeks?
 
UdjinM6

UdjinM6

Official Dash Dev
Dash Core Group
D

DYGYs

New member
UdjinM6 said:
PS. Friendly reminder - going offtopic for more than one post is not a good practice for your karma ;)
/
Click to expand...

Duly noted :D

Back to dashman, while it's auto-update notification didn't kick in (this time), a manual "dashman sync" did indeed the trick, running now the very latest git release :)
 
M

martinf

New member
I'm seeing some strange masternode queue positions being reported by dashman.

When a masternode has been really unlucky and not been paid in the last 1.2*number_of_masternodes the lastPaid is set to zero. See:
https://github.com/dashpay/dash/blob/master/src/masternode.cpp#L255-L260

This causes dashman to treat the node as one that hasn't been paid. And sorts it at the very end of the queue. See:
https://github.com/moocowmoo/dashman/blob/master/lib/dashman_functions.sh#L840

I think even ignoring the zeroing of lastpaid the assumption that all unpaid nodes should be at the end of the sorted list is incorrect.

I think the correct way of sorting would be to sort all nodes in one list. The list should be sorted on lastpaid, unless lastpaid is zero. If lastpaid is zero the node should be sorted on (now - activeseconds). Right?
 
exact

exact

New member
Hi!

Please tell when you plan to upgrade to version 12.1? It makes sense to wait or try to update manually?

Thank you very much in advance. :)
 
You must log in or register to reply here.
Top