Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
tiras, yes like togo wrote: i dit it same
VPS rebooted, started daemon then started watchdog and then in controller wallet did command : masternode start-alias POKUS and worked
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
"04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
"a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
"a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
"8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
"7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
"d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
"404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
"be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
"e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
"b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
"c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
"44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
"847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"
I upgraded mine to 1.0.6 and after re-syncing it's showing "watchdog expired" . Watchdog is running with no errors. I didn't touch it.
"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
./biblepay-cli masternode list
{
"04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
"a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
"a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
"8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
"7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
"d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
"404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
"be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "EXPIRED",
"e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
"b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
"c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
"44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
"847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "EXPIRED"
hi,
exists anybody except ADMIN whom working stable masternode?
yauWFekmt47YpzzQaZxFRkM7Zk5RjGQTsa- one 1mln please
ill try setup masternode on 2 clean machines(linuxmasternode+wincontroller),may be problem is with my big setups
thanks
whats the IP of the node that wont sync? Ill check to see if you were banned.
Also see if you delete your banlist.dat and restart you may sync?
Next if it does not sync then check the end of the debug.log for an error.
mnsync status
11:50:02
{
"AssetID": 1,
"AssetName": "MASTERNODE_SYNC_SPORKS",
"Attempt": 0,
"IsBlockchainSynced": false,
"IsMasternodeListSynced": false,
"IsWinnersListSynced": false,
"IsSynced": false,
"IsFailed": false,
"MasternodesEnabled": true
}
11:52:55
masternode start-alias MNode1
11:52:55
{
"alias": "MNode1",
"result": "failed",
"errorMessage": "Sync in progress. Must wait until sync is complete to start Masternode"
}
Yeah, that happens when watchman is not actually running in the cron.
Please do this:
type 'crontab -e' , copy the exact command you typed into your cron into notepad.
exit crontab.
Now type the command from bash. Tell me if it throws an error (Im sure it will most likely).
Then fix the crontab.
Klondike, this guide is not for newbies. Why dont you have your Senior IT specialists google other coins like Chaincoin and Dash and explain how their video is better? Its NOT. It requires patience and doing it exact. I went through the guide and it works. I updated the one entry for the crontab yesterday. I believe your "WATCHDOG EXPIRED" is the same issue as above. Let me know what the output of the above command is.
Once you figure it out, go ahead and make a video for us, and we will post it here.
By the way, the correct commands are not preceded by biblepay-cli. Some people use RPC, some use bitnet, some use biblepayd, its common sense to precede your commands with biblepay-cli, so the guide stays as is.
Nov 13 10:07:01 BUS7-14 CRON[11263]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)
Nov 13 10:08:01 BUS7-14 CRON[11275]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)
Nov 13 10:09:01 BUS7-14 CRON[11291]: (root) CMD (cd /root/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1)finished configuring the test sanctuary .
now it shows in the "masternode list" output as "PRE_ENABLED" .
Do I need to do anything else to finalize it ?
root@BUS7-14:~/biblepay/src# ./biblepay-cli masternode list
{
"2b41b04ac488c033073562090aba186ccf57faf8ecae00dbc1f072a0ac9eebdf-1": "ENABLED",
"82da38dd4db20bc6fa5fd30ebeda707d1edbce1b3890c386497db7f4abffe90c-1": "ENABLED",
"04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
"a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
"a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
"8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "EXPIRED",
"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"
Good to have another sanctuary tester on board. I have sent you some coins
A little update here for everyone on TestNet:
I decided to modify the testnet chain to have 1 minute blocks, so when someone is actually testing, we can test 700% faster.
For example, if we want to mock up a proposal, a vote, a budget and a superblock, we wont have to wait as long.
On my local nodes, I had to erase all my testnet chains. The code is out for linux but not for Windows yet.
Also, another major change is Sanctuaries require another piece of linux side software called Watchman on the wall. Im working on it now, and will update asap.
This will allow us to test sanctuaries in testnet a little early (IE within 30 days from now). Giving myself 30 days of time max to get the web proposal/budget working.
