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

Couldn't connect to server when restarting dashman

lombardo2

New member
Hello all,

Sorry for this noob mistake.

I had a masternode running for a few days and I withdrew the collateral without stopping the masternode. Now I sent the collateral to a different address and changed the conf file to include the new masternode private key. I also changed the rpcuser and password. However when I try to restart dashman I get:

--> Stopping dashd. Please wait...DONE!
--> Deleting cache files, debug.log... DONE!
--> Starting dashd... DONE!
--> Waiting for dashd to respond...DONE!
--> dash-cli getinfo
error: couldn't connect to server

Exiting.​

It the same IP and server as before. I updated to the latest version too. What am I doing wrong?
 
That's weird. Try the following:

Can you see dashd running in your list of processes: ps aux | grep dashd
If not, what result do you see when you start it manually: .dashcore/dashd
Can you connect if you issue the commands manually: .dashcore/dash-cli getinfo
How did you update - manually or with dashman? Try getting dashman to reinstall everything: dashman/dashman reinstall

Post back here with your results...
 
Sorry for the late reply. Work has been taking up too much time. Since I have enough funds for a masternode, maybe I should cut down on work and spend more time helping Dash. I have already tried some of the things you mentioned, but will try again.

The result of the commands:

ps aux | grep dashd

root 10670 0.0 0.0 14516 992 pts/0 S+ 22:07 0:00 grep --color=au to dashd
root 23092 1.9 21.4 1120060 438984 ? SLsl Nov17 512:02 /root/.dashcore


.dashcore/dashd

Error: Cannot obtain a lock on data directory /root/.dashcore. Dash Core is probably already running.

.dashcore/dash-cli getinfo


{
"version": 120201,
"protocolversion": 70208,
"walletversion": 61000,
"balance": 0.00000000,
"privatesend_balance": 0.00000000,
"blocks": 767900,
"timeoffset": 0,
"connections": 8,
"proxy": "",
"difficulty": 37838661.95859334,
"testnet": false,
"keypoololdest": 1507663119,
"keypoolsize": 1001,
"paytxfee": 0.00000000,
"relayfee": 0.00010000,
"errors": ""
}

dashman/dashman reinstall

dashman version 0.1.25 (37-g38fb02f) - Mon Dec 4 22:13:48 UTC 2017
gathering info, please wait... DONE!

*** dash version 0.12.2.1 is up-to-date. ***

reinstall to /root/.dashcore? [y/N] y
--> Downloading https://www.dash.org/binaries/dashcore-0.12.2.1-linux64.tar.gz... DONE!
--> Checksumming dashcore-0.12.2.1-linux64.tar.gz... DONE!
--> Unpacking dashcore-0.12.2.1-linux64.tar.gz... DONE!
--> Stopping dashd. Please wait...DONE!
--> Removing old version... DONE!
--> Launching dashd... DONE!
--> Waiting for dashd to respond...DONE!
--> updating sentinel... DONE!
--> updating crontab... DONE!

dash successfully upgraded to version 0.12.2.1

Installed in /root/.dashcore

lrwxrwxrwx 1 root root 17 Dec 4 22:14 dash-cli -> dash-cli-0.12.2.1
-rwxr-xr-x 1 root root 2801592 Jan 1 2017 dash-cli-0.12.2.1
-rw-r--r-- 1 root root 27639563 Nov 11 09:17 dashcore-0.12.2.1-linux64.tar.gz
-rw-r--r-- 1 root root 1303 Nov 11 09:18 dashcore-0.12.2.1-linux64.tar.gz.DIGESTS.txt
lrwxrwxrwx 1 root root 14 Dec 4 22:14 dashd -> dashd-0.12.2.1
-rwxr-xr-x 1 root root 10966288 Jan 1 2017 dashd-0.12.2.1
lrwxrwxrwx 1 root root 16 Dec 4 22:14 dash-qt -> dash-qt-0.12.2.1
-rwxr-xr-x 1 root root 35404800 Jan 1 2017 dash-qt-0.12.2.1

Exiting.

Even after the reinstall, it does not start.
 
That looks good to me. What does dashman/dashman status get you? Have you sent a start command from your wallet?
 
Thanks again for the answer :)

I get:

hostname : removed
host uptime/load average : removed
dashd bind ip address : removed
dashd version : 0.12.2.1
dashd up-to-date : YES
dashd running : YES
dashd uptime : removed
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 8
dashd blocks synced : NO
last block (local dashd) : 767900
(chainz) : 782306
(dash.org) : 782306
(dashwhale) : 782305
(masternode.me) : 782305 - no forks detected
dashd current difficulty : 37838661.95859334
masternode started : NO
masternode visible (local) : NO
masternode visible (ninja) : YES
masternode address : removed
masternode funding txn : removed
masternode queue/count : 0/0
masternode mnsync state : MASTERNODE_SYNC_INITIAL
masternode network state :
masternode last payment : never
masternode balance : 1000.000000000
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : NO - sync incomplete
Exiting.

I just started it using a Trezor and I get: WATCHDOG_EXPIRED

From what I remember, that was what it was last time. The block count hasn't changed since my first post.
 
Your masternode has not finished synchronising yet. Wait until the mnsync state reads "MASTERNODE_SYNC_FINISHED" and then issue your start command again.
 
The problem is that the block count never increases. It's always at 767900. The first time I set up the masternode, I remember the sync being quite quick. But now it has been stuck at that block for weeks.
 
Try
Code:
dash-cli reconsiderblock 000000000000004174c0517d02532e514ad9944f9b6ecfb7b038bcabeed3d714
or
Code:
dash-cli reconsiderblock 000000000000002a3c26c452c9b7f84d8d1eba19c2e0d5bbd8d57f663e489794
 
Back
Top