✅|ANN| 🌍DESIRE |NeoScrypt| |🔨MasterNodes🔨| - COIN OF YOUR DREAMS!

[TonyYoun]

I don't know why Sentinel isn't working.
When I run

sudo SENTINEL_DEBUG=1 ./venv/bin/python bin/sentinel.py

I get this message:
Cannot connect to desired. Please ensure desired is running and the JSONRPC port is open to Sentinel.

So, I changed my desired.conf to:

rpcuser=<user>
rpcpassword=<password>
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
staking=0
logtimestamps=1
txindex=1
maxconnections=256

port=9998
externalip=IP:9919
masternode=1
masternodeprivkey=<PrivateKey>

Now, when I run

sudo SENTINEL_DEBUG=1 ./venv/bin/python bin/sentinel.py

I get

Code:

Traceback (most recent call last):
  File "bin/sentinel.py", line 265, in <module>
    main()
  File "bin/sentinel.py", line 164, in main
    if not is_desired_port_open(desired):
  File "bin/sentinel.py", line 151, in is_desired_port_open
    info = desired.rpc_command('getgovernanceinfo')
  File "lib/desired.py", line 42, in rpc_command
    return self.rpc_connection.__getattr__(params[0])(*params[1:])
  File "/home/ubuntu/sentinel/venv/local/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 139, in __call__
    response = self._get_response()
  File "/home/ubuntu/sentinel/venv/local/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 179, in _get_response
    http_response = self.__conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1089, in getresponse
    response.begin()
  File "/usr/lib/python2.7/httplib.py", line 444, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.7/httplib.py", line 408, in _read_status
    raise BadStatusLine(line)
httplib.BadStatusLine: ''

Any ideas what to do??

I think its supposed to be rpcport=9998, not port.

I tried rpcport=9998 and now I get

Code:

-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to desired. Please ensure desired is running and the JSONRPC port is open to Sentinel.

Please help me!

[1714831630]

1714831630

[thethunderbird]

 I checked out the chat of http://mnrank.com/

 and they disabled the coin till fixing the network of desire.

 so I think we shall wait till maintenance completed.

[mining_drone_143]

I tried rpcport=9998 and now I get

Code:

-342: non-JSON HTTP response with '401 Unauthorized' from server
Cannot connect to desired. Please ensure desired is running and the JSONRPC port is open to Sentinel.

Please help me!

So its replying with Unauthorized, probably because there is a mismatch with the settings when it started and the ones you have now, look at this post and do step 1.
https://bitcointalk.org/index.php?topic=2272607.msg24525799#msg24525799

(always do backups!)

[Blasphemer]

WATCHDOG_EXPIRED status

[captainbluff]

Why am I supposed to do any of that dancing. Other coins's MN that I have run for weeks without problems. With this one I already lost payments for several days after a wallet update. Looks like it's another time for me. Still, after all the dances, I see WATCHDOG_EXPIRED  message.

Then I don't know :-(

Thats the price of being early I guess. Also don't blame me, I'm not part of the dev team, just a humble mining drone ;-)

Same issue here, running MNs on windows, all of them are showing WATCHDOG_EXPIRED. I've deleted entire DesireCore folder ( backed up configs and wallet.dat )

However issuing masternode status, says masternode has started. Am I still wrecked?

[MNRank]

I checked out the chat of http://mnrank.com/

 and they disabled the coin till fixing the network of desire.

 so I think we shall wait till maintenance completed.

Desire re-enabled, after network stuck there is just few active node, so ROI is high. Thanks for assist.

[Chisinau]

After entire day , did everything completely from scratch and still damn WATCHDOG_EXPIRED status  

Was working so good and trouble free before that wallet update and now cant get my masternodes working even after doing all from scratch . What WATCHDOG_EXPIRED status wants i dont know    Some people are talking about some Sentinel that needs to be installed but can not find one for Windows , is there one for Windows or is it just something for Linux ?  

Judging by masternodelist nearly everyone having same problem , only few masternodes showing as "enabled" and like 90% WATCHDOG_EXPIRED status  

[hatuey]

My node is among the few survivors.

I didn't do any updates anywhere and maybe that's why I am still going strong? --- Regardless.... don't try to fix what ain't broken. See you guys later when all the dust settles....


Note to devs: Please run a test net with updates prior to pushing anything on the main net. This coin will sink faster than you can blink if all you do is fork off some X coin and leave it to the wind when it comes to upgrades.

[tek-g]

Same issue here... WATCHDOG_EXPIRED. Lovely.... nothing like having a worthless masternode

[GhostMinerBox]

My node is among the few survivors.

I didn't do any updates anywhere and maybe that's why I am still going strong? --- Regardless.... don't try to fix what ain't broken. See you guys later when all the dust settles....


Note to devs: Please run a test net with updates prior to pushing anything on the main net. This coin will sink faster than you can blink if all you do is fork off some X coin and leave it to the wind when it comes to upgrades.

Do you receive rewards or just your masternode shows up as Enabled without any rewards?

[DCP]

Something weird happening on Coinsmarkets, when I click on DSR it goes to Litecoin, is that because they temporarily disabled it?

[GhostMinerBox]

Something weird happening on Coinsmarkets, when I click on DSR it goes to Litecoin, is that because they temporarily disabled it?

Did you contact them to find out?

[kadrcalmness]

Something weird happening on Coinsmarkets, when I click on DSR it goes to Litecoin, is that because they temporarily disabled it?

News on Coinsmarkets  :
"Desire (DSR) wallet update
Time : 2017-11-13
We are working on desire wallet update , trading will be disabled until we finish"

[lazy_boozer]

Updating to 12.2 - Users

Upgrading and downgrading
How to Upgrade

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or dashd/dash-qt (on Linux).

For a detailed guide of the download, verification and installation process, see How to install Desire Core.

Downgrade warning

Downgrade to a version < 0.12.2

Because release 0.12.2 includes DIP0001 (2 MB block size hardfork) plus a transaction fee reduction and a fix for masternode rank calculation algo (which activation also depends on DIP0001) this release will not be backwards compatible after DIP0001 lock in/activation happens.

This does not affect wallet forward or backward compatibility.


======================================================================================================================================================

Updating to 12.2 - Masternodes

Periodically, the Desire Core development team will release updates to Desire. Since normal nodes rely on them for services and copies of the blockchain, masternodes are expected to update to new versions of Desire and Sentinel promptly. In some cases, hardware upgrades (more CPU, RAM or disk space, or even custom GPU hardware) may also be necessary. Not updating will eventually result in your masternode being removed from the payment queue. If you run a hosted masternode, your host will take care of updates for you. If not, the method of updating depends on how you installed Desire.
Minor version updates to Desire usually do not result in changes to the protocol version, while major version updates (e.g. from 0.12.1.5 to 0.12.2.0) will usually increase the network protocol version. If the protocol version did not change, you DO NOT need to restart your masternode if you complete the update within 60 minutes. If the protocol version did change, you must issue a start command from your wallet. Do not send start commands to your masternode if not necessary, as it may send you to the back of the payment queue.

Manual update

To update Desire manually, log in to your server using ssh or PuTTY. First we need to stop Desire running:

Code:

~/.desirecore/desire-cli stop

To manually download and install the components of your Desire masternode, visit https://github.com/lazyboozer/Desire/releases/tag/Desire-v.0.12.2.1 on your computer to find the link to the latest Desire Core wallet. Click Linux, then right-click on Download TGZ for Desire Core Linux and select Copy link address. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Desire Core (0.12.2.1 in the example) by right clicking or pressing Ctrl V.

Code:

cd ~
wget https://github.com/lazyboozer/Desire/releases/download/Desire-v.0.12.2.1/desire-0.12.2.1-linux.tar.gz

Remove the old binaries from the working directory, extract the compressed archive, copy the new files to the directory and set them as executable:

Code:

rm ~/.desirecore/desired
rm ~/.desirecore/desire-cli
tar xfvz desirecore-0.12.2.1-linux.tar.gz
cp desirecore-0.12.2/bin/desired ~/.desirecore/
cp desirecore-0.12.2/bin/desire-cli ~/.desirecore/
Clean up unneeded files:
rm desirecore-0.12.2.1-linux64.tar.gz
rm -r desirecore-0.12.2/

Restart Desire:

Code:

~/.desirecore/desired

You will see a message reading "Desire Core server starting". We will now update Sentinel.

Code:

cd ~/.desirecore/sentinel/
git pull

If the protocol version changed during this update, you will need to issue a start command from your wallet. If you are using a hardware wallet, you can issue the start command by simply clicking the button in DMT. If you are using Desire Core wallet, update it to the latest version, then open the debug console and enter this command, where MN1 is the alias for your masternode:

Code:

masternode start-alias MN1

Monitor the status of your masternode as it starts up:

Code:

~/.desirecore/desire-cli getinfo
~/.desirecore/desire-cli mnsync status
~/.desirecore/desire-cli masternode debug

In particular, the last command should return the status "Masternode successfully started". If you see an error similar to "Invalid protocol version", then the protocol version has changed and you must send a start command from your wallet again. You can also monitor the status of your masternode from Sentinel. If Sentinel detects a functioning masternode, the following command should return nothing:

Code:

cd ~/.desirecore/sentinel
venv/bin/python bin/sentinel.py

Finally, you can check for your masternode by its collateral address using DesireNinja, or search the consensus list of masternodes using this command and entering your masternode IP address:

Code:

~/.desirecore/desire-cli masternode list full | grep <your ip address>

[mrsa]

many thanks bounty received



onward and upward DSR !!

[CHAOSiTEC]

@Desire Dev Team - please see the merge request on github

[lazy_boozer]

We are looking forward to adding Desire to Mercatox.com

Listing will be made within 5 - 14 days.

[Chisinau]

lazy_boozer any suggestion how to fix "watchdog expired" on windows masternodes ? Downgrade to 12.2 from 12.2.1 ? How to downgrade in Windows ?

[Adriano2010]

We are looking forward to adding Desire to Mercatox.com

Listing will be made within 5 - 14 days.

This is good news. Hope to get more on volume on this exchange than on coinsmarkets. Also hope to works ok new wallet.

[hatuey]

Code:

root@MIAMNZEN1:~/Desire/src/sentinel# ./venv/bin/py.test ./test
============================= test session starts ==============================
platform linux2 -- Python 2.7.12, pytest-3.0.1, py-1.4.31, pluggy-0.3.1
rootdir: /root/Desire/src/sentinel, inifile:
collected 23 items

test/integration/test_jsonrpc.py F
test/unit/test_desire_config.py .
test/unit/test_desired_data_shims.py ..
test/unit/test_desirey_things.py ......
test/unit/test_misc.py .
test/unit/test_models.py ..
test/unit/test_submit_command.py .
test/unit/models/test_proposals.py ....
test/unit/models/test_superblocks.py .....

=================================== FAILURES ===================================
_________________________________ test_desired _________________________________

    def test_desired():
        config_text = DesireConfig.slurp_config_file(config.desire_conf)
        network = 'mainnet'
        is_testnet = False
        genesis_hash = u'00000ffd590b1485b3caadc19b22e6379c733355108f107a430458c                                                                                                                                                                                                                                             df3407ab6'
        for line in config_text.split("\n"):
            if line.startswith('testnet=1'):
                network = 'testnet'
                is_testnet = True
                genesis_hash = u'00000bafbc94add76cb75e2ec92894837288a481e5c005f                                                                                                                                                                                                                                             6563d91623bf8bc2c'

        creds = DesireConfig.get_rpc_creds(config_text, network)
        desired = DesireDaemon(**creds)
        assert desired.rpc_command is not None

        assert hasattr(desired, 'rpc_connection')

        # Desire testnet block 0 hash == 00000bafbc94add76cb75e2ec92894837288a48                                                                                                                                                                                                                                             1e5c005f6563d91623bf8bc2c
        # test commands without arguments
        info = desired.rpc_command('getinfo')
        info_keys = [
            'blocks',
            'connections',
            'difficulty',
            'errors',
            'protocolversion',
            'proxy',
            'testnet',
            'timeoffset',
            'version',
        ]
        for key in info_keys:
            assert key in info
        assert info['testnet'] is is_testnet

        # test commands with args
>       assert desired.rpc_command('getblockhash', 0) == genesis_hash
E       assert '00000f79a81b...93c42978c2027' == '00000ffd590b1...458cdf3407ab6'
E         - 00000f79a81b6318e0f36dc486adf4bb5bb1fa34025d69b991893c42978c2027
E         + 00000ffd590b1485b3caadc19b22e6379c733355108f107a430458cdf3407ab6

test/integration/test_jsonrpc.py:51: AssertionError
===================== 1 failed, 22 passed in 0.84 seconds ======================                                                                                                                         

I get 1 failed, 22 passed when testing sentinel. Should I start from scratch here is there anything that could be done to fix this one error?