Open Newar417 opened 7 years ago
"No JSON object could be decoded DONE!" it's happening again on an updated server, how do you fix this?
thanks
@Newar417 @fher98
It's a broken DashNinja. No way to fix it, so I removed it.
@dotexx Thank you for working on it! I installed your version and I would like to report an issue, but it seems you have issue functionality disabled?
@Newar417 By default it's not allowed. Fixed. You are welcome to open an issue.
MN is running fine and receives payments. However:
`dashman version 0.1.25 (32-g6aabce1) - 2017 / 5 / 5 12:29:47 CEST gathering info, please wait... No JSON object could be decoded DONE!
hostname : xxx host uptime/load average : 62 days, 2.77 2.62 2.62 dashd bind ip address : xxx.xxx.xxx.xxx dashd version : 0.12.1.4 dashd up-to-date : NO dashd running : YES dashd uptime : 42 days, 17 hours, 14 mins, 16 secs dashd responding (rpc) : YES dashd listening (ip) : YES dashd connecting (peers) : YES dashd port open : YES dashd connection count : 22 dashd blocks synced : YES last block (local dashd) : 664632 (chainz) : 0 (dash.org) : 0 (dashwhale) : 664631 (masternode.me) : 664632 - no forks detected dashd current difficulty : 167291.3584837048 masternode started : YES masternode visible (local) : YES masternode visible (ninja) : NO masternode address : masternode funding txn : - masternode queue/count : 448/4441 masternode mnsync state : MASTERNODE_SYNC_FINISHED masternode network state : ENABLED masternode last payment : never masternode balance : 0 sentinel installed : YES sentinel tests passed : /home/xxx/dashman/lib/dashman_functions.sh: line 1123: [: too many arguments NO sentinel crontab enabled : YES sentinel online : YES Exiting. `