Quote from: mninfo on November 15, 2017, 01:10:01 AM

Quote from: GhostMinerBox on November 15, 2017, 12:50:26 AM

Quote from: mninfo on November 15, 2017, 12:38:15 AM

Quote from: GhostMinerBox on November 15, 2017, 12:30:36 AM

No errors this time. MN status still shows WATCHDOG_EXPIRED though in the controlling wallet. Maybe I should wait a little. While I am waiting... What should I do if I have a masternode for another coin, i.e. VIVO on the same VPS that is having the same issue. How would I start the Sentinel for that coin too? Noone is replying in VIVO topic about this.

That's some progress Cheesy

It's weird though that it doesn't show PRE_ENABLED :/ Have you ran through all the "masternode start" process? If so, let's wait for a few minutes and check if it changes (I might be sleeping by that time, if so I'll check in 7-9h)

For VIVO, copy sentinel-win64.exe to another place and create a new sentinel.conf in that new place, this time make "desire_conf" point to the VIVO config file (still, name it desire_conf=xxx, as that is what it's expecting).
Once this is done, modify vivo.conf (or whatever it is called) to also contain all that data, but make sure to change "rpcport" to something else, whatever as long as it is greater than 1024, I'll use 9928 here

rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9928
rpcconnect=127.0.0.1

someuser and somepass need not be the same as before, you can/want to change them

After I restarted my controlling wallet it showed PRE_ENABLED for a minute and then went back to WATCHDOG_EXPIRED. It is definitely some progress but we are not there yet. ((

I was reading through the dash code and it seems like before there was some governance message for the vote order of masternodes for it to update the watchdog. Now thas has changed to sentinel.
What block are you at right now?? Just to make sure it is not stuck (and thus not receving updates)

Could you upload a copy of your "debug.log" (inside desirecore) to somewhere? I believe it doesn't contain sensitive information, but if you want to be sure, simply check for lines with "CMasternode::Check" or "MNPING -- Masternode" or "CActiveMasternode::SendMasternodePing" and upload those.

I am at block 16725
OK, we got something!!!! I have several MNs and was applying your changed to all of them and one of them just changed ENABLED. For that particular MN I deleted all files in data dir exept for wallet and .conf files and started from scratch. Let me do the same for another MN and see if it is exactly the thing that fixed it.