[TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 6.

catia

full member

Activity: 288

Merit: 105

Quote from: uvt9 on July 24, 2014, 09:48:20 AM

i downloaded lastest binary for 14.04 Trusty from http://gpile.it/cryptonite/, i got following error:

Code:

terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted

It may be that you do not have locales setup. In which case:

sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

May also have to apt-get install locales if it is not installed. We do not have non-en_US locale support due to lack translations. So even if locales are installed, you may have to generate en_US.UTF-8 anyways and then run

LC_ALL="en_US.UTF-8" ./cryptonited -testnet

uvt9

sr. member

Activity: 300

Merit: 250

i downloaded lastest binary for 14.04 Trusty from http://gpile.it/cryptonite/, i got following error:

Code:

terminate called after throwing an instance of 'std::runtime_error'
  what():  locale::facet::_S_create_c_locale name not valid
Aborted

What i did:

Code:

sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install libboost-all-dev libdb4.8-dev libdb4.8++-dev libminiupnpc-dev libqt4-dev libprotobuf-dev protobuf-compiler libgmp-dev

My Ubuntu version arcording to /etc/issue is Ubuntu 14.04 LTS, an Amazon instance.

watuba

full member

Activity: 211

Merit: 100

Quote from: catia on July 24, 2014, 03:25:56 AM

Uh, we're only on block ~4000. Maybe you did not delete data folder since we reset the testnet chain?

Right, I'm pretty confused. I think I used a different computer instead. Sorry to get in the way!

mrvegad

hero member

Activity: 616

Merit: 500

Quote from: ajeef on July 24, 2014, 04:38:35 AM

test c9hSsMbggivBDAZETgKYAEQwH9vE1uBsda

..\roaming\Cryptonite
4000blocks 27M

Incoming!

ajeef

sr. member

Activity: 728

Merit: 251

test c9hSsMbggivBDAZETgKYAEQwH9vE1uBsda

..\roaming\Cryptonite
4000blocks 27M

catia

full member

Activity: 288

Merit: 105

Uh, we're only on block ~4000. Maybe you did not delete data folder since we reset the testnet chain?

watuba

full member

Activity: 211

Merit: 100

Ah, thanks for the explanation catia. That seems right as I ran it twice, and both times it got to the Ban at the same point. However, I'm not sure if it worked properly after that. I don't think I could use the daemon. The second time I ran the client, the output repeated:
Getting size for height : 16816
Update: 16817 16818 16817 16820 1
Update: 16945 16818 16817 16820 0
Getting size for height : 16817
Update: 16818 16819 16818 16820 1
Update: 16946 16819 16818 16820 0
Getting size for height : 16818
Update: 16819 16820 16819 16820 1
Update: 16947 16820 16819 16820 0
Getting size for height : 16819
Update: 16820 16820 16820 16820 1
Update: 16948 16820 16820 16820 0
OS 16821 NS 16821
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
Accept block header
Ban
Finalize Node
...

I was using the second to latest build, the one right before you said "Updated source, only because I couldn't sync, so this won't do much for you otherwise".

Unfortunately, it seems I can't get the debug.log because my instance got terminated, sorry. If it happens again, I'll be sure to grab it.

Thanks for the great work!

catia

full member

Activity: 288

Merit: 105

The bans are happening from coinbase transactions being submitted to the network.

Presumably this happens when wallet tries to replay transactions not found in the blockchain, perhaps a mined block that got orphaned. But there is code to prevent this, so I'm not exactly sure how it is happening. Will look into it.

Edit: also no bans have happened since 7pm EST on 7/22. So if you are having some problem, ban is not the cause.

@Watuba, your log there indicates that your node banned someone else, not other way around. Would be interesting to see your debug.log. Were you running latest code? Stuff of the 7/22/18 vintage has code to stop bans in an incorrect case.

watuba

full member

Activity: 211

Merit: 100

Tried it again on a new instance, and didn't get banned! So, it appears I have two clients running with the same wallet now.

watuba

full member

Activity: 211

Merit: 100

Everytime I get banned, I feel a little guilty, like I did something wrong

billotronic

legendary

Activity: 1610

Merit: 1000

Crackpot Idealist

mayhaps... I was banned last night for reasons unknown so we shall see

watuba

full member

Activity: 211

Merit: 100

Well please do try it yourself. I've been known to do things the wrong way Wink

Maybe catia put strict ban requirements for now or something.

billotronic

legendary

Activity: 1610

Merit: 1000

Crackpot Idealist

damn thats not what I wanted to hear... was fixing to set that up tonight myself.

watuba

full member

Activity: 211

Merit: 100

Yes, I was trying what you and catia described below. Is that the wrong way to do it?

Quote from: catia on July 10, 2014, 08:32:17 PM

Quote from: billotronic on July 10, 2014, 07:32:41 PM

ok then silly question, can I have multiple daemons connect to one central daemon and just mine to one wallet?

You have a couple of options here. One is to take the wallet.dat file from your main machine and copy it over the file on any miners. This will cause all blocks to get mined into your same accounts, but it is risky because if any miner gets compromised the attacker would have all of your keys. Other possibility is that when you first setup a miner, run dumpwallet to export all keys and then import all keys from all miners into your main setup. So a little bit of work, but no master/slave thing is really needed.

billotronic

legendary

Activity: 1610

Merit: 1000

Crackpot Idealist

As in running two clients at the same time with the same wallet?

watuba

full member

Activity: 211

Merit: 100

Just got banned. Tried copying the same wallet over to another computer and running.

Getting size for height : 16816
Update: 16817 16818 16817 16820 1
Update: 16945 16818 16817 16820 0
Getting size for height : 16817
Update: 16818 16819 16818 16820 1
Update: 16946 16819 16818 16820 0
Getting size for height : 16818
Update: 16819 16820 16819 16820 1
Update: 16947 16820 16819 16820 0
Getting size for height : 16819
Update: 16820 16820 16820 16820 1
Update: 16948 16820 16820 16820 0
OS 16821 NS 16821
Accept block header
Ban
Finalize Node

billotronic

legendary

Activity: 1610

Merit: 1000

Crackpot Idealist

thanks!

Kinda sucks with this reduced block reward I am gonna have to give the wallet another core or two cause I am gonna run out coins to spam

idev

hero member

Activity: 860

Merit: 1004

BTC OG and designer of the BitcoinMarket.com logo

Quote from: billotronic on July 22, 2014, 06:40:24 PM

ready for abuse

cHfQUBVdSoQvADZo6biWARNF4BfqT3gigX

Sent you some.

billotronic

legendary

Activity: 1610

Merit: 1000

Crackpot Idealist

ready for abuse

cHfQUBVdSoQvADZo6biWARNF4BfqT3gigX

catia

full member

Activity: 288

Merit: 105

New builds up. I had some problems syncing, if your already synced, then these won't do much for you.

Topic: [TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 6. (Read 19305 times)