Restarting your MN whiteout access to Trezor

R

reddy

New member
Hi,

my MN stopped running because of the missing update. Now I updated everything with Dashman to 0.12.3.2, but it looks like I have to start the MN with DMT. The problem is I´m traveling and have no access to my Trezor with the collateral on it. Is there another change to make the MN run again?

Another question: Can I get a notification when a update is needed without checking the status of my MN manually all the time?

Thanks for your help!
 
reddy said:
Hi,

my MN stopped running because of the missing update. Now I updated everything with Dashman to 0.12.3.2, but it looks like I have to start the MN with DMT. The problem is I´m traveling and have no access to my Trezor with the collateral on it. Is there another change to make the MN run again?

Another question: Can I get a notification when a update is needed without checking the status of my MN manually all the time?

Thanks for your help!
Click to expand...

yep u need the trezor and DMT for start command

there is a mailing list reg MN updates
sign up for it on dash.org
 
Thanks for your answer, tungfa!

In the meantime I arrived back home and started the MN with DMT. After several hours DMT says "NEW_START_REQUIRED". I already restarted Dashman and started the MN with DMT again. Maybe it´s because of an old Trezor wallet version?

Here is the status:

gathering info, please wait... DONE!
hostname : dmstrnd01
host uptime/load average : 3XX days, 0.15 0.05 0.01
dashd bind ip address : XX.XXX.XXXX
dashd version : 0.12.3.3
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 08 hours, 30 mins, 21 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : NO
dashd port open : YES
dashd connection count : 0
dashd blocks synced : NO
last block (local dashd) : 940145
(chainz) : 940440
(dash.org) : 940441
(dashwhale) : 940439
(masternode.me) : 940439 - no forks detected
dashd current difficulty : 59445283.25794929
masternode started : NO
masternode visible (local) : NO
masternode visible (ninja) : YES
masternode address : XXXXX
masternode funding txn : XXXXXXXX
masternode queue/count : 0/0
masternode mnsync state : MASTERNODE_SYNC_WAITING
masternode network state :
masternode last payment : 1.68598 in 929249 on 08/XX/2018 2X:XX:21 (
masternode balance : 1008.XXXX
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : NO - sync incomplete
Exiting.
 
Ah, now the MN is running. It was just the problem with the new version what was already discussed in another thread. I just did this and it worked:
dash-cli addnode 52.14.192.211 onetry

But I still need help where I can find the mailing list :)
 
reddy said:
Ah, now the MN is running. It was just the problem with the new version what was already discussed in another thread. I just did this and it worked:
dash-cli addnode 52.14.192.211 onetry

But I still need help where I can find the mailing list :)
Click to expand...
You can always write on support.dash.org or simply go to dash chat.org and ask the community.
 
You must log in or register to reply here.
Back
Top