Delegates, start your engines!

Started by toast, June 09, 2014, 01:54:36 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 ... 6 7 8 9 10 11 12 13 14 15 16 17
User actions

bytemaster

#65
June 09, 2014, 02:35:45 PM
Quote from: Xeldal on June 09, 2014, 02:33:11 PM
Code Select
root@xt:~/bitshares_toolkit# screen -r delegate
There are screens on:
        15988.delegate  (06/09/2014 10:23:17 AM)        (Attached)
        13899.delegate  (06/09/2014 09:59:52 AM)        (Attached)
        12728.delegate  (06/08/2014 11:10:05 PM)        (Attached)
        12713.delegate  (06/08/2014 11:08:16 PM)        (Attached)
There is no screen to be resumed matching delegate.


You can run all delegates in a single process...

You can reattach to these screens with:

Code Select
screen -r -D 12713.delegate 
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

#64
June 09, 2014, 02:34:39 PM
Quote from: toast on June 09, 2014, 02:24:41 PM
Quote from: alt on June 09, 2014, 02:19:18 PM
I have run about 12 hours with 2 computer,
but I still produce 0 block.
Is this correct?
my account is init-delegate-17, init-delegate-18,init-delegate-19,init-delegate-20

I see that you are producing blocks, where do you see that you produced 0?

This is probably because we don't expose the delegate's pay which is separate from their normal balance.  If delegates are looking for 'coinbase' transactions, they don't exist... your pay is a property of your account.

Quotedefault (unlocked) >>> blockchain_get_account_record init-delegate-17
{
  "id": 17,
  "name": "init-delegate-17",
  "public_data": null,
  "owner_key": "XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM",
  "active_key_history": [[
      "19700101T000000",
      "XTS57VJ3pc85WWJWCwNzPBcwNHEqHstavbhgFfHgc8nTmCchXGJAM"
    ]
  ],
  "delegate_info": {
    "votes_for": 91796978110,
    "votes_against": 0,
    "blocks_produced": 18,
    "blocks_missed": 13,
    "pay_balance": 80020,
    "next_secret_hash": "8074d5a45dffa7031980c1188d853a514cab88c0",
    "last_block_num_produced": 655
  },
  "registration_date": "20140601T000000",
  "last_update": "20140601T000000",
  "meta_data": null
}
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

Xeldal

#63
June 09, 2014, 02:33:11 PM
Code Select
root@xt:~/bitshares_toolkit# screen -r delegate
There are screens on:
        15988.delegate  (06/09/2014 10:23:17 AM)        (Attached)
        13899.delegate  (06/09/2014 09:59:52 AM)        (Attached)
        12728.delegate  (06/08/2014 11:10:05 PM)        (Attached)
        12713.delegate  (06/08/2014 11:08:16 PM)        (Attached)
There is no screen to be resumed matching delegate.

toast

#62
June 09, 2014, 02:29:38 PM
Quote from: Xeldal on June 09, 2014, 02:28:51 PM
I get the following error trying to launch client

Code Select
Loading blockchain from "/root/.BitSharesXTS/chain"
------------ error --------------
10001
Unable to open database /root/.BitSharesXTS/chain/fork_number_db
        IO error: lock /root/.BitSharesXTS/chain/fork_number_db/LOCK: Resource temporarily unavailable
    {"db":"/root/.BitSharesXTS/chain/fork_number_db","msg":"IO error: lock /root/.BitSharesXTS/chain/fork_number_db/LOCK: Resource temporarily unavailable"}
    th_a  level_map.hpp:46 open

    {"data_dir":"/root/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:877 open

    {"data_dir":"/root/.BitSharesXTS"}
    th_a  client.cpp:352 open


You have the client running already. Did you use screen and then detach?
Try "screen -r delegate"
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Xeldal

#61
June 09, 2014, 02:28:51 PM
I get the following error trying to launch client

Code Select
Loading blockchain from "/root/.BitSharesXTS/chain"
------------ error --------------
10001
Unable to open database /root/.BitSharesXTS/chain/fork_number_db
        IO error: lock /root/.BitSharesXTS/chain/fork_number_db/LOCK: Resource temporarily unavailable
    {"db":"/root/.BitSharesXTS/chain/fork_number_db","msg":"IO error: lock /root/.BitSharesXTS/chain/fork_number_db/LOCK: Resource temporarily unavailable"}
    th_a  level_map.hpp:46 open

    {"data_dir":"/root/.BitSharesXTS/chain"}
    th_a  chain_database.cpp:877 open

    {"data_dir":"/root/.BitSharesXTS"}
    th_a  client.cpp:352 open

bytemaster

#60
June 09, 2014, 02:28:13 PM
Could some of you attempt to use this API call to import your keyhotee IDs:

wallet_import_keyhotee <firstname> <middlename> <lastname> <brainkey> <keyhoteeid>                   

For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

xeroc

#59
June 09, 2014, 02:25:30 PM
I successfully produced 18 blocks with 2 delegates each

toast

#58
June 09, 2014, 02:24:41 PM
Quote from: alt on June 09, 2014, 02:19:18 PM
I have run about 12 hours with 2 computer,
but I still produce 0 block.
Is this correct?
my account is init-delegate-17, init-delegate-18,init-delegate-19,init-delegate-20

I see that you are producing blocks, where do you see that you produced 0?
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

toast

#57
June 09, 2014, 02:19:56 PM
Quote from: networker on June 09, 2014, 02:18:52 PM
Can I join the dry run if I missed the public key generated part?
I just build the bitshares_toolkit successfully

You can join and even register as delegate if you have funds to import but you will not be an active delegate unless you convince people to vote for you
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

alt

#56
June 09, 2014, 02:19:18 PM
I have run about 12 hours with 2 computer,
but I still produce 0 block.
Is this correct?
my account is init-delegate-17, init-delegate-18,init-delegate-19,init-delegate-20

networker

#55
June 09, 2014, 02:18:52 PM
Can I join the dry run if I missed the public key generated part?
I just build the bitshares_toolkit successfully

bytemaster

#54
June 09, 2014, 02:08:44 PM
Quote from: changematey on June 09, 2014, 12:43:48 PM
Well looks like none of my private WIF keys are working. The public key list:
https://bitsharestalk.org/index.php?topic=4913.msg64544#msg64544

I guess missed the bus for this initial test.

Try this now.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

#53
June 09, 2014, 02:07:40 PM
Quote from: bytemaster on June 09, 2014, 01:29:51 PM
Quote from: xeroc on June 09, 2014, 01:09:01 PM
Importing my PTS/BTC privkeys only worked after doing the following steps

1.) get wif for pts/btc address
2.) go to brainwallet and convert Base65Check privkey to hex
3.) use key_to_wif to convert brainwallet hex key to privkey
4.) Both priv keys differ in the last view bytes (i suspect thats the Check-part)

@Devs: Please doublecheck the CHECK-procedure of your WIF formats in the code!!!

Thanks for the notice I will look into this: https://github.com/BitShares/bitshares_toolkit/issues/241

This has been resolved.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

#52
June 09, 2014, 01:34:39 PM Last Edit: June 09, 2014, 02:08:13 PM by bytemaster
Quote from: sfinder on June 09, 2014, 04:56:03 AM
Quote from: toast on June 09, 2014, 04:24:09 AM
@sfinder  I'm not sure what's going on, have not encountered this issue yet on any build I tried. Which OS version?
my os is ubuntu 14.04 and i got following CMAKE error

CMake Error at programs/client/CMakeLists.txt:8 (target_include_directories):
  target_include_directories called with invalid arguments

daniel@ubuntu:~/bitshares_toolkit$ cmake .
-- The C compiler identification is GNU 4.8.2
....
-- Found the following Boost libraries:
--   thread
ontext
--   locale
--   coroutine
-- Setting up OpenSSL root and include vars to , /include
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libssl.a;/usr/lib/x86_64-linux-gnu/l                        ibcrypto.a (found version "1.0.1f")
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
-- Finished fc module configuration...
-- Found Curses: /usr/lib/x86_64-linux-gnu/libcurses.so
-- Found Readline: /usr/include
-- Using  as BerkeleyDB root
-- Looking for: db_cxx-6.0
-- debug/usr/lib/x86_64-linux-gnu/libdb_cxx.sooptimized/usr/lib/x86_64-linux-gnu                        /libdb_cxx.so
-- Found BerkeleyDB: /usr/include
-- Enabling Bitcoin Core Wallet Imports
CMake Error at programs/client/CMakeLists.txt:8 (target_include_directories):
  target_include_directories called with invalid arguments
-- Configuring incomplete, errors occurred!

Eric tells me this is fixed now.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

#51
June 09, 2014, 01:31:13 PM
Quote from: networker on June 09, 2014, 12:46:29 PM
Quote from: emski on June 09, 2014, 12:42:41 PM
Quote from: networker on June 09, 2014, 12:38:38 PM
Quote from: sfinder on June 09, 2014, 03:33:00 AM
daniel@ubuntu:~/bitshares_toolkit$ cmake /V
cmake version 2.8.12.2

Quote from: toast on June 09, 2014, 03:31:00 AM
What is your cmake --version?

Code Select
cmake version 2.8.12.2

May need to Temporarily set CURSES_USE_NCURSES to TRUE to force the use of NCURSES, rather than letting CMake try to find CURSES.
When I use "cmake ." try to build bitshare toolkit,  I met the problem" Could not find Curses(missing: CURESES_LIBRARY CURSES_INCLUDE_PATH)
How can I fix it ?
How to set CURSES_USE_NCURSES to TRUE?

Try to checkout this revision: 035357b7ffbcc394236fec5e2cb8d0e9bf707c97  .
It works for me without modifications.
What does revision mean? I can't understand 0353......7c97
Sorry

This is just the version the number is the 'hash' of the state of the code.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.
Print
Go Up Pages 1 ... 6 7 8 9 10 11 12 13 14 15 16 17
User actions