Any chance of this being updated for 12.1? Can't find anything about doing a fresh install of it.
It means your node have not yet seen proper "watchdog" message (which is triggered by Sentinel) from the masternode in WATCHDOG_EXPIRED state. While in migrations period it's ok to see this for all 12.0 masternodes (they don't have one) and for some 12.1 masternodes (due to connectivity issues - 12.1 masternode could be surrounded by 12.0 nodes only which do not recognize this message and do not relay it).Can anybody please let me know what the status "WATCHDOG_EXPIRED" means?
Thank you,
What's the output of "dash-cli masternode status", same for both? Check for special characters in the RPC settings in dash.conf (RPC user and pass), that's caused trouble for some. looks like then need alphanumeric only.I have the same problem. Running 2 MN on 1 Server with 2 different IP's on VULTR (15GB SSD, 1 CPU 768MB Memory 1000GB Bandwidth).
On my local PC it showed ENABLED first but after a while is the status WATCHDOG_EXPIRED.
Also on dashninja.pl it was 100% active but now it shows the status Inactive(0%).
But if I look on Server, both 2 dasd demons are running.
ps ax| grep dashd
22216 ? SLsl 0:51 ./dashd
22271 ? SLsl 0:57 ./dashd
Also staus shows
./dash-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
So should I not care about it in migration period? Or is something wrong with it please?
Masternodes in WATCHDOG_EXPIRED should be paid during migration period too. The issue most likely is caused by lack of connectivity (e.g. 12.1 mn is surrounded by 12.0 nodes only, which can't relay new messages).I have the same problem. Running 2 MN on 1 Server with 2 different IP's on VULTR (15GB SSD, 1 CPU 768MB Memory 1000GB Bandwidth).
On my local PC it showed ENABLED first but after a while is the status WATCHDOG_EXPIRED.
Also on dashninja.pl it was 100% active but now it shows the status Inactive(0%).
But if I look on Server, both 2 dash demons are running.
ps ax| grep dashd
22216 ? SLsl 0:51 ./dashd
22271 ? SLsl 0:57 ./dashd
Also staus shows
./dash-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
So should I not care about it in migration period? Or is something wrong with it please?
dash-cli masternode statusWhat's the output of "dash-cli masternode status", same for both? Check for special characters in the RPC settings in dash.conf (RPC user and pass), that's caused trouble for some. looks like then need alphanumeric only.
Thanks for InfoMasternodes in WATCHDOG_EXPIRED should be paid during migration period too. The issue most likely is caused by lack of connectivity (e.g. 12.1 mn is surrounded by 12.0 nodes only, which can't relay new messages).
"dash-cli getpeerinfo" to get full info or "dash-cli getpeerinfo | grep version" to get only list of their protocolsThanks for Info
When I look peers on my local PC there are more 12.1 MN's surrounded then 12.0 MN's.
How can I display peers in console on the Server please?
Thank you very much.It means your node have not yet seen proper "watchdog" message (which is triggered by Sentinel) from the masternode in WATCHDOG_EXPIRED state. While in migrations period it's ok to see this for all 12.0 masternodes (they don't have one) and for some 12.1 masternodes (due to connectivity issues - 12.1 masternode could be surrounded by 12.0 nodes only which do not recognize this message and do not relay it).
It can still be isolated in other parts of the network, there are a lot of islands with one version or the other. It's perfectly normal, you don't realise it as a user but it's kind of scary from an admin perspectiveIt seams to be 12.1 majority... similar by both MN's
dash-cli getpeerinfo | grep subver
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.0.58/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.0.58/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
"subver": "/Dash Core:0.12.1/",
The Problem was that this command did not run from crontab (advised to run every 5 min., I set it up every one minit):On my local PC it showed ENABLED first but after a while is the status WATCHDOG_EXPIRED.
You've changed YOURUSERNAME to the name of your home folder? It shouldn't be run as root and if it has you may need to change permissions on some files before it can be run as a normal user.The Problem was that this command did not run from crontab (advised to run every 5 min., I set it up every one minit):
cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log
Of course I changed YOURUSERNAMeYou've changed YOURUSERNAME to the name of your home folder? It shouldn't be run as root and if it has you may need to change permissions on some files before it can be run as a normal user.
Ah ok, you've got it fixed, Sorry, I thought you where still having problems with itOf course I changed YOURUSERNAMe
I run it as MNuser (not root) and it wors fine.
but I receive:venv/bin/python bin/sentinel.py
should return nothing but silence. This is how you know it's working.
it wont let me copy the full listTraceback (most recent call last):
File "bin/sentinel.py", line 209, in <module>
main()
File "bin/sentinel.py", line 144, in main
if not is_dashd_port_open(dashd):
Traceback (most recent call last):
File "bin/sentinel.py", line 206, in <module>
Transient.set(mutex_key, misc.now(), timeout_seconds)
File "lib/models.py", line 662, in set
setting, created = Setting.get_or_create(name=setting_name, defaults=setting_dikt)
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 4807, in get_or_create
return cls.create(**params), True
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 4776, in create
inst.save(force_insert=True)
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/playhouse/signals.py", line 69, in save
ret = super(Model, self).save(*args, **kwargs)
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 4982, in save
pk_from_cursor = self.insert(**field_dict).execute()
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 3435, in execute
cursor = self._execute()
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 2826, in _execute
return self.database.execute_sql(sql, params, self.require_commit)
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 3683, in execute_sql
self.commit()
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 3507, in __exit__
reraise(new_type, new_type(*exc_args), traceback)
File "/home/mrmime/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 3676, in execute_sql
cursor.execute(sql, params or ())
peewee.OperationalError: attempt to write a readonly database
Does dashd have an option similar to the banhammer that qt has? I monitor the peers list and give any 12.0 node a 1 week banhammer in qt...Masternodes in WATCHDOG_EXPIRED should be paid during migration period too. The issue most likely is caused by lack of connectivity (e.g. 12.1 mn is surrounded by 12.0 nodes only, which can't relay new messages).
Does dashd have an option similar to the banhammer that qt has? I monitor the peers list and give any 12.0 node a 1 week banhammer in qt...
help setban
setban "ip(/netmask)" "add|remove" (bantime) (absolute)
Attempts add or remove a IP/Subnet from the banned list.
Arguments:
1. "ip(/netmask)" (string, required) The IP/Subnet (see getpeerinfo for nodes ip) with a optional netmask (default is /32 = single ip)
2. "command" (string, required) 'add' to add a IP/Subnet to the list, 'remove' to remove a IP/Subnet from the list
3. "bantime" (numeric, optional) time in seconds how long (or until when if [absolute] is set) the ip is banned (0 or empty means using the default time of 24h which can also be overwritten by the -bantime startup argument)
4. "absolute" (boolean, optional) If set, the bantime must be a absolute timestamp in seconds since epoch (Jan 1 1970 GMT)
Examples:
> dash-cli setban "192.168.0.6" "add" 86400
> dash-cli setban "192.168.0.0/24" "add"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setban", "params": ["192.168.0.6", "add" 86400] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/