Dry Run 8: Need for Speed

[alt]

@alt: known issue .. BM already noticed that in this thread

sorry, I missed that. 

[xeroc]

@alt: known issue .. BM already noticed that in this thread

[alt]

my client stop sync block again,
last time when this happened, I am unlock through web wallet.
this time I have do nothing.

Code: [Select]

default (unlocked) >>> info
{
  "blockchain_head_block_num": 8611,
  "blockchain_head_block_age": "3 hours old",
  "blockchain_head_block_timestamp": "20140710T041100",
from the log file, I found many database store error
some times the error happened when store a transaction

Code: [Select]

20140710T040939.589721       th_a       handle_message ] CLIENT: just received transaction 541ccae9676cfdb24a1dd454342b25ddd4ea283b                     client.cpp:910
20140710T040939.605413       th_a       handle_message ] CLIENT: just received transaction 5334bf58174a989b3b59fd3361a2a484f10d7b9a                     client.cpp:910
20140710T040939.722093       th_a       handle_message ] CLIENT: just received transaction 375893fc56a191a2d7c6781f50827b325447fcdd                     client.cpp:910
20140710T040939.762042       th_a       handle_message ] CLIENT: just received transaction 5318643396766f90713875cd81bcfa6780864080                     client.cpp:910
20140710T040939.962398       th_a       handle_message ] CLIENT: just received transaction 542f8e4bc99001fe72eb4cf6d94c66a97ba157fc                     client.cpp:910
20140710T040940.774578       th_a       handle_message ] CLIENT: just received transaction 54396206dd5a8e21137d27bced6a0d9c79dcb3a1                     client.cpp:910
20140710T040940.792349       th_a                store ] storing error in database: .......... client.cpp:372
.......

some times it happened when store block. here you can see  how block 8611 was lost.

Code: [Select]

20140710T041101.561453       th_a         on_new_block ] Received a new block from the p2p network, current head block is 8610, new block is .........., current head block is 8610                     client.cpp:810
20140710T041101.564998       th_a      store_and_index ]            we already know about its previous: 4ed5d11df6c31207ab0164d19acb381776198fb4                        chain_database.cpp:423
20140710T041101.568464       th_a   apply_transactions ] Applying transactions from block: 8611                 chain_database.cpp:517
20140710T041101.608607       th_a       handle_message ] CLIENT: just received transaction 5e7ad620b2c22f9e89c74dd4c2d5b217d7526fa8                     client.cpp:910
20140710T041101.757095       th_a         on_new_block ] After push_block, current head block is 8611                   client.cpp:826
20140710T041101.779538       th_a       handle_message ] CLIENT: just received transaction 5ea6cf69af2f33b20c90873f16bfabc5940c9704                     client.cpp:910
20140710T041101.888100       th_a       handle_message ] CLIENT: just received transaction 2d96353239a0ff8916163835d406fec1b6e95cce                     client.cpp:910
20140710T041101.960162       th_a       handle_message ] CLIENT: just received transaction 5f13daa66fe2efda501192a3fcdff9e196c23ab2                     client.cpp:910
20140710T041102.147807       th_a       handle_message ] CLIENT: just received transaction 5f78d9fd926216f437bf3d0e0542a9490e23b23f                     client.cpp:910
......................
20140710T041111.818869       th_a       handle_message ] CLIENT: just received transaction 6f421a267186a39a6e637722f12eaecab0cbb729                     client.cpp:910
20140710T041111.852776       th_a       handle_message ] CLIENT: just received transaction 6829ade9bf68d4b50746d24f11a95aef6d2b9089                     client.cpp:910
20140710T041112.131368       th_a       handle_message ] CLIENT: just received transaction 6d7bcbebde00258b68d4d0d717c9238adc834f64                     client.cpp:910
20140710T041112.137844       th_a       handle_message ] CLIENT: just received transaction 6f4c103951449f2cfd368831e4914d87917f99ed                     client.cpp:910
20140710T041112.210913       th_a       handle_message ] CLIENT: just received transaction 6e69022eac4461683a80cf59e5764e8ecc22baa6                     client.cpp:910
20140710T041112.383471       th_a       handle_message ] CLIENT: just received transaction 6f943dbe7ceb440b7e6128bebf6604cb4eefd613                     client.cpp:910
20140710T041112.440864       th_a       handle_message ] CLIENT: just received transaction 6f421a267186a39a6e637722f12eaecab0cbb729                     client.cpp:910
20140710T041113.010481       th_a       handle_message ] CLIENT: just received transaction 6f7f86805e824582076489d3ee585b26996d23b9                     client.cpp:910
20140710T041113.024071       th_a       handle_message ] CLIENT: just received transaction 70532ae4e51b230a6cf6aaea89ceee0604682913                     client.cpp:910
20140710T041113.595862       th_a       handle_message ] CLIENT: just received transaction 7091699a416b646417bca0181828f2f34d7db9ca                     client.cpp:910
20140710T041113.649058       th_a       handle_message ] CLIENT: just received block cda77c576cbfa4919270a32644b8391a4866bfdb                   client.cpp:902
20140710T041113.653660       th_a         on_new_block ] Received a new block from the p2p network, current head block is 8611, new block is ...., current head block is 8611                   client.cpp:810
20140710T041113.658469       th_a      store_and_index ]            we already know about its previous: e2af818b73a717925c0079abfa55dd040314666d                        chain_database.cpp:423
20140710T041113.659922       th_a   apply_transactions ] Applying transactions from block: 8612                 chain_database.cpp:517
20140710T041113.685028       th_a         extend_chain ] error applying block: 10000 db_exception: Database in Use
database error: IO error: data/chain/index/block_id_to_block_record_db/000040.log: Too many open files
    {"msg":"IO error: data/chain/index/block_id_to_block_record_db/000040.log: Too many open files"}
    th_a  level_map.hpp:243 store
error storing cda77c576cbfa4919270a32644b8391a4866bfdb = .............
    {"key":"cda77c576cbfa4919270a32644b8391a4866bfdb","value":.........}
    th_a  level_map.hpp:245 store

    {"trx_num":19}
    th_a  chain_database.cpp:550 apply_transactions                     chain_database.cpp:817


[sumantso]

For starters, my 2nd delegate registration just worked after some time. I have no idea what the bug initially was, have a look if you get time.

Anyways, sumantso has almost 0.02% approval, while suman is <0.01%. Please send a few votes suman's way.

[puppies]

Well that makes complete sense then why I can't get it working. Carry on

You can build your own gui client on Ubuntu.  You will need to

Code: [Select]

sudo apt-get install qt5-default libqt5webkit5-dev npm (I thnk those are the only dependencies needed.)
Then follow the Ubuntu instructions to build the text client.  After you do the git submodule update you will need to

Code: [Select]

cd programs
git clone https://github.com/bitshares/web_wallet.git
git clone https://github.com/bitshares/qt_wallet.git
cd web_wallet
sudo npm install -g lineman
sudo npm install
lineman run
Lineman should run for a bit and then get to a point where its just waiting.  Go ahead and ctrl C, or just open a new terminal.  You will then need to take the folder named generated in bitshares_toolkit/programs/webwallet, move it to bitshares_toolkit/programs/qt_wallet and name it htdocs.  Then cd back to /bitshares_toolkit and run

Code: [Select]

cmake -DINCLUDE_QT_WALLET=ON ../bitshares_toolkit
makeIf all goes well you will have an executable named BitSharesXT in /bitshares_toolkit/programs/qt_wallet that will be your gui wallet.

I typed this up from memory, its been a few days since I've built the gui wallet, so I may have missed something.  Also please forgive any typing errors.

[bitmeat]

Just do wallet_get_account crabbypattie and you should see the "profit". or you can do blockchain_list_active_delegates 1 100 to see all of them

Thank you, betax! So, this balance - when and how does it get distributed? Is it when you stop producing blocks? It doesn't seem to be reflected in my acct.

Also - I spent 800K on delegate positions, they have produced about 20K each so far.

[betax]

So my 2 delegates have forged about 100 blocks. I have not seen any profit made from it.

How and when do delegates get paid?

I've asked this a few times now... I suppose there is info on that somewhere on the wiki? Can someone point me to it?

Just do wallet_get_account crabbypattie and you should see the "profit". or you can do blockchain_list_active_delegates 1 100 to see all of them

[muse-umum]

can confirm everyone here in VA thinks alt is amazing

Sent from my SCH-I535 using Tapatalk

 
For those who are yet to know alt, here is his picture I took yesterday.   

[bitmeat]

So my 2 delegates have forged about 100 blocks. I have not seen any profit made from it.

How and when do delegates get paid?

I've asked this a few times now... I suppose there is info on that somewhere on the wiki? Can someone point me to it?

[gordonhucn]

Just tried to create asset with XTS balance over 100,but failed with error message:

RPC Server Error: In method 'wallet_asset_create': 20010 insufficient_funds: insufficient funds

I tried the same in version 0.0.7 and it worked.

[bitmeat]

So my 2 delegates have forged about 100 blocks. I have not seen any profit made from it.

How and when do delegates get paid?

[toast]

can confirm everyone here in VA thinks alt is amazing

Sent from my SCH-I535 using Tapatalk

[alt]

GOOD catch alt. I3/BM  should promote you to be chief QA....

lol 
thank you anyway
I know I am far away from  QA
But I'll try my best

[vikram]

Anyone able to point me to some documentation to automate a start up script?  I attempted the following with no luck:

Code: [Select]

./bitshares_client --input-log "/home/myuser/myconfig.conf"
What CLI args should be included within the input-log file?  Those associated with ./bitshares_client or those within the running software? 

My goal is to script the open and unlock of my wallet so my delegate produces following a reboot.

Thanks,

Code: [Select]

wallet_approve_delegate fox

Look in tests/regression_tests/ for examples. We will document the usage as soon as we can.

[sfinder]

GOOD catch alt. I3/BM  should promote you to be chief QA....

client didn't sent FIN when receive FIN from the socekt.
when my client is running, many connect keep with stat "CLOSE_WAIT" untill TIMEOUT

Code: [Select]

tcp        0      0 106.185.26.162:8761     216.252.204.39:59187    CLOSE_WAIT  14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     107.170.30.182:8801     ESTABLISHED 14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     216.252.204.39:59422    CLOSE_WAIT  14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     216.252.204.39:60225    CLOSE_WAIT  14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     107.170.90.142:41604    CLOSE_WAIT  14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     210.22.128.4:59874      ESTABLISHED 14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     216.252.204.39:59923    CLOSE_WAIT  14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     14.153.94.151:48057     ESTABLISHED 14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     46.252.21.49:37252      ESTABLISHED 14252/bitshares_cli
tcp        0      0 106.185.26.162:8761     107.170.90.142:37794    CLOSE_WAIT  14252/bitshares_cli
when my client is closed, many connect keep with stat "FIN_WAIT2" untill TIMEOUT

Code: [Select]

tcp        0      0 106.185.26.162:8761     117.89.62.3:14548       FIN_WAIT2   -               
tcp        0      0 106.185.26.162:8761     222.76.149.26:43475     FIN_WAIT2   -               
tcp        0      0 106.185.26.162:8761     50.160.116.123:58971    FIN_WAIT2   -               
tcp        0      0 106.185.26.162:8761     76.170.153.137:52757    FIN_WAIT2   -               
tcp        0      0 106.185.26.162:8761     107.170.30.182:8802     TIME_WAIT   -               
tcp        0      0 106.185.26.162:8761     162.245.145.70:54940    FIN_WAIT2   -