dashman - linux masternode mangement made mootastic

[moocowmoo]

fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.

that indicates the pull didn't complete for some reason (new one to me), so you're running the same code.
notice how the line numbers didn't shift.

Also, this one is concerning:

gathering info, please wait...which: no dash-cli in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/xxxxx/bin)

It shouldn't even be continuing. odd.

The JSON error is due to dashwhale sometimes not having the file in place for a few seconds (during their update) (another bug I need to squash)


In the meantime, try it by hand:

cd dashman
git fetch
git checkout master
git reset --hard origin/master
./dashman status

 

[Jeztah]

that indicates the pull didn't complete for some reason (new one to me), so you're running the same code.
notice how the line numbers didn't shift.

Also, this one is concerning:



It shouldn't even be continuing. odd.

The JSON error is due to dashwhale sometimes not having the file in place for a few seconds (during their update) (another bug I need to squash)


In the meantime, try it by hand:

cd dashman
git fetch
git checkout master
git reset --hard origin/master
./dashman status

Thanks.

I did as you said but the status is the same.

git fetch
From https://github.com/moocowmoo/dashman
* [new branch] dev -> origin/dev
* [new branch] master -> origin/master
[[email protected] dashman]# git checkout master
Already on 'master'
[[email protected] dashman]# git reset --hard origin/master
HEAD is now at 52f7369 bugfix - detect netcat -4,-6 switch support before embarking, prompt to install appropriate package

./dashman status
Connection to 8.8.8.8 53 port [tcp/domain] succeeded!
dashman version 0.1.11
gathering info, please wait...which: no dash-cli in (/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/xxxxxxxx/bin)
No JSON object could be decoded
/xxxxx/dashman/lib/dashman_functions.sh: line 702: [: too many arguments
DONE!

host uptime/load average : 413 days, 0.23 0.12 0.10
dashd bind ip address : xxxxxxxxxxxxxxxxxxxx
dashd version : 0.12.0.55
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 01 hours, 21 mins, 33 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : /xxxxx/dashman/lib/dashman_functions.sh: line 787: [: too many arguments
NO
dashd connection count : 8
dashd blocks synced : YES
last block (local dashd) : 355624
(chainz) : 355624
(darkcoin.qa) : 355624
(dashwhale) : /xxxxx/dashman/lib/dashman_functions.sh: line 793: [: -gt: unary operator expected

(masternode.me) : 355624 - no forks detected
masternode count : 3315
Exiting.

Thanks!!

 

[moocowmoo]

I'm spinning up a centos6.2 vagrant instance now. I'll let you know what I find.

 

[moocowmoo]

I've pushed a patch that will get rid of most of the stderr noise your older distro was creating. as well as fixes to work with git 1.7.

I wasn't able to reproduce the netcat error that is causing the failed local-port-open test.

Try this version and see if the problem remains:

cd dashman
git fetch
git remote update
git checkout master
git reset --hard origin/master
./dashman status

 

[Jeztah]

I've pushed a patch that will get rid of most of the stderr noise your older distro was creating. as well as fixes to work with git 1.7.

I wasn't able to reproduce the netcat error that is causing the failed local-port-open test.

Try this version and see if the problem remains:

cd dashman
git fetch
git remote update
git checkout master
git reset --hard origin/master
./dashman status

Thank you for helping with my second mn setup! My other one is on an old Windows server.
It looks perfect except for that dashwhale stuff. Thanks so very much. I'll send you my last mn payment tonight as a small token of thanks.

host uptime/load average : 413 days, 0.16 0.09 0.06
dashd bind ip address : xxxxxxxxxxxxxx
dashd version : 0.12.0.55
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 03 hours, 34 mins, 44 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 9
dashd blocks synced : YES
last block (local dashd) : 355677
(chainz) : 355677
(darkcoin.qa) : 355677
(dashwhale) : /xxxxxxxx/dashman/lib/dashman_functions.sh: line 793: [: -gt: unary operator expected

(masternode.me) : 355677 - no forks detected
masternode count : 3316
Exiting.

 

[moocowmoo]

It looks perfect except for that dashwhale stuff.

Is that failure consistent or intermittent?

Thanks so very much. I'll send you my last mn payment tonight as a small token of thanks.

You're welcome! Glad I could help!
And, much appreciated!

 

[Jeztah]

Is that failure consistent or intermittent?
That error was there since initial install. Consistent.

 

[moocowmoo]

see if this command returns anything (this is what dashman is trying to pull)

time curl -s https://www.dashwhale.org/api/v1/public

and note if it takes longer than 7 seconds (dashmans timeout)

 

[moocowmoo]

dashman version 0.1.12 released

added payment queue display!

 

[Jeztah]

see if this command returns anything (this is what dashman is trying to pull)

time curl -s https://www.dashwhale.org/api/v1/public

and note if it takes longer than 7 seconds (dashmans timeout)

real 0m0.688s
user 0m0.035s
sys 0m0.061s

 

[moocowmoo]

real 0m0.688s
user 0m0.035s
sys 0m0.061s

did it return a json string?

I couldn't reproduce this issue running stock centos-6.2-final.
maybe something else is older than I'm expecting..

 

[Jeztah]

did it return a json string?

I couldn't reproduce this issue running stock centos-6.2-final.
maybe something else is older than I'm expecting..

@gandalf ~]# time curl -s https://www.dashwhale.org/api/v1/public

real 0m0.688s
user 0m0.035s
sys 0m0.061s
@gandalf ~]# cd /xxxx/dashman

I don't need the dashwhale stuff working..... I don't think anyway.

 

[moocowmoo]

@gandalf ~]# time curl -s https://www.dashwhale.org/api/v1/public

real 0m0.688s
user 0m0.035s
sys 0m0.061s
@gandalf ~]# cd /xxxx/dashman

I don't need the dashwhale stuff working..... I don't think anyway.

there's your problem. Try to figure out why you can't pull that url from that server.
Open it in your browser to see what's supposed to come back.

--
no, you don't need it, but you'll have to put up with error messages until you figure out whats up there.

see if running curl without the -s (silent) switch shows you an error message hinting at what's going on.

 

[Jeztah]

there's your problem. Try to figure out why you can't pull that url from that server.
Open it in your browser to see what's supposed to come back.

--
no, you don't need it, but you'll have to put up with error messages until you figure out whats up there.

see if running curl without the -s (silent) switch shows you an error message hinting at what's going on.

@gandalf ~]# time curl https://www.dashwhale.org/api/v1/public
curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

I'll look into updating the certs.

Thanks again

 

[moocowmoo]

@gandalf ~]# time curl https://www.dashwhale.org/api/v1/public
curl: (60) Peer certificate cannot be authenticated with known CA certificates

Must not have been installed during your upgrade path.
I didn't run into that on my vagrant image of centos-6.2-Final. ( vagrant image: rafacas/centos62-plain)

 

[moocowmoo]

dashman v0.1.13 released

- added polish translation! (thanks tombtc!)
- fail gracefully when dashninja api is down

This is a significant update, and now requires bash version 4 (which most people already have)

PLEASE let me know if you run into trouble and I'll push a hotfix. [email protected]

Also, if anybody wants to contribute translations, let me know or submit a pull request!

 

[Jeztah]

dashman v0.1.13 released

- added polish translation! (thanks tombtc!)
- fail gracefully when dashninja api is down

This is a significant update, and now requires bash version 4 (which most people already have)

PLEASE let me know if you run into trouble and I'll push a hotfix. [email protected]

Also, if anybody wants to contribute translations, let me know or submit a pull request!

What is the proper procedure for updating the script?

 

[moocowmoo]

What is the proper procedure for updating the script?

It's self updating. Just run any command!

 

[Bridgewater]

I'm trying to do a fresh install, but I want to use udjin's bootstrap to save download time. I noticed that dashman starts dashd immediately after installing, so before running ./dashman install, I created a .dash folder and put just the bootstrap.dat in there.

The problem is "./dashman install" doesn't work because a .dash folder already exists, and "./dashman reinstall" fails because there are no previous dashd/dash-cli files there. Do you have a way to force one of these commands? Thanks!

 

[moocowmoo]

I'm trying to do a fresh install, but I want to use udjin's bootstrap to save download time. I noticed that dashman starts dashd immediately after installing, so before running ./dashman install, I created a .dash folder and put just the bootstrap.dat in there.

The problem is "./dashman install" doesn't work because a .dash folder already exists, and "./dashman reinstall" fails because there are no previous dashd/dash-cli files there. Do you have a way to force one of these commands? Thanks!

Just delete or rename the .dash folder, do 'dashman install' then stop dashd and move the bootstrap file into the folder per instructions then do 'dashman restart'

I think dashd just processes the file if it's in place, but I've not used the bootstrap myself so I'm fuzzy on the details.

 

[Bridgewater]

Wow, thanks for the lightning-fast reply! That sounds like a fine solution. You're already spoiling me with all this automatic stuff, I totally forgot I could manually stop the daemon.

In hindsight, it looks like the bootstrap is making much less difference now than in my previous experience with it. I think it's a moot point. Thanks for helping me out though!

 

[moocowmoo]

Wow, thanks for the lightning-fast reply! That sounds like a fine solution. You're already spoiling me with all this automatic stuff, I totally forgot I could manually stop the daemon.

In hindsight, it looks like the bootstrap is making much less difference now than in my previous experience with it. I think it's a moot point. Thanks for helping me out though!

You're welcome.

Glad to hear it. Is why I built it. Now everyone can enjoy my laziness!

For masternode.me I just spin them up ahead of time and keep a pool ready for the next signup.
For other needs I copy (rsync) the blocks and chainstate directories from other (stopped) instances.
I haven't timed (or had to wait for) a sync in ages.

 

[moocowmoo]

dashvote version 0.0.3 released

• added current yes/no vote counts
• added voter turnout percentage
• added proposal passing/failing colorizing
• added previous vote detection/display
• added vim navigation binding
• added loading screen

do 'dashman sync vote' to pull in this update and cast your votes!

or, if you don't have dashman yet: (what have you been waiting for?!)

sudo apt-get install git curl netcat6
git clone https://github.com/moocowmoo/dashman.git
dashman/dashman vote

 

[MangledBlue]

I really like those numbers -

uh - lol - can you make them into columns?? :-D



edit: BASF it

 

[MangledBlue]

Just found v14
tried the VOTE - looks GREAT!!!

YEAH!!!! \o/

 

[moocowmoo]

Dashman 0.1.14/Dashvote 0.0.5 released

https://github.com/moocowmoo/dashman/

• added git checkout info to version header
• added few more lines in polish
• bugfix - ip-lookup failover to http if https fails (older distro cert issue)
• bugfix - support symlink invocation
• dashvote - added git checkout info to version header
• dashvote - added loading screen, previous vote detection, vim navigation binding
• dashvote - added vote-counts, turnout percentage
• dashvote - bugfix - use alias for vote display - added threshold coloring, sort vote display by block start
• dashvote - align count/percentage columns
• dashvote - display vote hash during voting
• dashvote - ignore unmapped keystrokes

to install:

git clone https://github.com/moocowmoo/dashman.git
#then run
dashman/dashman
#for help

dashman vote

dashman status

contact me here, by email, or github if you have any problems/suggestions: [email protected]

 

[MangledBlue]

Looking good....

Just noticed that there is a rolling internet outage in my area - so far not affected here but I'm only about 24 hours away from MN payout.
See if your "setup" over-comes any "drop-outs"...... nail biting lol - so far so good :-D


edit for spelling

 

[MangledBlue]

Running very stable now for the past 12 days - looking good

 

[Bridgewater]

Every node that I setup from scratch with dashman a few weeks ago is suddenly gone from the MN network today, I had to issue a start-missing. :sad:

Could this have anything to do with dashman being recently updated? When I logged into the VPS dashd was running fine, but dash-cli masternode status showed the "not activated hot node" message, and when I tried dashman status it asked me to update dashman (which i did by pressing "y"), and showed

asternode started         : NO
  masternode visible (local) : NO
  masternode visible (ninja) : NO
  masternode address         :
  masternode funding txn     : -
  masternode queue/count     : 0/0
  masternode last payment    : never
  masternode balance         : 0

I know it must be user error on my part somehow, but I'm just trying to troubleshoot to make sure this does not happen again (missed payments suck). I used dashman fully to setup these nodes, and the only thing i changed was the dash.conf later on to add in my masternodeprivkey and lock the dash.conf to read-only and then dashman restart. None of my other nodes which were setup without dashman on the same VPS provider and same location went down.

Any ideas would be helpful. TIA

 

[moocowmoo]

Every node that I setup from scratch with dashman a few weeks ago is suddenly gone from the MN network today, I had to issue a start-missing. :sad:

Could this have anything to do with dashman being recently updated?

Sorry to hear that.

No. The recent updates were mostly in the voting code.

I know it must be user error on my part somehow, but I'm just trying to troubleshoot to make sure this does not happen again (missed payments suck). I used dashman fully to setup these nodes, and the only thing i changed was the dash.conf later on to add in my masternodeprivkey and lock the dash.conf to read-only and then dashman restart. None of my other nodes which were setup without dashman on the same VPS provider and same location went down.

Any ideas would be helpful. TIA

If your nodes were online long enough to receive payments, you did everything right.

I can't think of anything helpful.
Dashman doesn't do anything fancy or non-standard when installing or upgrading.
It's a simple download, unpack, start.
And the conf files it builds run all my nodes with no issues for over a year now.

Sounds like your provider did something. Did you check the host uptimes?