Author Topic: Dry Run 2: The Real Deal  (Read 87910 times)

0 Members and 1 Guest are viewing this topic.

Offline networker

  • Sr. Member
  • ****
  • Posts: 322
    • View Profile
Can someone vote for my delegate?

I just voted for you ;)

Can you vote me for the delegate?
I have been testing for ten days, just solve the forking problem and need to test block produce.
Thank you in advance
my account is networker.  You sent me XTS before.

Offline HackFisher

  • Hero Member
  • *****
  • Posts: 883
    • View Profile
I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

I'm running a VPS with 1GB, you might need this to compile toolkit with only 1GB RAM:

https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
They missed to tell us about a recent commit:
https://github.com/BitShares/bitshares_toolkit/commit/55053c244f3057841b86a5b46fad654d7e1ce636

You need to run:
wallet_toggle_delegate_block_production <delegate> true

In order for delegates to produce blocks!

EDIT: doesn't seem to work .. i reverted to the previous commit to keep my delegate online AND producing blocks
Bytemaster fixed an issue with that feature:

It's now called
wallet_enable_delegate_block_production <delegate> true

Offline bytemaster

Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.
Good point!
I like it.

I get toast on it.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.
Good point!
I like it.

Xeldal

  • Guest
Im wondering, if we're manually adding a bunch of delegates for Dry Run 3.  Would it not be just as easy, for the people with existing init-delegates, to change the name of one of them to something more desirable?  rather than making an additional one.

Offline bytemaster

I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

This is a g++ limitation as our code does not require that much to run.   
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster


Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.


Sent from my iPhone using Tapatalk

https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.

Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.

Thanks
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline Kenof

  • Full Member
  • ***
  • Posts: 71
    • View Profile
It worked for me on dry run 1 with 1GB RAM, but on dry run 2 server just crashed when installing. After setting instance with 2GB RAM it now works like charm. OS is Ubuntu 14.04.

Hope to get elected to be active delegate in the next dry run. It could take very large marketing campaign in the future to stay a delegate.
« Last Edit: June 18, 2014, 01:06:08 pm by Kenof »
Making life easier.

Offline svk

I missed the  entire dry run 2, because it became impossible to install on a server with only 1GB RAM.

2GB seems enough. It's more expensive though.

I've got it up and running on a 512mb Amazon free tier micro server so that's not quite true. First compile failed, then I setup a 1gb swap and it worked.

It takes forever to compile though so by the time it's done, lots of new changes have alreade been pushed, lol.
Worker: dev.bitsharesblocks

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Can someone vote for my delegate?

I just voted for you ;)
wallet_account_set_approval spartako

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Can someone vote for my delegate?
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

Offline mauritso

  • Full Member
  • ***
  • Posts: 64
    • View Profile

Is there any way we could get the wiki updated with the recently added debug commands? Like list_errors and max_connections and all that? That way those of us who came a little late can be more helpful.


Sent from my iPhone using Tapatalk

https://github.com/BitShares/bitshares_toolkit/wiki should be done. Generated with the api json documents.

Created a pull request: https://github.com/BitShares/bitshares_toolkit/pull/332
Manually fixed the JSON.
BTS: maurits

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Having troubles issuing assets.

Code: [Select]
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>

Code: [Select]
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
    {}
    th_a  wallet.cpp:1772 issue_asset
Is your account-name really 'default' .. not wallet name... it's accountname .. list your account names via wallet_list_receive_accounts

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
Having troubles issuing assets.

Code: [Select]
Usage:
wallet_asset_issue <amount> <symbol> <to_account_name> <memo_message>

Code: [Select]
>>> wallet_asset_issue 1000000 BEE default "Bees are people too"
10 assert_exception: Assert Exception
my->_blockchain->is_valid_symbol( symbol ):
    {}
    th_a  wallet.cpp:1772 issue_asset
>>> approve bitcoiners