Quote from: emski on August 22, 2014, 10:43:51 AM
I think the fork is caused by subset of these nodes:

MISSED  2014-08-22T10:27:10 daslab                          N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:40:50 btsnow                          N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:39:00 delegate.adam                   N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:38:20 delegate2.adam                  N/A     N/A     N/A             N/A     N/A

Perhaps the owners of these delegates can check if I'm correct.

toast?

Quote from: bytemaster on August 22, 2014, 11:19:52 AM
Ok. We are looking into this top priority.   


Sent from my iPhone using Tapatalk

I also have full node cleanly compiled and stuck at the fork even though it connects to seed nodes.
100% repro. All the data is available.

Quote from: bytemaster on August 22, 2014, 11:19:52 AM
Ok. We are looking into this top priority.   


Sent from my iPhone using Tapatalk

Anything I can provide/test from my side let me know. I'll be around all day. I'm also trying to take next week off work so I can be focused on this full time.

Ok. We are looking into this top priority.   


Sent from my iPhone using Tapatalk

Quote from: dannotestein on August 22, 2014, 04:57:28 AM

Quote from: Riverhead on August 22, 2014, 04:37:21 AM
It's running in gdb now. Do I just wait for a crash?

The backtrace will be useful, but probably the most useful thing will be the logs around the time of the crash.

I have my logs directory tar.gz'd. Is there an email I can send them to? Also, is there anything in there I shouldn't be sending? I'm assuming by this point the logs are scrubbed of private data but want to be sure.

I think the fork is caused by subset of these nodes:

MISSED  2014-08-22T10:27:10 daslab                          N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:40:50 btsnow                          N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:39:00 delegate.adam                   N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-22T10:38:20 delegate2.adam                  N/A     N/A     N/A             N/A     N/A

Perhaps the owners of these delegates can check if I'm correct.

Quote from: liondani on August 22, 2014, 09:28:37 AM
I upgraded one linux server to 0.4.5

and I am getting often this message:     (and only for 23.239.5.30:39242 )

"I am disconnecting peer 23.239.5.30:39242 for reason: You offered us a block that we reject as invalid"

I checked the block explorer:
http://blockchain.bitsuperlab.com/

and I am not missing blocks yet and I am not on a fork...
should I be concerned or can I safely upgrade my second server too?

thats what I see right now:

I am disconnecting peer 80.240.133.79:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 69.90.132.209:45783 for reason: You offered us a block that we reject as invalid
--- in sync with p2p network
--- there are now 23 active connections to the p2p network
--- there are now 24 active connections to the p2p network
--- syncing with p2p network, 598 blocks left to fetch
I am disconnecting peer 80.240.133.79:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 69.90.132.209:45783 for reason: You offered us a block that we reject as invalid
--- there are now 23 active connections to the p2p network
--- in sync with p2p network
--- there are now 24 active connections to the p2p network
--- syncing with p2p network, 598 blocks left to fetch
I am disconnecting peer 80.240.133.79:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 69.90.132.209:45783 for reason: You offered us a block that we reject as invalid
--- there are now 23 active connections to the p2p network
--- in sync with p2p network


A silver lining to these delegate crashes is we'll see who is on their game and who is an absentee delegate :).

Guys,

since I am not very tech savvy can I still use my old version (0.4.3 i think) or do I need to update? Last night I was trying to connect but was taking too long so I just gave up.

Since I am reading that most people have issues with the new version should I just wait for a new release and when should this be expected?

In any case when Bitusd will be available I will again need to download a newer version?

Thanks

I upgraded one linux server to 0.4.5

and I am getting often this message:     (and only for 23.239.5.30:39242 )

"I am disconnecting peer 23.239.5.30:39242 for reason: You offered us a block that we reject as invalid"

I checked the block explorer:
http://blockchain.bitsuperlab.com/

and I am not missing blocks yet and I am not on a fork...
should I be concerned or can I safely upgrade my second server too?

Fresh install on Ubuntu with 0.4.5.

stuck at block 284575. "8 hours old"

20 active connections.

I really hope exchanges don't get forked or something, that would be some disaster.

Quote from: dannotestein on August 22, 2014, 04:57:28 AM

Quote from: Riverhead on August 22, 2014, 04:37:21 AM
It's running in gdb now. Do I just wait for a crash?

The backtrace will be useful, but probably the most useful thing will be the logs around the time of the crash.

Here is the trace. Which log files do you need, or just all of them? If it'd be easier I can tar them up and email them.




Python Exception <class 'ImportError'> No module named 'gdb':
#0  get_tail (next=<synthetic pointer>, h=0x1e0) at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1  fc::mutex::unlock (this=this@entry=0x2539a18) at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2  0x00000000007b5290 in ~scoped_lock (this=<synthetic pointer>, __in_chrg=<optimized out>)
    at /home/riverhead/github/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3  bts::net::detail::message_oriented_connection_impl::send_message (this=0x2539850, message_to_send=...)
    at /home/riverhead/github/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4  0x00000000007b5928 in bts::net::message_oriented_connection::send_message (this=this@entry=0x26c0948, message_to_send=...)
    at /home/riverhead/github/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5  0x00000000007ab220 in bts::net::peer_connection::send_queued_messages_task (this=0x26c08e0)
    at /home/riverhead/github/bitsharesx/libraries/net/peer_connection.cpp:178
#6  0x00000000007ab91c in operator() (__closure=<optimized out>)
    at /home/riverhead/github/bitsharesx/libraries/net/peer_connection.cpp:222
#7  fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (
    functor=<optimized out>, prom=0x1d4fca0) at /home/riverhead/github/bitsharesx/libraries/fc/include/fc/thread/task.hpp:56
#8  0x000000000066c483 in fc::task_base::run_impl (this=this@entry=0x1d4fcb0)
    at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/task.cpp:42
#9  0x000000000066cb35 in fc::task_base::run (this=this@entry=0x1d4fcb0)
    at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/task.cpp:31
#10 0x000000000066acbb in run_next_task (this=0x184f350) at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/thread_d.hpp:379
#11 fc::thread_d::process_tasks (this=this@entry=0x184f350)
    at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/thread_d.hpp:402
#12 0x000000000066af06 in fc::thread_d::start_process_tasks (my=25490256)
    at /home/riverhead/github/bitsharesx/libraries/fc/src/thread/thread_d.hpp:359
#13 0x0000000000d4a85e in make_fcontext ()
#14 0x000000000184f350 in ?? ()
#15 0x0000000000000000 in ?? ()


I've updated Win client to 0.4.5 and it crashed, when trying to send crash report, following error occured:



Seems like, when I restarted client, error message was sent with no error.

This crash happened when I run client for the first time after setup is finished (and Run checkbox is selected).

I think that when I clicked Finish/Close on last setup window, the setup process was not finished.

I think this is the problem block:
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    TOTAL FEES      LATENCY PROCESSING TIME
===================================================================================================================
275169  2014-08-21T00:01:30 btsnow                          0       166     0.00000 BTSX    109139  0.006298


And here is the whole console.log - http://pastebin.com/kDBzihvJ

Apparently it is a fork with lots of missed blocks before this one. The rest of the network rejects it. I dont know why my client is not synchronizing to the real one.

Fresh checkout of 0.4.5.
Fresh compile.
Running with new data-dir.
No wallet opened.
Stops synchronization at block 275170.
High CPU usage.
--- there are now 6 active connections to the p2p network
--- there are now 7 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 275170,
  "blockchain_head_block_age": "31 hours old",
  "blockchain_head_block_timestamp": "2014-08-21T00:18:20",
  "blockchain_average_delegate_participation": "0.86 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_accumulated_fees": "222,945.09399 BTSX",
  "blockchain_delegate_pay_rate": "1.84313 BTSX",
  "blockchain_share_supply": "1,999,946,839.85184 BTSX",
  "blockchain_blocks_left_in_round": 55,
  "blockchain_next_round_time": "at least 9 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-22T07:18:10",
  "blockchain_random_seed": "892ba7eb32d3de2c58a98cc66e91ba0a6b5cc381",
  "client_data_dir": "/home/emski/bitsharesnodeTock/bitsharesx/programs/client/dd4.5",
  "network_num_connections": 7,
  "network_num_connections_max": 200,
  "ntp_time": "2014-08-22T07:09:08",
  "ntp_time_error": 0.00049100000000000001,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
Peer 80.240.133.79:1777 disconnected us: You offered us a block that we reject as invalid



MISSED  2014-08-20T22:45:00 emski.bitdelegate               N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:50 init4                           N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:40 black-widow                     N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:30 angel.bitdelegate               N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:20 b.delegate.xeroc                N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:10 delegate1-galt                  N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:44:00 mrs.agsexplorer                 N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:50 clout-delegate3                 N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:40 init28                          N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:30 delegate.redflag                N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:20 bitcoiners                      N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:10 delegate.taolje                 N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:43:00 anchor.crazybit                 N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:42:50 delegate.adam                   N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:42:40 spartako2                       N/A     N/A     N/A             N/A     N/A
MISSED  2014-08-20T22:42:30 d.dacsun                        N/A     N/A     N/A             N/A     N/A
275164  2014-08-20T22:42:20 init8                           0       166     0.00000 BTSX    113888  0.000359
275163  2014-08-20T22:42:10 calabiyau                       0       166     0.00000 BTSX    113898  0.000363
275162  2014-08-20T22:42:00 democracy                       0       166     0.00000 BTSX    113908  0.000385
275161  2014-08-20T22:41:50 crazybit                        0       166     0.00000 BTSX    113918  0.000431
MISSED  2014-08-20T22:41:40 skyscraperfarms                 N/A     N/A     N/A             N/A     N/A
275160  2014-08-20T22:41:30 angel-delegate                  0       166     0.00000 BTSX    113938  0.000357
275159  2014-08-20T22:41:20 init65                          0       166     0.00000 BTSX    113948  0.000373
275158  2014-08-20T22:41:10 mr.scroodge                     0       166     0.00000 BTSX    113958  0.00044
275157  2014-08-20T22:41:00 init18                          0       166     0.00000 BTSX    113968  0.000385
275156  2014-08-20T22:40:50 delegated-proof-of-steak        1       410     0.50000 BTSX    113978  0.001152
275155  2014-08-20T22:40:40 init9                           0       166     0.00000 BTSX    113988  0.000395
275154  2014-08-20T22:40:30 delegate.follow-my-vote         0       166     0.00000 BTSX    113998  0.000346


100% reproducible!
I'll delay the update for now until this is resolved.