Many mns inactives dashninja.pl

Watchdog expired error message on all my masternodes, restarting my masternodes also does not help
Sentinel maybe under attack or malfunctioning ?
 
WATCHDOG_EXPIRED here as well.

Running ./venv/bin/python bin/sentinel.py comes up with errors (sometimes)

Code: 
Traceback (most recent call last):
  File "bin/sentinel.py", line 244, in <module>
    main()
  File "bin/sentinel.py", line 191, in main
    perform_dashd_object_sync(dashd)
  File "bin/sentinel.py", line 24, in perform_dashd_object_sync
    GovernanceObject.sync(dashd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_dashd(dashd, item)
  File "lib/models.py", line 142, in import_gobject_from_dashd
    subobj, created = subclass.get_or_create(object_hash=object_hash, defaults=subdikt)
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 4800, in get_or_create
    return query.get(), False
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 3090, in get
    return next(clone.execute())
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 2267, in next
    obj = self.iterate()
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 2253, in iterate
    return self.process_row(row)
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 2331, in process_row
    setattr(instance, column, func(row[i]))
  File "/home/dash/.dashcore/sentinel/venv/local/lib/python2.7/site-packages/peewee.py", line 1072, in python_value
    return decimal.Decimal(str(value))
  File "/usr/lib/python2.7/decimal.py", line 547, in __new__
    "Invalid literal for Decimal: %r" % value)
  File "/usr/lib/python2.7/decimal.py", line 3873, in _raise_error
    raise error(explanation)
decimal.InvalidOperation: Invalid literal for Decimal: '47,5'
 
thanks! no errors anymore.
but i guess we have to restart masternode from the wallet?
if yes, then payment counter resets. :(
 
theatab said:
thanks! no errors anymore.
but i guess we have to restart masternode from the wallet?
if yes, then payment counter resets. :(
Click to expand...

No restart necessary, unless too much time expired. First try git pull and check if your masternode gets ENABLED (./dash-cli masternode list full | grep -e IPADDRESS).
I'm keeping my fingers crossed that my masternodes have not expired yet, we have more or less about a hour to fix this, before we get bumped off the payment list.

Update : in this specific case there is no time limit, your masternode does not risk getting bumped of the payment list.
 
Last edited:
thanks man! you are awesome!
i see "enabled". 1 and a half hour has passed.
but what does "waited too long" means? how many hours inactive?
edit: i see "active" now so i hope all are back on track ;)
 
theatab said:
thanks man! you are awesome!
i see "enabled". 1 and a half hour has passed.
but what does "waited too long" means? how many hours inactive?
Click to expand...
1 hour i think, so it could be a close call for some.

Update : in this specific case there is no time limit, your masternode does not risk getting bumped of the payment list.

Note : dashninja.pl shows the current state of masternodes faster then Dash Central,
just give it some time if you are checking on Dash Central..
 
Last edited:
theatab said:
then there are some problems (like sentinel) that are not affecting payments?
Click to expand...

In this case the problem was Sentinel crashing before being able to vote on the watchdog.
There is a timeout window of 180min until a watchdog vote MUST be done

Code: 
static const int MASTERNODE_NEW_START_REQUIRED_SECONDS  = 180 * 60;

So if you have updated your Sentinel during this 180min window your node will be fine. If you have missed this window, your node will be degraded to NEW_START_REQUIRED state - and this means you'll need to restart your node, affecting the payment...
 
flare said:
In this case the problem was Sentinel crashing before being able to vote on the watchdog.
There is a timeout window of 180min until a watchdog vote MUST be done

Code: 
static const int MASTERNODE_NEW_START_REQUIRED_SECONDS  = 180 * 60;

So if you have updated your Sentinel during this 180min window your node will be fine. If you have missed this window, your node will be degraded to NEW_START_REQUIRED state - and this means you'll need to restart your node, affecting the payment...
Click to expand...

So having spork 14 off does not keep masternodes active as nmarley mentioned in his edit ?

Note: This is required or your Masternode will go offline!
(edit: Apparently w/spork 14 off this isn't enforce, so crisis averted!)
Click to expand...

Link : https://www.dash.org/forum/threads/masternode-operators-sentinel-hotfix-action-required.17568/
 
You must log in or register to reply here.
Back
Top