BitShares Forum
Main => General Discussion => Topic started by: her0 on July 25, 2014, 08:24:37 am
-
--- there are now 1 active connections to the p2p network
I am disconnecting peer 95.85.33.16:8764 for reason: You offered us a block that we reject as invalid
--- there are now 0 active connections to the p2p network
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 libbz2-dev libboost-dev libboost-all-dev
git clone https://github.com/dacsunlimited/bitsharesx.git
cd bitsharesx
git pull
git checkout 0.2.3
git submodule init
git submodule update
cmake .
make
-
That's interesting. That's my node. Give me a minute and I'll get you some new peers to connect to.
-
Try
network_add_node "88.204.169.242:14524" add
network_add_node "184.148.69.210:1275" add
network_add_node "72.43.205.34:35536" add
network_add_node "173.72.65.56:43453" add
Enter each of these lines separately into the _console tab on your wallet. These are just the first four of the 76 nodes currently connected to my seed node. If upon entering this, you do not see an improvement within about 2 minutes, let me know and I will post some more for you.
-
bitshares_toolkit / libraries / net / node.cpp
2321-2332
// invalid message received
std::list<peer_connection_ptr> peers_to_disconnect;
for( const peer_connection_ptr& peer : _active_connections )
if( !peer->ids_of_items_to_get.empty() &&
peer->ids_of_items_to_get.front() == block_message_to_process.block_id )
peers_to_disconnect.push_back( peer );
for( const peer_connection_ptr& peer : peers_to_disconnect )
{
wlog( "disconnecting client ${endpoint} because it offered us the rejected block", ("endpoint", peer->get_remote_endpoint() ) );
disconnect_from_peer( peer.get(), "You offered us a block that we reject as invalid", true, handle_message_exception );
}
break;
-
--- syncing with p2p network, 105 blocks left to fetch
I am disconnecting peer 104.131.234.136:8765 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 95.85.33.16:8764 for reason: You offered us a block that we reject as invalid
after sync all node reject me.
-
can you post the output of a get_info ?
You are using the exact same build instructions I use.
-
0 active connections the peer info is null
ywallet (locked) >>> get_info
{
"blockchain_head_block_num": 51067,
"blockchain_head_block_age": "3 minutes old",
"blockchain_head_block_timestamp": "20140725T084830",
"blockchain_average_delegate_participation": "81.45 %",
"blockchain_delegate_pay_rate": "1.94565 BTSX",
"blockchain_blocks_left_in_round": 39,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "235,346.43020 BTSX",
"blockchain_share_supply": "1,999,682,412.77983 BTSX",
"blockchain_random_seed": "96dfccceb84f7402dbb556b07330fe498b9d35ea",
"blockchain_database_version": 117,
"blockchain_version": 109,
"network_num_connections": 0,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": null,
"ntp_error": null,
"wallet_open": true,
"wallet_unlocked": false,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
mywallet (locked) >>>
-
I am more interested in the ntp time being null. If you are running NTP outside of the client that will lead to those two lines reading as null. I am not an expert at all, but an NTP refresh may fix it. If nothing else system reboot should do the trick.