Bitcoin Forum
April 26, 2019, 09:22:46 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: .
.
.

Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 527 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 729363 times)
waffles99
Sr. Member
****
Offline Offline

Activity: 275
Merit: 250


View Profile
March 24, 2016, 01:08:37 PM
 #1401

Need to reiterate my statement. several nodes with status enabled, were still stuck at blocks 707* mostly, one at 69*

I have had externalip= set from the beginning with all nodes. that problem still happened.

1556270566
Hero Member
*
Offline Offline

Posts: 1556270566

View Profile Personal Message (Offline)

Ignore
1556270566
Reply with quote  #2

1556270566
Report to moderator
1556270566
Hero Member
*
Offline Offline

Posts: 1556270566

View Profile Personal Message (Offline)

Ignore
1556270566
Reply with quote  #2

1556270566
Report to moderator
1556270566
Hero Member
*
Offline Offline

Posts: 1556270566

View Profile Personal Message (Offline)

Ignore
1556270566
Reply with quote  #2

1556270566
Report to moderator
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1556270566
Hero Member
*
Offline Offline

Posts: 1556270566

View Profile Personal Message (Offline)

Ignore
1556270566
Reply with quote  #2

1556270566
Report to moderator
1556270566
Hero Member
*
Offline Offline

Posts: 1556270566

View Profile Personal Message (Offline)

Ignore
1556270566
Reply with quote  #2

1556270566
Report to moderator
DRPD
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001


View Profile
March 24, 2016, 01:42:45 PM
 #1402




Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes

some masternodes run on the latest version 1000201, some on version 10001 the behavior is the same.

seems the "epired / restart" problem has nothing to do with the sync problem or version.

all my masternodes where running fine for several days until version 10002 came out and nothing seems to solve the problem so far.

tetsted the following steps:
- every version from 10001 - 1000201
- restart  vps
- delete and clean reinstall of masternode sw (with all versions)
- all steps above on 2 different hoster (to be sure the problem is independent from hoster)

let me know if i can test anything else, i guess there must be a dnet network problem i have no other explanation - but i'm not a blockcain expert  Tongue

my last payout is also more than 12 hrs ago even if have a script running all 10 minutes to execute "masternode start-missing"

on the plus side the out of sync problem seems to be fixed in the latest version (note: my upgrade is only about 5 hrs ago )



borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
March 24, 2016, 01:51:41 PM
 #1403




Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes

some masternodes run on the latest version 1000201, some on version version 10001 the behavior is the same.

seems the "epired / restart" problem has nothing to do with the sync problem or version.

all my masternodes where running fine for several days until version 10002 came out and nothing seems to solve the problem so far.

tetsted the following steps:
- every version from 10001 - 1000201
- restart  vps
- delete and clean reinstall of masternode sw (with all versions)
- all steps above on 2 different hoster (to be sure the problem is independent from hoster)

let me know if i can test anything else, i guess there must be a dnet network problem i have no other explanation - but i'm not a blockcain expert  Tongue

my last payout is also more than 12 hrs ago even if have a scripts running all 10 minutes to execute "masternode start-missing"

on the plus side the out of sync problem seems to be fixed in the latest version (note my upgrade is only about 5 hrs ago )





My masternodes are on 1.0.1.0 downgraded using mp hosting. They are in sync and i am recieving regular payouts again now after 12 hours or so. i am running the 1.0.2.1 wallet on my controller windows pc and it has not got stuck yet...I am not risking upgrading the masternodes again until this is 100% fixed
DRPD
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001


View Profile
March 24, 2016, 01:57:02 PM
 #1404




Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

yes and even my masternodes running on the new version where the out of sync problem should be fixed expires all 2 hors or so

edit: masternodes on version 10001, 10002 and 1000201 all have the same problems will check the sync problem a littlebit further on version 1000201 as soon as i can ....

ok i just checked this again on several masternodes that are listed as expired again.
they are all in sync and syncprocess is going forward just fine on this matsernodes
..................


My masternodes are on 1.0.1.0 downgraded using mp hosting. They are in sync and i am recieving regular payouts again now after 12 hours or so. i am running the 1.0.2.1 wallet on my controller windows pc and it has not got stuck yet...I am not risking upgrading the masternodes again until this is 100% fixed

my mn's on mp hosting also run on version 1.0.1.0 most of them (not all) go in expired mode from time to time .... no payout for 14 hrs now  Huh
i guess you are lucky hehe
Tecem
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
March 24, 2016, 02:26:14 PM
 #1405

Went back to version 1 wallet since version 2 was acting strange. Blocks where stuck. Now on version 1 it also went stuck a few times. Now its running fine but I didn't get a payout for 14+ hours. A friend is running a mastered at home and he got payed 8 times in 3 minutes. So something strange is going on. few days ago my mastered was just running fine with payments every 6-8 hours.
jakiman
Legendary
*
Offline Offline

Activity: 1120
Merit: 1000


jakiman is back!


View Profile
March 24, 2016, 02:45:56 PM
 #1406

For past 24 hours, I've received about 50% of what i should have got. Angry

I just upgraded few MN to 1.0.2.1 along with my controller wallet.
But I've left most MN at 1.0.1.0 still. Let's see how this goes....

BitcoinFX
Legendary
*
Offline Offline

Activity: 1792
Merit: 1074


youtu.be/jO5VV5PISHU


View Profile WWW
March 24, 2016, 03:00:57 PM
 #1407


Linux / Cloud VPS - DNET command line upgrade guide from: v1.0.1.0 or v1.0.2.0 to: v1.0.2.1

Stop the Dnet daemon:

Code:
cd Darknet

Code:
cd src

Code:
./darknet-cli stop

Code:
cd


Remove the 'old' Dnet folder and daemon etc:

Code:
rm -rv Darknet


Download Dnet v1.0.2.1 :

Code:
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v1.0.2.1/Darknet-Qt-Linux-Wallet-v1.0.2.1.zip


Re-make the Dnet directory:

Code:
mkdir Darknet

Code:
cd Darknet

Code:
mkdir src

Code:
cd


Unzip the download :

Code:
unzip Darknet-Qt-Linux-Wallet-v1.0.2.1.zip -d Darknet/src


Move the unzipped files to the 'default' directory :

Code:
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknetd Darknet/src/

Code:
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-cli Darknet/src/

Code:
mv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1/darknet-tx Darknet/src/


Tidy up:

Code:
rm -rv Darknet/src/Darknet-Qt-Linux-Wallet-v1.0.2.1

Code:
rm -rv Darknet/src/__MACOSX

Code:
rm -R Darknet-Qt-Linux-Wallet-v1.0.2.1.zip


Restart the Dnet daemon:

Code:
cd Darknet

Code:
cd src

Code:
./darknetd

Code:
./darknet-cli getinfo

Code:
./darknet-cli masternode start

Guide at: http://xeronet.c0m.li/dnet-crypto.php - to be updated.

EDIT: Go here: https://github.com/Darknet-Crypto/Darknet - If you prefer to build from source.

Bitcoin without polity !?! | Get a Gapcoin slice of Mathematically constant π + new world record and attempt ongoing! | "The industry of the integrated spectacle and immaterial command owes me (us all) money." | We do not Forgive. We do not Forget. Expect Revolution Renaissance! for we are all Satoshi now? | Vision does not = Prescient | "the multiple and the multiplex!" | HODL BTC and/or buy Pizza's | Read the first chapter ... | P.S. "I Eye love found you!" 456 | Mostly harmless ... 42 | "INSERT COIN" break blocks!
BitcoinFX
Legendary
*
Offline Offline

Activity: 1792
Merit: 1074


youtu.be/jO5VV5PISHU


View Profile WWW
March 24, 2016, 03:07:20 PM
 #1408

For past 24 hours, I've received about 50% of what i should have got. Angry

I just upgraded few MN to 1.0.2.1 along with my controller wallet.
But I've left most MN at 1.0.1.0 still. Let's see how this goes....

Guess everyone is pretty much in the same boat here, except those that didn't upgrade. 

Posted Upgrade instructions for linux cloud VPS above anyway.


P.S. This has all been a bit like 'upgrading' from Windows 7 to Windows 10 ?   Cheesy

Bitcoin without polity !?! | Get a Gapcoin slice of Mathematically constant π + new world record and attempt ongoing! | "The industry of the integrated spectacle and immaterial command owes me (us all) money." | We do not Forgive. We do not Forget. Expect Revolution Renaissance! for we are all Satoshi now? | Vision does not = Prescient | "the multiple and the multiplex!" | HODL BTC and/or buy Pizza's | Read the first chapter ... | P.S. "I Eye love found you!" 456 | Mostly harmless ... 42 | "INSERT COIN" break blocks!
DRPD
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001


View Profile
March 24, 2016, 03:13:09 PM
 #1409

Went back to version 1 wallet since version 2 was acting strange. Blocks where stuck. Now on version 1 it also went stuck a few times. Now its running fine but I didn't get a payout for 14+ hours. A friend is running a mastered at home and he got payed 8 times in 3 minutes. So something strange is going on. few days ago my mastered was just running fine with payments every 6-8 hours.

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes   Undecided

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
March 24, 2016, 04:10:31 PM
 #1410

any updates on everyones results? i have 1 mn and controller going and they still in sync so far...
djselery
Legendary
*
Offline Offline

Activity: 1260
Merit: 1001

www.codex.one


View Profile WWW
March 24, 2016, 04:12:04 PM
 #1411

Had to restart my wallet and mn again was stuck visually at block 726xx with no rewards shown. After restart it seems it was running fine just the wallet was not updating because after restart and resync i had 300 dnet waiting for me in the chain. Is there a repairwallet command or something to fix this issue?

                  ░    ████▒                
                ░███   ░█████               
               ███████   ▒████▓             
               ████████    █████░           
            ░    ████████   ▒█████          
          ▒███    ▒███████░   █████░        
         ██████▒    ████████   ▒█████       
       ░█████████    ░███████    █████▒     
      ████████████    ░████████   █████░    
       ██████████░   █████████   █████▒     
         ███████    ████████   ▒█████       
          ████    █████████   █████░        
            █   ░████████   ▒█████          
               █████████   █████░           
               ███████   ░█████             
                ▒███▒  ░█████░              
                  ▒    ████▒                
  CODEX
        www.codex.one
]|[
  CRYPTO CURRENCY EXCHANGE OF TOMORROW ■ ■
ANN | BOUNTY | REDDIT | TELEGRAM | TWITTER | FACEBOOK | MEDIUM
]|[
LOW FEES | LICENSED
ECC API | TRADE MINING
AFFILIATE & LOYALTY PROGRAM
EleanorZ
Sr. Member
****
Offline Offline

Activity: 358
Merit: 270



View Profile
March 24, 2016, 04:13:27 PM
 #1412

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes   Undecided

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....

Just confirming that mine are also still having the missing/expired problem. Have received two payouts in the last 48 hours. Annoying.

On the other hand, syncing is fine.
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
March 24, 2016, 04:23:43 PM
 #1413

yeah same here i had payouts all 6-8 hours now nothing since 16 hrs for 35 masternodes   Undecided

the expire problem seems to be a lot worse with the newst version so i recommend to stay with version 1.0.1.0
with the new version they are listed as expired every 2 hrs regulary....

Just confirming that mine are also still having the missing/expired problem. Have received two payouts in the last 48 hours. Annoying.

On the other hand, syncing is fine.

what version?
StakeBox
Full Member
***
Offline Offline

Activity: 226
Merit: 100


View Profile WWW
March 24, 2016, 04:30:50 PM
 #1414

Just an update folks, we have been working diligently to figure out what the hell is going on. s3v3n and I are in the same boat as everyone else, and are exhausting all of our options to remedy this. I have held off on saying much, but I think that the fact that there are wallets of all versions, 1.0.1.0, 1.0.2.0, and 1.0.2.1 acting up suggests that something other than a wallet issue is at play. We reverted most of the changes that were brought about in v1.0.2.0 with v1.0.2.1 just to make sure that there wasn't something we were missing, it would seem that there wasn't.

The only thing that can ever cause a Masternode's state to go to "EXPIRED" is if it hasn't been able to be pinged by the network for 65 minutes. If you go to http://www.yougetsignal.com/tools/open-ports/ and verify that you Masternode is reachable on port 51472 then you should sending and receiving pings. If it is reachable, and your Masternode is going to expired the only remaining explanation is that something, or someone, is blocking communication somehow. After checking quite a few Masternode addresses at random and finding them reachable, I have to assume there is something nefarious afoot.

Please bear with us as we work to figure out exactly what is happening, and how to alleviate the problem. Communication from us is limited as we are trying to focus all of our energy on getting things back to the smooth operations we had prior to this. Please, keep posting anything you are noticing, good, bad, or indifferent, we may not respond immediately, but are checking in here often for updates from you guys.

Thanks for your patience while we work this out, as soon as we are certain of the next move we will let you know.

Low power dedicated staking hardware, learn more at StakeBox.com
Raspberry Pi wallets at github.com/StakeBox
EleanorZ
Sr. Member
****
Offline Offline

Activity: 358
Merit: 270



View Profile
March 24, 2016, 04:36:24 PM
 #1415

what version?

1.0.2 and 1.0.2.1. Haven't gone back to 1.0.1 yet since I was hoping for a fix in 1.0.2.1, but may be the next step. I was just letting the devs know that the "other" issue is still unresolved for me. I had no issues with 1.0.1 before, but the fact that others are now getting expired nodes even after downgrading makes me think there's something else going on.

And devs, thanks for the update. Good luck getting things sorted out--better to have hiccups now than later on in the roadmap, I guess.
DRPD
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001


View Profile
March 24, 2016, 04:44:31 PM
 #1416

Just an update folks, we have been working diligently to figure out what the hell is going on. s3v3n and I are in the same boat as everyone else, and are exhausting all of our options to remedy this. I have held off on saying much, but I think that the fact that there are wallets of all versions, 1.0.1.0, 1.0.2.0, and 1.0.2.1 acting up suggests that something other than a wallet issue is at play. We reverted most of the changes that were brought about in v1.0.2.0 with v1.0.2.1 just to make sure that there wasn't something we were missing, it would seem that there wasn't.

The only thing that can ever cause a Masternode's state to go to "EXPIRED" is if it hasn't been able to be pinged by the network for 65 minutes. If you go to http://www.yougetsignal.com/tools/open-ports/ and verify that you Masternode is reachable on port 51472 then you should sending and receiving pings. If it is reachable, and your Masternode is going to expired the only remaining explanation is that something, or someone, is blocking communication somehow. After checking quite a few Masternode addresses at random and finding them reachable, I have to assume there is something nefarious afoot.

Please bear with us as we work to figure out exactly what is happening, and how to alleviate the problem. Communication from us is limited as we are trying to focus all of our energy on getting things back to the smooth operations we had prior to this. Please, keep posting anything you are noticing, good, bad, or indifferent, we may not respond immediately, but are checking in here often for updates from you guys.

Thanks for your patience while we work this out, as soon as we are certain of the next move we will let you know.

ok checked this ping thing  Cheesy on port 51472 on 20 of my masternodes no problem Port 51472 is open.
i have to repeat: i have 2 hosters mp-hosting and a hoster in russia masternodes on both hosters have the same problem

thanks for working so hard on this and take your time! as we all know shit happens with IT stuff!

edit: i got some payouts until yesterday even with the expired problem. but now no payouts are incoming anymore.
some of my masternodes don't go to expired state (not much only ~5 of 35) so i guess there is a problem with payouts 2 even if the masternodes works fine without "expired" interruptions
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
March 24, 2016, 05:08:23 PM
 #1417

my last payout was 3.15 and have stopped by looks of it. usually get regular hourly payments as well. All are still enabled tho. Only one is on 1.0.2.1 and that is still in sync and has been for a couple of hours now. The rest are on 1.0.1.0. the controller is 1.0.2.1 and that is in sync as well.
danonthehill
Hero Member
*****
Offline Offline

Activity: 710
Merit: 500


View Profile
March 24, 2016, 06:04:58 PM
 #1418

I am still receiving payouts from all my masternodes on MP hosting.  I only get MISSING EXPIRED or REMOVE if I use old .1 local wallet to connect to masternodes which are running newer .2.   
Tecem
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
March 24, 2016, 06:44:34 PM
Last edit: March 24, 2016, 06:57:39 PM by Tecem
 #1419

I See a lot of traffic incoming to my mastered port. Is there an attack on the network going on what causes the payouts to be stuck? The problem isn't in the wallet it self. Seems an external issue with the blockchain or something.

the 10k coins are not locking also. so a lot seems to be messed up Sad
BitcoinFX
Legendary
*
Offline Offline

Activity: 1792
Merit: 1074


youtu.be/jO5VV5PISHU


View Profile WWW
March 24, 2016, 06:51:46 PM
 #1420

Everyone upgrading to v1.0.2.1 seems the best option now - It is mostly the same as 1.0.1.0, with the block rewards corrected.

Best to reset / upgrade Masternodes and controller wallets asap. Advise server restarts, where possible.

Check for or add;

Quote
listen=1
discover=1

and/or

Quote
externalip=<put your masternode ip address here>

are added in your masternodes  darknet.conf

and reindex on re-start;

Code:
./darknetd -reindex


~ Also, now waiting to see if MN's are getting 'stuck' on blocks after upgrading. Monitoring nodes for any signs of 'packet flooding' etc.,
  

Bitcoin without polity !?! | Get a Gapcoin slice of Mathematically constant π + new world record and attempt ongoing! | "The industry of the integrated spectacle and immaterial command owes me (us all) money." | We do not Forgive. We do not Forget. Expect Revolution Renaissance! for we are all Satoshi now? | Vision does not = Prescient | "the multiple and the multiplex!" | HODL BTC and/or buy Pizza's | Read the first chapter ... | P.S. "I Eye love found you!" 456 | Mostly harmless ... 42 | "INSERT COIN" break blocks!
Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 527 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!