BitShares Forum

Main => General Discussion => Topic started by: abit on January 28, 2016, 11:36:17 pm

Title: Network problem now fixed, all nodes please update
Post by: abit on January 28, 2016, 11:36:17 pm
All seed nodes, witnesses please update.

Code: [Select]
git checkout bitshares
git pull
make witness_node

Or new clone:
Code: [Select]
git clone https://github.com/bitshares/bitshares-2.git
git submodule update --init --recursive
cmake .
make witness_node

=======original post==========
{
  head_block_num: 3,067,958
  head_block_age: 21 minutes ago
}


Code: [Select]
2016-01-28T23:15:09 th_a:invoke handle_block         handle_block ] Got block: #3067957 time: 2016-01-28T23:15:09 latency: 368 ms from
: delegate-1.lafona  irreversible: 3067935 (-22)                  application.cpp:496
2016-01-28T23:15:10 th_a:invoke handle_transaction   handle_transaction ] Got 1 transactions from network                       applic
ation.cpp:545
2016-01-28T23:15:12 th_a:Witness Block Production block_production_loo ] Generated block #3067958 with timestamp 2016-01-28T23:15:12 a
t time 2016-01-28T23:15:12                        witness.cpp:185

Code: [Select]
2016-01-28T23:16:27 th_a:Witness Block Production block_production_loo ] Got exception while generating block:
3030007 insufficient_fee: insufficient fee
Insufficient Fee Paid
    {"core_fee_paid":0,"required":10000}
    th_a  evaluator.hpp:230 evaluate

    {}
    th_a  evaluator.cpp:46 start_evaluate

    {}
    th_a  db_block.cpp:653 apply_operation

    {"next_block.block_num()":3067959}
    th_a  db_block.cpp:536 _apply_block
Title: Re: Network problem now.
Post by: abit on January 28, 2016, 11:52:17 pm
It seems that this transaction is unable to be included into the chain:
Code: [Select]
{"ref_block_num":53301,"ref_block_prefix":3943068053,"expiration":"2016-01-28T23:15:39","operations":[[2,{"fee":{"amount":10000,"asset_id":"1.3.0"},"fee_paying_account":"1.2.97184","order":"1.7.31917","extensions":[]}]],"extensions":[],"signatures":["201c4f122098dba6a959035c686b260b46018c4fd1c3bae71a1a087640cbea174a575391f56afa8a3b145e2790821fbc407fa904fb7acb2dcd5f04ca1e9b921314"],"operation_results":[[2,{"amount":1,"asset_id":"1.3.781"}]]}
Title: Re: Network problem now.
Post by: bytemaster on January 29, 2016, 12:04:01 am
I am looking into the problem now... any help or proposed fixes welcome.
Title: Re: Network problem now.
Post by: Akado on January 29, 2016, 12:09:56 am
So this means asshole1 who is trying to get the fees from the UIAs is actually helping the network by finding issues? Who would have guessed.
http://cryptofresh.com/b/3067958
Title: Re: Network problem now.
Post by: clayop on January 29, 2016, 12:11:45 am
So this means asshole1 who is trying to get the fees from the UIAs is actually helping the network by finding issues? Who would have guessed.
http://cryptofresh.com/b/3067958

Nobody guessed I think. But he is already rewarded :)
Title: Re: Network problem now.
Post by: BunkerChainLabs-DataSecurityNode on January 29, 2016, 12:21:36 am
So this means asshole1 who is trying to get the fees from the UIAs is actually helping the network by finding issues? Who would have guessed.
http://cryptofresh.com/b/3067958

Yeah.. so far a handful of witnesses are now trying to coordinate to fix the situation.
Title: Re: Network problem now.
Post by: roadscape on January 29, 2016, 12:35:31 am
Could this be a fee pool issue? The asset in question has an empty fee pool (https://cryptofresh.com/a/ABTSLA) and otherwise the trx looks fine.. and the account has enough balance to pay the fee as far as i can tell
Title: Re: Network problem now.
Post by: lovejoy on January 29, 2016, 12:37:21 am
(http://cdn.someecards.com/someecards/usercards/MjAxMy0wMWFiNTFkNmMwMTFjYWI3.png)
Title: Re: Network problem now.
Post by: tonyk on January 29, 2016, 12:38:05 am
So this means asshole1 who is trying to get the fees from the UIAs is actually helping the network by finding issues? Who would have guessed.
http://cryptofresh.com/b/3067958

Me for one... but I am weird that way... the masses (and BM included btw) think speaking positively is the only way to "help"
...well besides selling their BTS...
@fuzzy

I also like the name... #1asshole beats it but I think it is not a vary valid name in bts... 2.0.

Title: Re: Network problem now.
Post by: roadscape on January 29, 2016, 12:39:04 am
The fee pool balance is 1 satoshi (0.00001 BTS).. might that have some significance?

Code: [Select]
get_object 2.3.781
get_object 2.3.781
[{
    "id": "2.3.781",
    "current_supply": 2000000000,
    "confidential_supply": 0,
    "accumulated_fees": 2500000,
    "fee_pool": 1
  }
]
Title: Re: Network problem now.
Post by: abit on January 29, 2016, 12:40:27 am
Update: I tried to generate an empty block but failed. Why still need fee?
Code: [Select]
2112038ms th_a       db_block.cpp:195              _push_block          ] Failed to push new block:                         [114/1936]
3030007 insufficient_fee: insufficient fee
Insufficient Fee Paid
    {"core_fee_paid":0,"required":10000}
    th_a  evaluator.hpp:230 evaluate

    {}
    th_a  evaluator.cpp:46 start_evaluate

    {}
    th_a  db_block.cpp:653 apply_operation

    {"next_block.block_num()":3067959}
    th_a  db_block.cpp:536 _apply_block
2112038ms th_a       witness.cpp:178               block_production_loo ] Got exception while generating block:
3030007 insufficient_fee: insufficient fee
Insufficient Fee Paid
    {"core_fee_paid":0,"required":10000}
    th_a  evaluator.hpp:230 evaluate

    {}
    th_a  evaluator.cpp:46 start_evaluate

    {}
    th_a  db_block.cpp:653 apply_operation

    {"next_block.block_num()":3067959}
    th_a  db_block.cpp:536 _apply_block

    {"new_block":{"previous":"002ed036dea60c5872751faccc904c4c04d8edc0","timestamp":"2016-01-29T00:35:12","witness":"1.6.35","transact
ion_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f2eb9e040001a6aee45bdf4dbc0845c00d91
b0418cd5eaa577643a8b72bc7f73838f904a2dc23d40dc8a36f224b5c63205200f9ade4d195baed079d9ec14375a9","transactions":[]}}
    th_a  db_block.cpp:201 _push_block

    {"witness_id":"1.6.35"}
    th_a  db_block.cpp:405 _generate_block

Title: Re: Network problem now.
Post by: BunkerChainLabs-DataSecurityNode on January 29, 2016, 12:48:28 am
The fee pool balance is 1 satoshi (0.00001 BTS).. might that have some significance?

Code: [Select]
get_object 2.3.781
get_object 2.3.781
[{
    "id": "2.3.781",
    "current_supply": 2000000000,
    "confidential_supply": 0,
    "accumulated_fees": 2500000,
    "fee_pool": 1
  }
]

Can the fees have a precision beyond the asset?
Title: Re: Network problem now.
Post by: bytemaster on January 29, 2016, 01:00:35 am
I have identified the problem, fix to be pushed shortly.
Title: Re: Network problem now.
Post by: BunkerChainLabs-DataSecurityNode on January 29, 2016, 01:20:29 am
Fix is in.. several witnesses are building right now and should be back online shortly.
Title: Re: Network problem now fixed, all nodes please update
Post by: abit on January 29, 2016, 02:18:55 am
bump
Title: Re: Network problem now fixed, all nodes please update
Post by: BunkerChainLabs-DataSecurityNode on January 29, 2016, 03:03:55 am
Network is back in action.. still waiting for more witnesses to update.
Title: Re: Network problem now.
Post by: fuzzy on January 29, 2016, 05:50:26 am
So this means asshole1 who is trying to get the fees from the UIAs is actually helping the network by finding issues? Who would have guessed.
http://cryptofresh.com/b/3067958

Me for one... but I am weird that way... the masses (and BM included btw) think speaking positively is the only way to "help"
...well besides selling their BTS...
@fuzzy

I also like the name... #1asshole beats it but I think it is not a vary valid name in bts... 2.0.

tony...i have no clue why you continue assuming you know so much about me.  at some point lieing about people starts seeming like slander.  in fact your willingness to do this to me made me put you on ignore because to be frank im really busy trying to make our community wealthier and more able to help change a world gone to shit.  I honestly dont have time for this and the only reason I know about it this time is because apparently you so miss my responses that you felt it necessary to mention me. 

the funny thing is at first i thought you were being super cool and mentioning me in a discussion we should be having tomorrow...which would have been cool because it would have been overtly helpful.

Then i had to continue reading....LOL
Title: Re: Network problem now fixed, all nodes please update
Post by: xeroc on January 29, 2016, 07:52:44 am
Network is back in action.. still waiting for more witnesses to update.
Well done guys ..
Downtime still was in the line of bitcoins waiting time for your transaction :)
Title: Re: Network problem now fixed, all nodes please update
Post by: rnglab on January 29, 2016, 08:18:17 am
>70% participation now, growing as western witnesses wakes up. The fix is working good so far.
Title: Re: Network problem now fixed, all nodes please update
Post by: monsterer on January 29, 2016, 08:49:35 am
Would this issue have caused a fork, or just a network stall?
Title: Re: Network problem now fixed, all nodes please update
Post by: CalabiYau on January 29, 2016, 08:56:55 am
Network is back in action.. still waiting for more witnesses to update.
Well done guys ..
Downtime still was in the line of bitcoins waiting time for your transaction :)

+ 100%
Title: Re: Network problem now fixed, all nodes please update
Post by: abit on January 29, 2016, 09:25:15 am
Would this issue have caused a fork, or just a network stall?
No fork so far.
Title: Re: Network problem now fixed, all nodes please update
Post by: BunkerChainLabs-DataSecurityNode on January 29, 2016, 12:54:07 pm
Network is back in action.. still waiting for more witnesses to update.
Well done guys ..
Downtime still was in the line of bitcoins waiting time for your transaction :)

Haha.. we can call these our bitcoin moments. :)
Title: Re: Network problem now fixed, all nodes please update
Post by: monsterer on January 29, 2016, 04:28:00 pm
Would this issue have caused a fork, or just a network stall?
No fork so far.

I can confirm there was some kind of fork, because metaexchange sent transactions which never arrived.
Title: Re: Network problem now fixed, all nodes please update
Post by: abit on January 29, 2016, 05:10:11 pm
Would this issue have caused a fork, or just a network stall?
No fork so far.

I can confirm there was some kind of fork, because metaexchange sent transactions which never arrived.
All nodes have been restarted, all transactions in the cache are gone. If you have a backup of your transactions, try broadcast them again.

There were network splits for sure, upgraded nodes in a network, and un-upgraded nodes in the other, but no fork since the un-upgraded nodes are unable to produce blocks.