Watchdog problem :
https://github.com/kushirikiana/sentinel
Also, I have a block explorer with masternode under contruction, feel free to use it if you want!
http://139.99.194.48/masternodes
Topic: [ANN] [CPU mining] WAVI [YescryptR32] [NO Pre-mine] [Masternode] - page 8. (Read 57548 times)
June 28, 2018, 01:50:16 PM
LOL !!
Watchdog problem :
https://github.com/kushirikiana/sentinel
Also, I have a block explorer with masternode under contruction, feel free to use it if you want!
http://139.99.194.48/masternodes
Watchdog problem :
https://github.com/kushirikiana/sentinel
Also, I have a block explorer with masternode under contruction, feel free to use it if you want!
http://139.99.194.48/masternodes
June 28, 2018, 12:59:38 PM
The development of Sentinel for WAVI is finished. This solves the problem of WATCHDOG_EXPIRED. Installation instructions for Ubuntu 16.04 here:
https://github.com/wavicom/sentinel/blob/master/README.md
Good luck!
UP
https://github.com/wavicom/sentinel/blob/master/README.md
Good luck!
Quote
Guys, vote for WAVI:
1. https://shardax.com/votes/coin?coin=WAVI - You can now upvote every 24 hours.
2. https://newcpucoins.com/coins/wavi - 1 IP = 1 vote.
3. https://c-cex.com/?id=vote&coin=wavi - At least 0.1 BTC balance on exchange required for voting. Also, regardless of the balance on the exchange, you can vote using BTC (1 vote = 0.001 BTC).
New vote (HOT):
4. https://voting.saronite.exchange/ - 1 IP = 1 vote.
1. https://shardax.com/votes/coin?coin=WAVI - You can now upvote every 24 hours.
2. https://newcpucoins.com/coins/wavi - 1 IP = 1 vote.
3. https://c-cex.com/?id=vote&coin=wavi - At least 0.1 BTC balance on exchange required for voting. Also, regardless of the balance on the exchange, you can vote using BTC (1 vote = 0.001 BTC).
New vote (HOT):
4. https://voting.saronite.exchange/ - 1 IP = 1 vote.
UP
June 28, 2018, 03:18:15 AM
At the moment 8 MNs are ENABLED. What do you think? Who is their owner?))
All are new or restarted masternodes (less 3 days olds).Yesterday i had setup a new MN. Ubuntu shows that "status": "Masternode successfully started"
and
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1530099597,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
But in the wallet - WATCHDOG_EXPIRED as my old MNs.
And new MN getting no rewards as other old MNs also.
P.S.
All old MNs was restarted yesterday and resynchronized.
Nothing happened, status still WATCHDOG_EXPIRED.
No idea about what is the issue/the solution for this watchdog message...
my MNs are still in watchdog_expired but they got a payout between 24 and 48 hours of restarting them. i confirm what other have already stated here and in discord.
https://imgur.com/a/nhM65Wv
https://imgur.com/a/QIs7o8W
June 28, 2018, 02:12:50 AM
At the moment 8 MNs are ENABLED. What do you think? Who is their owner?))
All are new or restarted masternodes (less 3 days olds).Yesterday i had setup a new MN. Ubuntu shows that "status": "Masternode successfully started"
and
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1530099597,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
But in the wallet - WATCHDOG_EXPIRED as my old MNs.
And new MN getting no rewards as other old MNs also.
P.S.
All old MNs was restarted yesterday and resynchronized.
Nothing happened, status still WATCHDOG_EXPIRED.
No idea about what is the issue/the solution for this watchdog message...
June 28, 2018, 01:42:31 AM
At the moment 8 MNs are ENABLED. What do you think? Who is their owner?))
All are new or restarted masternodes (less 3 days olds).Yesterday i had setup a new MN. Ubuntu shows that "status": "Masternode successfully started"
and
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1530099597,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
But in the wallet - WATCHDOG_EXPIRED as my old MNs.
And new MN getting no rewards as other old MNs also.
P.S.
All old MNs was restarted yesterday and resynchronized.
Nothing happened, status still WATCHDOG_EXPIRED.
June 28, 2018, 01:11:12 AM
At the moment 8 MNs are ENABLED. What do you think? Who is their owner?))
All are new or restarted masternodes (less 3 days olds). June 28, 2018, 12:16:46 AM
At the moment 8 MNs are ENABLED. What do you think? Who is their owner?))
June 27, 2018, 10:57:45 AM
network seems to be recovering. 3 MNs in enabled state at the moment while many stated (in discord and above) that despite the watchdog_expired status MNs are getting payments as they should.
sooo i guess all good
Still only 3 MN enabled : all the others are watchdoged or disable. sooo i guess all good
June 27, 2018, 06:18:36 AM
MNs are getting payments as they should.
For my MNs payouts was stoped 06.25.18
June 27, 2018, 03:13:16 AM
network seems to be recovering. 3 MNs in enabled state at the moment while many stated (in discord and above) that despite the watchdog_expired status MNs are getting payments as they should.
sooo i guess all good
sooo i guess all good
June 26, 2018, 09:34:32 PM
Everything seems ok to me, my masternodes are up for about 13 days.
https://imgur.com/a/lvYig6A
https://imgur.com/a/lvYig6A
June 26, 2018, 05:25:48 PM
Configuring a masternode following the documentation
# Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
click Tools - Debug - type masternode genkey# Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
Yes Thank you
June 26, 2018, 04:48:28 PM
Configuring a masternode following the documentation
# Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
click Tools - Debug - type masternode genkey # Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
June 26, 2018, 04:27:29 PM
Configuring a masternode following the documentation
# Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
# Masternode config file
# Format: alias IP:port masternodeprivkey collateral_output_txid collateral_output_index
# Example: mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
where can I find the masternodeprivkey ?
June 26, 2018, 09:30:10 AM
In the 768 WAVI masternodes list, only one has the "Enable" status : it is the IP 95.183.13.138, with the public address WY3QEEVD6HjZGQefyrzg1TJxsC4TYrM5Au.
This address got no reward since 48 h, then this is not there all rewards are going (http://www.wavi-blockchain.cloud/address/WY3QEEVD6HjZGQefyrzg1TJxsC4TYrM5Au).
This address got no reward since 48 h, then this is not there all rewards are going (http://www.wavi-blockchain.cloud/address/WY3QEEVD6HjZGQefyrzg1TJxsC4TYrM5Au).
June 26, 2018, 09:10:49 AM
Just kidding they're still down. I had all four go into Enabled for about 15 minutes, then back to watchdog expired.
June 26, 2018, 08:45:48 AM
You are wrong, update the master log list, only one node ENABLE, checked on two wallets.
June 26, 2018, 08:36:22 AM
Masternodes back online for me. Did all the troubleshooting others have listed, but I'm guessing the IPs were being ddos'd as they were previously unreachable.
June 26, 2018, 07:44:42 AM
Hello, Dev. Now the whole network consists of MN with the status of WATCHDOG_EXPIRED. Looks like the network needs Sentinel. Will you solve this problem?
June 26, 2018, 05:19:22 AM
It seems to me the network was attacked
Jump to: