How long it takes with mn to find a Block, more than 24 hours and nothing?!
It takes more than 24 hours for the first one. Then it's a bit more frequent after it.
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 430. (Read 782382 times)
May 14, 2016, 05:29:37 AM
It takes more than 24 hours for the first one. Then it's a bit more frequent after it.
May 14, 2016, 05:17:55 AM
How long it takes with mn to find a Block, more than 24 hours and nothing?!
May 13, 2016, 07:26:47 PM
We are about 40% updated.. Lets keep it going.. 
May 13, 2016, 12:36:04 PM
how i can see if my masternode works?
The best way is to run "masternode list full" in the debug console, copy the output into a text editor, and search for your masternode by IP address, DNET address, or TXID. Man, we really need to get the new website done, and have a FAQ section. No offense to you, I know it can be difficult to look through the haystack that is this thread for the specific needle you are wanting. It just gets a bit old repeating the same things over and over. May 13, 2016, 12:32:11 PM
I don't get the "fewer coins is bad for POS" concept. People can stake one coin, ten coins, one thousand coins etc. what matters is the proportional distribution of the coins and the amount of staking wallets not if there are total of 50 mil, 100 mil or 500 mil.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
I don't get the "fewer coins is bad for POS" concept. People can stake one coin, ten coins, one thousand coins etc. what matters is the proportional distribution of the coins and the amount of staking wallets not if there are total of 50 mil, 100 mil or 500 mil.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
I don't get why you would copy an old post from fedmahnkassad verbatim, after the change it was in support of has already been made.
May 13, 2016, 12:31:48 PM
how i can see if my masternode works?
May 13, 2016, 12:18:11 PM
I don't get the "fewer coins is bad for POS" concept. People can stake one coin, ten coins, one thousand coins etc. what matters is the proportional distribution of the coins and the amount of staking wallets not if there are total of 50 mil, 100 mil or 500 mil.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
Also guys here are acting as if there is no competition at all and you have all the time in the world to develop the coin and gain popularity.
There are tons of new coins coming up and will continue to come up. You need to decide if you want to be a predator or bottom of the food chain dweller.
May 13, 2016, 12:16:04 PM
you should only have to wait if you had to restart your masternodes from the controller wallet.
May 13, 2016, 10:41:53 AM
ok upgraded all my mn's and controller wallet 4-5 hrs ago
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
Will wait till update mine till can be looked into.
The update is fine, my nodes are running solid , no issues. Waiting is just delaying the issue for everyone. we need EVERYONE to update as soon as possible. Thanks!!
so i guess only bad luck for me that i had to redownload the whole blockchain for 10% of my mn's.
my upgrade process was the same on every mn so i can not see a fault on my side and i have not noticed same problem with the last upgrade.
however after blockchain redownload on the affected mn's no more problems so far.
is it normal to wait 24 -48 hrs for rewards again after upgrade?
because after last upgrade this was not the case, just asking .....
May 13, 2016, 10:28:44 AM
ok upgraded all my mn's and controller wallet 4-5 hrs ago
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
Will wait till update mine till can be looked into.
The update is fine, my nodes are running solid , no issues. Waiting is just delaying the issue for everyone. we need EVERYONE to update as soon as possible. Thanks!!
May 13, 2016, 10:27:17 AM
ok i just noticed that i had to run masternode start-missing from controller wallet after upgrading my mn's
some are started successful the first time some are reporting an error the first time:
"result" : "failed",
"errorMessage" : "Could not allocate vin
if i run masternode start-missing again it works and the error is gone
not sure if we have a problem here?
will check my mn's for the next 2 hrs (have to leave office afterwards for a while) and run masternode start-missing regularly and report here if i notice more probs
some are started successful the first time some are reporting an error the first time:
"result" : "failed",
"errorMessage" : "Could not allocate vin
if i run masternode start-missing again it works and the error is gone
not sure if we have a problem here?
will check my mn's for the next 2 hrs (have to leave office afterwards for a while) and run masternode start-missing regularly and report here if i notice more probs
This is common, and I believe it stems from there being so many different versions out on the network. If you keep submitting it, it will succeed, and then you will be good.
May 13, 2016, 10:15:58 AM
Thanks for those scripts.
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
the only daemons that are needed are the darknetd and the darknet-cli
May 13, 2016, 09:56:49 AM
ok upgraded all my mn's and controller wallet 4-5 hrs ago
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
Will wait till update mine till can be looked into.
May 13, 2016, 08:08:12 AM
All my v1.1.0.1 upgraded masternodes so far had no problems staying up for past 12+ hours.
None of them went disabled/expired yet and I don't expect them to. I'll upgrade rest later on.
Only 6.6 days to go until PoW Block Reduction from 250 to 50 happens...
Everyone upgrade to v1.1.0.1 before then or you'll be on the wrong fork!
None of them went disabled/expired yet and I don't expect them to. I'll upgrade rest later on.
Only 6.6 days to go until PoW Block Reduction from 250 to 50 happens...
Everyone upgrade to v1.1.0.1 before then or you'll be on the wrong fork!
May 13, 2016, 05:22:48 AM
ok upgraded all my mn's and controller wallet 4-5 hrs ago
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
summary of my experience so far:
- have to start all mn's with controller wallet after the upgrade. some reporting an error (see post abvoe) first time, second time it works fine
- zero rewards incoming since upgrade (maybe just have wait 24 - 48 hrs for rewards again)
- similar behavior like in the past. some mn's are going to expired and then disabled state at random times & have to start again with controller wallet
- Windows wallet is freezing sometimes (W7 64-bit. with 64-bit Wallet) just have to kill it with taskmanager and restart again. not sure if this is relevant but whenever this happens to me the debug console was open.
can't complain s3v3nh4cks told us it will be a bumpy ride
nice weekend all. i hope you all have a long one too
edit: all mn's going to expried / disabled state regularly after upgrade were out of sync (stuck around block 140977) even with 10 or
more connections. deleting blockchain and resync solved the problem for now
May 13, 2016, 02:02:01 AM
I think you have a problem with your
Code:
masternode.conf
try running Code:
darknet-cli masternode outputs
and check that the single digit at the end corresponds with the transaction id. (longer number).no 100% sure all output index's are right and the error was gone the second time i run masternode start-missing
so far 9 out 50 had the problem on the first start. not a big problem if it works after running the command again.
just want to report ...
May 13, 2016, 01:59:52 AM
I think you have a problem with your
Code:
masternode.conf
try running Code:
darknet-cli masternode outputs
and check that the single digit at the end corresponds with the transaction id. (longer number). May 13, 2016, 01:41:50 AM
ok i just noticed that i had to run masternode start-missing from controller wallet after upgrading my mn's
some are started successful the first time some are reporting an error the first time:
"result" : "failed",
"errorMessage" : "Could not allocate vin
if i run masternode start-missing again it works and the error is gone
not sure if we have a problem here?
will check my mn's for the next 2 hrs (have to leave office afterwards for a while) and run masternode start-missing regularly and report here if i notice more probs
some are started successful the first time some are reporting an error the first time:
"result" : "failed",
"errorMessage" : "Could not allocate vin
if i run masternode start-missing again it works and the error is gone
not sure if we have a problem here?
will check my mn's for the next 2 hrs (have to leave office afterwards for a while) and run masternode start-missing regularly and report here if i notice more probs
May 13, 2016, 01:19:17 AM
Thanks for those scripts.
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
good idea i noticed that too on some slow servers.
it was not necessary to update darknet-tx for the last update so i guess it is not necessary for the new update
i guess dev team will clarify this soon
May 13, 2016, 01:07:20 AM
Thanks for those scripts.
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
I had to add extra sleep 60 after "./darknet-cli stop" as sometimes it would take a long time to stop.
Also, does darknet-tx need to be updated also?
Jump to: