BitShares Forum

Main => General Discussion => Topic started by: bytemaster on May 25, 2014, 03:44:14 am

Title: [OVER] New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 03:44:14 am
I have launched a new test seed node that is running the latest p2p code.  Blocks are being produced by the default delegates.

If you are a Mac OS X user you can download the test client:

Download:
http://bitshares.org/documentation/xts_client_osx
and
https://github.com/BitShares/bitshares_toolkit/blob/master/tests/genesis.dat

And place them in the same directory...

chmod +x ./xts_client_osx

Then run ./xts_client_osx

Code: [Select]
>>> wallet_create  yourname
[enter password]
[enter password again]

>>> wallet_create_receive_account "from_bytemaster"
"XTS2mqExXN83xckVnooXZBz4kAiEofjtU6QCB8ATKbkUg7QhyArxwRAenAHkibTHQspxmwMKqbGzDXcbvfJzxwFNqiH69gcNc"

Post the address to the forum and I (or one of the devs) will send you some funds...

Instructions for starting the web interface will be forth coming.   More detailed docs are under production.   

Enjoy.

To send funds to someone do this:

Quote
wallet_create_sending_address "to_bytemaster" XTS2mqExXN83xckVnooXZBz4kAiEofjtU6QCB8ATKbkUg7QhyArxwRAenAHkibTHQspxmwMKqbGzDXcbvfJzxwFNqiH69gcNc

wallet_transfer 888899999  "to_bytemaster"
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: crazybit on May 25, 2014, 04:09:53 am
my acccount: XTS2F61RsDFxsacvZZ3tuNUDcipVAkd5BsvoKZHSbHh8LS4xKhQt6E9AhfWkYo2eeZVDFQAp57dheRVq3NzsbT3kCmfZnkEHj
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 25, 2014, 04:19:01 am
Does it work for Windows and Linux?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: crazybit on May 25, 2014, 04:23:25 am
Does it work for Windows and Linux?
BM's version should only work on Mac, i build it myself on Win7
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 04:37:44 am
Does it work for Windows and Linux?

Build instructions in top level of repo
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: Nimrod on May 25, 2014, 04:40:49 am
XTS2icppbHz3b5PTZhY5DXTEsKeQ3yVibwNgybk1NwhgFaR9iZFwky87LNdwQYw4c7mR7A2942HRHSsuh37EwNBZm9PtvrAjY

Thanks~ :)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cgafeng on May 25, 2014, 04:46:05 am
XTS3GQUUYhvCb3moBBHYPV78YRuCvmq6rVVG7F8GgabWNE7XFUMBa1M9vg2SahjCgXGtpaupdAC2VPhTY9sgD3bj37b8gn3Zv
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:56:15 am
my acccount: XTS2F61RsDFxsacvZZ3tuNUDcipVAkd5BsvoKZHSbHh8LS4xKhQt6E9AhfWkYo2eeZVDFQAp57dheRVq3NzsbT3kCmfZnkEHj

Sent you some funds... enjoy.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:57:25 am
XTS2icppbHz3b5PTZhY5DXTEsKeQ3yVibwNgybk1NwhgFaR9iZFwky87LNdwQYw4c7mR7A2942HRHSsuh37EwNBZm9PtvrAjY

Thanks~ :)

Sent you some funds.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:58:31 am
XTS3GQUUYhvCb3moBBHYPV78YRuCvmq6rVVG7F8GgabWNE7XFUMBa1M9vg2SahjCgXGtpaupdAC2VPhTY9sgD3bj37b8gn3Zv

Sent you some funds.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 05:31:05 am
There is a known bug on wallet_get_transaction_history_summary where it will crash. 

We will fix that in the morning, in the mean time wallet_get_transaction_history still works.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cgafeng on May 25, 2014, 05:47:11 am
the client crash suddenly while i did nothing.
the last log is:
Code: [Select]
2611357ms       th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:605
2619622ms       th_a          accept_loop ] accepted inbound connection from 104.35.126.165:5678 node.cpp:1735
2619633ms       th_a    accept_connection ] established inbound connection from 104.35.126.165:5678 node.cpp:418
2619850ms       th_a     on_hello_message ] Received a hello_message from peer 104.35.126.165:5678, sending reply to accept connection node.cpp:984
2620066ms       th_a on_address_request_m ] Received an address request message node.cpp:1066
2620321ms       th_a         get_item_ids ] attempting to fetch last_seen 288 client.cpp:220

there is a assert, i see, it can't get through in debug model.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 25, 2014, 06:42:51 am
heh.

XTS2soutSpwhjLzSs3tcsXyLFaqePcHjfZrA3r1aC9YSghphpXvGURJxVJEJTHLT53XgfDsbw6AiBD3MmPHHgpLdN89HQDT4F
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 25, 2014, 07:42:04 am
XTS2QfqbcG4U2rtBGof3pbmK5jkFhmo3WCsGztRUz5yktQQ2Gdu6mAnjpv3QkqThnETHXjiPnxWfm59bDCAwXRcKZFXTw9ajB
thanks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: crazybit on May 25, 2014, 08:06:38 am
any one can connect to the test network? seems i can not connect to test network and download the blockchain.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 25, 2014, 08:45:11 am
any one can connect to the test network? seems i can not connect to test network and download the blockchain.

Yes, I can
Code: [Select]
Attempting to map UPNP port...
UPnP: ExternalIPAddress = 192.168.1.2
UPnP Port Mapping successful.
Attempting to connect to peer 107.170.30.182:5678

alt (locked) >>> network_get_connection_count
1

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 25, 2014, 11:18:16 am
XTS2PNoTDtXmt1SYe5oJ58RvXJ6rHzTTA17JnBQWd1b5PsvpKxD1hotQTMjcpTSF83vpWLhLEcnH1bFXGtY2YHSUSMUcc8VmW

Thanks in advance.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 25, 2014, 12:03:52 pm
Can anyone share your get_info? I can see the following in my log but 0 connections in get_info.

177019ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                 node.cpp:561
177020ms       th_a display_current_conn ] Currently have 1 of 8 connections                    node.cpp:861
177020ms       th_a display_current_conn ]    my id is 281b1a748c848d873d54b8a6ec5832cd4a5fbe70                 node.cpp:862
177020ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870


(wallet closed) >>> get_info
{
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 0,
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0,
  "random_seed": "0000000000000000000000000000000000000000000000000000000000000000",
  "connections": 0,
  "rpc_port": 0,
  "_node_id": "281b1a748c848d873d54b8a6ec5832cd4a5fbe70",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "f82d0df05f66af9fcbb4035c909046aa9202daa1"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:53:38 pm
XTS2QfqbcG4U2rtBGof3pbmK5jkFhmo3WCsGztRUz5yktQQ2Gdu6mAnjpv3QkqThnETHXjiPnxWfm59bDCAwXRcKZFXTw9ajB
thanks

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:54:33 pm
heh.

XTS2soutSpwhjLzSs3tcsXyLFaqePcHjfZrA3r1aC9YSghphpXvGURJxVJEJTHLT53XgfDsbw6AiBD3MmPHHgpLdN89HQDT4F

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:55:28 pm
XTS2kzPMvhYGenhywjZb1ka9CJusNvjpcwcKSWYRo93hz7hWXcDGm3r4aBp25VqMJ2bRc45hTSdWwdG8FJYaxK2FpeMZpCQk3

~cheers

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:57:15 pm
the client crash suddenly while i did nothing.
the last log is:
Code: [Select]
2611357ms       th_a p2p_network_connect_ ] I don't need any more connections, waiting forever until something changes node.cpp:605
2619622ms       th_a          accept_loop ] accepted inbound connection from 104.35.126.165:5678 node.cpp:1735
2619633ms       th_a    accept_connection ] established inbound connection from 104.35.126.165:5678 node.cpp:418
2619850ms       th_a     on_hello_message ] Received a hello_message from peer 104.35.126.165:5678, sending reply to accept connection node.cpp:984
2620066ms       th_a on_address_request_m ] Received an address request message node.cpp:1066
2620321ms       th_a         get_item_ids ] attempting to fetch last_seen 288 client.cpp:220

there is a assert, i see, it can't get through in debug model.

There is a bug in the P2P networking code where the server gets full despite not having enough connections.  There is a chance that when you attempted to reconnect it rejected you.   I have filed a bug report for Eric to look into.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:58:20 pm
XTS2PNoTDtXmt1SYe5oJ58RvXJ6rHzTTA17JnBQWd1b5PsvpKxD1hotQTMjcpTSF83vpWLhLEcnH1bFXGtY2YHSUSMUcc8VmW

Thanks in advance.

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:58:50 pm
Quote
getinfo
{
  "balance": 56512282175300,
  "unlocked_until": "20170725T223345.651143",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 1150,
  "current_share_supply": 79999998199996,
  "shares_per_bip": 0,
  "random_seed": "1a6ac897417139b923baaf3d74b7a064be280fed000000000000000000000000",
  "connections": 3,
  "rpc_port": 0,
  "_node_id": "281be94560251432c73c93f4fe08b61af6931a95",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "b8d61f18221fb6adfa30d1213a5ea43957c86ad0"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 12:59:56 pm
Anyone else running a public node?   
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 25, 2014, 01:06:17 pm
XTS2p8GAAXBFgiDnZKLHAs5Sqa4Mkf13bkv6VLXKg29CZwSzKHjkVeMgTtajr6k6C5ruCgWLRLhAMymY6RzzHaSqTvYNRTzLS

please ;)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 25, 2014, 01:20:13 pm
Anyone else running a public node?   

I started a bts_server but it quited soon. Then I can't find any bts_**.exe more than bitshares_client.exe on windows.

In summary, I guess not me.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 01:40:14 pm
Anyone else running a public node?   

I started a bts_server but it quited soon. Then I can't find any bts_**.exe more than bitshares_client.exe on windows.

In summary, I guess not me.

BTS_SERVER is deprecated... if you run bitshares_client on a computer with UPNP or Static IP then others should be able to connect to you directly.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 01:41:03 pm
XTS2p8GAAXBFgiDnZKLHAs5Sqa4Mkf13bkv6VLXKg29CZwSzKHjkVeMgTtajr6k6C5ruCgWLRLhAMymY6RzzHaSqTvYNRTzLS

please ;)

Sent funds.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: spartako on May 25, 2014, 01:57:10 pm
XTS2QbbJPxRCd7FRyfCBhg74UeUoioR1gbKjKKCfjhgxiPh1wb7HQmfmUXuLF9AgHcBFQNwx679VGxNaf3wqn62rvDDgUNEhx
thanks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 25, 2014, 02:03:36 pm
Seems i cannot connect to network anymore.. =\
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: Troglodactyl on May 25, 2014, 02:03:53 pm
XTS2fqgzJ14NAEuBQvW3HBqgp7w1n8wjbUAe9ud2QxhcLss25AsS8SngmJYEg6VkL8kUiLWjPZpnZNonPjzWeEFRR8TP4UB6a

72.182.4.161 if you want to try to connect.

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 02:15:39 pm
XTS2QbbJPxRCd7FRyfCBhg74UeUoioR1gbKjKKCfjhgxiPh1wb7HQmfmUXuLF9AgHcBFQNwx679VGxNaf3wqn62rvDDgUNEhx
thanks

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 02:16:25 pm
XTS2fqgzJ14NAEuBQvW3HBqgp7w1n8wjbUAe9ud2QxhcLss25AsS8SngmJYEg6VkL8kUiLWjPZpnZNonPjzWeEFRR8TP4UB6a

72.182.4.161 if you want to try to connect.

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 02:17:00 pm
Seems i cannot connect to network anymore.. =\

I restarted the seed client to clear stale connections... see if it works.   
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 02:18:06 pm
The primary goal of this test is to see if we can keep it going and upgrade it in place with bug fixes. 

Things will likely break as we find bugs (like the stale connection issue)... but so long as the blockchain stays up and continues to grow we will be proving the most important thing.

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 25, 2014, 02:26:51 pm
XTS2QfqbcG4U2rtBGof3pbmK5jkFhmo3WCsGztRUz5yktQQ2Gdu6mAnjpv3QkqThnETHXjiPnxWfm59bDCAwXRcKZFXTw9ajB
thanks

Sent
Thx, but I can't see it in balance
Code: [Select]
alt (unlocked) >>> get_info
{
  "balance": 0,
  "unlocked_until": "20140525T142941.432976",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 1324,
  "current_share_supply": 79999997899996,
  "shares_per_bip": 0,
  "random_seed": "52bb75730ee15aef917e0b4d498346c6183ed955000000000000000000000000",
  "connections": 1,
  "rpc_port": 5679,
  "_node_id": "9e11ccff58f61ab97c70b37169478a3974dc83a2",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "e97f044371cb786dea277d4a803c10cbdb9329f5"
}
alt (unlocked) >>> wallet_list_receive_accounts
[[
    "from_bytemaster",
    "XTS2QfqbcG4U2rtBGof3pbmK5jkFhmo3WCsGztRUz5yktQQ2Gdu6mAnjpv3QkqThnETHXjiPnxWfm59bDCAwXRcKZFXTw9ajB"
  ]
]
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 25, 2014, 02:37:07 pm
The primary goal of this test is to see if we can keep it going and upgrade it in place with bug fixes. 

Things will likely break as we find bugs (like the stale connection issue)... but so long as the blockchain stays up and continues to grow we will be proving the most important thing.

Should pts and keyhotee import works? (also should i see it in my balance in case of import?)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 25, 2014, 02:59:09 pm
I'm having the below errors in log. Can anyone hint what I should do?

3437194ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:619
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:227
3440195ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5679                  node.cpp:1850
3440195ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:1873
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:168
3440195ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                      tcp_socket.cpp:105
3440195ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:751
3440196ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
3440196ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
3440196ms       th_a display_current_conn ]    my id is f8911c7113ce5c4cdd1d050358e4cf834df62aa0                        node.cpp:862
3440196ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                      node.cpp:870
3440196ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                      node.cpp:573
3440196ms       th_a p2p_network_connect_ ] Last attempt was 47 seconds ago (disposition: last_connection_failed)                     node.cpp:573

btw, my uname -r is:
2.6.32-5-amd64
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: spartako on May 25, 2014, 03:01:41 pm
XTS2QbbJPxRCd7FRyfCBhg74UeUoioR1gbKjKKCfjhgxiPh1wb7HQmfmUXuLF9AgHcBFQNwx679VGxNaf3wqn62rvDDgUNEhx
thanks

Sent

Thanks, I received funds.

I tried to send some bts to an other account but I get this error:
(unlocked) >>> wallet_transfer 10000 clientb
bad_cast
Invalid cast from type '5' to Object
    {"type":5}
    th_a  variant.cpp:498 get_object

    {"command":"wallet_transfer"}
    th_a  cli.cpp:396 execute_command


Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 25, 2014, 03:30:06 pm
XTS2p8GAAXBFgiDnZKLHAs5Sqa4Mkf13bkv6VLXKg29CZwSzKHjkVeMgTtajr6k6C5ruCgWLRLhAMymY6RzzHaSqTvYNRTzLS

please ;)

Sent funds.

Received successfully. ;D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 25, 2014, 03:32:12 pm
XTS2p8GAAXBFgiDnZKLHAs5Sqa4Mkf13bkv6VLXKg29CZwSzKHjkVeMgTtajr6k6C5ruCgWLRLhAMymY6RzzHaSqTvYNRTzLS

please ;)

Sent funds.

Received successfully. ;D
Can you send some to me as I haven't received fund from BM yet and I need to confirm whether it's caused by my address? Thanks.

default (unlocked) >>> wallet_list_receive_accounts
[[
    "johns",
    "XTS2PNoTDtXmt1SYe5oJ58RvXJ6rHzTTA17JnBQWd1b5PsvpKxD1hotQTMjcpTSF83vpWLhLEcnH1bFXGtY2YHSUSMUcc8VmW"
  ]
]
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:39:30 pm
XTS2p8GAAXBFgiDnZKLHAs5Sqa4Mkf13bkv6VLXKg29CZwSzKHjkVeMgTtajr6k6C5ruCgWLRLhAMymY6RzzHaSqTvYNRTzLS

please ;)

Sent funds.

Received successfully. ;D
Can you send some to me as I haven't received fund from BM yet and I need to confirm whether it's caused by my address? Thanks.

default (unlocked) >>> wallet_list_receive_accounts
[[
    "johns",
    "XTS2PNoTDtXmt1SYe5oJ58RvXJ6rHzTTA17JnBQWd1b5PsvpKxD1hotQTMjcpTSF83vpWLhLEcnH1bFXGtY2YHSUSMUcc8VmW"
  ]
]

I sent you some funds.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:41:18 pm
XTS2QbbJPxRCd7FRyfCBhg74UeUoioR1gbKjKKCfjhgxiPh1wb7HQmfmUXuLF9AgHcBFQNwx679VGxNaf3wqn62rvDDgUNEhx
thanks

Sent

Thanks, I received funds.

I tried to send some bts to an other account but I get this error:
(unlocked) >>> wallet_transfer 10000 clientb
bad_cast
Invalid cast from type '5' to Object
    {"type":5}
    th_a  variant.cpp:498 get_object

    {"command":"wallet_transfer"}
    th_a  cli.cpp:396 execute_command

Could you tell me if the following works:

(unlocked) >>> wallet_transfer 10000 clientb {}

I think this may be a known intermittent bug with the parsing of the CLI...   

See: https://github.com/BitShares/bitshares_toolkit/issues/104
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: spartako on May 25, 2014, 04:43:49 pm
XTS2QbbJPxRCd7FRyfCBhg74UeUoioR1gbKjKKCfjhgxiPh1wb7HQmfmUXuLF9AgHcBFQNwx679VGxNaf3wqn62rvDDgUNEhx
thanks

Sent

Thanks, I received funds.

I tried to send some bts to an other account but I get this error:
(unlocked) >>> wallet_transfer 10000 clientb
bad_cast
Invalid cast from type '5' to Object
    {"type":5}
    th_a  variant.cpp:498 get_object

    {"command":"wallet_transfer"}
    th_a  cli.cpp:396 execute_command

Could you tell me if the following works:

(unlocked) >>> wallet_transfer 10000 clientb {}


I think this may be a known intermittent bug with the parsing of the CLI...

Yes, it works!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 04:44:17 pm
I'm having the below errors in log. Can anyone hint what I should do?

3437194ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:619
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:227
3440195ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5679                  node.cpp:1850
3440195ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:1873
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:168
3440195ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                      tcp_socket.cpp:105
3440195ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:751
3440196ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
3440196ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
3440196ms       th_a display_current_conn ]    my id is f8911c7113ce5c4cdd1d050358e4cf834df62aa0                        node.cpp:862
3440196ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                      node.cpp:870
3440196ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                      node.cpp:573
3440196ms       th_a p2p_network_connect_ ] Last attempt was 47 seconds ago (disposition: last_connection_failed)                     node.cpp:573

btw, my uname -r is:
2.6.32-5-amd64

I'll have Eric look into this one...  posting an issue for it here https://github.com/BitShares/bitshares_toolkit/issues/131
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 05:03:27 pm
The primary goal of this test is to see if we can keep it going and upgrade it in place with bug fixes. 

Things will likely break as we find bugs (like the stale connection issue)... but so long as the blockchain stays up and continues to grow we will be proving the most important thing.

Should pts and keyhotee import works? (also should i see it in my balance in case of import?)

I believe it's using feb 28 snapshot but without all the keyhotee names

edit: actually I have no idea
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 05:15:18 pm
To protect private keys furring testing it does not use any snapshot.


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 25, 2014, 06:52:35 pm
can someone provide list of nodes?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 06:58:45 pm
Code: [Select]
107.170.30.182:5678
that's bitshares.org node

we just reset the network, don't panic
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 07:03:13 pm
testnet is DOWN, resetting shortly
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 07:43:55 pm
New OS X binaries have been uploaded..... this build fixes some of the following bugs:

 a) random seed mixup between sha256 and ripemd160
 b) hierarchical wallets had a major security issue
 c) wallet loading is more robust regarding non-cricital errors
 d) pretty print of transaction history works (partially)
 e) further insights allowed me to only use the public key, no need for extended keys for registered names.... this changed the blockchain structure. 

As a result of the hierarchical wallet issue all addresses from earlier in the test are invalid :(   

Chain is up and running again on block 18...
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 25, 2014, 07:50:51 pm
New OS X binaries have been uploaded..... this build fixes some of the following bugs:

 a) random seed mixup between sha256 and ripemd160
 b) hierarchical wallets had a major security issue
 c) wallet loading is more robust regarding non-cricital errors
 d) pretty print of transaction history works (partially)
 e) further insights allowed me to only use the public key, no need for extended keys for registered names.... this changed the blockchain structure. 

As a result of the hierarchical wallet issue all addresses from earlier in the test are invalid :(   

Chain is up and running again on block 18...

I cannot connect with binaries recently buit from git master

Code: [Select]
2959316ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1850
2959316ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:1873
2959316ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:751
2959317ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
2959317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2959317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2959317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2959317ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                        node.cpp:573
2959317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2959317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2959317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2959317ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:600
2959317ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                  node.cpp:645
2959317ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                    node.cpp:681
2959317ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)                    node.cpp:702
2966316ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194926                        client.cpp:76
2968316ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194928                        client.cpp:76
2970141ms       th_a       try_upgrade_db ] Database /home/alexxy/.BitSharesXTS/alexxy is not upgradeable                       upgrade_leveldb.cpp:44
2970142ms       th_a               unlock ] unlock: 300  37792288                       wallet.cpp:1033
2970414ms       th_a                 lock ] lock 37792288                       wallet.cpp:1019
2970414ms       th_a               unlock ] unlock: 300  37792288                       wallet.cpp:1033
2970414ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194930                        client.cpp:76
2972414ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194932                        client.cpp:76
2974317ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
2974317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2974317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2974317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2974317ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)                       node.cpp:573
2974317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2974317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2974317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2974317ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:600
2974415ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194934                        client.cpp:76
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 08:14:40 pm
strange, works fine for me.

Did you nuke the ~/.BitSharesXTS directory after the pull?


new testnet up, ask again for test shares
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 08:15:04 pm
New OS X binaries have been uploaded..... this build fixes some of the following bugs:

 a) random seed mixup between sha256 and ripemd160
 b) hierarchical wallets had a major security issue
 c) wallet loading is more robust regarding non-cricital errors
 d) pretty print of transaction history works (partially)
 e) further insights allowed me to only use the public key, no need for extended keys for registered names.... this changed the blockchain structure. 

As a result of the hierarchical wallet issue all addresses from earlier in the test are invalid :(   

Chain is up and running again on block 18...

I cannot connect with binaries recently buit from git master

Code: [Select]
2959316ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1850
2959316ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:1873
2959316ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:751
2959317ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
2959317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2959317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2959317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2959317ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                        node.cpp:573
2959317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2959317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2959317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2959317ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:600
2959317ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                  node.cpp:645
2959317ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                    node.cpp:681
2959317ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)                    node.cpp:702
2966316ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194926                        client.cpp:76
2968316ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194928                        client.cpp:76
2970141ms       th_a       try_upgrade_db ] Database /home/alexxy/.BitSharesXTS/alexxy is not upgradeable                       upgrade_leveldb.cpp:44
2970142ms       th_a               unlock ] unlock: 300  37792288                       wallet.cpp:1033
2970414ms       th_a                 lock ] lock 37792288                       wallet.cpp:1019
2970414ms       th_a               unlock ] unlock: 300  37792288                       wallet.cpp:1033
2970414ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194930                        client.cpp:76
2972414ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194932                        client.cpp:76
2974317ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
2974317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2974317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2974317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2974317ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)                       node.cpp:573
2974317ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
2974317ms       th_a display_current_conn ]    my id is 51406ffa8c07729559310ab2460ef9acbe84c25e                        node.cpp:862
2974317ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:870
2974317ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:600
2974415ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140525T194934                        client.cpp:76

You will have to delete ~/.BitSharesXTS/chain and restart...
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: denkhaus on May 25, 2014, 08:15:43 pm
plz send me some shares:

XTS2fwD3HF4xo1VuDCarbPTkxXVcfZGTd49acd3NRvPUpik4RYVA9ofkCY9BMtXbswfGamoNtvKjZhys3CcbEBG2NkLHd144z

thanks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 08:16:42 pm
plz send me some shares:

XTS2fwD3HF4xo1VuDCarbPTkxXVcfZGTd49acd3NRvPUpik4RYVA9ofkCY9BMtXbswfGamoNtvKjZhys3CcbEBG2NkLHd144z

thanks

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: Troglodactyl on May 25, 2014, 08:32:54 pm
I'm showing 2 connections, but on block 7:

Code: [Select]
(wallet closed) >>> get_info
{
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 7,
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0,
  "random_seed": "3bcace0f27b9d56d6e6fd9ac79ddf1aed0c30e1e000000000000000000000000",
  "connections": 2,
  "rpc_port": 5679,
  "_node_id": "ee2d8e5611b6515825615b3f243ad6880d0f47e7",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "b8d61f18221fb6adfa30d1213a5ea43957c86ad0"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 09:44:17 pm
I'm showing 2 connections, but on block 7:

Code: [Select]
(wallet closed) >>> get_info
{
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 7,
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0,
  "random_seed": "3bcace0f27b9d56d6e6fd9ac79ddf1aed0c30e1e000000000000000000000000",
  "connections": 2,
  "rpc_port": 5679,
  "_node_id": "ee2d8e5611b6515825615b3f243ad6880d0f47e7",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "b8d61f18221fb6adfa30d1213a5ea43957c86ad0"
}

You're using an old build I think
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 09:44:33 pm
also delete ~/.BitSharesXTS
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 25, 2014, 10:00:08 pm
I'm showing 2 connections, but on block 7:

Code: [Select]
(wallet closed) >>> get_info
{
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "version": 100,
  "protocolversion": 100,
  "walletversion": 100,
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 7,
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0,
  "random_seed": "3bcace0f27b9d56d6e6fd9ac79ddf1aed0c30e1e000000000000000000000000",
  "connections": 2,
  "rpc_port": 5679,
  "_node_id": "ee2d8e5611b6515825615b3f243ad6880d0f47e7",
  "_fc_revision": "9f6b52eac2221f398896b318bd46824ee54623e0",
  "_bitshares_toolkit_revision": "b8d61f18221fb6adfa30d1213a5ea43957c86ad0"
}

You're using an old build I think

bitshares revision: 4924159edf12bf767d9a7ca544ac78ca3c52ec17
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: spartako on May 25, 2014, 10:13:49 pm
XTS3CR1eDU98xvB95rkQtEF1CT77cRrFnKsbVASozQ66c6vWFVJW1Nf2TZU58Rf7YYp9YREnxuaymKLAiDhrTVHKmatsF5xxr
thanks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 25, 2014, 10:48:59 pm
XTS3CR1eDU98xvB95rkQtEF1CT77cRrFnKsbVASozQ66c6vWFVJW1Nf2TZU58Rf7YYp9YREnxuaymKLAiDhrTVHKmatsF5xxr
thanks

sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 25, 2014, 11:48:25 pm
also delete ~/.BitSharesXTS
new address:
XTS2D6nAWbpBbVzbHY9HD6a3uhyhDT5HyJonJ5Wm4KwaY3AkdJ2ZYXxrJuroieQQBxVZSP93wChCQv1BKJdCBZUgR6hfqBNfT

Thx
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 26, 2014, 12:13:08 am
also delete ~/.BitSharesXTS
new address:
XTS2D6nAWbpBbVzbHY9HD6a3uhyhDT5HyJonJ5Wm4KwaY3AkdJ2ZYXxrJuroieQQBxVZSP93wChCQv1BKJdCBZUgR6hfqBNfT

Thx

sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 26, 2014, 12:13:49 am
XTS2wmPTP3dPSYWaBh2Nr5khM9rAwjAN3MVp4d7BuR5HAjmV3xGSzsK31npzQJ3grCm86MC2GeRmRWPpWWC7LNWw4puZmeJSj

Thanks.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 26, 2014, 12:15:10 am
XTS2wmPTP3dPSYWaBh2Nr5khM9rAwjAN3MVp4d7BuR5HAjmV3xGSzsK31npzQJ3grCm86MC2GeRmRWPpWWC7LNWw4puZmeJSj

Thanks.

sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 12:35:23 am
very cool.
It's so fast just like central server
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 26, 2014, 12:46:43 am
very cool.
It's so fast just like central server

DPOS  +5%
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gyhy on May 26, 2014, 01:23:29 am
 +5%
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 02:05:54 am
bitshare_client is killed by kernel because of out of memory.
I think I am doing nothing when it happened.
my os is mint16 based ubuntu 1310

Code: [Select]
[79016.294101] bitshares_clien invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
[79016.294105] bitshares_clien cpuset=/ mems_allowed=0
[79016.294108] CPU: 3 PID: 13199 Comm: bitshares_clien Tainted: GF          O 3.11.0-12-generic #19-Ubuntu
[79016.294109] Hardware name: LENOVO 2352A31/2352A31, BIOS G7ET60WW (2.02 ) 09/11/2012
[79016.294111]  0000000000000000 ffff880100df9a60 ffffffff816e547a 00000000000280da
[79016.294114]  ffff880100df9ad0 ffffffff816e0556 0000000000064589 0000000001320122
[79016.294116]  0000000000000000 0000000000000000 ffff8800522c1770 0000000000000000
[79016.294118] Call Trace:
[79016.294124]  [<ffffffff816e547a>] dump_stack+0x45/0x56
[79016.294126]  [<ffffffff816e0556>] dump_header+0x7f/0x1c2
[79016.294129]  [<ffffffff81142299>] oom_kill_process+0x1a9/0x310
[79016.294132]  [<ffffffff812db7c5>] ? security_capable_noaudit+0x15/0x20
[79016.294135]  [<ffffffff811429d4>] out_of_memory+0x414/0x450
[79016.294138]  [<ffffffff811481b0>] __alloc_pages_nodemask+0x870/0x920
[79016.294141]  [<ffffffff8118593a>] alloc_pages_vma+0x9a/0x140
[79016.294144]  [<ffffffff81166ebb>] handle_pte_fault+0x73b/0xab0
[79016.294146]  [<ffffffff8116440a>] ? __pte_alloc+0x9a/0x140
[79016.294148]  [<ffffffff81167fd9>] handle_mm_fault+0x299/0x670
[79016.294151]  [<ffffffff816e9962>] ? down_write+0x12/0x30
[79016.294153]  [<ffffffff81161c2b>] ? anon_vma_interval_tree_insert+0x8b/0x90
[79016.294156]  [<ffffffff816f05f6>] __do_page_fault+0x156/0x540
[79016.294158]  [<ffffffff8116cc89>] ? vma_merge+0x229/0x330
[79016.294160]  [<ffffffff8116dda9>] ? do_brk+0x209/0x330
[79016.294162]  [<ffffffff816f0a0c>] do_page_fault+0x2c/0x50
[79016.294164]  [<ffffffff816ece18>] page_fault+0x28/0x30
[79016.294166] Mem-Info:
[79016.294167] Node 0 DMA per-cpu:
[79016.294168] CPU    0: hi:    0, btch:   1 usd:   0
[79016.294169] CPU    1: hi:    0, btch:   1 usd:   0
[79016.294170] CPU    2: hi:    0, btch:   1 usd:   0
[79016.294171] CPU    3: hi:    0, btch:   1 usd:   0
[79016.294172] Node 0 DMA32 per-cpu:
[79016.294173] CPU    0: hi:  186, btch:  31 usd:   1
[79016.294174] CPU    1: hi:  186, btch:  31 usd:  36
[79016.294175] CPU    2: hi:  186, btch:  31 usd: 172
[79016.294176] CPU    3: hi:  186, btch:  31 usd:  55
[79016.294177] Node 0 Normal per-cpu:
[79016.294178] CPU    0: hi:  186, btch:  31 usd:   2
[79016.294179] CPU    1: hi:  186, btch:  31 usd:  59
[79016.294179] CPU    2: hi:  186, btch:  31 usd: 156
[79016.294180] CPU    3: hi:  186, btch:  31 usd:  56
[79016.294183] active_anon:534535 inactive_anon:211789 isolated_anon:64
[79016.294183]  active_file:58 inactive_file:189 isolated_file:0
[79016.294183]  unevictable:0 dirty:0 writeback:5101 unstable:0
[79016.294183]  free:21393 slab_reclaimable:7889 slab_unreclaimable:8449
[79016.294183]  mapped:145908 shmem:52148 pagetables:7423 bounce:0
[79016.294183]  free_cma:0
[79016.294185] Node 0 DMA free:14816kB min:284kB low:352kB high:424kB active_anon:428kB inactive_anon:640kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15900kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:160 all_unreclaimable? yes
[79016.294189] lowmem_reserve[]: 0 2699 3635 3635
[79016.294191] Node 0 DMA32 free:53516kB min:49964kB low:62452kB high:74944kB active_anon:1721588kB inactive_anon:430192kB active_file:0kB inactive_file:148kB unevictable:0kB isolated(anon):256kB isolated(file):0kB present:2845884kB managed:2767364kB mlocked:0kB dirty:0kB writeback:7432kB mapped:571188kB shmem:155924kB slab_reclaimable:9148kB slab_unreclaimable:12292kB kernel_stack:1080kB pagetables:14776kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:10992 all_unreclaimable? yes
[79016.294194] lowmem_reserve[]: 0 0 936 936
[79016.294196] Node 0 Normal free:17240kB min:17328kB low:21660kB high:25992kB active_anon:416124kB inactive_anon:416324kB active_file:264kB inactive_file:608kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1021952kB managed:958820kB mlocked:0kB dirty:0kB writeback:12972kB mapped:12444kB shmem:52668kB slab_reclaimable:22408kB slab_unreclaimable:21488kB kernel_stack:2712kB pagetables:14916kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:11944 all_unreclaimable? yes
[79016.294199] lowmem_reserve[]: 0 0 0 0
[79016.294201] Node 0 DMA: 2*4kB (UM) 1*8kB (U) 1*16kB (M) 0*32kB 3*64kB (UM) 2*128kB (UM) 2*256kB (UM) 1*512kB (M) 1*1024kB (U) 2*2048kB (MR) 2*4096kB (M) = 14816kB
[79016.294209] Node 0 DMA32: 1909*4kB (UEM) 1098*8kB (UEM) 692*16kB (UE) 531*32kB (UEM) 81*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB (R) = 53764kB
[79016.294216] Node 0 Normal: 548*4kB (UE) 295*8kB (UE) 175*16kB (UE) 122*32kB (UEM) 32*64kB (UEM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB (R) = 17400kB
[79016.294223] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[79016.294224] 68981 total pagecache pages
[79016.294225] 16519 pages in swap cache
[79016.294226] Swap cache stats: add 256445, delete 239926, find 83/129
[79016.294227] Free swap  = 0kB
[79016.294227] Total swap = 1023996kB
[79016.301235] 976383 pages RAM
[79016.301241] 170952 pages reserved
[79016.301245] 1118820 pages shared
[79016.301248] 729408 pages non-shared
[79016.301252] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
[79016.301262] [  382]     0   382     4330       16      13       27             0 upstart-udev-br
[79016.301268] [  388]     0   388    10762       38      23      236         -1000 systemd-udevd
[79016.301274] [  612]     0   612     3848       29      13       44             0 upstart-socket-
[79016.301276] [  673]     0   673     4811       13      15       49             0 rpcbind
[79016.301278] [  823]     0   823     3818       32      12       27             0 upstart-file-br
[79016.301279] [  826]   101   826    61866       16      23       69             0 rsyslogd
[79016.301281] [  830]   102   830     7857      199      20      141             0 dbus-daemon
[79016.301283] [  849]     0   849    20871       94      47      121             0 modem-manager
[79016.301284] [  873]     0   873     9264       14      23       86             0 systemd-logind
[79016.301287] [  884]     0   884     4816       15      14       82             0 bluetoothd
[79016.301289] [  903]   109   903     8088       41      21       39             0 avahi-daemon
[79016.301290] [  905]   109   905     8057       17      20       47             0 avahi-daemon
[79016.301292] [  923]     0   923    64953      231      58      164             0 NetworkManager
[79016.301293] [  930]     0   930    68058      108      35      351             0 polkitd
[79016.301295] [  933]   112   933    73159      182      43      161             0 colord
[79016.301297] [  950]     0   950    17735       29      37      188             0 cups-browsed
[79016.301298] [  956]     0   956    32120       93      63      205             0 smbd
[79016.301300] [  958]     0   958    32249       97      61      222             0 smbd
[79016.301301] [ 1163]     0  1163     4377       12      12       41             0 getty
[79016.301303] [ 1166]     0  1166     4377       12      13       40             0 getty
[79016.301304] [ 1176]     0  1176     4377       12      12       40             0 getty
[79016.301306] [ 1177]     0  1177     4377       12      12       41             0 getty
[79016.301308] [ 1180]     0  1180     4377       12      13       41             0 getty
[79016.301309] [ 1215]     0  1215    15273       15      32      161         -1000 sshd
[79016.301311] [ 1220]     0  1220     1160        3       9       66             0 acpid
[79016.301313] [ 1238]     0  1238     6451       27      18       52             0 cron
[79016.301314] [ 1243]     0  1243    33645       20      65      253             0 mdm
[79016.301316] [ 1254]     0  1254     4790       38      14       30             0 irqbalance
[79016.301317] [ 1350]     0  1350    65632       21      96      377             0 mdm
[79016.301319] [ 1357]     0  1357    96078    17041     149     4812             0 Xorg
[79016.301321] [ 1361]   116  1361    72765       61      53      910             0 murmurd
[79016.301322] [ 1397]     0  1397     4377       12      13       41             0 getty
[79016.301324] [ 1421]   114  1421     6111        0      17       72             0 dbus-launch
[79016.301325] [ 1423]   114  1423     7595        0      19       75             0 dbus-daemon
[79016.301327] [ 1684]  1000  1684    55172       90      36      102             0 gnome-keyring-d
[79016.301329] [ 1689]     0  1689   523483      165      58      103             0 console-kit-dae
[79016.301330] [ 1760]  1000  1760    94624      302      87      462             0 cinnamon-sessio
[79016.301332] [ 1883]  1000  1883     3156        7       9       73             0 ssh-agent
[79016.301333] [ 1886]  1000  1886     6111        0      16       72             0 dbus-launch
[79016.301335] [ 1887]  1000  1887     7948      124      19      190             0 dbus-daemon
[79016.301337] [ 1929]  1000  1929    72053     4651     135    17025             0 fcitx
[79016.301338] [ 1934]  1000  1934     7794       74      21      128             0 dbus-daemon
[79016.301340] [ 1938]  1000  1938     3258       11      12       24             0 fcitx-dbus-watc
[79016.301341] [ 1940]  1000  1940    84352       47      31       82             0 at-spi-bus-laun
[79016.301343] [ 1944]  1000  1944     7628       75      20       56             0 dbus-daemon
[79016.301344] [ 1947]  1000  1947    31204       69      30       73             0 at-spi2-registr
[79016.301346] [ 1953]  1000  1953   109699      941     100      637             0 notify-osd
[79016.301347] [ 1960]  1000  1960   251721      886     175      921             0 cinnamon-settin
[79016.301349] [ 1966]  1000  1966    48545       70      31       69             0 gvfsd
[79016.301351] [ 1979]  1000  1979    84215        0      33      186             0 gvfsd-fuse
[79016.301352] [ 1989]     0  1989    58225      155      42      130             0 upowerd
[79016.301354] [ 1994]  1000  1994   107663      426      86      219             0 pulseaudio
[79016.301355] [ 1996]   107  1996    42230       29      20       43             0 rtkit-daemon
[79016.301357] [ 2168]     0  2168    69630       21      39      185             0 accounts-daemon
[79016.301358] [ 2174]  1000  2174    97072        0      86      346             0 csd-printer
[79016.301360] [ 2182]  1000  2182    60328       72      83     2258             0 cinnamon-launch
[79016.301361] [ 2184]  1000  2184   434998    10935     298     9238             0 cinnamon
[79016.301363] [ 2192]  1000  2192    55393      284      78      373             0 polkit-gnome-au
[79016.301365] [ 2194]  1000  2194   110737       91      84      582             0 cinnamon-fallba
[79016.301366] [ 2195]  1000  2195   278696     1398     167     1252             0 nemo
[79016.301368] [ 2202]  1000  2202    71948      263      42      192             0 gvfs-udisks2-vo
[79016.301369] [ 2203]  1000  2203   165595      300     114     1367             0 nm-applet
[79016.301371] [ 2206]     0  2206    90695      212      44      323             0 udisksd
[79016.301372] [ 2224]  1000  2224    47271        4      27      143             0 gvfs-mtp-volume
[79016.301374] [ 2233]  1000  2233    70834        0      36      182             0 gvfs-afc-volume
[79016.301376] [ 2238]  1000  2238    50312        0      33      193             0 gvfs-gphoto2-vo
[79016.301377] [ 2248]  1000  2248    13776      101      32      105             0 gconfd-2
[79016.301379] [ 2255]  1000  2255   616847      169     140     1335             0 fcitx-qimpanel
[79016.301380] [ 2257]  1000  2257    87081        0      37      200             0 gvfsd-trash
[79016.301382] [ 2279]  1000  2279    29575        9      27      237             0 gvfsd-metadata
[79016.301383] [ 2293]  1000  2293   105703     1977      96      511             0 cinnamon-screen
[79016.301386] [ 2608]  1000  2608     6462       15      16      624             0 mintupdate-laun
[79016.301387] [ 2643]  1000  2643   158621     1452     125     3335             0 mintUpdate
[79016.301388] [ 4640]  1000  4640   156501     1081     137     1370             0 gnome-terminal
[79016.301390] [ 4647]  1000  4647     3708       11      13       41             0 gnome-pty-helpe
[79016.301392] [ 4648]  1000  4648     6084      227      17      267             0 bash
[79016.301393] [ 4918]     0  4918     8111       24      20      135             0 wpa_supplicant
[79016.301394] [ 4926] 65534  4926     8172        0      21       65             0 dnsmasq
[79016.301396] [ 5055]     0  5055    26773       87      53      155             0 winbindd
[79016.301397] [ 5060]     0  5060    22850       41      45      156             0 nmbd
[79016.301399] [ 5062]     0  5062    26773       82      51      148             0 winbindd
[79016.301400] [ 5808]  1000  5808    44554        9      24      214             0 dconf-service
[79016.301402] [ 5810]  1000  5810   256925      292     365    33412             0 thunderbird
[79016.301404] [ 5851]  1000  5851   218590       16     128      693             0 evolution-sourc
[79016.301405] [ 5857]  1000  5857   196793        0     107      637             0 evolution-addre
[79016.301407] [ 6398]  1000  6398     6060        9      17      482             0 bash
[79016.301408] [ 6760]  1000  6760     6078        9      16      478             0 bash
[79016.301411] [11095]     0 11095     2561       11      10      573             0 dhclient
[79016.301413] [11174]     0 11174     2561       11       8      575             0 dhclient
[79016.301414] [11447]     0 11447    18323       18      39      497             0 cupsd
[79016.301416] [12566]  1000 12566   320082    10114     479    88987             0 firefox
[79016.301417] [12702]  1000 12702   104441      632     166     4633             0 plugin-containe
[79016.301419] [13199]  1000 13199   755285   623195    1374    65791             0 bitshares_clien
[79016.301421] [13664]  1000 13664   574765   141929     542     1432             0 VirtualBox
[79016.301423] [13668]  1000 13668    30181      542      58        0             0 VBoxXPCOMIPCD
[79016.301424] [13673]  1000 13673   158919      929      93       45             0 VBoxSVC
[79016.301426] Out of memory: Kill process 13199 (bitshares_clien) score 579 or sacrifice child
[79016.301428] Killed process 13199 (bitshares_clien) total-vm:3021140kB, anon-rss:2492696kB, file-rss:84kB
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 02:13:56 am
bitshare_client is killed by kernel because of out of memory.
I think I am doing nothing when it happened.
my os is mint16 based ubuntu 1310

Code: [Select]
[79016.294101] bitshares_clien invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0
[79016.294105] bitshares_clien cpuset=/ mems_allowed=0
[79016.294108] CPU: 3 PID: 13199 Comm: bitshares_clien Tainted: GF          O 3.11.0-12-generic #19-Ubuntu
[79016.294109] Hardware name: LENOVO 2352A31/2352A31, BIOS G7ET60WW (2.02 ) 09/11/2012
[79016.294111]  0000000000000000 ffff880100df9a60 ffffffff816e547a 00000000000280da
[79016.294114]  ffff880100df9ad0 ffffffff816e0556 0000000000064589 0000000001320122
[79016.294116]  0000000000000000 0000000000000000 ffff8800522c1770 0000000000000000
[79016.294118] Call Trace:
[79016.294124]  [<ffffffff816e547a>] dump_stack+0x45/0x56
[79016.294126]  [<ffffffff816e0556>] dump_header+0x7f/0x1c2
[79016.294129]  [<ffffffff81142299>] oom_kill_process+0x1a9/0x310
[79016.294132]  [<ffffffff812db7c5>] ? security_capable_noaudit+0x15/0x20
[79016.294135]  [<ffffffff811429d4>] out_of_memory+0x414/0x450
[79016.294138]  [<ffffffff811481b0>] __alloc_pages_nodemask+0x870/0x920
[79016.294141]  [<ffffffff8118593a>] alloc_pages_vma+0x9a/0x140
[79016.294144]  [<ffffffff81166ebb>] handle_pte_fault+0x73b/0xab0
[79016.294146]  [<ffffffff8116440a>] ? __pte_alloc+0x9a/0x140
[79016.294148]  [<ffffffff81167fd9>] handle_mm_fault+0x299/0x670
[79016.294151]  [<ffffffff816e9962>] ? down_write+0x12/0x30
[79016.294153]  [<ffffffff81161c2b>] ? anon_vma_interval_tree_insert+0x8b/0x90
[79016.294156]  [<ffffffff816f05f6>] __do_page_fault+0x156/0x540
[79016.294158]  [<ffffffff8116cc89>] ? vma_merge+0x229/0x330
[79016.294160]  [<ffffffff8116dda9>] ? do_brk+0x209/0x330
[79016.294162]  [<ffffffff816f0a0c>] do_page_fault+0x2c/0x50
[79016.294164]  [<ffffffff816ece18>] page_fault+0x28/0x30
[79016.294166] Mem-Info:
[79016.294167] Node 0 DMA per-cpu:
[79016.294168] CPU    0: hi:    0, btch:   1 usd:   0
[79016.294169] CPU    1: hi:    0, btch:   1 usd:   0
[79016.294170] CPU    2: hi:    0, btch:   1 usd:   0
[79016.294171] CPU    3: hi:    0, btch:   1 usd:   0
[79016.294172] Node 0 DMA32 per-cpu:
[79016.294173] CPU    0: hi:  186, btch:  31 usd:   1
[79016.294174] CPU    1: hi:  186, btch:  31 usd:  36
[79016.294175] CPU    2: hi:  186, btch:  31 usd: 172
[79016.294176] CPU    3: hi:  186, btch:  31 usd:  55
[79016.294177] Node 0 Normal per-cpu:
[79016.294178] CPU    0: hi:  186, btch:  31 usd:   2
[79016.294179] CPU    1: hi:  186, btch:  31 usd:  59
[79016.294179] CPU    2: hi:  186, btch:  31 usd: 156
[79016.294180] CPU    3: hi:  186, btch:  31 usd:  56
[79016.294183] active_anon:534535 inactive_anon:211789 isolated_anon:64
[79016.294183]  active_file:58 inactive_file:189 isolated_file:0
[79016.294183]  unevictable:0 dirty:0 writeback:5101 unstable:0
[79016.294183]  free:21393 slab_reclaimable:7889 slab_unreclaimable:8449
[79016.294183]  mapped:145908 shmem:52148 pagetables:7423 bounce:0
[79016.294183]  free_cma:0
[79016.294185] Node 0 DMA free:14816kB min:284kB low:352kB high:424kB active_anon:428kB inactive_anon:640kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15900kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:160 all_unreclaimable? yes
[79016.294189] lowmem_reserve[]: 0 2699 3635 3635
[79016.294191] Node 0 DMA32 free:53516kB min:49964kB low:62452kB high:74944kB active_anon:1721588kB inactive_anon:430192kB active_file:0kB inactive_file:148kB unevictable:0kB isolated(anon):256kB isolated(file):0kB present:2845884kB managed:2767364kB mlocked:0kB dirty:0kB writeback:7432kB mapped:571188kB shmem:155924kB slab_reclaimable:9148kB slab_unreclaimable:12292kB kernel_stack:1080kB pagetables:14776kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:10992 all_unreclaimable? yes
[79016.294194] lowmem_reserve[]: 0 0 936 936
[79016.294196] Node 0 Normal free:17240kB min:17328kB low:21660kB high:25992kB active_anon:416124kB inactive_anon:416324kB active_file:264kB inactive_file:608kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1021952kB managed:958820kB mlocked:0kB dirty:0kB writeback:12972kB mapped:12444kB shmem:52668kB slab_reclaimable:22408kB slab_unreclaimable:21488kB kernel_stack:2712kB pagetables:14916kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:11944 all_unreclaimable? yes
[79016.294199] lowmem_reserve[]: 0 0 0 0
[79016.294201] Node 0 DMA: 2*4kB (UM) 1*8kB (U) 1*16kB (M) 0*32kB 3*64kB (UM) 2*128kB (UM) 2*256kB (UM) 1*512kB (M) 1*1024kB (U) 2*2048kB (MR) 2*4096kB (M) = 14816kB
[79016.294209] Node 0 DMA32: 1909*4kB (UEM) 1098*8kB (UEM) 692*16kB (UE) 531*32kB (UEM) 81*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB (R) = 53764kB
[79016.294216] Node 0 Normal: 548*4kB (UE) 295*8kB (UE) 175*16kB (UE) 122*32kB (UEM) 32*64kB (UEM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 1*4096kB (R) = 17400kB
[79016.294223] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[79016.294224] 68981 total pagecache pages
[79016.294225] 16519 pages in swap cache
[79016.294226] Swap cache stats: add 256445, delete 239926, find 83/129
[79016.294227] Free swap  = 0kB
[79016.294227] Total swap = 1023996kB
[79016.301235] 976383 pages RAM
[79016.301241] 170952 pages reserved
[79016.301245] 1118820 pages shared
[79016.301248] 729408 pages non-shared
[79016.301252] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
[79016.301262] [  382]     0   382     4330       16      13       27             0 upstart-udev-br
[79016.301268] [  388]     0   388    10762       38      23      236         -1000 systemd-udevd
[79016.301274] [  612]     0   612     3848       29      13       44             0 upstart-socket-
[79016.301276] [  673]     0   673     4811       13      15       49             0 rpcbind
[79016.301278] [  823]     0   823     3818       32      12       27             0 upstart-file-br
[79016.301279] [  826]   101   826    61866       16      23       69             0 rsyslogd
[79016.301281] [  830]   102   830     7857      199      20      141             0 dbus-daemon
[79016.301283] [  849]     0   849    20871       94      47      121             0 modem-manager
[79016.301284] [  873]     0   873     9264       14      23       86             0 systemd-logind
[79016.301287] [  884]     0   884     4816       15      14       82             0 bluetoothd
[79016.301289] [  903]   109   903     8088       41      21       39             0 avahi-daemon
[79016.301290] [  905]   109   905     8057       17      20       47             0 avahi-daemon
[79016.301292] [  923]     0   923    64953      231      58      164             0 NetworkManager
[79016.301293] [  930]     0   930    68058      108      35      351             0 polkitd
[79016.301295] [  933]   112   933    73159      182      43      161             0 colord
[79016.301297] [  950]     0   950    17735       29      37      188             0 cups-browsed
[79016.301298] [  956]     0   956    32120       93      63      205             0 smbd
[79016.301300] [  958]     0   958    32249       97      61      222             0 smbd
[79016.301301] [ 1163]     0  1163     4377       12      12       41             0 getty
[79016.301303] [ 1166]     0  1166     4377       12      13       40             0 getty
[79016.301304] [ 1176]     0  1176     4377       12      12       40             0 getty
[79016.301306] [ 1177]     0  1177     4377       12      12       41             0 getty
[79016.301308] [ 1180]     0  1180     4377       12      13       41             0 getty
[79016.301309] [ 1215]     0  1215    15273       15      32      161         -1000 sshd
[79016.301311] [ 1220]     0  1220     1160        3       9       66             0 acpid
[79016.301313] [ 1238]     0  1238     6451       27      18       52             0 cron
[79016.301314] [ 1243]     0  1243    33645       20      65      253             0 mdm
[79016.301316] [ 1254]     0  1254     4790       38      14       30             0 irqbalance
[79016.301317] [ 1350]     0  1350    65632       21      96      377             0 mdm
[79016.301319] [ 1357]     0  1357    96078    17041     149     4812             0 Xorg
[79016.301321] [ 1361]   116  1361    72765       61      53      910             0 murmurd
[79016.301322] [ 1397]     0  1397     4377       12      13       41             0 getty
[79016.301324] [ 1421]   114  1421     6111        0      17       72             0 dbus-launch
[79016.301325] [ 1423]   114  1423     7595        0      19       75             0 dbus-daemon
[79016.301327] [ 1684]  1000  1684    55172       90      36      102             0 gnome-keyring-d
[79016.301329] [ 1689]     0  1689   523483      165      58      103             0 console-kit-dae
[79016.301330] [ 1760]  1000  1760    94624      302      87      462             0 cinnamon-sessio
[79016.301332] [ 1883]  1000  1883     3156        7       9       73             0 ssh-agent
[79016.301333] [ 1886]  1000  1886     6111        0      16       72             0 dbus-launch
[79016.301335] [ 1887]  1000  1887     7948      124      19      190             0 dbus-daemon
[79016.301337] [ 1929]  1000  1929    72053     4651     135    17025             0 fcitx
[79016.301338] [ 1934]  1000  1934     7794       74      21      128             0 dbus-daemon
[79016.301340] [ 1938]  1000  1938     3258       11      12       24             0 fcitx-dbus-watc
[79016.301341] [ 1940]  1000  1940    84352       47      31       82             0 at-spi-bus-laun
[79016.301343] [ 1944]  1000  1944     7628       75      20       56             0 dbus-daemon
[79016.301344] [ 1947]  1000  1947    31204       69      30       73             0 at-spi2-registr
[79016.301346] [ 1953]  1000  1953   109699      941     100      637             0 notify-osd
[79016.301347] [ 1960]  1000  1960   251721      886     175      921             0 cinnamon-settin
[79016.301349] [ 1966]  1000  1966    48545       70      31       69             0 gvfsd
[79016.301351] [ 1979]  1000  1979    84215        0      33      186             0 gvfsd-fuse
[79016.301352] [ 1989]     0  1989    58225      155      42      130             0 upowerd
[79016.301354] [ 1994]  1000  1994   107663      426      86      219             0 pulseaudio
[79016.301355] [ 1996]   107  1996    42230       29      20       43             0 rtkit-daemon
[79016.301357] [ 2168]     0  2168    69630       21      39      185             0 accounts-daemon
[79016.301358] [ 2174]  1000  2174    97072        0      86      346             0 csd-printer
[79016.301360] [ 2182]  1000  2182    60328       72      83     2258             0 cinnamon-launch
[79016.301361] [ 2184]  1000  2184   434998    10935     298     9238             0 cinnamon
[79016.301363] [ 2192]  1000  2192    55393      284      78      373             0 polkit-gnome-au
[79016.301365] [ 2194]  1000  2194   110737       91      84      582             0 cinnamon-fallba
[79016.301366] [ 2195]  1000  2195   278696     1398     167     1252             0 nemo
[79016.301368] [ 2202]  1000  2202    71948      263      42      192             0 gvfs-udisks2-vo
[79016.301369] [ 2203]  1000  2203   165595      300     114     1367             0 nm-applet
[79016.301371] [ 2206]     0  2206    90695      212      44      323             0 udisksd
[79016.301372] [ 2224]  1000  2224    47271        4      27      143             0 gvfs-mtp-volume
[79016.301374] [ 2233]  1000  2233    70834        0      36      182             0 gvfs-afc-volume
[79016.301376] [ 2238]  1000  2238    50312        0      33      193             0 gvfs-gphoto2-vo
[79016.301377] [ 2248]  1000  2248    13776      101      32      105             0 gconfd-2
[79016.301379] [ 2255]  1000  2255   616847      169     140     1335             0 fcitx-qimpanel
[79016.301380] [ 2257]  1000  2257    87081        0      37      200             0 gvfsd-trash
[79016.301382] [ 2279]  1000  2279    29575        9      27      237             0 gvfsd-metadata
[79016.301383] [ 2293]  1000  2293   105703     1977      96      511             0 cinnamon-screen
[79016.301386] [ 2608]  1000  2608     6462       15      16      624             0 mintupdate-laun
[79016.301387] [ 2643]  1000  2643   158621     1452     125     3335             0 mintUpdate
[79016.301388] [ 4640]  1000  4640   156501     1081     137     1370             0 gnome-terminal
[79016.301390] [ 4647]  1000  4647     3708       11      13       41             0 gnome-pty-helpe
[79016.301392] [ 4648]  1000  4648     6084      227      17      267             0 bash
[79016.301393] [ 4918]     0  4918     8111       24      20      135             0 wpa_supplicant
[79016.301394] [ 4926] 65534  4926     8172        0      21       65             0 dnsmasq
[79016.301396] [ 5055]     0  5055    26773       87      53      155             0 winbindd
[79016.301397] [ 5060]     0  5060    22850       41      45      156             0 nmbd
[79016.301399] [ 5062]     0  5062    26773       82      51      148             0 winbindd
[79016.301400] [ 5808]  1000  5808    44554        9      24      214             0 dconf-service
[79016.301402] [ 5810]  1000  5810   256925      292     365    33412             0 thunderbird
[79016.301404] [ 5851]  1000  5851   218590       16     128      693             0 evolution-sourc
[79016.301405] [ 5857]  1000  5857   196793        0     107      637             0 evolution-addre
[79016.301407] [ 6398]  1000  6398     6060        9      17      482             0 bash
[79016.301408] [ 6760]  1000  6760     6078        9      16      478             0 bash
[79016.301411] [11095]     0 11095     2561       11      10      573             0 dhclient
[79016.301413] [11174]     0 11174     2561       11       8      575             0 dhclient
[79016.301414] [11447]     0 11447    18323       18      39      497             0 cupsd
[79016.301416] [12566]  1000 12566   320082    10114     479    88987             0 firefox
[79016.301417] [12702]  1000 12702   104441      632     166     4633             0 plugin-containe
[79016.301419] [13199]  1000 13199   755285   623195    1374    65791             0 bitshares_clien
[79016.301421] [13664]  1000 13664   574765   141929     542     1432             0 VirtualBox
[79016.301423] [13668]  1000 13668    30181      542      58        0             0 VBoxXPCOMIPCD
[79016.301424] [13673]  1000 13673   158919      929      93       45             0 VBoxSVC
[79016.301426] Out of memory: Kill process 13199 (bitshares_clien) score 579 or sacrifice child
[79016.301428] Killed process 13199 (bitshares_clien) total-vm:3021140kB, anon-rss:2492696kB, file-rss:84kB

Can you send the log file at ~/.BitSharesXTS/default.log
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 02:33:41 am
can't post it here, always time out
I have send email to you( .....) with attachment
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 02:35:26 am
Got it, thanks.

Is everything working OK after restart of client?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 02:38:32 am
Got it, thanks.

Is everything working OK after restart of client?
Yes, I have try several times.
Everything is ok, but the process always be killed in about 5 minutes.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 02:44:29 am
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.

Code: [Select]
(wallet closed) >>> get_info
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 850,
  "random_seed": "3b40f23a293158b6b538a5ca1d63ae30485004ad",
  "current_share_supply": 79999999000000,
  "shares_per_bip": 0.079999999000000002,
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "connections": 1,
  "maximum_number_of_connections": 12,
  "rpc_port": 5679,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "3e96573cae6d93411ba103ced38f7d994e219e3e",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 26, 2014, 03:03:22 am
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.

Code: [Select]
(wallet closed) >>> get_info
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 850,
  "random_seed": "3b40f23a293158b6b538a5ca1d63ae30485004ad",
  "current_share_supply": 79999999000000,
  "shares_per_bip": 0.079999999000000002,
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "connections": 1,
  "maximum_number_of_connections": 12,
  "rpc_port": 5679,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "3e96573cae6d93411ba103ced38f7d994e219e3e",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
Are you using Debug build? I encountered similar segment fault in OSX Xcode Debug build.
https://github.com/BitShares/bitshares_toolkit/issues/126 (https://github.com/BitShares/bitshares_toolkit/issues/126)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: ernest on May 26, 2014, 03:12:28 am
XTS2Q4aacNiNxk3J8JRAo7HYziMYojEvy61CBhjBeYhJdsdmbwZ8mnCmnj4nYjz4LWp1EFJiAw9JSJ4fj62pdm9NotHhZo16a
thx
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 26, 2014, 03:29:36 am
XTS2Q4aacNiNxk3J8JRAo7HYziMYojEvy61CBhjBeYhJdsdmbwZ8mnCmnj4nYjz4LWp1EFJiAw9JSJ4fj62pdm9NotHhZo16a
thx

sent, also welcome!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 03:44:04 am
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.
Are you using Debug build? I encountered similar segment fault in OSX Xcode Debug build.
https://github.com/BitShares/bitshares_toolkit/issues/126 (https://github.com/BitShares/bitshares_toolkit/issues/126)
I am using normal build.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 04:33:19 am
XTS2biXF8M5DyWT7EpRHSwFfa4jLb7xpcXCZRwaaUaEZBoUcGVrcDBkC3aPyTshtKRGiG7CUJNMbc7ADMS32KYNP3Ve3LT99p
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 04:39:59 am
Don't send to that address. I accidentally hit ctr + c and exited without saving. Also can we use the web wallet per the instructions on readme in htdocs?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: zhangweis on May 26, 2014, 04:41:24 am
I'm having the below errors in log. Can anyone hint what I should do?

3437194ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:619
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:227
3440195ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5679                  node.cpp:1850
3440195ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:1873
3440195ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:168
3440195ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                      tcp_socket.cpp:105
3440195ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:751
3440196ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:561
3440196ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:861
3440196ms       th_a display_current_conn ]    my id is f8911c7113ce5c4cdd1d050358e4cf834df62aa0                        node.cpp:862
3440196ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                      node.cpp:870
3440196ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                      node.cpp:573
3440196ms       th_a p2p_network_connect_ ] Last attempt was 47 seconds ago (disposition: last_connection_failed)                     node.cpp:573

btw, my uname -r is:
2.6.32-5-amd64

I'll have Eric look into this one...  posting an issue for it here https://github.com/BitShares/bitshares_toolkit/issues/131

Thanks and I've bypassed it by removing the code for sock binding to the local address and port in tcp_socket.cpp.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 04:43:25 am
Don't send to that address. I accidentally hit ctr + c and exited without saving. Also can we use the web wallet per the instructions on readme in htdocs?

You can give it a try... I am not certain what state the web wallet is in right now.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 04:44:00 am
XTS3H9FsYaW4kFQU8yMxEmU2weUvoL48QY8Pz3DPrpmnE3JqxDbSxLn4JM6ThLsbmp2pYS7P46tdDc7ixqaKn7KB3fZ7iTA3p

Heres my real address
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 04:44:04 am
Don't send to that address. I accidentally hit ctr + c and exited without saving. Also can we use the web wallet per the instructions on readme in htdocs?

It should have saved before you even saw the address.  ctr+c shouldn't have harmed anything.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 04:45:42 am
XTS3H9FsYaW4kFQU8yMxEmU2weUvoL48QY8Pz3DPrpmnE3JqxDbSxLn4JM6ThLsbmp2pYS7P46tdDc7ixqaKn7KB3fZ7iTA3p

Heres my real address

Code: [Select]
"16250beee60df1fdaa50cc46539cc56ba522dd68",{
        "expiration": null,
        "delegate_id": null,
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM",
              "amount": 989998989,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 989898989,
              "condition": {
                "asset_id": 0,
                "delegate_id": 2,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "XTSFBQBydA64TDzYRczQCqDQULB3a2FKzBit"
                }
              }
            }
          }
        ],
        "signatures": [
          "1f3177bf667ff5c3422ae1951d47ee147946c28596d79ce05c397d5573ecc3e9c658f64de4992a36ce8bf40ed8c60fe7c9c72cc6cee978cb52bdc0861fce26563b"
        ]
      }
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 26, 2014, 05:01:35 am
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.
Are you using Debug build? I encountered similar segment fault in OSX Xcode Debug build.
https://github.com/BitShares/bitshares_toolkit/issues/126 (https://github.com/BitShares/bitshares_toolkit/issues/126)
I am using normal build.

Then should not be the same issue, my issue is only reproducible in Debug build.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 05:02:23 am
XTS3H9FsYaW4kFQU8yMxEmU2weUvoL48QY8Pz3DPrpmnE3JqxDbSxLn4JM6ThLsbmp2pYS7P46tdDc7ixqaKn7KB3fZ7iTA3p

Heres my real address

Code: [Select]
"16250beee60df1fdaa50cc46539cc56ba522dd68",{
        "expiration": null,
        "delegate_id": null,
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM",
              "amount": 989998989,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 989898989,
              "condition": {
                "asset_id": 0,
                "delegate_id": 2,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "XTSFBQBydA64TDzYRczQCqDQULB3a2FKzBit"
                }
              }
            }
          }
        ],
        "signatures": [
          "1f3177bf667ff5c3422ae1951d47ee147946c28596d79ce05c397d5573ecc3e9c658f64de4992a36ce8bf40ed8c60fe7c9c72cc6cee978cb52bdc0861fce26563b"
        ]
      }

Not really sure what that's supposed to mean
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 05:13:15 am
XTS3H9FsYaW4kFQU8yMxEmU2weUvoL48QY8Pz3DPrpmnE3JqxDbSxLn4JM6ThLsbmp2pYS7P46tdDc7ixqaKn7KB3fZ7iTA3p

Heres my real address

Code: [Select]
"16250beee60df1fdaa50cc46539cc56ba522dd68",{
        "expiration": null,
        "delegate_id": null,
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM",
              "amount": 989998989,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 989898989,
              "condition": {
                "asset_id": 0,
                "delegate_id": 2,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "XTSFBQBydA64TDzYRczQCqDQULB3a2FKzBit"
                }
              }
            }
          }
        ],
        "signatures": [
          "1f3177bf667ff5c3422ae1951d47ee147946c28596d79ce05c397d5573ecc3e9c658f64de4992a36ce8bf40ed8c60fe7c9c72cc6cee978cb52bdc0861fce26563b"
        ]
      }

Not really sure what that's supposed to mean

I sent you funds, did you get them?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 05:16:20 am
no i didn't... :-\
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 05:18:48 am
no i didn't... :-\

I sent you another transaction... I think I screwed up the first one and sent your first address instead of your new address.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 26, 2014, 05:23:02 am
yep got it!  :D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 26, 2014, 05:26:57 am
XTS2AL9DiHXSRUsNiBVpokZyYdPrt13vFZVjYfLuxiZZkPpNheQijYq8oWYNZPi4hzqbtDpjcxDMXjAFJ4ybBShBAr6V3XbPE

Thanks =D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 05:28:35 am
XTS2AL9DiHXSRUsNiBVpokZyYdPrt13vFZVjYfLuxiZZkPpNheQijYq8oWYNZPi4hzqbtDpjcxDMXjAFJ4ybBShBAr6V3XbPE

Thanks =D

Sent: d31be7924311fa6dd52938886aa60a5cf7ac8317
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 26, 2014, 05:30:48 am
XTS2AL9DiHXSRUsNiBVpokZyYdPrt13vFZVjYfLuxiZZkPpNheQijYq8oWYNZPi4hzqbtDpjcxDMXjAFJ4ybBShBAr6V3XbPE

Thanks =D

Sent: d31be7924311fa6dd52938886aa60a5cf7ac8317

got it =D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: dcchong on May 26, 2014, 06:25:59 am
to_dcchong
XTS3AdoxdVpXCAdwoQmw5GfEpQpNT7NvE5qbFVBZyWQTMGQhSqU5H2dmGFTnd7kUJhZaAt4okJHSWvFdYGPnR9zmjv6RChinF

thanks!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: denkhaus on May 26, 2014, 06:58:48 am

XTS2v9ZxnKbUvYScHVvC9K5E6BeNKg1tKDdy3wDKVV5xwT6GkbYBVH8vxjk7LGbA18GxKoAXQnmzQBUfQSWPxuM4iuC31XdCb

thanks!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 26, 2014, 07:02:10 am
http://dotp2p.io/visualize.php
is it  Update in real time?
toast  would you please add some statistics fuctions:how many nodes and Delegates?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: spartako on May 26, 2014, 07:47:02 am
XTS3CR1eDU98xvB95rkQtEF1CT77cRrFnKsbVASozQ66c6vWFVJW1Nf2TZU58Rf7YYp9YREnxuaymKLAiDhrTVHKmatsF5xxr
thanks

sent

Received :)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: jwiz168 on May 26, 2014, 10:14:21 am
try to send to this address

XTS2RRrWqvHQWYqxdwhpYrqtMX1GfRToNnJ9frZce1SQQstG9CYccM6Ejm3J1iDDEjvh18cip13XH7HwC7fm5sQVc4BMYywFo

thanks BM
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 26, 2014, 01:08:40 pm
XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau

plz :D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 01:34:59 pm
XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau

plz :D

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 01:35:45 pm
try to send to this address

XTS2RRrWqvHQWYqxdwhpYrqtMX1GfRToNnJ9frZce1SQQstG9CYccM6Ejm3J1iDDEjvh18cip13XH7HwC7fm5sQVc4BMYywFo

thanks BM

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 26, 2014, 01:41:53 pm
XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau

plz :D

Sent

Received
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 02:34:56 pm
Main seed node is reporting 7 connections.. how many connections do you all see to each other?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 26, 2014, 02:36:08 pm
Main seed node is reporting 7 connections.. how many connections do you all see to each other?

Mine has 2 connections. And it last about 2 hous without floating.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 02:52:44 pm
Main seed node is reporting 7 connections.. how many connections do you all see to each other?

Mine has 2 connections. And it last about 2 hous without floating.

My local client has 4 connections at the moment.   I noticed that it got stuck around block 1600 and I had to delete the chain and force a re-sync...   Fortunately that worked.   I think the P2P networking code has a few bugs to work out.   But so far things are progressing nicely.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 26, 2014, 02:58:07 pm
Main seed node is reporting 7 connections.. how many connections do you all see to each other?

Mine has 2 connections. And it last about 2 hous without floating.

My local client has 4 connections at the moment.   I noticed that it got stuck around block 1600 and I had to delete the chain and force a re-sync...   Fortunately that worked.   I think the P2P networking code has a few bugs to work out.   But so far things are progressing nicely.

I did nothing but it's 3 connections at the moment.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 03:11:47 pm
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.
I have try my best, but not finish it yet.
I have to go to bed now. here is what I am doing.
1. here is a shell script, try to break client with gdb before it is be killed.
Code: [Select]
#!/bin/bash

PROG_NAME="bitshares_client"
PID=`pidof $PROG_NAME`
echo "Pid of $PROG_NAME is : $PID"
while true; do
  MEM_USAGE=`ps -C bitshares_client -o rss | tail -n 1`
  echo "rss in kBytes: $MEM_USAGE"
  if [ "$MEM_USAGE" -gt 10000 ]; then
    gdb ./$PROG_NAME $PID
    break
  fi
  sleep 0.1
done

2. after several minutes, gdb attach the pid.
you can see some memory is very big, about 196M.
Code: [Select]
alt@alt-ThinkPad-T430s ~/workspace/bitshares_toolkit/build/programs/client $ pmap -x `pidof bitshares_client`
....
0000000000de4000  196708  196608  196608 rwx--    [ anon ]
....

3. watch the address in gdb
Code: [Select]
(gdb) awatch *0xcde4ffd
Hardware access (read/write) watchpoint 3: *0xcde4ffd
(gdb) c
Continuing.
Hardware access (read/write) watchpoint 3: *0xcde4ffd

Value = 0
fc::task_base::task_base (this=0xcde4ff0, __vtt_parm=0x8494c8 <VTT for fc::task<void, 24ul>+40>, func=0xcde4fd8, __in_chrg=<optimized out>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:22
22   _functor(func){
(gdb) bt
#0  fc::task_base::task_base (this=0xcde4ff0, __vtt_parm=0x8494c8 <VTT for fc::task<void, 24ul>+40>, func=0xcde4fd8, __in_chrg=<optimized out>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:22
#1  0x00000000007338ee in task<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a7179>, this=0xcde4fd0,
    __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:81
#2  async<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (prio=..., desc=0x8499e0 "",
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a70f9>, this=0xe1cae0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/thread.hpp:59
#3  async<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (prio=..., desc=0x8499e0 "",
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a70af>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/thread.hpp:176
#4  read_loop (this=0xec5250) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/rpc/json_connection.cpp:207
#5  operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/rpc/json_connection.cpp:266
#6  fc::detail::void_functor_run<fc::rpc::json_connection::exec()::__lambda1>::run(void *, void *) (functor=<optimized out>, prom=0xecefc0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#7  0x0000000000708b0a in fc::task_base::run_impl (this=this@entry=0xecefd0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#8  0x0000000000708dc5 in fc::task_base::run (this=this@entry=0xecefd0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#9  0x00000000007075f7 in run_next_task (this=0xe1cb00) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#10 fc::thread_d::process_tasks (this=this@entry=0xe1cb00) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#11 0x00000000007078f1 in fc::thread_d::start_process_tasks (my=14797568) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#12 0x0000000000809e6e in make_fcontext ()
#13 0x0000000000e1cb00 in ?? ()
#14 0x0000000000000000 in ?? ()
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 03:17:00 pm
I comile from the source, here is the version info.
If this don't happen in your guys, you can leave this task  for me, I'll try to fix it this evening.
I have try my best, but not finish it yet.
I have to go to bed now. here is what I am doing.
1. here is a shell script, try to break client with gdb before it is be killed.
Code: [Select]
#!/bin/bash

PROG_NAME="bitshares_client"
PID=`pidof $PROG_NAME`
echo "Pid of $PROG_NAME is : $PID"
while true; do
  MEM_USAGE=`ps -C bitshares_client -o rss | tail -n 1`
  echo "rss in kBytes: $MEM_USAGE"
  if [ "$MEM_USAGE" -gt 10000 ]; then
    gdb ./$PROG_NAME $PID
    break
  fi
  sleep 0.1
done

2. after several minutes, gdb attach the pid.
you can see some memory is very big, about 196M.
Code: [Select]
alt@alt-ThinkPad-T430s ~/workspace/bitshares_toolkit/build/programs/client $ pmap -x `pidof bitshares_client`
....
0000000000de4000  196708  196608  196608 rwx--    [ anon ]
....

3. watch the address in gdb
Code: [Select]
(gdb) awatch *0xcde4ffd
Hardware access (read/write) watchpoint 3: *0xcde4ffd
(gdb) c
Continuing.
Hardware access (read/write) watchpoint 3: *0xcde4ffd

Value = 0
fc::task_base::task_base (this=0xcde4ff0, __vtt_parm=0x8494c8 <VTT for fc::task<void, 24ul>+40>, func=0xcde4fd8, __in_chrg=<optimized out>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:22
22   _functor(func){
(gdb) bt
#0  fc::task_base::task_base (this=0xcde4ff0, __vtt_parm=0x8494c8 <VTT for fc::task<void, 24ul>+40>, func=0xcde4fd8, __in_chrg=<optimized out>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:22
#1  0x00000000007338ee in task<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a7179>, this=0xcde4fd0,
    __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:81
#2  async<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (prio=..., desc=0x8499e0 "",
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a70f9>, this=0xe1cae0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/thread.hpp:59
#3  async<fc::rpc::detail::json_connection_impl::read_loop()::__lambda0> (prio=..., desc=0x8499e0 "",
    f=<unknown type in /home/alt/workspace/bitshares_toolkit/build/programs/client/bitshares_client, CU 0x106bfc4, DIE 0x10a70af>)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/thread.hpp:176
#4  read_loop (this=0xec5250) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/rpc/json_connection.cpp:207
#5  operator() (__closure=<optimized out>) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/rpc/json_connection.cpp:266
#6  fc::detail::void_functor_run<fc::rpc::json_connection::exec()::__lambda1>::run(void *, void *) (functor=<optimized out>, prom=0xecefc0)
    at /home/alt/workspace/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:54
#7  0x0000000000708b0a in fc::task_base::run_impl (this=this@entry=0xecefd0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:38
#8  0x0000000000708dc5 in fc::task_base::run (this=this@entry=0xecefd0) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#9  0x00000000007075f7 in run_next_task (this=0xe1cb00) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:347
#10 fc::thread_d::process_tasks (this=this@entry=0xe1cb00) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:370
#11 0x00000000007078f1 in fc::thread_d::start_process_tasks (my=14797568) at /home/alt/workspace/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:328
#12 0x0000000000809e6e in make_fcontext ()
#13 0x0000000000e1cb00 in ?? ()
#14 0x0000000000000000 in ?? ()


Great debugging, it looks like a JSON parser running into infinity rather than failing with an error at the end of the stream.  It also appears to be doing something with json_connection which shouldn't be in use... are you running with --server and attempting to use the web interface?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 03:20:28 pm
yes, I run with --server, but have not used the web interface.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 26, 2014, 03:23:25 pm
Main seed node is reporting 7 connections.. how many connections do you all see to each other?

Mine has 2 connections. And it last about 2 hous without floating.

My local client has 4 connections at the moment.   I noticed that it got stuck around block 1600 and I had to delete the chain and force a re-sync...   Fortunately that worked.   I think the P2P networking code has a few bugs to work out.   But so far things are progressing nicely.


I get same issue. However i delete peers.leveldb and it forced resync
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 03:56:56 pm
yes, I run with --server, but have not used the web interface.

Ok... at least we know where to look... good work!  I'll have Stan send you a tip of 30 PTS for your effort.  Post an address and contact him for details.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 26, 2014, 05:20:41 pm
tks

XTS31WEmshRSeWq9eYeNN9fybDj66r3mhZ3d6zFohnGtcHifgMeuWwGVWBQvgaxZ1QHUXJJzw1byaupdcRnFj4FBgVuFhkj2q
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 26, 2014, 05:28:28 pm
tks

XTS31WEmshRSeWq9eYeNN9fybDj66r3mhZ3d6zFohnGtcHifgMeuWwGVWBQvgaxZ1QHUXJJzw1byaupdcRnFj4FBgVuFhkj2q

enjoy
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 26, 2014, 05:49:59 pm
@bytemaster are there any interest in testing bitshares over ipv6 nodes?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 05:53:09 pm
@bytemaster are there any interest in testing bitshares over ipv6 nodes?

We have no ipv6 support right now.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alexxy on May 26, 2014, 06:04:44 pm
@bytemaster are there any interest in testing bitshares over ipv6 nodes?

We have no ipv6 support right now.

Ok. I have native ipv6 here. So i'll be able to test.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 26, 2014, 06:08:38 pm
tks

XTS31WEmshRSeWq9eYeNN9fybDj66r3mhZ3d6zFohnGtcHifgMeuWwGVWBQvgaxZ1QHUXJJzw1byaupdcRnFj4FBgVuFhkj2q

enjoy

i run bts user  OSX10.9 in virtualbox(hosts win8.1   i try to complie but failed  because i‘am not a IT industry personnel )


seems not working 

Last login: Mon May 26 10:58:42 on ttys001
jerrydeMac-mini:~ jerry$ /Users/jerry/Desktop/xts_client_osx ; exit;
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/Users/jerry/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/jerry/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/jerry/Library/Application Support/BitSharesXTS/config.json"
Loading blockchain from "/Users/jerry/Library/Application Support/BitSharesXTS/chain"
Using genesis block from file "/Users/jerry/genesis.dat"
Initializing genesis state
Not starting rpc server, use --server to enable the rpc interface
Listening to P2P connections on port 5678
Attempting to map UPNP port...
Attempting to connect to peer 107.170.30.182:5678
(wallet closed) >>> getinfo
{
  "chain_id": "e55197e9887bdac2dff24b1fc75dd16d2667c8a3c1f8710e69f8529350f29d63",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 0,
  "random_seed": "0000000000000000000000000000000000000000",
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0.080000000000000002,
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "connections": 0,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "744ac6a3aec1a41f81b141c45d79a893e6fe4ca5",
  "_bitshares_toolkit_revision": "36c0c3aabecfadf9ab251161abe7ce1371649031",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
(wallet closed) >>>

Delay time is longe  i’am at china mainland
ping 107.170.30.182
time=264ms TTL=38


hope to release exe version with UI

bts_wallet from http://bitshares.org/resources/downloads/
named Nightly Builds.  but seems like still the old version.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 26, 2014, 06:15:49 pm
Dan takes the bitshares.org node up and down pretty frequently, try again soonish

Sent from my SCH-I535 using Tapatalk

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 26, 2014, 09:17:04 pm
yes, I run with --server, but have not used the web interface.

Ok... at least we know where to look... good work!  I'll have Stan send you a tip of 30 PTS for your effort.  Post an address and contact him for details.
Thx, My pts address:  Pj9F2ooTAGD314Xw7KZ228Yegiut84HUnb
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 26, 2014, 09:42:29 pm
tks

XTS31WEmshRSeWq9eYeNN9fybDj66r3mhZ3d6zFohnGtcHifgMeuWwGVWBQvgaxZ1QHUXJJzw1byaupdcRnFj4FBgVuFhkj2q

enjoy

i run bts user  OSX10.9 in virtualbox(hosts win8.1   i try to complie but failed  because i‘am not a IT industry personnel )


seems not working 

Last login: Mon May 26 10:58:42 on ttys001
jerrydeMac-mini:~ jerry$ /Users/jerry/Desktop/xts_client_osx ; exit;
================================================================
=                                                              =
=             Welcome to BitShares XTS                         =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
Logging to file "/Users/jerry/Library/Application Support/BitSharesXTS/default.log"
Logging RPC to file "/Users/jerry/Library/Application Support/BitSharesXTS/rpc.log"
Loading config "/Users/jerry/Library/Application Support/BitSharesXTS/config.json"
Loading blockchain from "/Users/jerry/Library/Application Support/BitSharesXTS/chain"
Using genesis block from file "/Users/jerry/genesis.dat"
Initializing genesis state
Not starting rpc server, use --server to enable the rpc interface
Listening to P2P connections on port 5678
Attempting to map UPNP port...
Attempting to connect to peer 107.170.30.182:5678
(wallet closed) >>> getinfo
{
  "chain_id": "e55197e9887bdac2dff24b1fc75dd16d2667c8a3c1f8710e69f8529350f29d63",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 0,
  "random_seed": "0000000000000000000000000000000000000000",
  "current_share_supply": 80000000000000,
  "shares_per_bip": 0.080000000000000002,
  "balance": 0,
  "unlocked_until": "19700101T000000",
  "connections": 0,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "744ac6a3aec1a41f81b141c45d79a893e6fe4ca5",
  "_bitshares_toolkit_revision": "36c0c3aabecfadf9ab251161abe7ce1371649031",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
(wallet closed) >>>

Delay time is longe  i’am at china mainland
ping 107.170.30.182
time=264ms TTL=38


hope to release exe version with UI

bts_wallet from http://bitshares.org/resources/downloads/
named Nightly Builds.  but seems like still the old version.

This is what the server says:

Code: [Select]
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 3128,
  "random_seed": "b9dee529de0f0b6fe8307a772ab7a15d50bec4a3",
  "current_share_supply": 79999997099998,
  "shares_per_bip": 0.079999997099997999,
  "balance": 58164969781501,
  "unlocked_until": "20140919T114230.017637",
  "connections": 3,
  "maximum_number_of_connections": 12,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "b0dfe9e4d594d669ce60e937b429a4808753a668",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}

Eric has some small patches developed and soon to be committed to help accelerate the connection process.  This will help you connect. 

In the mean time you can delete ~/.BitSharesPTS/peers.leveldb (after closing the client) and it will probably connect right away.

Dan 
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: Stan on May 26, 2014, 10:08:44 pm
yes, I run with --server, but have not used the web interface.

Ok... at least we know where to look... good work!  I'll have Stan send you a tip of 30 PTS for your effort.  Post an address and contact him for details.
Thx, My pts address:  Pj9F2ooTAGD314Xw7KZ228Yegiut84HUnb

Status: 0/unconfirmed, broadcast through 5 nodes
Date: 5/26/14 18:03
To: Alt Tip - https://bitsharestalk.org/index.php?topic=4714.msg60703#msg60703 Pj9F2ooTAGD314Xw7KZ228Yegiut84HUnb
Debit: -30.00 PTS
Net amount: -30.00 PTS
Transaction ID: df77592e9f00c3998bac4e9c28812ada73f9c089903ad2db5b09106923ae8606
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 27, 2014, 12:27:44 am

Eric has some small patches developed and soon to be committed to help accelerate the connection process.  This will help you connect. 

In the mean time you can delete ~/.BitSharesPTS/peers.leveldb (after closing the client) and it will probably connect right away.

Dan

I have the same problem. It still doesn't work after I deleted the whole directory .BitSharesXTS/
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gamey on May 27, 2014, 01:27:42 am
XTS2Tsnv6XDc5573zKym7oyNcsJPYd8aT4Ye4Td4JhCEXbScMEPVsbZLoTx1RZjXCMTm3NLFKQ66KSSFFujmYJviDpJgqcRWV

Someone make me feel rich !
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 27, 2014, 01:57:13 am
how do you register a delegate?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 27, 2014, 02:29:06 am
how do you register a delegate?

wallet_register_delegate name ""

But the default wallet just picks random delegates at the moment, no way for people to vote for you
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: vikram on May 27, 2014, 02:52:53 am
how do you register a delegate?

wallet_register_delegate name ""

But the default wallet just picks random delegates at the moment, no way for people to vote for you

Just opened an issue about it here: https://github.com/BitShares/bitshares_toolkit/issues/140
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: laow on May 27, 2014, 04:15:51 am
XTS2y9XmdcvHRU9pPt5wWZEwy4JzLVBX1UKAw6CEseFRv8b3BcvnpU9jQf9nNzQhgkK4QQLK3Dg422YwwJLhYw3ELjAJkQixX

thanks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 27, 2014, 06:45:41 am
building from git-master-HEAD .. cannot connect to the network :-(

EDIT:
It says:
Code: [Select]
2976973ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2014
2976974ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104

Quote
32 3104875ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:973
 33 3104875ms       th_a display_current_conn ]    my id is f31b6c18d1bebb3c616ba750be767efa214821a5   node.cpp:974
 34 3104875ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:982
 35 3104875ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)   node.cpp:639
 36 3104875ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:973                                                                                                       
 37 3104875ms       th_a display_current_conn ]    my id is f31b6c18d1bebb3c616ba750be767efa214821a5   node.cpp:974
 38 3104875ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:982
 39 3104875ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:667
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 27, 2014, 02:34:38 pm
XTS2Tsnv6XDc5573zKym7oyNcsJPYd8aT4Ye4Td4JhCEXbScMEPVsbZLoTx1RZjXCMTm3NLFKQ66KSSFFujmYJviDpJgqcRWV

Someone make me feel rich !
XTS2y9XmdcvHRU9pPt5wWZEwy4JzLVBX1UKAw6CEseFRv8b3BcvnpU9jQf9nNzQhgkK4QQLK3Dg422YwwJLhYw3ELjAJkQixX

thanks

sent both
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 27, 2014, 02:45:14 pm
Could someone resend me to following address for testing, previous bts may lost due to an early chain re-org, related trx was not included.

XTS2H1KdkGzXXepafDQrRrgusqi5K6VVavFohimUzRK34v89QLnoBsW3muU1Srhnc4LM8Kmn73R3CyzF3zRxZXh63cNWzG6RV
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 27, 2014, 02:50:31 pm
yes, I run with --server, but have not used the web interface.

Ok... at least we know where to look... good work!  I'll have Stan send you a tip of 30 PTS for your effort.  Post an address and contact him for details.
Thx, My pts address:  Pj9F2ooTAGD314Xw7KZ228Yegiut84HUnb

Status: 0/unconfirmed, broadcast through 5 nodes
Date: 5/26/14 18:03
To: Alt Tip - https://bitsharestalk.org/index.php?topic=4714.msg60703#msg60703 Pj9F2ooTAGD314Xw7KZ228Yegiut84HUnb
Debit: -30.00 PTS
Net amount: -30.00 PTS
Transaction ID: df77592e9f00c3998bac4e9c28812ada73f9c089903ad2db5b09106923ae8606
Thx!
I try to continue the debug, but I can't reproduce now.
I have build program with new vertion today.
Code: [Select]
"_bitshares_toolkit_revision": "67fcc43c69328dab7965c2993e5ebdb18c9ed9b1",
  "_fc_revision": "65361f1fce1fb2565ef76bb046b69286e05cfabb",
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 27, 2014, 05:45:05 pm
Could someone resend me to following address for testing, previous bts may lost due to an early chain re-org, related trx was not included.

XTS2H1KdkGzXXepafDQrRrgusqi5K6VVavFohimUzRK34v89QLnoBsW3muU1Srhnc4LM8Kmn73R3CyzF3zRxZXh63cNWzG6RV

sent, check
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gamey on May 27, 2014, 06:36:03 pm

Anything useful we can do besides acknowledge receipt of funds ?  ( I did receive funds.. )
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 27, 2014, 09:35:54 pm

Anything useful we can do besides acknowledge receipt of funds ?  ( I did receive funds.. )

Leave your client running so that we can test P2P network code and longevity issues.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 27, 2014, 09:47:30 pm

Anything useful we can do besides acknowledge receipt of funds ?  ( I did receive funds.. )

Leave your client running so that we can test P2P network code and longevity issues.
+5%
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gamey on May 27, 2014, 09:59:19 pm

And I assume being locked is just as useful as being unlocked ?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 27, 2014, 10:37:43 pm

And I assume being locked is just as useful as being unlocked ?

Yes
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 01:12:53 am
I saw network_num_connections is always 1
so I check the netstat, I am wondering why so many state is SYN_SENT?
It's because of firewall?
or does the p2p network depend on upnp when the node is behind a local gateway?

Code: [Select]
alt@alt-ThinkPad-T430s ~ $ netstat -nap | grep bitshares
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5679          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5680          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:5679      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        79.173.81.171:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:36560     SYN_SENT    22148/bitshares_cli
tcp        0      0 10.10.40.72:5678        107.170.30.182:5678     ESTABLISHED 22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        171.105.59.67:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        42.2.241.201:5678       SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        112.64.144.162:5678     SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        93.48.105.80:5678       SYN_SENT    22148/bitshares_cli
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 01:15:20 am
I saw network_num_connections is always 1
so I check the netstat, I am wondering why so many state is SYN_SENT?
It's because of firewall?
or does the p2p network depend on upnp when the node is behind a local gateway?

Code: [Select]
alt@alt-ThinkPad-T430s ~ $ netstat -nap | grep bitshares
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5679          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5680          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:5679      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        79.173.81.171:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:36560     SYN_SENT    22148/bitshares_cli
tcp        0      0 10.10.40.72:5678        107.170.30.182:5678     ESTABLISHED 22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        171.105.59.67:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        42.2.241.201:5678       SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        112.64.144.162:5678     SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        93.48.105.80:5678       SYN_SENT    22148/bitshares_cli

Right now it depends upon UPNP...
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 01:23:54 am
I saw network_num_connections is always 1
so I check the netstat, I am wondering why so many state is SYN_SENT?
It's because of firewall?
or does the p2p network depend on upnp when the node is behind a local gateway?

Code: [Select]
alt@alt-ThinkPad-T430s ~ $ netstat -nap | grep bitshares
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5679          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      0 127.0.0.1:5680          0.0.0.0:*               LISTEN      22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:5679      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        79.173.81.171:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        223.65.189.69:36560     SYN_SENT    22148/bitshares_cli
tcp        0      0 10.10.40.72:5678        107.170.30.182:5678     ESTABLISHED 22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        171.105.59.67:5678      SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        42.2.241.201:5678       SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        112.64.144.162:5678     SYN_SENT    22148/bitshares_cli
tcp        0      1 10.10.40.72:5678        93.48.105.80:5678       SYN_SENT    22148/bitshares_cli
Right now it depends upon UPNP...
So if nodeA and nodeB both behind the local gateway, and without upnp support, then can never connect directly.
But if nodeC has upnp support, nodeA and nodeB both can connect directly with nodeC?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 28, 2014, 02:46:10 am
Could someone resend me to following address for testing, previous bts may lost due to an early chain re-org, related trx was not included.

XTS2H1KdkGzXXepafDQrRrgusqi5K6VVavFohimUzRK34v89QLnoBsW3muU1Srhnc4LM8Kmn73R3CyzF3zRxZXh63cNWzG6RV

sent, check

received.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 07:29:27 am
I still cannot connect to network from most recent git-master-head
Code: [Select]
1693768ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable                   upgrade_leveldb.cpp:44
1693773ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable                  upgrade_leveldb.cpp:44
1693778ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable                      upgrade_leveldb.cpp:44
1693817ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable                      upgrade_leveldb.cpp:44
1693819ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable                 upgrade_leveldb.cpp:44
1693823ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable                    upgrade_leveldb.cpp:44
1693826ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable                       upgrade_leveldb.cpp:44
1693829ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable                     upgrade_leveldb.cpp:44
1693833ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable                   upgrade_leveldb.cpp:44
1693839ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable                 upgrade_leveldb.cpp:44
1693850ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable                       upgrade_leveldb.cpp:44
1693857ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable                  upgrade_leveldb.cpp:44
1693863ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable                    upgrade_leveldb.cpp:44
1693869ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable                  upgrade_leveldb.cpp:44
1693874ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable                   upgrade_leveldb.cpp:44
1693878ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable                   upgrade_leveldb.cpp:44
1693882ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable                   upgrade_leveldb.cpp:44
1693886ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable                 upgrade_leveldb.cpp:44
1693889ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable                    upgrade_leveldb.cpp:44
1693892ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable                      upgrade_leveldb.cpp:44
1693908ms       th_a   load_configuration ] Loaded configuration from file /home/coin/.BitSharesXTS/node_config.json                    node.cpp:1953
1693914ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable                  upgrade_leveldb.cpp:44
1693914ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:690
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:226
1696915ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1999
1696915ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2022
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:167
1696915ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104
1696915ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                  node.cpp:716
1696915ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                    node.cpp:752
1696915ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                        node.cpp:641
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1696916ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)                    node.cpp:773
1696916ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:822
1701922ms       upnp           operator() ] No valid UPnP IGDs found                    upnp.cpp:145
1703915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072823                        client.cpp:78
1705915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072825                        client.cpp:78
1707915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072827                        client.cpp:78
1709915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072829                        client.cpp:78
1711916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072831                        client.cpp:78
1711916ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)                       node.cpp:641
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1713916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072833                        client.cpp:78
1715916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072835                        client.cpp:78
1717916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072837                        client.cpp:78
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 07:44:25 am
The default node seed is  "107.170.30.182:5678"
I am wondering how many is the max connections set in this node?
When the connection is up to the max,  If the new node can get other node list from this node?
If the answer is yes, you'll get a list, but I doubt the other nodes can accept your connection request because of the UPNP feature maybe not open.
At least, I can't connect to other node except 107.170.30.182.
I'll try to open UPNP when I arrive home this evening.

Code: [Select]
alt (locked) >>> get_info
{
...
  "network_num_connections": 1,
  "network_num_connections_max": 12,
...
}
I still cannot connect to network from most recent git-master-head
Code: [Select]
1693768ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable                   upgrade_leveldb.cpp:44
1693773ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable                  upgrade_leveldb.cpp:44
1693778ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable                      upgrade_leveldb.cpp:44
1693817ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable                      upgrade_leveldb.cpp:44
1693819ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable                 upgrade_leveldb.cpp:44
1693823ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable                    upgrade_leveldb.cpp:44
1693826ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable                       upgrade_leveldb.cpp:44
1693829ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable                     upgrade_leveldb.cpp:44
1693833ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable                   upgrade_leveldb.cpp:44
1693839ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable                 upgrade_leveldb.cpp:44
1693850ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable                       upgrade_leveldb.cpp:44
1693857ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable                  upgrade_leveldb.cpp:44
1693863ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable                    upgrade_leveldb.cpp:44
1693869ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable                  upgrade_leveldb.cpp:44
1693874ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable                   upgrade_leveldb.cpp:44
1693878ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable                   upgrade_leveldb.cpp:44
1693882ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable                   upgrade_leveldb.cpp:44
1693886ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable                 upgrade_leveldb.cpp:44
1693889ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable                    upgrade_leveldb.cpp:44
1693892ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable                      upgrade_leveldb.cpp:44
1693908ms       th_a   load_configuration ] Loaded configuration from file /home/coin/.BitSharesXTS/node_config.json                    node.cpp:1953
1693914ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable                  upgrade_leveldb.cpp:44
1693914ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:690
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:226
1696915ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1999
1696915ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2022
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:167
1696915ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104
1696915ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                  node.cpp:716
1696915ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                    node.cpp:752
1696915ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                        node.cpp:641
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1696916ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)                    node.cpp:773
1696916ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:822
1701922ms       upnp           operator() ] No valid UPnP IGDs found                    upnp.cpp:145
1703915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072823                        client.cpp:78
1705915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072825                        client.cpp:78
1707915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072827                        client.cpp:78
1709915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072829                        client.cpp:78
1711916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072831                        client.cpp:78
1711916ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)                       node.cpp:641
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1713916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072833                        client.cpp:78
1715916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072835                        client.cpp:78
1717916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072837                        client.cpp:78
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 07:50:37 am
I tried
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add

still no connections :-(
Quote
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "09b45e088af94f853ac2ad69b2203e02ee5bbcc23ca353793c48fe23419c06fe",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "cd397fef9148cd08138b32eb803b20249c98f53d"
}

The default node seed is  "107.170.30.182:5678"
I am wondering how many is the max connections set in this node?
When the connection is up to the max,  If the new node can get other node list from this node?
If the answer is yes, you'll get a list, but I doubt the other nodes can accept your connection request because of the UPNP feature maybe not open.
At least, I can't connect to other node except 107.170.30.182.
I'll try to open UPNP when I arrive home this evening.

Code: [Select]
alt (locked) >>> get_info
{
...
  "network_num_connections": 1,
  "network_num_connections_max": 12,
...
}
I still cannot connect to network from most recent git-master-head
Code: [Select]
1693768ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable                   upgrade_leveldb.cpp:44
1693773ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable                  upgrade_leveldb.cpp:44
1693778ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable                      upgrade_leveldb.cpp:44
1693817ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable                      upgrade_leveldb.cpp:44
1693819ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable                 upgrade_leveldb.cpp:44
1693823ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable                    upgrade_leveldb.cpp:44
1693826ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable                       upgrade_leveldb.cpp:44
1693829ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable                     upgrade_leveldb.cpp:44
1693833ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable                   upgrade_leveldb.cpp:44
1693839ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable                 upgrade_leveldb.cpp:44
1693850ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable                       upgrade_leveldb.cpp:44
1693857ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable                  upgrade_leveldb.cpp:44
1693863ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable                    upgrade_leveldb.cpp:44
1693869ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable                  upgrade_leveldb.cpp:44
1693874ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable                   upgrade_leveldb.cpp:44
1693878ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable                   upgrade_leveldb.cpp:44
1693882ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable                   upgrade_leveldb.cpp:44
1693886ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable                 upgrade_leveldb.cpp:44
1693889ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable                    upgrade_leveldb.cpp:44
1693892ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable                      upgrade_leveldb.cpp:44
1693908ms       th_a   load_configuration ] Loaded configuration from file /home/coin/.BitSharesXTS/node_config.json                    node.cpp:1953
1693914ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable                  upgrade_leveldb.cpp:44
1693914ms       th_a trigger_p2p_network_ ] Triggering connect loop now                 node.cpp:690
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:226
1696915ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1999
1696915ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2022
1696915ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT                  tcp_socket.cpp:167
1696915ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104
1696915ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop                  node.cpp:716
1696915ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep                    node.cpp:752
1696915ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)                        node.cpp:641
1696916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1696916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1696916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1696916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1696916ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)                    node.cpp:773
1696916ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory                       node.cpp:822
1701922ms       upnp           operator() ] No valid UPnP IGDs found                    upnp.cpp:145
1703915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072823                        client.cpp:78
1705915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072825                        client.cpp:78
1707915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072827                        client.cpp:78
1709915ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072829                        client.cpp:78
1711916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072831                        client.cpp:78
1711916ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)                       node.cpp:641
1711916ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
1711916ms       th_a display_current_conn ]    my id is a75359d89e069142f7db0c381de98c19cd24ae89                        node.cpp:976
1711916ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]                       node.cpp:984
1711916ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669
1713916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072833                        client.cpp:78
1715916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072835                        client.cpp:78
1717916ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T072837                        client.cpp:78
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 07:52:58 am
I'll disconnect now.
You must try ASAP...
Tell me the result please.
I tried
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add

still no connections :-(
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 08:19:29 am
I'll disconnect now.
You must try ASAP...
Tell me the result please.
I tried
network_add_node "107.170.30.182:5678" onetry
and
network_add_node "107.170.30.182:5678" add

still no connections :-(
Didn't work out :-( too bad ..

anyway .. there seems to be an issue with the seed node max_connection and the p2p-code.

EDIT: thanks anyway
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gulu on May 28, 2014, 10:29:08 am
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 28, 2014, 10:39:47 am
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK

Sent.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gulu on May 28, 2014, 11:02:35 am
Not received yet. I am connected.
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK

Sent.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 28, 2014, 11:14:38 am
Not received yet. I am connected.
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK

Sent.

My number connections now is zero, how about you?
Quote
"network_num_connections": 0,
"blockchain_block_num": 7565,
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 11:16:44 am
No changes :-(

Code: [Select]
  "network_num_connections": 0,
  "network_num_connections_max": 12,

My log file says:

Code: [Select]
10464 1004943ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().   node.cpp:602
10465 1004943ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:975
10466 1004943ms       th_a display_current_conn ]    my id is a1274c434667c1993ecbfb73935953ae2fd3842c   node.cpp:976
10467 1004943ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
10468 1004943ms       th_a p2p_network_connect_ ] Last attempt was 45 seconds ago (disposition: last_connection_failed)   node.cpp:641
10469 1004943ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:975
10470 1004943ms       th_a display_current_conn ]    my id is a1274c434667c1993ecbfb73935953ae2fd3842c   node.cpp:976
10471 1004943ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
10472 1004943ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:669

Not received yet. I am connected.
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK

Sent.

My number connections now is zero, how about you?
Quote
"network_num_connections": 0,
"blockchain_block_num": 7565,
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 28, 2014, 12:17:04 pm
I tried with newest code but still failed to connect to the P2P network.

The UPNP in my router is ON.

Code: [Select]
616714ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
616714ms       th_a display_current_conn ] Currently have 0 of 8 connections node.cpp:975
616715ms       th_a display_current_conn ]    my id is 221bea418d8678ee6b54e6f669f9d42a00eef18e node.cpp:976
616715ms       th_a p2p_network_connect_ ] Last attempt was 180 seconds ago (disposition: last_connection_failed) node.cpp:641
616715ms       th_a display_current_conn ] Currently have 0 of 8 connections node.cpp:975
616715ms       th_a display_current_conn ]    my id is 221bea418d8678ee6b54e6f669f9d42a00eef18e node.cpp:976
616715ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in  15 seconds node.cpp:669
618422ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T121018 client.cpp:78
620423ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T121020 client.cpp:78
622423ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T121022 client.cpp:78
624425ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140528T121024 client.cpp:78

Code: [Select]
heyD (unlocked) >>> wallet_rescan_blockchain 1
OK
heyD (unlocked) >>> wallet_rescan_blockchain_state
OK
heyD (unlocked) >>> getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": true,
  "wallet_unlocked_until": "20140528T122002",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "221bea418d8678ee6b54e6f669f9d42a00eef18e"
}

My address:XTS2mMgxH6EAaoYsvJRBGykHXGi1sYAtvqa5767gi57CHQBEA6ppftGmDt1Q9eWfwPtBMPUwdcueDZ1qPFQ7WQ2H8J1dYp6Yk
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 01:09:31 pm
I am at home now, and with upnp on.
here is my ip: 180.157.208.228:5678
you can try add this node now
Code: [Select]
alt@alt-ThinkPad-T430s ~/workspace/bitshares_toolkit/build/programs/client $ ./bitshares_client
Logging to file "/home/alt/.BitSharesXTS/default.log"
Logging RPC to file "/home/alt/.BitSharesXTS/rpc.log"
Loading config "/home/alt/.BitSharesXTS/config.json"
Loading blockchain from "/home/alt/.BitSharesXTS/chain"
Using genesis block from file "/home/alt/workspace/bitshares_toolkit/build/programs/client/genesis.dat"
Not starting rpc server, use --server to enable the rpc interface
Listening to P2P connections on port 5678
Attempting to map UPNP port...
UPnP: ExternalIPAddress = 180.157.208.228
UPnP Port Mapping successful.
Attempting to connect to peer 107.170.30.182:5678
(wallet closed) >>>
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gulu on May 28, 2014, 01:20:41 pm
I received. Now I am connected with two nodes. And my ip is  218.82.233.79; you can try to connect me. I intend to keep the client running for the next 24 hours.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 01:34:05 pm
My account: XTS2PAVmogb7YS5hyA7RX1RARWxjRWyjqB7oEdMvodU9CYmB1kg8ei2C7xRVVQahSDsT2D2At5JLVtrX5uQAneo7iuZakhQSD
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 01:35:11 pm
I received. Now I am connected with two nodes. And my ip is  218.82.233.79; you can try to connect me. I intend to keep the client running for the next 24 hours.
I have connected to you.  :)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 01:41:07 pm
I received. Now I am connected with two nodes. And my ip is  218.82.233.79; you can try to connect me. I intend to keep the client running for the next 24 hours.
I have connected to you.  :)

And I have been connected (automatically) to you :)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 01:48:12 pm
I received. Now I am connected with two nodes. And my ip is  218.82.233.79; you can try to connect me. I intend to keep the client running for the next 24 hours.
I have connected to you.  :)

And I have been connected (automatically) to you :)
Have send you a little
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 01:59:04 pm
Too bad:
Code: [Select]
20171 3468985ms       th_a display_current_conn ]    my id is a1274c434667c1993ecbfb73935953ae2fd3842c   node.cpp:976
20172 3468985ms       th_a display_current_conn ]    handshaking: 218.82.233.79:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
20173 3468985ms       th_a display_current_conn ]    handshaking: 180.157.208.228:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
20174 3468985ms       th_a p2p_network_connect_ ] Last attempt was 299 seconds ago (disposition: last_connection_failed)   node.cpp:641
20175 3468985ms       th_a p2p_network_connect_ ] Last attempt was 34 seconds ago (disposition: last_connection_failed)   node.cpp:641                                                                 
20176 3468985ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed)   node.cpp:641
.....
20202 3483985ms       th_a display_current_conn ] Currently have 2 of 8 connections   node.cpp:975
20203 3483985ms       th_a display_current_conn ]    my id is a1274c434667c1993ecbfb73935953ae2fd3842c   node.cpp:976
20204 3483985ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [unknown]   node.cpp:984
20205 3483985ms       th_a display_current_conn ]    handshaking: 218.82.233.79:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
20206 3483985ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:669
20207 3483985ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use   tcp_socket.cpp:104
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 01:59:31 pm
What is:
Code: [Select]
20207 3483985ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use   tcp_socket.cpp:104
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 28, 2014, 02:02:45 pm
What is:
Code: [Select]
20207 3483985ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use   tcp_socket.cpp:104
Maybe  the port 5678 is used by another program?
netstat -nap | grep 5678
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 02:05:36 pm
I received. Now I am connected with two nodes. And my ip is  218.82.233.79; you can try to connect me. I intend to keep the client running for the next 24 hours.
I have connected to you.  :)

And I have been connected (automatically) to you :)
Have send you a little

Thanks! Haven't received it yet, though, this is weird because it's been like more than 15mins...

It looks like I'm still on block 4267 (have been during all that time), maybe that's the issue?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 02:07:21 pm
It looks like I'm still on block 4267 (have been during all that time), maybe that's the issue?

That should have been 4627, sorry
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 02:10:26 pm
What is:
Code: [Select]
20207 3483985ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use   tcp_socket.cpp:104
Maybe  the port 5678 is used by another program?
netstat -nap | grep 5678

Nop .. It opend correclty .. But still not connected to any node?! :-(
Code: [Select]
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      7688/bitshares_clie
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 28, 2014, 02:19:53 pm
Can someone explain what happened?

where did my 100000  shares go?

Code: [Select]
coolspeed (unlocked) >>> wallet_rescan_blockchain
OK

coolspeed (unlocked) >>> getbalance
[[
    88888788888,
    "XTS"
  ]
]

coolspeed (unlocked) >>> wallet_get_transaction_history_summary
  #    BLK.TRX  TIMESTAMP           FROM                                 TO                                    AMOUNT    FEE     VOTE         ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1   2161.0    2014-05-26T13:35:00 XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM from_coolspeed_                      +88888888888    0      +delegate-2   23266449171d19794ebab56bad897cef00b109af
  2   7987.0    2014-05-28T14:08:30 from_coolspeed_                      from_coolspeed_                       0   -100000 +delegate-6   1c871a096db28a80817870cbc36c3f959ca2ebd7
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 02:20:37 pm
Quote
getinfo
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 8010,
  "random_seed": "34218babb2101e99e6d7bb5db5a6c8686997ab46",
  "current_share_supply": 79999995799989,
  "shares_per_bip": 0.079999995799988996,
  "balance": 58164525237057,
  "unlocked_until": "20140919T114230.017637",
  "connections": 5,
  "maximum_number_of_connections": 12,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "b0dfe9e4d594d669ce60e937b429a4808753a668",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 02:22:47 pm
Quote
getinfo
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 8010,
  "random_seed": "34218babb2101e99e6d7bb5db5a6c8686997ab46",
  "current_share_supply": 79999995799989,
  "shares_per_bip": 0.079999995799988996,
  "balance": 58164525237057,
  "unlocked_until": "20140919T114230.017637",
  "connections": 5,
  "maximum_number_of_connections": 12,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "b0dfe9e4d594d669ce60e937b429a4808753a668",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
So why can't I connect then?

edit://
may it be related to:
Code: [Select]
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "cc09ce92f7be354d57d9323aac7c48f16e886a26"
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 02:25:08 pm
Can someone explain what happened?

Code: [Select]
coolspeed (unlocked) >>> wallet_rescan_blockchain
OK

coolspeed (unlocked) >>> getbalance
[[
    88888788888,
    "XTS"
  ]
]

coolspeed (unlocked) >>> wallet_get_transaction_history_summary
  #    BLK.TRX  TIMESTAMP           FROM                                 TO                                    AMOUNT    FEE     VOTE         ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1   2161.0    2014-05-26T13:35:00 XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM from_coolspeed_                      +88888888888    0      +delegate-2   23266449171d19794ebab56bad897cef00b109af
  2   7987.0    2014-05-28T14:08:30 from_coolspeed_                      from_coolspeed_                       0   -100000 +delegate-6   1c871a096db28a80817870cbc36c3f959ca2ebd7

I have seen that bug, did you try to send to someone at any point?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 02:26:09 pm
Quote
getinfo
{
  "chain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "symbol": "XTS",
  "interval_seconds": 30,
  "blocks": 8010,
  "random_seed": "34218babb2101e99e6d7bb5db5a6c8686997ab46",
  "current_share_supply": 79999995799989,
  "shares_per_bip": 0.079999995799988996,
  "balance": 58164525237057,
  "unlocked_until": "20140919T114230.017637",
  "connections": 5,
  "maximum_number_of_connections": 12,
  "rpc_port": 0,
  "blockchain_version": 100,
  "wallet_version": 100,
  "protocol_version": 100,
  "_node_id": "b0dfe9e4d594d669ce60e937b429a4808753a668",
  "_bitshares_toolkit_revision": "8ac79016eff06168e86c702a588bbf0f3348b5a9",
  "_fc_revision": "ac03a71f3da1ea2cd78e5923cc930e2238c4b28c"
}
So why can't I connect then?

edit://
may it be related to:
Code: [Select]
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "cc09ce92f7be354d57d9323aac7c48f16e886a26"

I didn't upgrade the seed node until just now... getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000656251753,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 8013,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "3d1db87cdb33306788b6fced6f5bce78b8c1b28f",
  "blockchain_shares": 79999995799989,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 58164525237057,
  "wallet_balance_bips": 727056603633784.12,
  "wallet_open": true,
  "wallet_unlocked_until": "19091229T094124",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "daadb79345df8bec3826798e67a804c0e25c8f0f"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 02:29:07 pm
I didn't upgrade the seed node until just now... getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000656251753,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 8013,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "3d1db87cdb33306788b6fced6f5bce78b8c1b28f",
  "blockchain_shares": 79999995799989,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 58164525237057,
  "wallet_balance_bips": 727056603633784.12,
  "wallet_open": true,
  "wallet_unlocked_until": "19091229T094124",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "daadb79345df8bec3826798e67a804c0e25c8f0f"
}
lol

and I am just downgrading :-)
Gonna head back to master :-)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 28, 2014, 02:30:27 pm
Can someone explain what happened?

Code: [Select]
coolspeed (unlocked) >>> wallet_rescan_blockchain
OK

coolspeed (unlocked) >>> getbalance
[[
    88888788888,
    "XTS"
  ]
]

coolspeed (unlocked) >>> wallet_get_transaction_history_summary
  #    BLK.TRX  TIMESTAMP           FROM                                 TO                                    AMOUNT    FEE     VOTE         ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1   2161.0    2014-05-26T13:35:00 XTSHVKAFtdSsTeN3h1gB8NsD2mn3VuNQM8mM from_coolspeed_                      +88888888888    0      +delegate-2   23266449171d19794ebab56bad897cef00b109af
  2   7987.0    2014-05-28T14:08:30 from_coolspeed_                      from_coolspeed_                       0   -100000 +delegate-6   1c871a096db28a80817870cbc36c3f959ca2ebd7

I have seen that bug, did you try to send to someone at any point?

Yes, I did.
I did not know how to send some shares, and I've tried the following:

Code: [Select]
coolspeed (unlocked) >>> wallet_transfer 10000 "from_coolspeed_send_"
{
  "payments": [[
      "1c871a096db28a80817870cbc36c3f959ca2ebd7",{
        "expiration": null,
        "delegate_id": null,
        "operations": [{
            "type": "withdraw_op_type",
            "data": {
              "balance_id": "XTSLwLSaahYvZDKgsdnzk19QxzFRVBmE57W8",
              "amount": 110000,
              "claim_input_data": ""
            }
          },{
            "type": "deposit_op_type",
            "data": {
              "amount": 10000,
              "condition": {
                "asset_id": 0,
                "delegate_id": 6,
                "type": "withdraw_signature_type",
                "data": {
                  "owner": "XTS55v9bmpXCyLUQFK4yP69CqZ2jFjYuVvQC"
                }
              }
            }
          }
        ],
        "signatures": [
          "20afd384043f39421855ff4f6e10ae75cec0c30a0af3b37b3c7e0d054a628b641ff7edb073c98abb66b1933918219c091176536a2deb78de
5f48fa289f0d0e2b3b"
        ]
      }
    ]
  ],
  "from_account": "*",
  "to_account": "from_coolspeed_send_",
  "sending_invoice_index": 1,
  "last_sending_payment_index": 0
}

where the "from_coolspeed_send_" is my sending address??

Code: [Select]
coolspeed (unlocked) >>> wallet_list_sending_accounts
[[
    "from_coolspeed_send_",
    "XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau"
  ]
]
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 02:33:34 pm
coolspeed...  I gather you created the account in a different wallet and not the same wallet?

If that is so, then this is a bug I have seen in my own payouts...

Code: [Select]
  #    BLK.TRX  TIMESTAMP           FROM                                 TO                                    AMOUNT          FEE     VOTE         ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1      8.0    2014-05-25T03:01:30 delegate8                            XTSDBC6iJHhnUVcdvqmyT6eRnsDmsCAyh83Y -500000000      -100000 +delegate-2   bcaccdc239d3c5e416d4bd036623495deee759e8
  2     74.0    2014-05-25T20:11:30 delegate8                            XTSHTm3p5L4rGpMxKM6q9NykxoDYit9M3Gvr -4444444444     -100000 +delegate-5   8e2ec194532be23ea3037b26a9b062ccb2a5cd81
  3     77.0    2014-05-25T20:13:00 delegate8                            XTSHTm3p5L4rGpMxKM6q9NykxoDYit9M3Gvr -55555555555    -100000 +delegate-3   eedc58cf410230768cac9a927d45feb2680ba9c1
  4     82.0    2014-05-25T03:38:30 delegate8                            XTSPwdXUhyqCA42MmHTcb3YZCwYJmwjseELy -8800880000     -100000 +delegate-5   b87ed8237551febbd9c985c4d2b01e3619106617
  5     85.0    2014-05-25T20:17:00 delegate8                            XTSH7CAfXGuMJFmMKuB3Bcj6mbPQ7tvnsGvH -34343434343    -100000 +delegate-6   e9b507e1445b4c48e20f29ffcd7a924c6405efab
  6     85.0    2014-05-25T03:40:00 delegate8                            XTSJ8Hu2mhppXNnmaigHP9HpgLLbAiP3Qs6w -550055000000   -100000 +delegate-3   9b7f5f0188b45e2ea3146b2094d5bfd52b58545d
  7    117.0    2014-05-25T01:59:05 delegate0                            XTSNVZKr1dvNJagmRDACRSB2mhHYuLZJcHWW -100000000      -100000 +delegate-2   c0ce41989180637fceea8f7114aece2b9a61894e
  8    190.0    2014-05-25T02:09:00 delegate0                            XTSLPLiDpjzQ8xRHKYUY1TqTMYhSPHkq1x7r -30000000000    -100000 +delegate-5   b04127c27fc618ef6a1f350042db2ce188f81213
  9    237.0    2014-05-25T04:56:00 delegate8                            XTSyykpoga1z64jiU1cofbZcChf3oTvaJZn  -550055000000   -100000 +delegate-6   60396bd00402c0237df7be8989951aee2708db49
 10    240.0    2014-05-25T04:57:30 delegate8                            XTSLXJSy6V3GfFP72m9JPNzcwmuqVFgRWEJ8 -550055000000   -100000 +delegate-2   d84ca1b9e42d4d15c4e436f693323b5d65450d3b
 11    242.0    2014-05-25T04:58:30 delegate8                            XTS8cKzUBE3RSdSwEq3MEa5ancuHGv1uzP8x -550055000000   -100000 +delegate-4   d53274669830a48527dba919593dd7b2193f0ce3
 12    695.0    2014-05-26T01:22:00 delegate1                            XTSDHzS6gqrMP4Tx9JPKNn9Z1KSgpnbSQFDT -54321          -100000 +delegate-2   be8c124a1e55d8cc42c785dd3db3cb2c102abd21
 13   1101.0    2014-05-26T04:45:00 delegate8                            clout                                 0              -100000 +delegate-2   16250beee60df1fdaa50cc46539cc56ba522dd68
 14   1110.0    2014-05-25T12:35:00 delegate8                            XTSNVZKr1dvNJagmRDACRSB2mhHYuLZJcHWW -90000000       -100000 +delegate-2   bc5ebd2507829a3abd4bbbcf449ef553e34697f1
 15   1132.0    2014-05-25T12:49:30 delegate8                            XTSDBC6iJHhnUVcdvqmyT6eRnsDmsCAyh83Y -30000000       -100000 +delegate-2   846cb6dc1bcc4cd7e784d32e26d9c978b548351c
 16   1140.0    2014-05-25T12:53:30 delegate8                            XTS8JXVpcp2UuyeksoA3ZVXYUiJAmdB22i8f -50000000       -100000 +delegate-5   211ee7fd5cc37c8703f8ca36122129d33b9ce8ea
 17   1142.0    2014-05-25T12:54:30 delegate8                            XTSFj8RKHANm9RAaoxUdr7tcoYhqrqt3KpjV -500000000      -100000 +delegate-3   95c969678738aa526f59130cbb67d99903dddda5
 18   1144.0    2014-05-25T12:55:30 delegate8                            XTS2DGCxFUpZxrq9N233TFhjWFkE4T9bDLaG -30000000       -100000 +delegate-6   1d1bfd7e37687b639a73dd2e3bb172c5177586bd
 19   1150.0    2014-05-25T12:58:30 delegate8                            XTSAhvqJfKzJKCosaJa6ZEvEKornRZX7mUB9 -900000000      -100000 +delegate-2   76d03a62fb280300453629195ce41e796ff7e937
 20   1168.0    2014-05-26T05:18:30 delegate8                            XTSGajkuWusMWV9zBGZnRohdrA82Y8tXBRGS -98989898555    -100000 +delegate-5   a80fce1563d27eeb63121218fd0a6d08773c57e3
 21   1188.0    2014-05-26T05:28:30 delegate8                            XTSFXXL4o87Yoxm1rjpbbHDCe4jaNoFnuHvc -3456789012     -100000 +delegate-3   d31be7924311fa6dd52938886aa60a5cf7ac8317
 22   1235.0    2014-05-25T13:41:00 delegate8                            XTSK1bvv8sJrzcQsjhLpD9Y7qfJwsEDqY8wK -8888888899     -100000 +delegate-4   226c6b32646895a0c743b1ffc338c550234e5832
 23   1304.0    2014-05-25T14:15:30 delegate8                            XTSDhsWxyRQfkqLiSY5PbA72zN1nBtQChajL -777777777      -100000 +delegate-2   a6c84683c72d0d817e3fd7e31760a1243aa82d81
 24   1306.0    2014-05-25T14:16:30 delegate8                            XTS3tfYj9YVJD6CBAM8dPowidz9gxCgjfETn -4444444444     -100000 +delegate-5   cf4e72c62bf8385adfd007e4ae528a86be90a552
 25   1471.0    2014-05-25T15:39:00 delegate8                            XTSLbcacA8mpEXq6xUBSrtSs5toa6p4upFge -7777777777     -100000 +delegate-6   816f320ecaf8868fa009df7ba5bb3ccf642c2587
 26   1480.0    2014-05-25T15:43:30 XTSNmEj55KMrQrFaHaZ6xHULi2AqPmoe2DxQ XTSEVEuEjtCQH4i5yFdPnG7Mn6ZudVG8HiUD  0               0      +delegate-1   073610e44539ba50c55cf53823fde726d9937f67
 27   1592.0    2014-05-25T16:39:30 delegate8                            XTSAhvqJfKzJKCosaJa6ZEvEKornRZX7mUB9 -555444555      -100000 +delegate-2   84e5f0c017c6e6346a515da83ebc3d58818f200f
 28   2161.0    2014-05-26T13:35:00 delegate8                            XTS55v9bmpXCyLUQFK4yP69CqZ2jFjYuVvQC -88888888888    -100000 +delegate-2   23266449171d19794ebab56bad897cef00b109af
 29   2163.0    2014-05-26T13:36:00 delegate8                            XTSHbxvzHbfqg289uTTjZp8dVdnTDMdpgUgp -66666666666    -100000 +delegate-4   94d65ee26043c1675c77eadae868d11873573e54
 30   2280.0    2014-05-26T14:34:30 delegate8                            tostan                                0              -100000 +delegate-4   fbc0921b50022926f90eeb605be22d16bbf7ed5c
 31   2675.0    2014-05-26T17:52:00 tostan                               XTS6CWxt6ScWR4XX3zQmk4za9iVZu82jSLea -198519552015   -100000 +delegate-3   dcb5379a74fffd7424e4d8c315f274b9fccf929f
 32   2742.0    2014-05-26T18:26:00 delegate8                            XTSHbFAojyFoPFXzpvdCejKJCQpheDtmLsvQ -4567890000     -100000 +delegate-2   8cdce37c73cd4d6a5a3f4dcd31ad67ddb76ab5ac
 33   2772.0    2014-05-26T18:41:00 delegate8                            XTS8dmfp9uJoTGgkqXCTYiHXCJDsSEqmhwZ8 -3333333333     -100000 +delegate-5   096b4d700999f62ea9be4692625036b38fb4282c
 34   6514.0    2014-05-28T01:52:00 delegate8                            XTSGDrWUchFaFaMQoawy5pWDXekmQsWDMnQZ -444444444      -100000 +delegate-3   79a01a77a5bd3f6c5f82016a1407f8dec196dd50

You can see it happened to me 3 times... trying to get to the heart of it.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 02:39:20 pm
Still no connections:
Code: [Select]
(wallet closed) >>> get_info
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "05ccc4f3990d868f602d93f9466b4fe4747a229a1b2ae755a93b01c2929b3a1b",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "e696cf202adf3d292bf23bfecf2a38e130266d54"
}

Code: [Select]
2342481ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().                        node.cpp:602
2342481ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
2342481ms       th_a display_current_conn ]    my id is e696cf202adf3d292bf23bfecf2a38e130266d54                        node.cpp:976
2342481ms       th_a display_current_conn ]    handshaking: 180.157.208.228:5678 with 0000000000000000000000000000000000000000  [outbound]                      node.cpp:984
2342481ms       th_a p2p_network_connect_ ] Last attempt was 101 seconds ago (disposition: last_connection_failed)                      node.cpp:641
2342481ms       th_a p2p_network_connect_ ] Last attempt was 30 seconds ago (disposition: last_connection_failed)                       node.cpp:641
2342481ms       th_a display_current_conn ] Currently have 1 of 8 connections                   node.cpp:975
2342481ms       th_a display_current_conn ]    my id is e696cf202adf3d292bf23bfecf2a38e130266d54                        node.cpp:976
2342481ms       th_a display_current_conn ]    handshaking: 180.157.208.228:5678 with 0000000000000000000000000000000000000000  [outbound]                      node.cpp:984
2342481ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds                      node.cpp:669

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: coolspeed on May 28, 2014, 02:45:56 pm
coolspeed...  I gather you created the account in a different wallet and not the same wallet?

If that is so, then this is a bug I have seen in my own payouts...

Code: [Select]
  #    BLK.TRX  TIMESTAMP           FROM                                 TO                                    AMOUNT          FEE     VOTE         ID
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1      8.0    2014-05-25T03:01:30 delegate8                            XTSDBC6iJHhnUVcdvqmyT6eRnsDmsCAyh83Y -500000000      -100000 +delegate-2   bcaccdc239d3c5e416d4bd036623495deee759e8
  2     74.0    2014-05-25T20:11:30 delegate8                            XTSHTm3p5L4rGpMxKM6q9NykxoDYit9M3Gvr -4444444444     -100000 +delegate-5   8e2ec194532be23ea3037b26a9b062ccb2a5cd81
  3     77.0    2014-05-25T20:13:00 delegate8                            XTSHTm3p5L4rGpMxKM6q9NykxoDYit9M3Gvr -55555555555    -100000 +delegate-3   eedc58cf410230768cac9a927d45feb2680ba9c1
  4     82.0    2014-05-25T03:38:30 delegate8                            XTSPwdXUhyqCA42MmHTcb3YZCwYJmwjseELy -8800880000     -100000 +delegate-5   b87ed8237551febbd9c985c4d2b01e3619106617
  5     85.0    2014-05-25T20:17:00 delegate8                            XTSH7CAfXGuMJFmMKuB3Bcj6mbPQ7tvnsGvH -34343434343    -100000 +delegate-6   e9b507e1445b4c48e20f29ffcd7a924c6405efab
  6     85.0    2014-05-25T03:40:00 delegate8                            XTSJ8Hu2mhppXNnmaigHP9HpgLLbAiP3Qs6w -550055000000   -100000 +delegate-3   9b7f5f0188b45e2ea3146b2094d5bfd52b58545d
  7    117.0    2014-05-25T01:59:05 delegate0                            XTSNVZKr1dvNJagmRDACRSB2mhHYuLZJcHWW -100000000      -100000 +delegate-2   c0ce41989180637fceea8f7114aece2b9a61894e
  8    190.0    2014-05-25T02:09:00 delegate0                            XTSLPLiDpjzQ8xRHKYUY1TqTMYhSPHkq1x7r -30000000000    -100000 +delegate-5   b04127c27fc618ef6a1f350042db2ce188f81213
  9    237.0    2014-05-25T04:56:00 delegate8                            XTSyykpoga1z64jiU1cofbZcChf3oTvaJZn  -550055000000   -100000 +delegate-6   60396bd00402c0237df7be8989951aee2708db49
 10    240.0    2014-05-25T04:57:30 delegate8                            XTSLXJSy6V3GfFP72m9JPNzcwmuqVFgRWEJ8 -550055000000   -100000 +delegate-2   d84ca1b9e42d4d15c4e436f693323b5d65450d3b
 11    242.0    2014-05-25T04:58:30 delegate8                            XTS8cKzUBE3RSdSwEq3MEa5ancuHGv1uzP8x -550055000000   -100000 +delegate-4   d53274669830a48527dba919593dd7b2193f0ce3
 12    695.0    2014-05-26T01:22:00 delegate1                            XTSDHzS6gqrMP4Tx9JPKNn9Z1KSgpnbSQFDT -54321          -100000 +delegate-2   be8c124a1e55d8cc42c785dd3db3cb2c102abd21
 13   1101.0    2014-05-26T04:45:00 delegate8                            clout                                 0              -100000 +delegate-2   16250beee60df1fdaa50cc46539cc56ba522dd68
 14   1110.0    2014-05-25T12:35:00 delegate8                            XTSNVZKr1dvNJagmRDACRSB2mhHYuLZJcHWW -90000000       -100000 +delegate-2   bc5ebd2507829a3abd4bbbcf449ef553e34697f1
 15   1132.0    2014-05-25T12:49:30 delegate8                            XTSDBC6iJHhnUVcdvqmyT6eRnsDmsCAyh83Y -30000000       -100000 +delegate-2   846cb6dc1bcc4cd7e784d32e26d9c978b548351c
 16   1140.0    2014-05-25T12:53:30 delegate8                            XTS8JXVpcp2UuyeksoA3ZVXYUiJAmdB22i8f -50000000       -100000 +delegate-5   211ee7fd5cc37c8703f8ca36122129d33b9ce8ea
 17   1142.0    2014-05-25T12:54:30 delegate8                            XTSFj8RKHANm9RAaoxUdr7tcoYhqrqt3KpjV -500000000      -100000 +delegate-3   95c969678738aa526f59130cbb67d99903dddda5
 18   1144.0    2014-05-25T12:55:30 delegate8                            XTS2DGCxFUpZxrq9N233TFhjWFkE4T9bDLaG -30000000       -100000 +delegate-6   1d1bfd7e37687b639a73dd2e3bb172c5177586bd
 19   1150.0    2014-05-25T12:58:30 delegate8                            XTSAhvqJfKzJKCosaJa6ZEvEKornRZX7mUB9 -900000000      -100000 +delegate-2   76d03a62fb280300453629195ce41e796ff7e937
 20   1168.0    2014-05-26T05:18:30 delegate8                            XTSGajkuWusMWV9zBGZnRohdrA82Y8tXBRGS -98989898555    -100000 +delegate-5   a80fce1563d27eeb63121218fd0a6d08773c57e3
 21   1188.0    2014-05-26T05:28:30 delegate8                            XTSFXXL4o87Yoxm1rjpbbHDCe4jaNoFnuHvc -3456789012     -100000 +delegate-3   d31be7924311fa6dd52938886aa60a5cf7ac8317
 22   1235.0    2014-05-25T13:41:00 delegate8                            XTSK1bvv8sJrzcQsjhLpD9Y7qfJwsEDqY8wK -8888888899     -100000 +delegate-4   226c6b32646895a0c743b1ffc338c550234e5832
 23   1304.0    2014-05-25T14:15:30 delegate8                            XTSDhsWxyRQfkqLiSY5PbA72zN1nBtQChajL -777777777      -100000 +delegate-2   a6c84683c72d0d817e3fd7e31760a1243aa82d81
 24   1306.0    2014-05-25T14:16:30 delegate8                            XTS3tfYj9YVJD6CBAM8dPowidz9gxCgjfETn -4444444444     -100000 +delegate-5   cf4e72c62bf8385adfd007e4ae528a86be90a552
 25   1471.0    2014-05-25T15:39:00 delegate8                            XTSLbcacA8mpEXq6xUBSrtSs5toa6p4upFge -7777777777     -100000 +delegate-6   816f320ecaf8868fa009df7ba5bb3ccf642c2587
 26   1480.0    2014-05-25T15:43:30 XTSNmEj55KMrQrFaHaZ6xHULi2AqPmoe2DxQ XTSEVEuEjtCQH4i5yFdPnG7Mn6ZudVG8HiUD  0               0      +delegate-1   073610e44539ba50c55cf53823fde726d9937f67
 27   1592.0    2014-05-25T16:39:30 delegate8                            XTSAhvqJfKzJKCosaJa6ZEvEKornRZX7mUB9 -555444555      -100000 +delegate-2   84e5f0c017c6e6346a515da83ebc3d58818f200f
 28   2161.0    2014-05-26T13:35:00 delegate8                            XTS55v9bmpXCyLUQFK4yP69CqZ2jFjYuVvQC -88888888888    -100000 +delegate-2   23266449171d19794ebab56bad897cef00b109af
 29   2163.0    2014-05-26T13:36:00 delegate8                            XTSHbxvzHbfqg289uTTjZp8dVdnTDMdpgUgp -66666666666    -100000 +delegate-4   94d65ee26043c1675c77eadae868d11873573e54
 30   2280.0    2014-05-26T14:34:30 delegate8                            tostan                                0              -100000 +delegate-4   fbc0921b50022926f90eeb605be22d16bbf7ed5c
 31   2675.0    2014-05-26T17:52:00 tostan                               XTS6CWxt6ScWR4XX3zQmk4za9iVZu82jSLea -198519552015   -100000 +delegate-3   dcb5379a74fffd7424e4d8c315f274b9fccf929f
 32   2742.0    2014-05-26T18:26:00 delegate8                            XTSHbFAojyFoPFXzpvdCejKJCQpheDtmLsvQ -4567890000     -100000 +delegate-2   8cdce37c73cd4d6a5a3f4dcd31ad67ddb76ab5ac
 33   2772.0    2014-05-26T18:41:00 delegate8                            XTS8dmfp9uJoTGgkqXCTYiHXCJDsSEqmhwZ8 -3333333333     -100000 +delegate-5   096b4d700999f62ea9be4692625036b38fb4282c
 34   6514.0    2014-05-28T01:52:00 delegate8                            XTSGDrWUchFaFaMQoawy5pWDXekmQsWDMnQZ -444444444      -100000 +delegate-3   79a01a77a5bd3f6c5f82016a1407f8dec196dd50

You can see it happened to me 3 times... trying to get to the heart of it.

I have only one wallet, I believe, which is named "coolspeed".

my command history:

Code: [Select]

coolspeed (locked) >>> wallet_list_receive_accounts
[[
    "from_coolspeed_",
    "XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau"
  ]
]

coolspeed (unlocked) >>> wallet_create_sending_account "from_coolspeed_send_" "XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau"

coolspeed (unlocked) >>> wallet_list_sending_accounts
[[
    "from_coolspeed_send_",
    "XTS3FhJaxUUFj2FGJjNCnSM3tz9ycEv24xxbtWgRmro61gLaKCyGMBfgBr7bsZSf6RkyyswxaFyxamZ9XGiiRJaaau4oXhZau"
  ]
]




What I really don't know is what I really did when I ran:
coolspeed (unlocked) >>> wallet_transfer 10000 "from_coolspeed_send_"

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 02:47:54 pm
Thanks! Haven't received it yet, though, this is weird because it's been like more than 15mins...

It looks like I'm still on block 4267 (have been during all that time), maybe that's the issue?

Must have been stuck somehow, I restarted the client and now it got all the blocks as well as the shares, thanks!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 28, 2014, 03:36:21 pm
Not received yet. I am connected.
My account:
XTS3DCe7B5UfPhXTzGEqbzZVQksdx7GNFGKL59ykb3JjwPtR1dWQQo24dDxaNHybj6qaa5aFz1pDEyGHP9wbcUiwEJqHLPUxK

Sent.

My number connections now is zero, how about you?
Quote
"network_num_connections": 0,
"blockchain_block_num": 7565,

My chain was broken, might due to a sudden computer power off. After I delete the old chain data,there are connections now.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 28, 2014, 04:33:45 pm
looks like I have the same connection problems as xeroc... Running on a linux box with a public IP address (ie: not behind a router, so maybe upnp is the problem somehow?). The OSX client I run behind a router has no problems connecting.

relevant (I hope) parts of the log:

Code: [Select]
1150666ms       th_a trigger_p2p_network_ ] Triggering connect loop now node.cpp:690
1153668ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678 node.cpp:1999
1153669ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678) node.cpp:2022
1153670ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use tcp_socket.cpp:104
1153671ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop node.cpp:716
1153671ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep node.cpp:752
1153671ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1153671ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1153672ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1153672ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1153672ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed) node.cpp:641
1153672ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1153672ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1153672ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1153673ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds node.cpp:669
1153673ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch) node.cpp:773
1153674ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory node.cpp:822
1158678ms       upnp           operator() ] No valid UPnP IGDs found upnp.cpp:145
1168673ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1168673ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1168673ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1168674ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1168674ms       th_a p2p_network_connect_ ] Last attempt was 15 seconds ago (disposition: last_connection_failed) node.cpp:641
1168674ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1168674ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1168674ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1168675ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds node.cpp:669
1183675ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1183675ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1183676ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1183676ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1183676ms       th_a p2p_network_connect_ ] Last attempt was 30 seconds ago (disposition: last_connection_failed) node.cpp:641
1183676ms       th_a display_current_conn ] Currently have 1 of 8 connections node.cpp:975
1183676ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1183677ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound] node.cpp:984
1183677ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds node.cpp:669
1198671ms       th_a terminate_inactive_c ] Disconnecting from handshaking peer 107.170.30.182:5678 due to inactivity of at least 45 seconds node.cpp:898
1198677ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop(). node.cpp:602
1198677ms       th_a display_current_conn ] Currently have 0 of 8 connections node.cpp:975
1198677ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1198678ms       th_a p2p_network_connect_ ] Last attempt was 45 seconds ago (disposition: last_connection_failed) node.cpp:641
1198678ms       th_a display_current_conn ] Currently have 0 of 8 connections node.cpp:975
1198678ms       th_a display_current_conn ]    my id is 68a60fdde6c58e2060340a93c60a7613441f2af6 node.cpp:976
1198678ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds node.cpp:669

This part in particular looks strange:
Code: [Select]
Disconnecting from handshaking peer 107.170.30.182:5678 due to inactivity of at least 45 seconds

and then the client goes on for a while on 0 connections, then tries again on 107.170.30.182:5678 and fails again with the same message.

This is compiled from master from a couple of hours ago.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 04:48:58 pm
I wiped my ~/.BitSharesXTS....
please send
XTS2w5F6c6Vzt9BkwAeYPvcLj9j1PvBzxRzuM7akxkzwa5f8dyE12jztjn4vUKMvftgEZR87XuFe81CEZeEQyUafSdsT8Yneu
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 28, 2014, 04:53:31 pm
I wiped my ~/.BitSharesXTS....
please send
XTS2w5F6c6Vzt9BkwAeYPvcLj9j1PvBzxRzuM7akxkzwa5f8dyE12jztjn4vUKMvftgEZR87XuFe81CEZeEQyUafSdsT8Yneu

Sent
Quote
4   8309.0    2014-05-28T16:51:00 default                              toast                                -12345678
    -100000 +delegate-7   60c6bb7a2d817b836a39c0fa303934933be85761

But my synced bock header stop at 8307:
Quote
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000656251753,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 8307,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "691e69c726aebbf30c5d2ae36a375f30f69110d3",
  "blockchain_shares": 79999995799989,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 3,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 80598879,
  "wallet_balance_bips": 1007486040.3931557,
  "wallet_open": true,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "9b962306d44bdb2f5fc96eccb6bad3c4467873da",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "905eebc827e7bf88cd88c62b7435918dbe77e175"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 28, 2014, 04:57:43 pm
Hackfisher, any ideas about the situation wackou and xeroc met? I have the same problem.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 28, 2014, 05:03:37 pm
I too have public IP
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 28, 2014, 05:04:35 pm
please send me some xts


jerry (unlocked) >>> wallet_create_receive_account "test"
"XTS2QNjLRsQZPeMcQLYtNJFRdhoy5HhmnfW3o9GCeW9atEZ9iyzCiE4YR4TLcAJX7hsR2Nss8vdBK8d41p9TM4xnJMvrAqLi4"


updated

osx in virtualbox  compiled success  but connect failed
ubuntu  in virtualbox  compiled , connect & sync success.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 05:14:30 pm
That address isn't passing checksum for some reason. Try generating another one while we investigate

Also, "from bytemaster"... you should not need to create new receive accounts per transaction. They are not like bitcoin receive addresses, but a whole "account" which will use new addresses for each incoming tx automatically. You'll be able to organize by who it's from within one account
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: solaaire on May 28, 2014, 05:42:00 pm
XTS3GZi93Ww4MNS2hSJhPb5C58XjwcbXKxZTXR19rByedyrz1amriZpEYH23XTxPz2enqSyBBcQCZBK6fBsrmAa4JG3m7xZXg

ready to test! pls send some xts my way :)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 28, 2014, 06:13:51 pm
XTS3GZi93Ww4MNS2hSJhPb5C58XjwcbXKxZTXR19rByedyrz1amriZpEYH23XTxPz2enqSyBBcQCZBK6fBsrmAa4JG3m7xZXg

ready to test! pls send some xts my way :)
Sent
fd08a8812397d67807c480738b418d67c7c17752
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 28, 2014, 06:19:52 pm
XTS3GZi93Ww4MNS2hSJhPb5C58XjwcbXKxZTXR19rByedyrz1amriZpEYH23XTxPz2enqSyBBcQCZBK6fBsrmAa4JG3m7xZXg

ready to test! pls send some xts my way :)
Sent
fd08a8812397d67807c480738b418d67c7c17752

please send me some xts
XTS2QNjLRsQZPeMcQLYtNJFRdhoy5HhmnfW3o9GCeW9atEZ9iyzCiE4YR4TLcAJX7hsR2Nss8vdBK8d41p9TM4xnJMvrAqLi4
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 06:23:31 pm
XTS3GZi93Ww4MNS2hSJhPb5C58XjwcbXKxZTXR19rByedyrz1amriZpEYH23XTxPz2enqSyBBcQCZBK6fBsrmAa4JG3m7xZXg

ready to test! pls send some xts my way :)
Sent
fd08a8812397d67807c480738b418d67c7c17752

please send me some xts
XTS2QNjLRsQZPeMcQLYtNJFRdhoy5HhmnfW3o9GCeW9atEZ9iyzCiE4YR4TLcAJX7hsR2Nss8vdBK8d41p9TM4xnJMvrAqLi4

Look:

That address isn't passing checksum for some reason. Try generating another one while we investigate

Also, "from bytemaster"... you should not need to create new receive accounts per transaction. They are not like bitcoin receive addresses, but a whole "account" which will use new addresses for each incoming tx automatically. You'll be able to organize by who it's from within one account
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 28, 2014, 06:35:58 pm
囧  how can i get the right address?


jerry (locked) >>> getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000703126759,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 8515,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "4a698e21fdad4600c19a2f6ad94229825fcb0549",
  "blockchain_shares": 79999995499989,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 5680,
  "client_rpc_port": 5679,
  "network_num_connections": 1,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": true,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "5f61176a67115ea0b0594d218253b0341b063a95",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "45017830c6d8aea6df75e12bee7787f7a871d268"
}
jerry (locked) >>>
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 06:40:31 pm
The address generated by your client was for some reason bad. Do the same thing you did before, just make a new receiving account and we will try again.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 28, 2014, 06:52:50 pm
The address generated by your client was for some reason bad. Do the same thing you did before, just make a new receiving account and we will try again.

ok  i generated a new one

jerry (unlocked) >>> wallet_create_receive_account "from_talk"
"XTS2j9of1YxVQ7LFuwAjBCX5cyEYTkSLq76G9eWb5z34vgc53MBqAANZ2ou2WwtedHFXaKFppRka2acwbeQoT9brKKAe5VRXF"




seems something wrong
error  invalid  command   “validate_address”


Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 07:02:23 pm
Oh it looks like you have an old revision which uses a different format.
Try doing a "git pull" and "git submodule update" and then rebuilding.

My revision is: 67cfe3e8767a69b898e31f7e843119217b9bcd3a
Yours is:         5f61176a67115ea0b0594d218253b0341b063a95
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 07:03:42 pm
(delete ~/.BitSharesXTS too and start from scratch)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: solaaire on May 28, 2014, 07:15:43 pm
XTS3GZi93Ww4MNS2hSJhPb5C58XjwcbXKxZTXR19rByedyrz1amriZpEYH23XTxPz2enqSyBBcQCZBK6fBsrmAa4JG3m7xZXg

ready to test! pls send some xts my way :)
Sent
fd08a8812397d67807c480738b418d67c7c17752

received, thanks! ill try to leave this computer on the network as often as i can
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 28, 2014, 11:42:42 pm
Oh it looks like you have an old revision which uses a different format.
Try doing a "git pull" and "git submodule update" and then rebuilding.

My revision is: 67cfe3e8767a69b898e31f7e843119217b9bcd3a
Yours is:         5f61176a67115ea0b0594d218253b0341b063a95

git pull    compile
now is 70766ff1b1c737b988c9d27f9f4802984ba388b7
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 28, 2014, 11:47:08 pm
Oh it looks like you have an old revision which uses a different format.
Try doing a "git pull" and "git submodule update" and then rebuilding.

My revision is: 67cfe3e8767a69b898e31f7e843119217b9bcd3a
Yours is:         5f61176a67115ea0b0594d218253b0341b063a95

git pull    compile
now is 70766ff1b1c737b988c9d27f9f4802984ba388b7

that should work, make another receive account
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 29, 2014, 12:04:53 am
alt, how'd you create a delegate. i still can't seem to get it working. a

also i'm trying to use the web wallet and wasn't sure of step 1

Quote
1. Specify path to web_wallet/generated as htdocs in client's config.json.

where is the config.json?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 29, 2014, 12:09:26 am
alt, how'd you create a delegate. i still can't seem to get it working. a

also i'm trying to use the web wallet and wasn't sure of step 1

Quote
1. Specify path to web_wallet/generated as htdocs in client's config.json.

where is the config.json?
Just run the command "wallet_register_delegate"
I got no vote, lol
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 29, 2014, 12:10:49 am
Hackfisher, any ideas about the situation wackou and xeroc met? I have the same problem.
Do you guys connect to network?
I have connected to you.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 12:26:18 am
Oh it looks like you have an old revision which uses a different format.
Try doing a "git pull" and "git submodule update" and then rebuilding.

My revision is: 67cfe3e8767a69b898e31f7e843119217b9bcd3a
Yours is:         5f61176a67115ea0b0594d218253b0341b063a95

git pull    compile
now is 70766ff1b1c737b988c9d27f9f4802984ba388b7

that should work, make another receive account

3q

(wallet closed) >>> wallet_create jerry
new passphrase:
new passphrase (verify):
Wallet unlocked for 5 minutes, use wallet_unlock for more time
OK
jerry (unlocked) >>> wallet_create_receive_account "frome_btstalk"
"XTS359cFBkEZ55g53NwPZoo6qVh87shp2r83uQ5bWDsPH3VFjtX9Yz4xZMqmv83xnyxg87nX4H6WjnWXDL3uE21rJ94ydmJsW"

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 29, 2014, 12:42:30 am
Hackfisher, any ideas about the situation wackou and xeroc met? I have the same problem.
Do you guys connect to network?
I have connected to you.

Thanks to alt and sudo.

@xeroc and @wackou :
For those who are running Ubuntu in virtual machine, try using Bridge instead of NAT in the network setting. Also launch your client this way ./bitshares_client --server  (add parameter --server)    In this way my connection problem got solved.

My address:XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY

Can anyone send me some bips?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 29, 2014, 01:09:03 am
It's weired, Can't create account for your key or sudo's key.
I can create account for toast's key

Code: [Select]
alt (unlocked) >>> wallet_create_sending_account heyD XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY
assert
checksum == fc::ripemd160::hash( data.data(), sizeof(*this) )._hash[0]:
    {}
    th_a  extended_address.cpp:171 extended_address
decoding address XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY
    {"address":"XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY"}
    th_a  extended_address.cpp:173 extended_address

    {"command":"wallet_create_sending_account"}
    th_a  cli.cpp:401 execute_command
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gyhy on May 29, 2014, 01:10:56 am
有没有windows版本啊。我的笔记本是win7啊
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 01:30:26 am
Very strange that some people's clients are generating extended pubkeys that don't validate.

Did you guys do "git submodule update" as well as git pull?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 01:51:37 am
Very strange that some people's clients are generating extended pubkeys that don't validate.

Did you guys do "git submodule update" as well as git pull?

yes

git pull
git submodule init
git submodule update
cmake .
make
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gyhy on May 29, 2014, 02:23:36 am
光看到测试发送接收了,咋没看到交易呢。buy/sell
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 03:01:41 am
It's weired, Can't create account for your key or sudo's key.
I can create account for toast's key

Code: [Select]
alt (unlocked) >>> wallet_create_sending_account heyD XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY
assert
checksum == fc::ripemd160::hash( data.data(), sizeof(*this) )._hash[0]:
    {}
    th_a  extended_address.cpp:171 extended_address
decoding address XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY
    {"address":"XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY"}
    th_a  extended_address.cpp:173 extended_address

    {"command":"wallet_create_sending_account"}
    th_a  cli.cpp:401 execute_command

i tested ok

 wallet_create_sending_account jerry  XTS359cFBkEZ55g53NwPZoo6qVh87shp2r83uQ5bWDsPH3VFjtX9Yz4xZMqmv83xnyxg87nX4H6WjnWXDL3uE21rJ94ydmJsW
OK


jerry (unlocked) >>> wallet_create_sending_account heyD XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY
OK

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 29, 2014, 05:07:31 am
Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      toast                                -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

then I quit the client, run again, show the history, it can't show the address with account name.

Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      XTSHms9EYNLKEHYDQa3qDjKn4y2Dyb61Dj94 -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

I must transfer another bts to toast agian, then it can show the account name correctly.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 05:20:58 am
Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      toast                                -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

then I quit the client, run again, show the history, it can't show the address with account name.

Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      XTSHms9EYNLKEHYDQa3qDjKn4y2Dyb61Dj94 -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

I must transfer another bts to toast agian, then it can show the account name correctly.


would you please send some xts to me? tks
XTS359cFBkEZ55g53NwPZoo6qVh87shp2r83uQ5bWDsPH3VFjtX9Yz4xZMqmv83xnyxg87nX4H6WjnWXDL3uE21rJ94ydmJsW
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 05:23:00 am
can this visual(http://dotp2p.io/visualize.php)  embedded in client?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 29, 2014, 09:17:20 am
Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      toast                                -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

then I quit the client, run again, show the history, it can't show the address with account name.

Code: [Select]
alt (locked) >>> wallet_get_transaction_history_summary
...
 13   9771.0    2014-05-29T05:02:00 from_bytemaster                      XTSHms9EYNLKEHYDQa3qDjKn4y2Dyb61Dj94 -12345678       -100000 +delegate-2   bc6b040afd3e525f7da8e485e0c76febdd4792dd

I must transfer another bts to toast agian, then it can show the account name correctly.


would you please send some xts to me? tks
XTS359cFBkEZ55g53NwPZoo6qVh87shp2r83uQ5bWDsPH3VFjtX9Yz4xZMqmv83xnyxg87nX4H6WjnWXDL3uE21rJ94ydmJsW

Can not transfer due to following issue, which version are you using, try upgrading:

https://github.com/BitShares/bitshares_toolkit/issues/147 (https://github.com/BitShares/bitshares_toolkit/issues/147)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on May 29, 2014, 09:44:41 am
I'm up and running on Ubuntu :)

Can anyone send me some bts pls?

XTS2bcpFdgfoVYm6L9yh6vKdukyGUXFcm5kEeMYeLcWTto3ZdfDZCPrfPuEMJc91k4D5tEhQJsPfn1zf8mFH1RzqVqXMt1Z3R

Got quickly caught up on blocks I think, without any freezes, currently at 10335.

I tried to register a delegate but I see there's a minimum fee. What's the second, <data> parameter of the command though?

Code: [Select]
wallet_register_delegate <name> <data> 
           Registers a delegate to be voted upon by shareholders
 

PS. A line break would be nice in the command explanations, at the moment the formatting is strange in the terminal. Someone just needs to modify the make_short_description method in rpc_server.cpp:
Code: [Select]
sstream << help_string << " " << method_data.description << "\n";
to:
Code: [Select]
sstream << help_string << "\n   : " << method_data.description << "\n";
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 29, 2014, 10:21:57 am
@xeroc and @wackou :
For those who are running Ubuntu in virtual machine, try using Bridge instead of NAT in the network setting. Also launch your client this way ./bitshares_client --server  (add parameter --server)    In this way my connection problem got solved.

My address:XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY

Can anyone send me some bips?
Not working :-(
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: radiumlau on May 29, 2014, 11:57:47 am
send some, please:

XTS2XWdKLzGS9BqJgEMHfLxphNxpkDqHwGBVEYCATsR2SRRdrftwTWEeZay41um4C677hHRcJc2rcgqqzQVhDzNy5TCL8iiQy
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 29, 2014, 12:03:01 pm
I'm up and running on Ubuntu :)

Can anyone send me some bts pls?

XTS2bcpFdgfoVYm6L9yh6vKdukyGUXFcm5kEeMYeLcWTto3ZdfDZCPrfPuEMJc91k4D5tEhQJsPfn1zf8mFH1RzqVqXMt1Z3R

Got quickly caught up on blocks I think, without any freezes, currently at 10335.

I tried to register a delegate but I see there's a minimum fee. What's the second, <data> parameter of the command though?

Code: [Select]
wallet_register_delegate <name> <data> 
           Registers a delegate to be voted upon by shareholders
 

PS. A line break would be nice in the command explanations, at the moment the formatting is strange in the terminal. Someone just needs to modify the make_short_description method in rpc_server.cpp:
Code: [Select]
sstream << help_string << " " << method_data.description << "\n";
to:
Code: [Select]
sstream << help_string << "\n   : " << method_data.description << "\n";

Quote
assert
checksum == fc::ripemd160::hash( data.data(), sizeof(*this) )._hash[0]:
    {}
    th_a  extended_address.cpp:171 bts::blockchain::extended_address::extended_address
decoding address XTS3GfntoKakKVWotiPDxGbDrsTaa33xAw4kFPmKWiQMr2PcYvYksdP3CBFLhjKjTNkP8HSSpsyN5vL75K1zsNycdsQEiHigY

could you try following and post a new account address?

Code: [Select]
git pull
git submodule update
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 29, 2014, 12:21:43 pm
send some, please:

XTS2XWdKLzGS9BqJgEMHfLxphNxpkDqHwGBVEYCATsR2SRRdrftwTWEeZay41um4C677hHRcJc2rcgqqzQVhDzNy5TCL8iiQy

Sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on May 29, 2014, 12:29:46 pm
.... quote removed....

could you try following and post a new account address?

Code: [Select]
git pull
git submodule update

Is the adress no good?

I only built it this morning, like 2-3 hours ago.. Here's a new address:

Code: [Select]
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git pull
Already up-to-date.
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git submodule update

Code: [Select]
(wallet closed) >>> wallet_create "second_wallet"
new passphrase:
new passphrase (verify):
Wallet unlocked for 5 minutes, use wallet_unlock for more time
OK
second_wallet (unlocked) >>> wallet_create_receive_account "second_receive"
"XTS2MNV9YJofhXef65qKNLETa2GLUVbfF7KofhxgZCufLVnwVeJoMkPxCBdbFGgNkmsza2MqXigXCQVLBLfpXX6iR7VQMApXJ"
second_wallet (unlocked) >>>
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 29, 2014, 12:37:20 pm
.... quote removed....

could you try following and post a new account address?

Code: [Select]
git pull
git submodule update

Is the adress no good?

I only built it this morning, like 2-3 hours ago.. Here's a new address:

Code: [Select]
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git pull
Already up-to-date.
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git submodule update

Code: [Select]
(wallet closed) >>> wallet_create "second_wallet"
new passphrase:
new passphrase (verify):
Wallet unlocked for 5 minutes, use wallet_unlock for more time
OK
second_wallet (unlocked) >>> wallet_create_receive_account "second_receive"
"XTS2MNV9YJofhXef65qKNLETa2GLUVbfF7KofhxgZCufLVnwVeJoMkPxCBdbFGgNkmsza2MqXigXCQVLBLfpXX6iR7VQMApXJ"
second_wallet (unlocked) >>>

Still can not create sending account for this address, could you help provide "getinfo" output here, which contains the code revision number of your build.
I'm not sure, could be a bug, or a compatible issue, let's check it.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on May 29, 2014, 01:10:12 pm
.... quote removed....

could you try following and post a new account address?

Code: [Select]
git pull
git submodule update

Is the adress no good?

I only built it this morning, like 2-3 hours ago.. Here's a new address:

Code: [Select]
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git pull
Already up-to-date.
sigve@sigve-UL30VT: ~/bitshares_toolkit $ git submodule update

Code: [Select]
(wallet closed) >>> wallet_create "second_wallet"
new passphrase:
new passphrase (verify):
Wallet unlocked for 5 minutes, use wallet_unlock for more time
OK
second_wallet (unlocked) >>> wallet_create_receive_account "second_receive"
"XTS2MNV9YJofhXef65qKNLETa2GLUVbfF7KofhxgZCufLVnwVeJoMkPxCBdbFGgNkmsza2MqXigXCQVLBLfpXX6iR7VQMApXJ"
second_wallet (unlocked) >>>

Still can not create sending account for this address, could you help provide "getinfo" output here, which contains the code revision number of your build.
I'm not sure, could be a bug, or a compatible issue, let's check it.

Sure, here you go:

Code: [Select]
second_wallet (unlocked) >>> getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.50000078125208,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 10744,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "4872a3e197793845fec3b7885c29e97140750318",
  "blockchain_shares": 79999994999987,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 1,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": true,
  "wallet_unlocked_until": "20140529T131340",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "70766ff1b1c737b988c9d27f9f4802984ba388b7",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "1e93c2e77eeada1e2fde35fa38fe701d6231d3d2"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 29, 2014, 01:43:00 pm
Could anyone send me some bips ?

XTS3F32RC7KCyxjjmDeTbUbXU3nDNAcK3xnKR9rBg4yLBRob894MKhxj8Cg99WMgp2h8P49yxKnM1xmhoAGsb6dAiFRswXcgt

哪位大爷行行好,送我一顿晚餐?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: crazybit on May 29, 2014, 01:50:09 pm
appreciated if could sent me some fund.

XTS393aySU6RQ1sWGJxKX2vMwxbLJwjopVmBpgkREYWYXQvdVZLftsVJhXrMaeyHRg6rdagvrjEUg3hKHr2BM6krSUd2ktqBN

and my node:58.62.197.239, see if anyone can connect to me.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on May 29, 2014, 02:03:00 pm
Could anyone send me some bips ?

XTS3F32RC7KCyxjjmDeTbUbXU3nDNAcK3xnKR9rBg4yLBRob894MKhxj8Cg99WMgp2h8P49yxKnM1xmhoAGsb6dAiFRswXcgt

哪位大爷行行好,送我一顿晚餐?

Are you running on 32 bit arch os? Can not create sending account for your address, which should be a bug.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 02:06:01 pm
I tested on a few more configs, here are my findings:

test machines:
- vps: debian stable + required libs from testing (boost 1.55, cmake), running on a virtual server with public IP
- vbox: debian stable + required libs from testing (boost 1.55, cmake), running in a virtualbox on my macbook
- macbook: OSX10.9, client precompiled by bytemaster

connection results:
- macbook has no problem connecting, tested at work and at home
- neither vps nor vbox can connect. I thought it was because of the public ip at first, but then vbox should be able to connect, however it doesn't. I tried launching it with --server, although I don't see why it should help, and it didn't. I also tried running vbox with bridge mode instead of NAT, to no avail. Did those multiple times, and after deleting ~/.Bitshares too.

So it looks like it might not be due to having a public ip but rather some problem with the config I'm using (some lib in debian that doesn't work but works in ubuntu?), or the upnp code not working properly in linux.

Here's the version I tried:
Code: [Select]
(wallet closed) >>> get_info
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "70766ff1b1c737b988c9d27f9f4802984ba388b7",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "365be6ac70a1dfbc69f331f44db6a90fa8d02c42"
}

Also, by looking at the diff between the logs, here's what I get on osx when it connects:
Code: [Select]
3184005ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678          node.cpp:1850
3184005ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)          node.cpp:1873
and then:
Code: [Select]
3184255ms       th_a           connect_to ] established outbound connection to 107.170.30.182:5678          node.cpp:440
3184255ms       th_a      connect_to_task ] Sent "hello" to remote peer 107.170.30.182:5678         node.cpp:1786
3184380ms       th_a on_hello_reply_messa ] Received a reply to my "hello" from 107.170.30.182:5678, connection is accepted         node.cpp:1034

and here's the same place in the log for the linux client which doesn't:
Code: [Select]
2770636ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1999
2770636ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2022
2770637ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104
and then
Code: [Select]
2775645ms       upnp           operator() ] No valid UPnP IGDs found                    upnp.cpp:145

let me know if there's anything else I can do to help. Also, should I report this to github or is here a good place to discuss?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 02:09:14 pm
will try using ubuntu in a virtualbox, then we'll know if this is a difference between debian/ubuntu or if it's something else... Trying 14.04, this one should be working, yes?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 02:50:50 pm
Could anyone send me some bips ?

XTS3F32RC7KCyxjjmDeTbUbXU3nDNAcK3xnKR9rBg4yLBRob894MKhxj8Cg99WMgp2h8P49yxKnM1xmhoAGsb6dAiFRswXcgt

哪位大爷行行好,送我一顿晚餐?

Are you running on 32 bit arch os? Can not create sending account for your address, which should be a bug.

32bit ubuntu  under virtualbox

my address  if it's ok?
XTS2UyMMa3DcyX697GvjVdMTqLyJjHd3UFT5G8jzMiBTH673gmvqX8nhcJhAxDXaN8Nj5MK996asuZGmbScGtRiNH9YNSuztn
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 29, 2014, 02:54:25 pm
Could anyone send me some bips ?

XTS3F32RC7KCyxjjmDeTbUbXU3nDNAcK3xnKR9rBg4yLBRob894MKhxj8Cg99WMgp2h8P49yxKnM1xmhoAGsb6dAiFRswXcgt

哪位大爷行行好,送我一顿晚餐?

Are you running on 32 bit arch os? Can not create sending account for your address, which should be a bug.

Yes, 32bit. Replied you via QQ
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 03:09:22 pm
ok, so:
- debian in a vbox doesn't connect
- ubuntu in a vbox does connect

so it must be something with the difference in dependencies... Maybe boost? (debian: 1.55, ubuntu: 1.54)

I'll try to investigate more if I can find some time to look into that.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 03:15:55 pm
ok, so:
- debian in a vbox doesn't connect
- ubuntu in a vbox does connect

so it must be something with the difference in dependencies... Maybe boost? (debian: 1.55, ubuntu: 1.54)

I'll try to investigate more if I can find some time to look into that.

boost seems the culprit, we require 1.54
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 29, 2014, 03:34:18 pm
boost seems the culprit, we require 1.54
+5% in correlation

Have
+public ip
+debian
+boost 1.55
+cannot connect :-(
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 29, 2014, 03:40:57 pm
boost seems the culprit, we require 1.54
+5% in correlation

Have
+public ip
+debian
+boost 1.55
+cannot connect :-(

Try my node: network_add_node "113.80.228.217:5678" add
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: mauritso on May 29, 2014, 04:13:01 pm
Code: [Select]
XTS2JBkPPFXd1FLNsjsfhpQSCc1JW72NqxW21SPNzcRUaqaxQvu1dhwHZkeAiAGS56mxYzPyyzp7V4wQPeabmDrcnmuZeDyJN
Got it running, can I have some "testnet" funds?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 29, 2014, 04:24:32 pm
Try my node: network_add_node "113.80.228.217:5678" add
Same negative result. I am pretty sure there is some library fuckup :-(
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 04:40:46 pm
wallet_import_bitcoin wallet.dat  =>  balance still 0

myaddress  XTS2UyMMa3DcyX697GvjVdMTqLyJjHd3UFT5G8jzMiBTH673gmvqX8nhcJhAxDXaN8Nj5MK996asuZGmbScGtRiNH9YNSuztn


jerry (unlocked) >>> getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000796877082,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 11166,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "d89955464899f3a2aba584517c098e8db875430e",
  "blockchain_shares": 79999994899987,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 5680,
  "client_rpc_port": 5679,
  "network_num_connections": 2,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": true,
  "wallet_unlocked_until": "20140529T164233",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "70766ff1b1c737b988c9d27f9f4802984ba388b7",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "c75c695cbd7d44adc4261aed7a2ad170efc063b0"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 04:42:25 pm
@xeroc try using a fresh debian but use "apt-get install libboost1.54-dev libboost1.54-dev-all"
The "BUILD_UBUNTU.md" really is just for ubuntu =P

@sudo This testnet does not have any of the snapshot keys
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 04:52:09 pm
@xeroc try using a fresh debian but use "apt-get install libboost1.54-dev libboost1.54-dev-all"
The "BUILD_UBUNTU.md" really is just for ubuntu =P

@sudo This testnet does not have any of the snapshot keys


seem can‘t use  the command  "validate_address"


jerry (locked) >>> validate_address XTS2UyMMa3DcyX697GvjVdMTqLyJjHd3UFT5G8jzMiBTH673gmvqX8nhcJhAxDXaN8Nj5MK996asuZGmbScGtRiNH9YNSuztn
Usage:
validate_address <address>                                                                            Return information about given BitShares address

TODO: bitcoin supports all below info

Arguments:
1. "bitsharesaddress" (string, required) The BitShares address to validate

Result:
{
"isvalid" : true|false, (boolean) If the address is valid or not. If not, this is the only property returned.
"address" : "bitsharesaddress", (string) The BitShares address validated
"ismine" : true|false, (boolean) If the address is yours or not
"isscript" : true|false, (boolean) If the key is a script
"pubkey" : "publickeyhex", (string) The hex value of the raw public key
"iscompressed" : true|false, (boolean) If the address is compressed
"account" : "account" (string) The account associated with the address, "" is the default account
}

Examples:
> bitshares-cli validate_address "1PSSGeFHDnKNxiEyFrD1wcEaHr9hrQDDWc"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "validate_address", "params": ["1PSSGeFHDnKNxiEyFrD1wcEaHr9hrQDDWc"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
jerry (locked) >>>

------------
bitshares-cli
Error: invalid command "bitshares-cli"
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 04:57:58 pm
validate_address is deprecated, says Dan.

To validate your own address I think you should be able to "wallet_create_sending_address" for yourself
^^ yep this works, do your own addresses validate?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 06:43:50 pm
boost seems the culprit, we require 1.54

Do you know why 1.54 is required? Is it because of this issue or sth else? Is it something in boost::asio?

I'd like to try to fix bitshares to be able to use 1.55 rather than use a fixed version of boost (although 1.54 is available in testing)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 29, 2014, 08:00:36 pm
boost seems the culprit, we require 1.54

Do you know why 1.54 is required? Is it because of this issue or sth else? Is it something in boost::asio?

I'd like to try to fix bitshares to be able to use 1.55 rather than use a fixed version of boost (although 1.54 is available in testing)

It should work with all 1.54 or newer versions.  If there is something in 1.55 that is causing an issue it is a bug to be fixed.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 08:17:01 pm
Actually, it seems like boost wasn't the culprit at all...

Just recompiled with boost 1.54 on debian, both on the machine with a public ip and my virtual box, and they still can't connect. Ubuntu on the same virtualbox can connect. So it must be something else, I'll try to investigate.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 08:43:29 pm
I might have broken the build... hold tight
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 29, 2014, 08:44:30 pm
recompiled on debian with gcc 4.8, libdb 5.3, boost 1.54 (same as ubuntu), still can't connect...
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 08:57:27 pm
recompiled on debian with gcc 4.8, libdb 5.3, boost 1.54 (same as ubuntu), still can't connect...

Try now. I had pushed bad changes, it may simply be that you were force disconnecting nodes since the validation was different
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: mauritso on May 29, 2014, 10:50:42 pm
Code: [Select]
XTS2JBkPPFXd1FLNsjsfhpQSCc1JW72NqxW21SPNzcRUaqaxQvu1dhwHZkeAiAGS56mxYzPyyzp7V4wQPeabmDrcnmuZeDyJN
Got it running, can I have some "testnet" funds?

Nothing shows when I run "wallet_get_balance" so I assume I didn't get send anything, can I get some to play around with please?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 29, 2014, 11:21:10 pm
Code: [Select]
XTS2JBkPPFXd1FLNsjsfhpQSCc1JW72NqxW21SPNzcRUaqaxQvu1dhwHZkeAiAGS56mxYzPyyzp7V4wQPeabmDrcnmuZeDyJN
Got it running, can I have some "testnet" funds?

Nothing shows when I run "wallet_get_balance" so I assume I didn't get send anything, can I get some to play around with please?

sent
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 29, 2014, 11:31:55 pm
i  install  ubuntu 14.04LTS 64bit into VirtualBox
get bitshares_toolkit up to date
my  new address is 

Code: [Select]
XTS2AUWwchqJwLb2kLKmg7QHKT55wDz5xWQZUaviwbvwa2Qm6RKU97wxBsAnjgNgaGwrpxb7yzBqG4LY6QNGcnVUUJJFhppjm
if it's work?  can anyone send some xts to me for test?



sudo apt-get update
sudo apt-get install cmake git libreadline-dev uuid-dev g++ libdb++-dev libdb-dev zip libssl-dev openssl build-essential python-dev autotools-dev libicu-dev build-essential libbz2-dev libboost-dev libboost-all-dev
git clone https://github.com/BitShares/bitshares_toolkit.git
cd bitshares_toolkit
git pull
git submodule init
git submodule update
cmake .
make

Code: [Select]
jerry (unlocked) >>> getinfo
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000468750329,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 3797,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "ffffe96cfd46627a5087b8ed30c64b1e7772c526",
  "blockchain_shares": 79999996999998,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 5680,
  "client_rpc_port": 5679,
  "network_num_connections": 1,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": true,
  "wallet_unlocked_until": "20140529T233231",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "f5673a6f09d6228caf3cb204dc641d70f8e8079d",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "5b00a6ffc18626ca521a0bda5e5bb16dcecb0e48"
}
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: mauritso on May 29, 2014, 11:45:37 pm
Code: [Select]
XTS2JBkPPFXd1FLNsjsfhpQSCc1JW72NqxW21SPNzcRUaqaxQvu1dhwHZkeAiAGS56mxYzPyyzp7V4wQPeabmDrcnmuZeDyJN
Got it running, can I have some "testnet" funds?

Nothing shows when I run "wallet_get_balance" so I assume I didn't get send anything, can I get some to play around with please?

sent

I got it, thanks.

Is there something we can do if we don't encounter bugs? (the output of certain commands for example)

Running the already compiled OS X client on 10.9. No issues so far.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: jwiz168 on May 30, 2014, 12:40:53 am
just keep on testing...
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 30, 2014, 12:44:08 am
So far this test has proven very productive... we are going for longevity here.  We have found and fixed many bugs.  The goal is to identify any bugs that may lead to a hard fork. 

We will have some major updates for you all to test next week.   
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gyhy on May 30, 2014, 12:57:28 am
So far this test has proven very productive... we are going for longevity here.  We have found and fixed many bugs.  The goal is to identify any bugs that may lead to a hard fork. 

We will have some major updates for you all to test next week.   
+5%加油
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: lzr1900 on May 30, 2014, 01:21:40 am
XTS2fERKqHrHDLp7Jmdrt1xXNSAKGe3Uow9FdRdeTWt4N4kgdBXm9YBKT4nTQZ8CTBC7VsrDZApA8NBWJGHUhTn9MY37rvFZp

thanks~ :D
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 30, 2014, 01:24:32 am
i  install  ubuntu 14.04LTS 64bit into VirtualBox
get bitshares_toolkit up to date
my  new address is 

Code: [Select]
XTS2AUWwchqJwLb2kLKmg7QHKT55wDz5xWQZUaviwbvwa2Qm6RKU97wxBsAnjgNgaGwrpxb7yzBqG4LY6QNGcnVUUJJFhppjm
if it's work?  can anyone send some xts to me for test?

works, sent

Quote
XTS2fERKqHrHDLp7Jmdrt1xXNSAKGe3Uow9FdRdeTWt4N4kgdBXm9YBKT4nTQZ8CTBC7VsrDZApA8NBWJGHUhTn9MY37rvFZp

sent

Quote
Is there something we can do if we don't encounter bugs? (the output of certain commands for example)

keep it running a while
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 30, 2014, 02:26:24 am
i  install  ubuntu 14.04LTS 64bit into VirtualBox
get bitshares_toolkit up to date
my  new address is 

Code: [Select]
XTS2AUWwchqJwLb2kLKmg7QHKT55wDz5xWQZUaviwbvwa2Qm6RKU97wxBsAnjgNgaGwrpxb7yzBqG4LY6QNGcnVUUJJFhppjm
if it's work?  can anyone send some xts to me for test?

works, sent

Quote
XTS2fERKqHrHDLp7Jmdrt1xXNSAKGe3Uow9FdRdeTWt4N4kgdBXm9YBKT4nTQZ8CTBC7VsrDZApA8NBWJGHUhTn9MY37rvFZp

sent

Quote
Is there something we can do if we don't encounter bugs? (the output of certain commands for example)

keep it running a while


seems like  not received 

jerry (unlocked) >>> wallet_get_balance
[[
    0,
    "XTS"
  ]
]
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 02:51:18 am
howto testing web wallet?
Are there some docments?
I have run
Code: [Select]
lineman up
./bitshares_client --server --httpport 9989
But when I open the web page, seems all rpc call is failed, here is the error msg from firefox
Code: [Select]
RPC error calling wallet_list_receive_accounts: prefixMatchingApiProxy is not defined (500)

I am not family with js, here is the error msg from console
Code: [Select]
ReferenceError: prefixMatchingApiProxy is not defined
    at /home/alt/workspace/web_wallet/config/server.js:21:57
    at callbacks (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/lib/router/index.js:164:37)
    at multipart (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/multipart.js:81:27)
    at /home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:57:9
    at urlencoded (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/urlencoded.js:46:27)
    at /home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:55:7
    at IncomingMessage.<anonymous> (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/json.js:72:9)
    at IncomingMessage.EventEmitter.emit (events.js:92:17)
    at _stream_readable.js:919:16
    at process._tickCallback (node.js:419:13)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 02:56:28 am
And when I view the web wallet from my phone, it can't display the menu field.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 30, 2014, 03:22:06 am
howto testing web wallet?
Are there some docments?
I have run
Code: [Select]
lineman up
./bitshares_client --server --httpport 9989
But when I open the web page, seems all rpc call is failed, here is the error msg from firefox
Code: [Select]
RPC error calling wallet_list_receive_accounts: prefixMatchingApiProxy is not defined (500)

I am not family with js, here is the error msg from console
Code: [Select]
ReferenceError: prefixMatchingApiProxy is not defined
    at /home/alt/workspace/web_wallet/config/server.js:21:57
    at callbacks (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/lib/router/index.js:164:37)
    at multipart (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/multipart.js:81:27)
    at /home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:57:9
    at urlencoded (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/urlencoded.js:46:27)
    at /home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/bodyParser.js:55:7
    at IncomingMessage.<anonymous> (/home/alt/workspace/web_wallet/node_modules/lineman/node_modules/express/node_modules/connect/lib/middleware/json.js:72:9)
    at IncomingMessage.EventEmitter.emit (events.js:92:17)
    at _stream_readable.js:919:16
    at process._tickCallback (node.js:419:13)


how to install  lineman?


./bitshares_client --server --httpport 9989
127.0.0.1:9989 on firefox

there appears a dialog   

Authentication Required
A username and password are being requested by  http://127.0.0.1:9989/
the site says:"bts wallet"
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 03:29:45 am
1. install nodejs
download from http://www.nodejs.org/download/
install it, and set the ENV PATH to your install bin path.

2. install nodejs modules: lineman,lineman-angular,lineman-less,html-minifier,ngmin
Code: [Select]
cd bitshares_toolkit/program/client/htdocs
npm install lineman lineman-angular lineman-less html-minifier ngmin
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: AdamBLevine on May 30, 2014, 04:07:44 am
Is this going well?  I can't tell from the posts lol.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 30, 2014, 04:38:52 am
Is this going well?  I can't tell from the posts lol.

tl;dr better than I expected

We haven't had to reset even once! Plenty of bugs but most stuff is at the level of the client (usability). Managed to make several very big updates without having to hard fork. Dan thinks we won't even need to reset for TITAN+architecture changes. Good chance this is our last testnet if that's true.

DPOS looks solid so far, what a relief. Big props to Eric for his huge network test suite. Really want to get delegate voting up so we can let people try to really misbehave and split the network.
As a non-delegate, any time I've made a bad change I just got disconnected and the rest of the network chugged along unaffected.

Worst bug so far is that the ECC library is totally broken for 32 bit machines... that's like half the windows users. Also some users experiencing mysterious connection issues. Minor issues w.r.t the network as a whole, but terrible if you're the one experiencing them =P.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 30, 2014, 04:39:39 am
main thing I've learned from this is that the skill gap between me and Dan+Eric is scary
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bodenliu on May 30, 2014, 04:56:12 am
main thing I've learned from this is that the skill gap between me and Dan+Eric is scary

you guys have done great job!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 05:04:55 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else

compile and try again.


I tested on a few more configs, here are my findings:

test machines:
- vps: debian stable + required libs from testing (boost 1.55, cmake), running on a virtual server with public IP
- vbox: debian stable + required libs from testing (boost 1.55, cmake), running in a virtualbox on my macbook
- macbook: OSX10.9, client precompiled by bytemaster

connection results:
- macbook has no problem connecting, tested at work and at home
- neither vps nor vbox can connect. I thought it was because of the public ip at first, but then vbox should be able to connect, however it doesn't. I tried launching it with --server, although I don't see why it should help, and it didn't. I also tried running vbox with bridge mode instead of NAT, to no avail. Did those multiple times, and after deleting ~/.Bitshares too.

So it looks like it might not be due to having a public ip but rather some problem with the config I'm using (some lib in debian that doesn't work but works in ubuntu?), or the upnp code not working properly in linux.

Here's the version I tried:
Code: [Select]
(wallet closed) >>> get_info
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "70766ff1b1c737b988c9d27f9f4802984ba388b7",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "365be6ac70a1dfbc69f331f44db6a90fa8d02c42"
}

Also, by looking at the diff between the logs, here's what I get on osx when it connects:
Code: [Select]
3184005ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678          node.cpp:1850
3184005ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)          node.cpp:1873
and then:
Code: [Select]
3184255ms       th_a           connect_to ] established outbound connection to 107.170.30.182:5678          node.cpp:440
3184255ms       th_a      connect_to_task ] Sent "hello" to remote peer 107.170.30.182:5678         node.cpp:1786
3184380ms       th_a on_hello_reply_messa ] Received a reply to my "hello" from 107.170.30.182:5678, connection is accepted         node.cpp:1034

and here's the same place in the log for the linux client which doesn't:
Code: [Select]
2770636ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678                  node.cpp:1999
2770636ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)                  node.cpp:2022
2770637ms       th_a           connect_to ] Exception binding outgoing connection to desired local endpoint: bind: Address already in use                       tcp_socket.cpp:104
and then
Code: [Select]
2775645ms       upnp           operator() ] No valid UPnP IGDs found                    upnp.cpp:145

let me know if there's anything else I can do to help. Also, should I report this to github or is here a good place to discuss?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 30, 2014, 06:49:22 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else
That's a no go on my side .. same thing :-( no connections
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: muse-umum on May 30, 2014, 06:57:28 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else
That's a no go on my side .. same thing :-( no connections

Wow, man you really need to burn your computer.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 07:20:05 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else
That's a no go on my side .. same thing :-( no connections
netstat -ap | grep bitshares
what's the output?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 30, 2014, 08:04:23 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else
That's a no go on my side .. same thing :-( no connections
netstat -ap | grep bitshares
what's the output?
Code: [Select]
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      5472/bitshares_clie
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 08:12:29 am
you should run netstat  after run bitshares_client.
what's the connect state to seed node: 107.170.30.182?
and you can run:
Code: [Select]
telnet 107.170.30.182 5678
test if you can connect  to the seed node.

If you can't telnet to the host, it's because of the network problem, you should add other node.
If you can telnet, but bitshares_client can't complete shaking hand with seed node, modify the souce code should work.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 30, 2014, 08:26:29 am
you should run netstat  after run bitshares_client.
what's the connect state to seed node: 107.170.30.182?
and you can run:
Code: [Select]
telnet 107.170.30.182 5678
test if you can connect  to the seed node.

If you can't telnet to the host, it's because of the network problem, you should add other node.
If you can telnet, but bitshares_client can't complete shaking hand with seed node, modify the souce code should work.

Code: [Select]
nc 107.170.30.182 5678
�t;AU��DҸ�l�7�
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 30, 2014, 08:30:24 am
When I run
Code: [Select]
watch -n1 "netstat -nap  | grep 107.170.30.182"and do a
Code: [Select]
network_add_node "107.170.30.182:5678" onetry
no connection appears :-(

When relaunching the bitshares deamon I could see a udp port open up .. and closing again after a few seconds

Code: [Select]
tcp        0      0 0.0.0.0:5678            0.0.0.0:*               LISTEN      5885/bitshares_clie
udp        0      0 0.0.0.0:50682           0.0.0.0:*                           5885/bitshares_clie


//EDIT:
interestingly:
Code: [Select]
36 3243129ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:986
 37 3243129ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:671
 38 3243129ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)   node.cpp:775
 39 3243129ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory   node.cpp:824
 40 3243315ms       th_a           connect_to ] established outbound connection to 107.170.30.182:5678   node.cpp:462
 41 3243316ms       th_a      connect_to_task ] Sent "hello" to remote peer 107.170.30.182:5678   node.cpp:1935
 42 3243409ms       th_a on_connection_reject ] Received a rejection in response to my "hello"   node.cpp:1198
 43 3243410ms       th_a            read_loop ] disconnected eof                                                                                                                                       
 44 End of file
 45     {"message":"End of file"}
 46     asio  asio.cpp:22 read_write_handler
 47
 48     {"len":16}
 49     th_a  stcp_socket.cpp:74 readsome   message_oriented_connection.cpp:131
 50 3243410ms       th_a on_connection_closed ] Remote peer 107.170.30.182:5678 closed their connection to us   node.cpp:1542

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: mauritso on May 30, 2014, 09:02:00 am
Probably nothing, running the client for more than a day now.

The output when doing nothing (for a while) is:

Code: [Select]
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.

Etc.

Is that expected behaviour or is there something wrong with UPnP on my end?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: wackou on May 30, 2014, 09:50:24 am
libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else

compile and try again.

that fixed it for me, both on the machine with public ip and the one in the virtualbox.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 30, 2014, 09:59:02 am
My full info:

Code: [Select]
  1 3451814ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_number_db is not upgradeable   upgrade_leveldb.cpp:44
  2 3451821ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/fork_db is not upgradeable   upgrade_leveldb.cpp:44
  3 3451827ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/property_db is not upgradeable   upgrade_leveldb.cpp:44
  4 3451832ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_db is not upgradeable   upgrade_leveldb.cpp:44
  5 3451840ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/proposal_vote_db is not upgradeable   upgrade_leveldb.cpp:44
  6 3452095ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/undo_state_db is not upgradeable   upgrade_leveldb.cpp:44
  7 3452100ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_num_to_id_db is not upgradeable   upgrade_leveldb.cpp:44
  8 3452105ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/block_id_to_block_db is not upgradeable   upgrade_leveldb.cpp:44
  9 3452109ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/pending_transaction_db is not upgradeable   upgrade_leveldb.cpp:44
 10 3452114ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/asset_db is not upgradeable   upgrade_leveldb.cpp:44
 11 3452118ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/balance_db is not upgradeable   upgrade_leveldb.cpp:44
 12 3452125ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_db is not upgradeable   upgrade_leveldb.cpp:44
 13 3452129ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/name_index_db is not upgradeable   upgrade_leveldb.cpp:44                                                     
 14 3452133ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/symbol_index_db is not upgradeable   upgrade_leveldb.cpp:44
 15 3452138ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/delegate_vote_index_db is not upgradeable   upgrade_leveldb.cpp:44
 16 3452143ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/ask_db is not upgradeable   upgrade_leveldb.cpp:44
 17 3452149ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/bid_db is not upgradeable   upgrade_leveldb.cpp:44
 18 3452156ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/short_db is not upgradeable   upgrade_leveldb.cpp:44
 19 3452163ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/collateral_db is not upgradeable   upgrade_leveldb.cpp:44
 20 3452168ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/chain/processed_transaction_id_db is not upgradeable   upgrade_leveldb.cpp:44
 21 3452200ms       th_a       try_upgrade_db ] Database /home/coin/.BitSharesXTS/peers.leveldb is not upgradeable   upgrade_leveldb.cpp:44
 22 3452200ms       th_a trigger_p2p_network_ ] Triggering connect loop now   node.cpp:690
 23 3455200ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT   tcp_socket.cpp:226
 24 3455201ms       th_a connect_to_p2p_netwo ] listening for connections on endpoint 0.0.0.0:5678   node.cpp:1999
 25 3455201ms       th_a           connect_to ] node_impl::connect_to(107.170.30.182:5678)   node.cpp:2022
 26 3455201ms       th_a    set_reuse_address ] Error setting SO_REUSEPORT   tcp_socket.cpp:167
 27 3455201ms       th_a fetch_sync_items_loo ] beginning another iteration of the sync items loop   node.cpp:716
 28 3455201ms       th_a fetch_sync_items_loo ] no sync items to fetch right now, going to sleep   node.cpp:752
 29 3455201ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().   node.cpp:602
 30 3455201ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:975
 31 3455201ms       th_a display_current_conn ]    my id is cf90da568ebc72eebae4cc5cf8ee16a285cb7237   node.cpp:976
 32 3455201ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
 33 3455201ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_failed)   node.cpp:641
 34 3455201ms       th_a display_current_conn ] Currently have 1 of 8 connections   node.cpp:975
 35 3455201ms       th_a display_current_conn ]    my id is cf90da568ebc72eebae4cc5cf8ee16a285cb7237   node.cpp:976
 36 3455201ms       th_a display_current_conn ]    handshaking: 107.170.30.182:5678 with 0000000000000000000000000000000000000000  [outbound]   node.cpp:984
 37 3455201ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:669
 38 3455201ms       th_a     fetch_items_loop ] beginning an iteration of fetch items (0 items to fetch)   node.cpp:773
 39 3455201ms       th_a advertise_inventory_ ] beginning an iteration of advertise inventory   node.cpp:822
 40 3455386ms       th_a           connect_to ] established outbound connection to 107.170.30.182:5678   node.cpp:460
 41 3455387ms       th_a      connect_to_task ] Sent "hello" to remote peer 107.170.30.182:5678   node.cpp:1933
 42 3455479ms       th_a on_connection_reject ] Received a rejection in response to my "hello"   node.cpp:1196
 43 3455480ms       th_a            read_loop ] disconnected eof
 44 End of file
 45     {"message":"End of file"}
 46     asio  asio.cpp:22 read_write_handler
 47
 48     {"len":16}
 49     th_a  stcp_socket.cpp:74 readsome   message_oriented_connection.cpp:131
 50 3455480ms       th_a on_connection_closed ] Remote peer 107.170.30.182:5678 closed their connection to us   node.cpp:1540
 51 3455480ms       th_a display_current_conn ] Currently have 0 of 8 connections   node.cpp:975
 52 3455480ms       th_a display_current_conn ]    my id is cf90da568ebc72eebae4cc5cf8ee16a285cb7237   node.cpp:976
 53 3455480ms       th_a trigger_p2p_network_ ] Triggering connect loop now   node.cpp:690
 54 3455480ms       th_a p2p_network_connect_ ] Starting an iteration of p2p_network_connect_loop().   node.cpp:602
 55 3455480ms       th_a display_current_conn ] Currently have 0 of 8 connections   node.cpp:975
 56 3455480ms       th_a display_current_conn ]    my id is cf90da568ebc72eebae4cc5cf8ee16a285cb7237   node.cpp:976
 57 3455480ms       th_a p2p_network_connect_ ] Last attempt was 0 seconds ago (disposition: last_connection_rejected)   node.cpp:641
 58 3455480ms       th_a display_current_conn ] Currently have 0 of 8 connections   node.cpp:975
 59 3455480ms       th_a display_current_conn ]    my id is cf90da568ebc72eebae4cc5cf8ee16a285cb7237   node.cpp:976
 60 3455480ms       th_a p2p_network_connect_ ] Still want to connect to more nodes, but I don't have any good candidates.  Trying again in 15 seconds   node.cpp:669
 61 3460208ms       upnp           operator() ] No valid UPnP IGDs found   upnp.cpp:145
 62 3462200ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140530T095742   client.cpp:78
 63 3464200ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140530T095744   client.cpp:78
 64 3466201ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140530T095746   client.cpp:78
 65 3468201ms       th_a        delegate_loop ] next block time: 19700101T000000  interval: 30 seconds  now: 20140530T095748   client.cpp:78

Code: [Select]
(wallet closed) >>> get_info
{
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.5,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_num": 0,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "1ce846fb372b41843c8dde6e1c109921f3e0c927fcf6ba2163166c0bd2b5b441",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "0000000000000000000000000000000000000000",
  "blockchain_shares": 80000000000000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "client_httpd_port": 0,
  "client_rpc_port": 0,
  "network_num_connections": 0,
  "network_num_connections_max": 12,
  "network_protocol_version": 100,
  "wallet_balance": 0,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100,
  "_bitshares_toolkit_revision": "2b520584e8ee10be9347d12c1c2a9f13b6f474a2",
  "_fc_revision": "54c66bbb86770d5d166c8b172b2658e9103e37cb",
  "_network_node_id": "cf90da568ebc72eebae4cc5cf8ee16a285cb7237"
}

No connections :-(

Would be nice if we could somehow figure this out
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 12:36:30 pm
feed node have received your shake hand request
But don't know why, it just  refused your connection....

Code: [Select]
42 3455479ms       th_a on_connection_reject ] Received a rejection in response to my "hello"   node.cpp:1196

No connections :-(

Would be nice if we could somehow figure this out
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: alt on May 30, 2014, 12:41:52 pm
you can see fc/src/network/tcp_socket.cpp, line 92 and line 96
The different is don't call this
Code: [Select]
    my->_sock.bind(boost::asio::ip::tcp::endpoint(boost::asio::ip::address_v4(local_endpoint.get_address()),
                                                                              local_endpoint.port()));
before
Code: [Select]
    fc::asio::tcp::connect(my->_sock, fc::asio::tcp::endpoint(boost::asio::ip::address_v4(remote_endpoint.get_address()), remote_endpoint.port()));
I am not  family with this code, but I think the problem is the node  can't connect to your port 5678 without upnp support or pub IP.

libraries/net/node.cpp, line 455, remove 3 lines:
Code: [Select]
//        if (local_endpoint.valid())
//          _message_connection.connect_to(remote_endpoint, *local_endpoint);
//        else

compile and try again.

that fixed it for me, both on the machine with public ip and the one in the virtualbox.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: Amazon on May 30, 2014, 02:02:40 pm
Is this going well?  I can't tell from the posts lol.

tl;dr better than I expected

We haven't had to reset even once! Plenty of bugs but most stuff is at the level of the client (usability). Managed to make several very big updates without having to hard fork. Dan thinks we won't even need to reset for TITAN+architecture changes. Good chance this is our last testnet if that's true.

DPOS looks solid so far, what a relief. Big props to Eric for his huge network test suite. Really want to get delegate voting up so we can let people try to really misbehave and split the network.
As a non-delegate, any time I've made a bad change I just got disconnected and the rest of the network chugged along unaffected.

Worst bug so far is that the ECC library is totally broken for 32 bit machines... that's like half the windows users. Also some users experiencing mysterious connection issues. Minor issues w.r.t the network as a whole, but terrible if you're the one experiencing them =P.

This is encouraging progress. Thanks,
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 30, 2014, 02:42:22 pm
Probably nothing, running the client for more than a day now.

The output when doing nothing (for a while) is:

Code: [Select]
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.
UPnP Port Mapping successful.

Etc.

Is that expected behaviour or is there something wrong with UPnP on my end?

Once every half hour it updates the UPnP connection status.  That is working.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: mauritso on May 31, 2014, 10:23:41 am
Once every half hour it updates the UPnP connection status.  That is working.

Alright, also, how much RAM do you need to run the client? The RAM use grew to 1.86GB after running the client for a day (Mac OS X 10.9 16GB RAM), is that necessary or does it use more RAM because there is more RAM available? (I get that this is not really the point of this test, just curious)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on May 31, 2014, 11:13:36 am
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cgafeng on May 31, 2014, 12:06:57 pm
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
they commit to other branch
https://github.com/BitShares/bitshares_toolkit/commits/titan (https://github.com/BitShares/bitshares_toolkit/commits/titan)
https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation (https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 31, 2014, 01:36:54 pm
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
they commit to other branch
https://github.com/BitShares/bitshares_toolkit/commits/titan (https://github.com/BitShares/bitshares_toolkit/commits/titan)
https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation (https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation)

We have successfully migrated the wallet to be based upon TITAN (Transfer Invisibly to Any Name) without having to hard-fork the blockchain.  To enhance maintainability and facilitate development of 3rd party APIs we have also switched to using code generation for a large part of the RPC API.   We can now use this JSON description of our API to auto-generate JavaScript wrappers for the API and help keep everything in sync as things change in the future.

The TITAN updates significantly enhance usability of the wallet as well as the privacy of the users.   The 97 character long addresses that you are swapping around today with every individual are now gone and instead you can publish a single ~40 character address once  (for everyone).  Then you can register this address (account) with the blockchain.

Users no longer deal with 100's of addresses or manually creating a new address for everyone they deal with.  You wallet is no longer a hodge-podge of 'pseudo-accounts' and instead you have real accounts each with their own balance and all transfers are 'from' one account 'to' another account.   Whether that other account is yours or someone elses. 

As a result the web interface will become very familiar to anyone who had used online banking + billpay.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on May 31, 2014, 02:04:41 pm
holy moly !!!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: NewMine on May 31, 2014, 06:15:06 pm
Is any trading happening yet? Has anyone delved into the bit assets portion of the exchange or are you guys still working on simply sending transactions?

A non techie status report for the simpletons would be cool.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on May 31, 2014, 07:13:19 pm
Is any trading happening yet? Has anyone delved into the bit assets portion of the exchange or are you guys still working on simply sending transactions?

A non techie status report for the simpletons would be cool.

So far we don't have trading, only creating/issuing assets. We are putting that off in favor of everything needed for XT launch.
We have had a functioning BitAsset market in previous versions though - it's not really the hard part.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: NewMine on May 31, 2014, 07:26:40 pm
Is any trading happening yet? Has anyone delved into the bit assets portion of the exchange or are you guys still working on simply sending transactions?

A non techie status report for the simpletons would be cool.

So far we don't have trading, only creating/issuing assets. We are putting that off in favor of everything needed for XT launch.
We have had a functioning BitAsset market in previous versions though - it's not really the hard part.

Thank you toast!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 31, 2014, 08:15:41 pm
why have delegates missed so many blocks?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on May 31, 2014, 08:41:08 pm
why have delegates missed so many blocks?

Because I have taken them off line.   We are preparing a new test chain that will address some issues:

1) We will be updating the P2P network communication layer to provide better forward compatibility
2) We are updating the founder accounts registered in the initial condition
3) We are adding a few tweaks to accelerate blockchain download 

Hold off testing on this on the current public chain.   We are preparing instructions for the new chain.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: clout on May 31, 2014, 09:22:44 pm
will it allow for delegate voting?
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on June 01, 2014, 05:04:30 am
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
they commit to other branch
https://github.com/BitShares/bitshares_toolkit/commits/titan (https://github.com/BitShares/bitshares_toolkit/commits/titan)
https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation (https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation)

how to git the branch?

git clone https://github.com/BitShares/bitshares_toolkit/tree/titan
Cloning into 'titan'...
fatal: repository 'https://github.com/BitShares/bitshares_toolkit/tree/titan/' not found
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: HackFisher on June 01, 2014, 05:34:20 am
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
they commit to other branch
https://github.com/BitShares/bitshares_toolkit/commits/titan (https://github.com/BitShares/bitshares_toolkit/commits/titan)
https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation (https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation)

how to git the branch?

git clone https://github.com/BitShares/bitshares_toolkit/tree/titan
Cloning into 'titan'...
fatal: repository 'https://github.com/BitShares/bitshares_toolkit/tree/titan/' not found

Code: [Select]
git clone https://github.com/BitShares/bitshares_toolkit
cd bitshares_toolkit
git checkout titan
git branch
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on June 01, 2014, 07:33:05 am
https://github.com/BitShares/bitshares_toolkit/commits/master
not updated today
all bug is fixed?
they commit to other branch
https://github.com/BitShares/bitshares_toolkit/commits/titan (https://github.com/BitShares/bitshares_toolkit/commits/titan)
https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation (https://github.com/BitShares/bitshares_toolkit/commits/json_code_generation)

how to git the branch?

git clone https://github.com/BitShares/bitshares_toolkit/tree/titan
Cloning into 'titan'...
fatal: repository 'https://github.com/BitShares/bitshares_toolkit/tree/titan/' not found

Code: [Select]
git clone https://github.com/BitShares/bitshares_toolkit
cd bitshares_toolkit
git checkout titan
git branch

tks
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: JoeyD on June 01, 2014, 07:56:35 am
On the github site I saw a notice that the titan-branch has been merged. Does this mean we no longer need to download and compile the titan-branch separately?

Will there be a notice when the new test-chain is up and the clients can be compiled and run? Currently I'm unable to compile the titan-branch on Ubuntu-14.04LTS with the topmost error being this:
Quote
[ 86%] Building CXX object libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_client.cpp.o
/home/joey/bitshares_toolkit/libraries/rpc_stubs/common_api_client.cpp: In member function ‘virtual std::vector<bts::blockchain::signed_transaction> bts::rpc_stubs::common_api_client::wallet_transfer(int64_t, const string&, const string&, const string&, const string&)’:
/home/joey/bitshares_toolkit/libraries/rpc_stubs/common_api_client.cpp:83:224: error: no matching function for call to ‘fc::rpc::json_connection::async_call(const char [16], fc::variant, fc::variant, fc::variant, fc::variant, fc::variant)’
   fc::variant result = get_json_connection()->async_call("wallet_transfer", fc::variant(amount_to_transfer), fc::variant(asset_symbol), fc::variant(from_account_name), fc::variant(to_account_name), fc::variant(memo_message)).wait();
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: sudo on June 01, 2014, 03:35:19 pm
compile  titan branch
seems like  can't connect


(wallet closed) >>> getinfo
{
  "blockchain_block_num": 15168,
  "network_num_connections": 0,
  "wallet_balance": 0,
  "wallet_unlocked_seconds_remaining": -1401636858,
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500001046877275,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "79ced0921c17a6034571220215444d59231c5b5b",
  "blockchain_shares": 79999993299986,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100
}
(wallet closed) >>>
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on June 01, 2014, 04:11:51 pm
On the github site I saw a notice that the titan-branch has been merged. Does this mean we no longer need to download and compile the titan-branch separately?

Will there be a notice when the new test-chain is up and the clients can be compiled and run? Currently I'm unable to compile the titan-branch on Ubuntu-14.04LTS with the topmost error being this:
Quote
[ 86%] Building CXX object libraries/api/CMakeFiles/bts_rpc_stubs.dir/__/rpc_stubs/common_api_client.cpp.o
/home/joey/bitshares_toolkit/libraries/rpc_stubs/common_api_client.cpp: In member function ‘virtual std::vector<bts::blockchain::signed_transaction> bts::rpc_stubs::common_api_client::wallet_transfer(int64_t, const string&, const string&, const string&, const string&)’:
/home/joey/bitshares_toolkit/libraries/rpc_stubs/common_api_client.cpp:83:224: error: no matching function for call to ‘fc::rpc::json_connection::async_call(const char [16], fc::variant, fc::variant, fc::variant, fc::variant, fc::variant)’
   fc::variant result = get_json_connection()->async_call("wallet_transfer", fc::variant(amount_to_transfer), fc::variant(asset_symbol), fc::variant(from_account_name), fc::variant(to_account_name), fc::variant(memo_message)).wait();

It hasn't been merged, and the most recent version builds
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: JoeyD on June 01, 2014, 04:46:52 pm
It hasn't been merged, and the most recent version builds

Did a fresh git clone and I got the Titan-branch to compile, thanks. Any ETA on when the testnet is up again? I'm assuming the net is down, because I'm getting the exact same output as sudo, including "blockchain_block_num": 15168, "network_num_connections": 0.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on June 01, 2014, 07:56:40 pm
It hasn't been merged, and the most recent version builds

Did a fresh git clone and I got the Titan-branch to compile, thanks. Any ETA on when the testnet is up again? I'm assuming the net is down, because I'm getting the exact same output as sudo, including "blockchain_block_num": 15168, "network_num_connections": 0.

You need to delete your old data dir (~/.BitSharesXTS by default). You're trying to sync an old chain.
The new testnet is up.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: JoeyD on June 01, 2014, 10:55:24 pm
You need to delete your old data dir (~/.BitSharesXTS by default). You're trying to sync an old chain.
The new testnet is up.

Oops, missed that, I've got the Titan-client running and connecting now.

I don't know how to register a name yet (did see an insufficient funds failure notice). Any chance of getting some test-funds as well? My receive address is XTS6wRNxsP7So5tx8bqP9GiuQgPpQxRYYiV3Q2QEGokvArquMJF3E
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cass on June 01, 2014, 11:09:56 pm
when trying to start client i get this error

Code: [Select]
{
  "rpc": {
    "rpc_user": "user",
    "rpc_password": "password",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "./htdocs"
  },
  "default_peers": [
    "107.170.30.182:8765"
  ],
  "ignore_console": false
}
Loading blockchain from "/home/bitshares/.BitSharesXTS/chain"
Using genesis block from file "/home/bitshares/bitshares_toolkit/programs/client/genesis.dat"
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

Listening to P2P connections on port 8765
Attempting to map UPNP port...
Attempting to connect to peer 107.170.30.182:8765


after a few minutes i've checked connections via

Code: [Select]
(wallet closed) >>> getinfo
{
  "blockchain_head_block_num": 828,
  "blockchain_head_block_time": "20140601T221000",
  "network_num_connections": 0,
  "wallet_balance": 0,
  "wallet_unlocked_seconds_remaining": 0,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140601T230623",
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500000093750002,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "1610cd0610680c57f8e08a68eff51288cc15c50bfa11a84290eaca429b1f0e14",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "a0e6741bfe17b6473cdc9d06b5fd353683e269ca",
  "blockchain_shares": 79999999400000,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100
}

Or did i miss something i had to do!?
Ubunutu 14 clean install
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: JoeyD on June 01, 2014, 11:27:52 pm
If you're also running the titan-branch client then you are running the same setup as I am. Are you running a firewall? I needed to allow access to port 8765 first before getting connections.

Also there is a log in .BitSharesXTS which might give you some more info.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cass on June 01, 2014, 11:28:23 pm
compile  titan branch
seems like  can't connect


(wallet closed) >>> getinfo
{
  "blockchain_block_num": 15168,
  "network_num_connections": 0,
  "wallet_balance": 0,
  "wallet_unlocked_seconds_remaining": -1401636858,
  "blockchain_asset_reg_fee": 301988160,
  "blockchain_asset_shares_max": 1000000000000000,
  "blockchain_bips_per_share": 12.500001046877275,
  "blockchain_block_fee_min": 1,
  "blockchain_block_interval": 30,
  "blockchain_block_size_max": 209715,
  "blockchain_block_size_target": 104857,
  "blockchain_delegate_fire_votes_min": 11428571428571,
  "blockchain_delegate_num": 7,
  "blockchain_delegate_reg_fee": 43141165,
  "blockchain_delegate_reward_min": 200,
  "blockchain_id": "ed2c3dba64a343002734f782bb3bc831a99a14c80490b85bfbf33751793469cc",
  "blockchain_name_size_max": 63,
  "blockchain_name_data_size_max": 4096,
  "blockchain_random_seed": "79ced0921c17a6034571220215444d59231c5b5b",
  "blockchain_shares": 79999993299986,
  "blockchain_size_max": 107374182400,
  "blockchain_symbol": "XTS",
  "blockchain_version": 100,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_balance_bips": 0,
  "wallet_open": false,
  "wallet_unlocked_until": "",
  "wallet_version": 100
}
(wallet closed) >>>

try

Code: [Select]
./bitshares_client --server 107.170.30.182:8765
this solved connection issue for me.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cass on June 01, 2014, 11:29:04 pm
If you're also running the titan-branch client then you are running the same setup as I am. Are you running a firewall? I needed to allow access to port 8765 first before getting connections.

Also there is a log in .BitSharesXTS which might give you some more info.

yup also titan branch installed
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on June 02, 2014, 06:54:10 am
I may now know a possible reason for my machine not connecting to the network.
My Maschine uses XEN for virtualizing and I set up routing for the machine like (debian network interface)
Quote
auto eth0
iface eth0 inet static
  address PUBLIC-IP
  netmask 255.255.255.255
  gateway MY-XEN-DOMU
  pointopoint MY-NEXT-HOP
As a result:
Quote
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         myGW    0.0.0.0         UG    0      0        0 eth0
10.0.0.0        10.0.0.2        255.255.255.0   UG    0      0        0 tun0
10.0.0.2        0.0.0.0         255.255.255.255 UH    0      0        0 tun0
myGW    0.0.0.0         255.255.255.255 UH    0      0        0 eth0

Further more on the DOM-U (the host machine):
Quote
net.ipv4.ip_forward=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.conf.default.proxy_arp = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.all.proxy_ndp = 1


See a german tutorial here: http://wiki.hetzner.de/index.php/Umstellung_Xen_3_auf_routed
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: JoeyD on June 02, 2014, 09:03:05 am
Odd, I had between 4/5 connections up until block 930 and now I can't connect anymore.
I have compiled the latest git revision, but that does not seem to want to connect either.

What method are people using to update from git and recompiling? Just running make clean doesn't seem to work for me, but deleting all contents by hand and redownloading is not particularly efficient.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: xeroc on June 02, 2014, 09:16:57 am
Odd, I had between 4/5 connections up until block 930 and now I can't connect anymore.
I have compiled the latest git revision, but that does not seem to want to connect either.

What method are people using to update from git and recompiling? Just running make clean doesn't seem to work for me, but deleting all contents by hand and redownloading is not particularly efficient.
I'd say the guys at 3i are working on the seed node:
Quote
944004ms       th_a           connect_to ] fatal: error connecting to peer 107.170.30.182:5678: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:56 error_handler
Seed node seems to be down
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on June 02, 2014, 11:47:01 am
A lot happens while I sleep.  Will look into things. 

Titan is still unstable with a few known bugs. We will likely merge back to master today and provide new binaries.


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: yinchanggong on June 02, 2014, 12:17:40 pm
known bugs are ok~unknown is trouble!

来自我的 M353 上的 Tapatalk

Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: gyhy on June 02, 2014, 01:15:15 pm
 +5%
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 07:45:15 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on June 02, 2014, 08:03:09 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 08:05:54 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).

Awesome, thanks. I decided to check out Titan and recompile though as I got the impression I was on the wrong net, might post a new address later on..
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: toast on June 02, 2014, 08:06:59 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).

Awesome, thanks. I decided to check out Titan and recompile though as I got the impression I was on the wrong net, might post a new address later on..

We're back on master now
You definitely need to wipe your data directory ("~/.BitSharesXTS") as we are on a new testnet
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 08:09:22 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).

Awesome, thanks. I decided to check out Titan and recompile though as I got the impression I was on the wrong net, might post a new address later on..

We're back on master now
You definitely need to wipe your data directory ("~/.BitSharesXTS") as we are on a new testnet

Ah so I was on the correct one to begin with, lol. Will clean out everything and recompile then :)

Edit: Recompile done, new address:

XTS5xhMyfXPNdnnjV8F28wjcxYZqnYJxm6xDP3kmaSRDZYB1mAG1v
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on June 02, 2014, 09:37:10 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).

Awesome, thanks. I decided to check out Titan and recompile though as I got the impression I was on the wrong net, might post a new address later on..

We're back on master now
You definitely need to wipe your data directory ("~/.BitSharesXTS") as we are on a new testnet

Ah so I was on the correct one to begin with, lol. Will clean out everything and recompile then :)

Edit: Recompile done, new address:

XTS5xhMyfXPNdnnjV8F28wjcxYZqnYJxm6xDP3kmaSRDZYB1mAG1v

Be sure to pull the latest but you should now have two trx from me.,
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 09:54:21 pm
I noticed a commit was made with a fix for the 32bit wallet problem, so I decided to reinstall to see if it worked. I had some issues during compile with "openssl.cnf", but got it working.

Running the client now I have a new issue, the rpc server won't start, I get

Code: [Select]
Starting json rpc server on 127.0.0.1:0
Starting http json rpc server on 127.0.0.1:0
Error starting rpc server

I've made a new wallet and account, can some try to send me some XTS pls to see if the 32bit bug has been resolved?

XTS6i4hCwfWUmWGwxaN1f1KRSycDfuvWjWzYkP7h89miuhDCQxyQi

Your key validates now, transfers are broken for an unrelated reason ATM but it looks like you're good. Will transfer when it's fixed (if I remember).

Awesome, thanks. I decided to check out Titan and recompile though as I got the impression I was on the wrong net, might post a new address later on..

We're back on master now
You definitely need to wipe your data directory ("~/.BitSharesXTS") as we are on a new testnet

Ah so I was on the correct one to begin with, lol. Will clean out everything and recompile then :)

Edit: Recompile done, new address:

XTS5xhMyfXPNdnnjV8F28wjcxYZqnYJxm6xDP3kmaSRDZYB1mAG1v

Be sure to pull the latest but you should now have two trx from me.,

Thanks, I've got 66891132 XTS, does that add up?

I see there's a lot of changes just in the last hour, recompiling once again, then I'll try to register a delegate.
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 09:58:07 pm
I couldn't find any "listtransactions" option earlier, but after the latest recompile we now have "wallet_account_transaction_history" :)

Good job, spacing is a bit generous in the terminal though.

Code: [Select]
#    BLK.TRX  TIMESTAMP           FROM                TO                  MEMO                 AMOUNT          FEE     VOTE         ID                                     
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  1    718.1    2014-06-02T21:37:00 delegate-1          unknown                                 33445566        0       TODO          d426ed6f9681cb77b0fc26d9dd2726b40dbb939a
  2    718.0    2014-06-02T21:37:00 delegate-1          unknown             (from bytemaster)   33445566        0       TODO          af2c74cb91f6267929b74d566e38e27a6cfe3dfd
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cass on June 02, 2014, 10:29:12 pm
XTS5G8mSVyyFXNszqVAxYTgNEHKn2kAnbBMWrhDQNLHqb4nKYfCkB
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: svk on June 02, 2014, 10:39:37 pm
XTS5G8mSVyyFXNszqVAxYTgNEHKn2kAnbBMWrhDQNLHqb4nKYfCkB

Sent you some from the huge stash BM sent me earlier.

I've registered a delegate as "svk", will leave it up during the night, time to go to bed now!
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: cass on June 02, 2014, 10:42:10 pm
XTS5G8mSVyyFXNszqVAxYTgNEHKn2kAnbBMWrhDQNLHqb4nKYfCkB

Sent you some from the huge stash BM sent me earlier.

I've registered a delegate as "svk", will leave it up during the night, time to go to bed now!

thx
Title: Re: New Public XTS Test for Developers and Savvy Users
Post by: bytemaster on June 02, 2014, 10:43:24 pm
https://bitsharestalk.org/index.php?topic=4836.msg62975#msg62975

This thread is closing down for being too long... move to new thread.