search

viabtc / viabtc_exchange_server

A trading engine with high-speed performance and real-time notification
MIT License
2.67k stars 1.49k forks source link

Issue in matching enginer restart #233

Closed sanada08 closed 3 years ago

sanada08 commented 4 years ago

When matching engine is restarted it throws:


=== matchengine: ready to exec
[2019-12-28 18:40:59.555427] me_persist.c:32(get_last_slice): get last slice time
[2019-12-28 18:40:59.555859] me_persist.c:135(init_from_db): last_slice_time: 1577552400, last_oper_id: 34060, last_order_id: 2, last_deals_id: 0
[2019-12-28 18:40:59.555878] me_persist.c:65(load_slice_from_db): load orders from: slice_order_1577552400
[2019-12-28 18:40:59.557899] me_persist.c:76(load_slice_from_db): load balance from: slice_balance_1577552400
[2019-12-28 18:40:59.641024] me_persist.c:94(load_operlog_from_db): load oper log from: operlog_20191228
[2019-12-28 18:40:59.644036] me_persist.c:105(load_operlog_from_db): load_operlog from operlog_20191228 fail: -417
process: matchengine version: 0.1.0, compile date: Dec 24 2019 08:43:54
./matchengine.exe: init from db fail: -107
process: matchengine version: 0.1.0, compile date: Dec 24 2019 08:43:54
=== matchengine has died, exitting docker...```

Please help me to resolve the issue.
sanada08 commented 4 years ago

@objectt @djpnewton @ohld

objectt commented 4 years ago

@sanada08 loading operlogs from 'operlog_20191228' table failed. Either you accidentally deleted logs from the table or logs have not been properly dumped to the table.

niyas commented 4 years ago

Hi @objectt, I am also facing the same issue, I changed the min_value of one of the market in config file and restarted the matching engine. I got the error failed to load 'operlog_20191228' db init failed. When I remove that operlog table the matching engine started fine but I lost the data for that day including the balance of some users. I just wonder is there anything wrong with my operlog data. I am posting the operlog data in the below gist link for your reference.

https://gist.github.com/niyas/1f7e24685322c16837d7cfd616dac567

lealife commented 4 years ago

Maybe you edit config.json and delete some old market(s), and there are some oper logs existed on operlog_20191228 which related to the old markets.

sanada08 commented 3 years ago

Issue resolved

MONO-ON commented 2 years ago

I am currently facing the same issue would you please let me know how you solved it?

auagho commented 2 years ago

Issue resolved

How to solve that?? :(