Topic: ✅|ANN| 🌍DESIRE |NeoScrypt| |🔨MasterNodes🔨| - COIN OF YOUR DREAMS! - page 96. (Read 167492 times)

Cheers, thanks for the reply.

I installed everything and sentinel is running fine but my masternode status is still reporting watchdog expired. I'm gonna try to reindex and everything to rule that out as a possibility. I'll also try updating my vivo nodes with the same setup.

Appreciate the response and dedication. Happy to send some coin your way if you provide donation address.

Dude, forgive the guys who don't know what you have actually accomplished today for them. Get some rest. You deserve it! Thanks again! All my MNs are ENABLED now and after some trial and error, I am sure the rest of the community will follow your guide and enable their MNs. Main thing is done - you stepped in for the dev team and found the working solution!

im gonna try few things


but the main problem that i have is the it if i just run masternode it cannot connect to my ip


its usualy when someone  has closed port  but i do not have those  because i opened them 2 weeks ago   and was fine


manage to go in the mn list with expired watchdog  but then it went off again i did not do anything


anyway i'll post tomorrow    good night

You should apply these steps to whichever wallet the masternode is running on, either if it is hot wallet or cold wallet. If it is a hot wallet, then simply apply it to the wallet (you should have only 1). If it is a cold wallet, apply it to the wallet the MN is running on.

I am assuming the masternode wallet and sentinel are running in the same machine. Then:

* rpcport CANNOT be 9919, that's the port for the masternode, not the rpc. I really recommend you to set it to 9918.
* rpcconnect must be the IP where the masternode is running on. If it is the same machine where sentinel will run, it should be 127.0.0.1, not your IPv4


Ignoring someone is kind of harsh when I'm doing this out of self-will and expecting nothing, don't you think it is quite more possible that after being +16h without sleeping, 7h of which I have been doing this standalone sentinel, I might have overread your question? Just a wild thought, I might be wrong

You should apply these steps to whichever wallet the masternode is running on, either if it is hot wallet or cold wallet. If it is a hot wallet, then simply apply it to the wallet (you should have only 1). If it is a cold wallet, apply it to the wallet the MN is running on.

im trying 2-3 different things gonna inform you if anything happens  but Im not hopefull

I tried asking that above too but mninfo ignored me.

We need clarification on what instance types need to have sentinel running.

Ive did this  i have 1 question

the desire.conf looks like this

masternode=1
masternodeprivkey=7qt9zSJWu******G943kK825pnuGPwEDZRjN7ohUdmJUynSK5Qc
externalip=78.204.***.214

then you said

at least, the following data:
rpcuser=someuser  ->ive set the username
rpcpassword=somepass > set pass
server=1   > let it as is
rpcport=9918>  9919
rpcconnect=127.0.0.1 ->  my IPV4

still sentiel says   Invalid Masternode Status, cannot continue.'






Im not sure if your guide is for the Hot wallet version

  Can someone teach me how to mine Desire with VEGA 56?

Then make sure to follow all the steps on the guide (check them from the original post above, I have upadated it). One by one, from the start, even if you think you've already did it.

since the usefull updates

my 2 Masternodes was knock off 


Ive runned them both from Windows like it appears on the first guide without VPS

This is for masternodes only, if you are not running a masternode, there is no need to do this.
Either linux and windows, VPS or not, but masternodes.

Is this Also for Windows hot wallet? or only for VPS? 


because invalid masternode status *which I understand, because in the wallet conf I have no Mn=1  my genkey or IP"


SO what can I do

Simply copy "sentinel-win64.exe" to multiple locations, each of them with a "sentinel.conf" file. Each of those "sentinel.conf" should have a different "desire_conf=xxx", pointing to the adequate configuration file. Start each of the "sentinel-win64.exe" and you are done


You might try to see if you repo has libboost version 1.54.0, ie: sudo apt-get install libboost1.54-dev

If it isn't in your repository, I would try to build desire from 0 with the latest libboost (sudo apt-get install libboost-all-dev).


It does the same (theoretically). I added a new step (just now) though, to manually delete "mncache.dat" and "mnpayments.dat", which it seems it is needed.

2. Resync the whole wallet, from the menu "Tools" > "Wallet Repair" > "Rebuild Index" - I dod not do it this way. I deleted the data directory. Gotta test out this way to make sure it will do the same.

Hi folks. I'm having real trouble upgrading on linux. I've spent several days working on it and I can't get it to work. I finally upgraded but now when I try to run desired i get the following error:

"desired: error while loading shared libraries: libboost_filesystem.so.1.54.0: cannot open shared object file: No such file or directory"

I spent many hours trying to install the missing libboost package but nothing I do works. Any suggestions?

Thanks in advance
 

thanks for posting this. I have a couple of different setups and was curious where this applies. If I have a controller wallet and multiple MNs, where does sentinel need to run? on the controller or the MNs or both?

Desire + Sentinel standalone (windows + linux)

You only need this if you are running a masternode and getting WATCHDOG_EXPIRED

This is a version of sentinel that requires nothing but to run an exe, make you to follow all steps! Backup "wallet.dat" first, just in case

Download: https://github.com/ZonnCash/sentinel/releases/tag/v1.1.0-win64
Virustotal (3/67): https://www.virustotal.com/es/file/3a65c0df1fb89607531d8c02bb2a3070f1c39f555944d118c67d8ee616be5b18/analysis/1510697796/

Use at your own risk, it has been compiled exactly as the Github repo says

Before running it

1. Make sure you are running v0.12.2.1

2. Close your wallet

3. Go to desirecore folder and delete "mncache.dat" and "mnpayments.dat"

4. Make sure your "desire.conf" contains, at least, the following data:
rpcuser=someuser
rpcpassword=somepass
server=1
rpcport=9918
rpcconnect=127.0.0.1

Try to make rcpuser and rpcpassword hard to guess, you won't need to remember/use them for anything else, so feel free to smash the keyboard

5. Open wallet. Resync the whole wallet, from the menu "Tools" > "Wallet Repair" > "Rebuild Index"

6. Make sure the wallet is running and completely synced before continuing

How to

To make it point to your desire.conf, you have three options:

A) Create a file sentinel.conf in the same folder as the EXE with the following content:
desire_conf=C:\path\to\desire.conf

Start sentinel-win64.exe

B) From a console, execute the EXE by passing arguments
sentinel-win64.exe --config=C:\path\to\desire.conf

C) By creating a shortcut

1) Right click the sentinel-win64.exe, "Create Shortcut".
2) Right click the shortcut, Properties
3) Edit Target and, at the end, add a SPACE and then "--config=C:\path\to\desire.conf" INCLUDING the quotes "

Double click the shortcut to start sentinel.

When everything fails
If you have followed all the steps and still get WATCHDOG_EXPIRED when issuing "masternode status":

1. Close the wallet

2. Delete all files inside "desireconf" except for "wallet.dat" and "desire.conf".
Please make sure you don't delete wallet.dat! Backup it, for real, that's your coins!

3. Restart wallet, open sentinel-win64.exe, and let it sync!

Awesome!  I'm trying it now, just waiting for it to resync

Yes, please! Thank you very much!
Would you like to do the same for VIVO? I am sure the crowd there will appreciated it too because right now their ship is also sinking.

Nice!!! That's so great news! I'll repost the whole instructions on how to run sentinel and so on, with this new information