« previous next »
Pages: 1 ... 21 22 23 24 25 26 27 [28] 29 30 31 32 33 34 35 ... 42   Go Down

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

0 Members and 1 Guest are viewing this topic.

June 15, 2014, 02:36:33 am Reply #218

Offline Troglodactyl

  • Hero Member
  • *****
  • Posts: 960
    • View Profile
Re: Dry Run 2: The Real Deal
Quote from: bytemaster on June 15, 2014, 02:03:35 am
Quote from: bitcoinerS on June 14, 2014, 11:53:17 pm
problems on latest build

Code: [Select]
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 5141,
  "blockchain_head_block_time": "20140614T235030",
  "blockchain_head_block_time_rel": "in the future",
  "blockchain_confirmation_requirement": 279,
  "blockchain_average_delegate_participation": 57.396449704142015,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 99999993,
  "wallet_next_block_production_time": "20140614T235700",
  "wallet_seconds_until_next_block_production": 297,
  "wallet_local_time": "20140614T235203",
  "blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
  "blockchain_shares": 10000061092614,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20170815T093836",
  "wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)

That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.

Excellent!
Logged
June 15, 2014, 02:03:35 am Reply #217

Offline bytemaster

Re: Dry Run 2: The Real Deal
Quote from: bitcoinerS on June 14, 2014, 11:53:17 pm
problems on latest build

Code: [Select]
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 5141,
  "blockchain_head_block_time": "20140614T235030",
  "blockchain_head_block_time_rel": "in the future",
  "blockchain_confirmation_requirement": 279,
  "blockchain_average_delegate_participation": 57.396449704142015,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 99999993,
  "wallet_next_block_production_time": "20140614T235700",
  "wallet_seconds_until_next_block_production": 297,
  "wallet_local_time": "20140614T235203",
  "blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
  "blockchain_shares": 10000061092614,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20170815T093836",
  "wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)

That problem has been fixed and we now know the problem for the peer connection issues as well and should have that fixed tonight.
Logged
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.
June 14, 2014, 11:53:17 pm Reply #216

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
Re: Dry Run 2: The Real Deal
problems on latest build

Code: [Select]
Loading blockchain from "/root/.BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
[New Thread 0x7ffff58ae700 (LWP 27247)]
Listening for P2P connections on port 53893
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
[New Thread 0x7ffff4ead700 (LWP 27248)]
[New Thread 0x7fffeffff700 (LWP 27249)]
--- there are now 1 active connections to the p2p network
I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
(wallet closed) >>> wallet_open default
OK
default (locked) >>> wallet_unlock 99999999
passphrase:
OK
default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 5141,
  "blockchain_head_block_time": "20140614T235030",
  "blockchain_head_block_time_rel": "in the future",
  "blockchain_confirmation_requirement": 279,
  "blockchain_average_delegate_participation": 57.396449704142015,
  "network_num_connections": 0,
  "wallet_unlocked_seconds_remaining": 99999993,
  "wallet_next_block_production_time": "20140614T235700",
  "wallet_seconds_until_next_block_production": 297,
  "wallet_local_time": "20140614T235203",
  "blockchain_random_seed": "fb039b4dd5ec0bef959de04a02fd0192f3caad69",
  "blockchain_shares": 10000061092614,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20170815T093836",
  "wallet_version": 100
}
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab14aa in EVP_EncryptUpdate ()
(gdb)
Logged
>>> approve bitcoiners
June 14, 2014, 11:06:46 pm Reply #215

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
Re: Dry Run 2: The Real Deal
after starting gdb and then process with > run
When creating a new wallet etc.. after 1-2 min i get this message
Clean installed system so no old data dir... Ubuntu 14.04

Code: [Select]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab142a in EVP_EncryptUpdate ()

Then i have to restart and then same error message again!

Don't know if it was discussed here before...just joined yet
Logged
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█
June 14, 2014, 10:16:02 pm Reply #214

Offline mauritso

  • Full Member
  • ***
  • Posts: 64
    • View Profile
Re: Dry Run 2: The Real Deal
Quote from: alexxy on June 14, 2014, 10:07:58 pm
Resync your blockchain

Thanks, normally I remove the datadir, but this time I had a wallet in which I imported all my keys and stuff. Need to adapt my rebuild script to leave the config.json and the wallet dir.

after a while:

Code: [Select]
Current executable set to './bitshares_client' (x86_64).
(lldb) run
Process 59989 launched: './bitshares_client' (x86_64)
Logging to file "/Users/maurits/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/maurits/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/maurits/Library/Application Support/BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "user",
    "rpc_password": "pass",
    "rpc_endpoint": "127.0.0.1:5681",
    "httpd_endpoint": "127.0.0.1:5680",
    "htdocs": "/Users/maurits/bitsharesxts/web_wallet/generated"
  },
  "default_peers": [
    "107.170.30.182:8764",
    "114.215.104.153:8764",
    "84.238.140.192:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [],
    "loggers": []
  }
}
Loading blockchain from "/Users/maurits/Library/Application Support/BitSharesXTS/chain"
Not starting RPC server, use --server to enable the RPC interface
Listening for P2P connections on port 58343
Attempting to connect to peer 107.170.30.182:8764
Attempting to connect to peer 114.215.104.153:8764
Attempting to connect to peer 84.238.140.192:8764
Process 59989 stopped
* thread #1: tid = 0x26f60e, 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x000000010056a97d bitshares_client`EVP_EncryptUpdate + 29
bitshares_client`EVP_EncryptUpdate + 29:
-> 0x10056a97d:  movq   (%r12), %rbx
   0x10056a981:  testb  $0x10, 0x12(%rbx)
   0x10056a985:  je     0x10056a9ad               ; EVP_EncryptUpdate + 77
   0x10056a987:  movq   %rdx, %r14
« Last Edit: June 14, 2014, 10:34:08 pm by mauritso »
Logged
BTS: maurits
June 14, 2014, 10:11:24 pm Reply #213

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Re: Dry Run 2: The Real Deal
I recompiled and removed chain/  and peers.leveldb/ and relunched but I get segfault after a while.

This is the log file
Code: [Select]
463053ms       th_a         get_property ] property last_random_seed_id                 chain_database.cpp:1711
463057ms       th_a         on_new_block ] After push_block, current head block is 3072                 client.cpp:534
463057ms       th_a process_backlog_of_s ] sync: client accpted the block, we now have only 1798 items left to fetch before we're in sync                       node.cpp:1924
463057ms       th_a process_backlog_of_s ] Popped item from front of 107.170.30.182:8764's sync list, new list length is 1798                   node.cpp:1954
463058ms       th_a process_backlog_of_s ] Currently backlog is 0 blocks                        node.cpp:2000
463058ms       th_a trigger_fetch_sync_i ] Triggering fetch sync items loop now                 node.cpp:794
463058ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                   node.cpp:748
463058ms       th_a request_sync_item_fr ] requesting item 22718b464eaa3d76d330ea6bf1dd847b072af4cf from peer 107.170.30.182:8764                       node.cpp:735
463058ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                     node.cpp:784
463152ms       th_a process_block_during ] received a sync block from peer 107.170.30.182:8764                  node.cpp:2023
463152ms       th_a process_backlog_of_s ] sync: this block is a potential first block, passing it to the client                        node.cpp:1895
463152ms       th_a       handle_message ] CLIENT: just received block 22718b464eaa3d76d330ea6bf1dd847b072af4cf                 client.cpp:599
463152ms       th_a         on_new_block ] Received a new block from the p2p network, current head block is 3072, new block is {"previous":"664e6900488c7fc11e445666fcb0abfdb3aefae4","block_num":3073,"fee_rate":1000,"delegate_pay_rate":42168,"timestamp":"20140614T075900","transaction_digest":"c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0","next_secret_hash":"21ac19c3861e30e51a5a18df3b21d0338bda7193","previous_secret":"b869a10fd0309834887795b225e9fd8da03cdc77","delegate_signature":"1fda702f83eeab2f9de5ff38fe5fdff5c0ce519305d8838a0cad86cde78326618f9dac8d6cfbd7f9be0ccba9bdf3e507998d0498a680b8fa28a195cdf0e0a3017e","user_transactions":[]}, current head block is 3072                 client.cpp:518
463152ms       th_a         get_property ] property last_random_seed_id                 chain_database.cpp:1711
463152ms       th_a      store_and_index ]            we already know about its previous: 664e6900488c7fc11e445666fcb0abfdb3aefae4                      chain_database.cpp:350
463152ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463152ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property confirmation_requirement                    chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property active_delegate_list_id                     chain_database.cpp:1711
463154ms       th_a         get_property ] property last_random_seed_id                 chain_database.cpp:1711
463154ms       th_a         get_property ] property last_random_seed_id                 chain_database.cpp:1711
463154ms       th_a         get_property ] property confirmation_requirement                    chain_database.cpp:1711
463155ms       th_a         get_property ] property last_random_seed_id                 chain_database.cpp:1711
463159ms       th_a         on_new_block ] After push_block, current head block is 3073                 client.cpp:534
463159ms       th_a process_backlog_of_s ] sync: client accpted the block, we now have only 1797 items left to fetch before we're in sync                       node.cpp:1924
463159ms       th_a process_backlog_of_s ] Popped item from front of 107.170.30.182:8764's sync list, new list length is 1797                   node.cpp:1954
463159ms       th_a process_backlog_of_s ] Currently backlog is 0 blocks                        node.cpp:2000
463159ms       th_a trigger_fetch_sync_i ] Triggering fetch sync items loop now                 node.cpp:794
463159ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                   node.cpp:748
463159ms       th_a request_sync_item_fr ] requesting item 6a9d99709e1b2fa7ef4f607c7d086ecb3b9f69fc from peer 107.170.30.182:8764                       node.cpp:735
463159ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                     node.cpp:784
463173ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:44341 due to inactivity of at least 45 seconds                   node.cpp:931
463173ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:34353 due to inactivity of at least 45 seconds                   node.cpp:931
463174ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 106.185.26.48:35830 due to inactivity of at least 45 seconds                     node.cpp:931
463174ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:34255 due to inactivity of at least 45 seconds                   node.cpp:931
463174ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:33142 due to inactivity of at least 45 seconds                   node.cpp:931
463174ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 202.96.137.243:42975 due to inactivity of at least 45 seconds                    node.cpp:931
463174ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 180.153.142.115:46048 due to inactivity of at least 45 seconds                   node.cpp:931
(END)


And this is the gdb output
Code: [Select]
default (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab2c88 in EVP_EncryptUpdate ()
(gdb)
Logged
wallet_account_set_approval spartako
June 14, 2014, 10:07:58 pm Reply #212

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Re: Dry Run 2: The Real Deal
Resync your blockchain
Logged
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy
June 14, 2014, 09:54:54 pm Reply #211

Offline mauritso

  • Full Member
  • ***
  • Posts: 64
    • View Profile
Re: Dry Run 2: The Real Deal
Same here:

Code: [Select]
Logging to file "/Users/maurits/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/maurits/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/maurits/Library/Application Support/BitSharesXTS/config.json"
{
  "rpc": {
    "rpc_user": "user",
    "rpc_password": "pass",
    "rpc_endpoint": "127.0.0.1:5681",
    "httpd_endpoint": "127.0.0.1:5680",
    "htdocs": "/Users/maurits/bitsharesxts/web_wallet/generated"
  },
  "default_peers": [
    "107.170.30.182:8764",
    "114.215.104.153:8764",
    "84.238.140.192:8764"
  ],
  "ignore_console": false,
  "logging": {
    "includes": [],
    "appenders": [],
    "loggers": []
  }
}
Loading blockchain from "/Users/maurits/Library/Application Support/BitSharesXTS/chain"
Starting JSON RPC server on port 5681 (localhost only)
Starting HTTP JSON RPC server on port 5680 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
    {"method":"read","len":23,"over":1}
    th_a  datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
    {"type":"uint8_t"}
    th_a  raw.hpp:440 unpack
optional<fc::exception>
    {"type":"fc::exception"}
    th_a  raw.hpp:164 unpack
Error unpacking field last_error
    {"field":"last_error"}
    th_a  raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
    {"type":"bts::net::potential_peer_record"}
    th_a  raw.hpp:440 unpack
Logged
BTS: maurits
June 14, 2014, 09:50:00 pm Reply #210

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
Re: Dry Run 2: The Real Deal
Latest build fails to start.

Code: [Select]
Loading blockchain from "/home/slava/.BitSharesXTS/chain"
Starting JSON RPC server on port 44428 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)
------------ error --------------
8 out_of_range_exception: Out of Range
read datastream of length 23 over by 1
    {"method":"read","len":23,"over":1}
    th_a  datastream.cpp:6 throw_datastream_range_error
error unpacking uint8_t
    {"type":"uint8_t"}
    th_a  raw.hpp:440 unpack
optional<fc::exception>
    {"type":"fc::exception"}
    th_a  raw.hpp:164 unpack
Error unpacking field last_error
    {"field":"last_error"}
    th_a  raw.hpp:222 operator()
error unpacking bts::net::potential_peer_record
    {"type":"bts::net::potential_peer_record"}

Logged
>>> approve bitcoiners
June 14, 2014, 09:13:39 pm Reply #209

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Re: Dry Run 2: The Real Deal
@bytemaster my public node now has 23 connections from peer db
Logged
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy
June 14, 2014, 09:11:09 pm Reply #208

Offline bytemaster

Re: Dry Run 2: The Real Deal
So I started adding nodes by hand and it would connect.... don't add the same node twice or it will disconnect (known bug)... we are working out why the peer database isn't doing the right thing, but for now this gets me better connected.

(wallet closed) >>> network_add_node "180.153.142.120:8764" add
OK
--- there are now 2 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "162.243.127.243:33933" add
OK
--- there are now 3 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "84.238.140.192:50546" add
OK
--- there are now 4 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "107.170.30.182:48499" add
OK
(wallet closed) >>> network_add_node "107.170.170.214:40767" add
OK
--- there are now 5 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "107.170.211.129:48199" add
OK
--- there are now 6 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "176.9.234.167:39251" add
OK
(wallet closed) >>> network_add_node "107.170.30.182:8764" add
OK
--- there are now 7 active connections to the p2p network
--- in sync with p2p network
(wallet closed) >>> network_add_node "106.185.24.234:48807" add
OK
--- there are now 8 active connections to the p2p network
--- in sync with p2p network
Logged
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.
June 14, 2014, 09:10:38 pm Reply #207

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Re: Dry Run 2: The Real Deal
Quote from: toast on June 14, 2014, 09:07:54 pm
Quote from: alexxy on June 14, 2014, 09:03:23 pm
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?

Was your KID not all lowercase? If so this might have fixed the issue, try now.
https://github.com/BitShares/bitshares_toolkit/pull/284

It was in lower case. So it shouldnt be issue. However i cannot import it. So any possibiliti to check if i use right brainwallet?
Logged
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy
June 14, 2014, 09:07:54 pm Reply #206

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Re: Dry Run 2: The Real Deal
Quote from: alexxy on June 14, 2014, 09:03:23 pm
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?

Was your KID not all lowercase? If so this might have fixed the issue, try now.
https://github.com/BitShares/bitshares_toolkit/pull/284
Logged
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.
June 14, 2014, 09:03:23 pm Reply #205

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Re: Dry Run 2: The Real Deal
Are there any way to import keyhotee id? I always get thet account already registered with different key. I'm sure that brainkey is valid however are there possibility to check it?
Logged
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy
June 14, 2014, 08:28:23 pm Reply #204

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Re: Dry Run 2: The Real Deal
Quote from: bitcoinerS on June 14, 2014, 08:26:49 pm
Quote from: toast on June 14, 2014, 08:16:55 pm
Quote from: bitcoinerS on June 14, 2014, 08:16:06 pm
Quote from: toast on June 14, 2014, 08:09:25 pm
@bitcoinerS @Trog   Eric is working on this exact issue right now. If you want a list of nodes to connect to for now you can use "network_list_potential_peers"

Code: [Select]
>>> network_list_potential_peers
Error: invalid command "network_list_potential_peers"


Are you up to date?

Code: [Select]
>>> about
{
  "bitshares_toolkit_revision": "096d7a830d80c7911e845eb9c3e5f05656444e24",
  "bitshares_toolkit_revision_age": "2 hours ago",
  "fc_revision": "eab346121d1e6a2f52246e84b503907d8ec705f1",
  "fc_revision_age": "46 hours ago",
  "compile_date": "compiled on Jun 14 2014 at 20:25:16"
}

You're not up to date. You can also check using github or just by trying to pull.
Logged
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.
Pages: 1 ... 21 22 23 24 25 26 27 [28] 29 30 31 32 33 34 35 ... 42   Go Up
« previous next »
 

Page created in 0.02 seconds with 18 queries.