Pages:
Author

Topic: [ANN] [KRB] Karbo (Ҝ) Кapбoвaнeць - Anon / stable transaction costs - page 54. (Read 493221 times)

legendary
Activity: 1750
Merit: 1101
karbo.io
can someone help me with this



its the only thing i couldnt find a way to fix it, already return to ubuntu 14.04 thinking it was the newst redis but still the same error..
i cant put my pool for everybody because of that... Undecided Undecided Undecided
already check wallet port, already checked firewall,router foward...but if it doesnt connect it doesnt give any error...just says failed
with the right wallet port gives me that error...

cant find anywere how to fix it   Undecided Undecided Undecided
what type of wallet are you trying to run? use simplewallet, but bear in mind you have to generate wallet in it, wallet container from walletd can't be opened in simplewallet.
legendary
Activity: 1512
Merit: 1442
thefuzzstone.github.io
Anyone trading KRB/BTC at Livecoin.net?
hero member
Activity: 701
Merit: 511
can someone help me with this



its the only thing i couldnt find a way to fix it, already return to ubuntu 14.04 thinking it was the newst redis but still the same error..
i cant put my pool for everybody because of that... Undecided Undecided Undecided
already check wallet port, already checked firewall,router foward...but if it doesnt connect it doesnt give any error...just says failed
with the right wallet port gives me that error...

cant find anywere how to fix it   Undecided Undecided Undecided
legendary
Activity: 1750
Merit: 1101
karbo.io
but krb.crypto-coins.club   99266   101941 H/s   7 is on the wrong chain, correct?
actual height is 99291

that i wanna know too dev how come that pool with that hash is finding blocks at that high....whats its the right high of blocks right now...i been checking democrats...using the forknote daemon, im sync with democrats and main pool....but theres a lot of miners on that pool with that high of blocks  Undecided Undecided Undecided Undecided Undecided

I think their daemon crashed or something, they are mining in vain unfortunately.

hero member
Activity: 701
Merit: 511
but krb.crypto-coins.club   99266   101941 H/s   7 is on the wrong chain, correct?
actual height is 99291

that i wanna know too dev how come that pool with that hash is finding blocks at that high....whats its the right high of blocks right now...i been checking democrats...using the forknote daemon, im sync with democrats and main pool....but theres a lot of miners on that pool with that high of blocks  Undecided Undecided Undecided Undecided Undecided
sr. member
Activity: 499
Merit: 254
but krb.crypto-coins.club   99266   101941 H/s   7 is on the wrong chain, correct?
actual height is 99291

seems like just daemon has crashed
full member
Activity: 142
Merit: 100
but krb.crypto-coins.club   99266   101941 H/s   7 is on the wrong chain, correct?
actual height is 99291
legendary
Activity: 1750
Merit: 1101
karbo.io
All back to normal, network is stable, http://explorer.karbowanec.com/ is fine now.
legendary
Activity: 1750
Merit: 1101
karbo.io
actually i did it two times deleted all .karbowanec folder data and resync
Just don't pay attention, if you're running forknote and it's on the same chain that http://democats.org/blockchain/?name=karbowanec you're ok.

Explorer http://explorer.karbowanec.com is constantly falling to fork chain and reogranizing.
legendary
Activity: 1750
Merit: 1101
karbo.io
Someone is still running pool on karbowanecd, please switch to forknoted - you're getting orphaned blocks anyway.
full member
Activity: 177
Merit: 100
actually i did it two times deleted all .karbowanec folder data and resync
legendary
Activity: 1750
Merit: 1101
karbo.io
is your node uptodate with the rest?

didnt get on this above line

daemon sync well and getting this warning in forknoted sync .

 WARNING Transaction 3fff73bb7f22237592fbcb0cd05c978cad2d0eb4f080c84f4fa662dce92d8cd9 is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:36:38.498805 WARNING Transaction fac61c9ea8642d36b6119fbfa6e64c476514d4c6cd3e7747b3931ed4d8e2be0d is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435107 WARNING Transaction a26fcb272fcfcc41fded6aa8c8c5533e0f6f63225b5eacd7c3dd55d0831ffcba is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435428 WARNING Transaction d0526c215ab3313e5d3dc566ff5b3de22d7dc4d3451eada4dbf3535b3577d4f4 is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435840 WARNING Transaction 28438f545ad69736b9af5d6c13b02c1a1cf2c0d4b244afe61f93d4ac9cff8aa7 is not valid. Reason: Transaction uses spent key image

Well, all I can suggest is to resync blockchain from scratch. 2.0 version forknote is using does this really fast.
full member
Activity: 177
Merit: 100
is your node uptodate with the rest?

didnt get on this above line

daemon sync well and getting this warning in forknoted sync .

 WARNING Transaction 3fff73bb7f22237592fbcb0cd05c978cad2d0eb4f080c84f4fa662dce92d8cd9 is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:36:38.498805 WARNING Transaction fac61c9ea8642d36b6119fbfa6e64c476514d4c6cd3e7747b3931ed4d8e2be0d is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435107 WARNING Transaction a26fcb272fcfcc41fded6aa8c8c5533e0f6f63225b5eacd7c3dd55d0831ffcba is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435428 WARNING Transaction d0526c215ab3313e5d3dc566ff5b3de22d7dc4d3451eada4dbf3535b3577d4f4 is not valid. Reason: Transaction uses spent key image
2017-Apr-17 12:37:53.435840 WARNING Transaction 28438f545ad69736b9af5d6c13b02c1a1cf2c0d4b244afe61f93d4ac9cff8aa7 is not valid. Reason: Transaction uses spent key image
legendary
Activity: 1750
Merit: 1101
karbo.io
....
btw , getting this error in simple wallet , dev

2017-Apr-17 12:28:52.605096 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
2017-Apr-17 12:28:57.645117 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
2017-Apr-17 12:29:02.684958 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error

can you try to reset wallet in Karbowanec wallet, just open it in GUI and do reset then feed it to forknote's simplewallet?
is your node uptodate with the rest?
full member
Activity: 177
Merit: 100
height 99001 blocks in my client atm... how to be sure I'm on right fork? 1.1.4 binary

Yes, this is the right height (now already 99002), but better use daemon and simplewallet from forknote with karbowanec config.

none of this solution work , block found but payment not working , and has many warning in daemon.

xcrypto.org pool is going down until new daemon is ready. we dont want to waste you hashing power.


thanks....
yesterday dev with help solved all this problems of fork....its not his fault that someone mess up transation creating a fork chain...all you have to do is READ THE LAST PAGES OF POST....connect to some especific nodes if your daemon is connecting to the fork chain and RESYNC!!!....
instead of bothering the dev....just fuck****g READ

well, behave your self man ,intention is not to blame dev.

btw , getting this error in simple wallet , dev

2017-Apr-17 12:28:52.605096 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
2017-Apr-17 12:28:57.645117 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
2017-Apr-17 12:29:02.684958 ERROR   [BlockchainSynchronizer] Failed to query blocks: NodeErrorCategory:5, Internal node error
hero member
Activity: 701
Merit: 511
height 99001 blocks in my client atm... how to be sure I'm on right fork? 1.1.4 binary

Yes, this is the right height (now already 99002), but better use daemon and simplewallet from forknote with karbowanec config.

none of this solution work , block found but payment not working , and has many warning in daemon.

xcrypto.org pool is going down until new daemon is ready. we dont want to waste you hashing power.


thanks....
yesterday dev with help solved all this problems of fork....its not his fault that someone mess up transation creating a fork chain...all you have to do is READ THE LAST PAGES OF POST....connect to some especific nodes if your daemon is connecting to the fork chain and RESYNC!!!....
instead of bothering the dev....just fuck****g READ
legendary
Activity: 1750
Merit: 1101
karbo.io
Wallets are compatible, just reset it if you was mining wrong chain
sr. member
Activity: 499
Merit: 254
height 99001 blocks in my client atm... how to be sure I'm on right fork? 1.1.4 binary

Yes, this is the right height (now already 99002), but better use daemon and simplewallet from forknote with karbowanec config.

none of this solution work , block found but payment not working , and has many warning in daemon.

xcrypto.org pool is going down until new daemon is ready. we dont want to waste you hashing power.


thanks....

Sorry, for me (krb.sberex.com) it is working properly. I wrote what I did myself.

may be you are using new wallet file for forknote

may be, I used old one.
full member
Activity: 177
Merit: 100
height 99001 blocks in my client atm... how to be sure I'm on right fork? 1.1.4 binary

Yes, this is the right height (now already 99002), but better use daemon and simplewallet from forknote with karbowanec config.

none of this solution work , block found but payment not working , and has many warning in daemon.

xcrypto.org pool is going down until new daemon is ready. we dont want to waste you hashing power.


thanks....

Sorry, for me (krb.sberex.com) it is working properly. I wrote what I did myself.

may be you are using new wallet file for forknote
sr. member
Activity: 499
Merit: 254
height 99001 blocks in my client atm... how to be sure I'm on right fork? 1.1.4 binary

Yes, this is the right height (now already 99002), but better use daemon and simplewallet from forknote with karbowanec config.

none of this solution work , block found but payment not working , and has many warning in daemon.

xcrypto.org pool is going down until new daemon is ready. we dont want to waste you hashing power.


thanks....

Sorry, for me (krb.sberex.com) it is working properly. I wrote what I did myself.
Pages:
Jump to: