can't start mining, sync is not completed, stay in 382798 block 2 hours...
what i should do?




2019-05-18 22:24:23.921 13516   INFO    global  src/daemon/main.cpp:214 Solo 'Han' (v1.0.4.4-9d37987)
2019-05-18 22:24:23.922 13516   INFO    global  src/daemon/protocol.h:53        Initializing cryptonote protocol...
2019-05-18 22:24:23.922 13516   INFO    global  src/daemon/protocol.h:58        Cryptonote protocol initialized OK
2019-05-18 22:24:23.923 13516   INFO    global  src/daemon/p2p.h:63     Initializing p2p server...
2019-05-18 22:24:27.944 13516   INFO    global  src/daemon/p2p.h:68     p2p server initialized OK
2019-05-18 22:24:27.946 13516   INFO    global  src/daemon/rpc.h:63     Initializing core RPC server...
2019-05-18 22:24:27.946 13516   INFO    global  contrib/epee/include/net/http_server_impl_base.h:77     Binding on 127.0.0.1:22424
2019-05-18 22:24:27.947 13516   INFO    global  src/daemon/rpc.h:69     core RPC server initialized OK on port: 22424
2019-05-18 22:24:27.947 13516   INFO    global  src/daemon/core.h:74    Initializing core...
2019-05-18 22:24:27.948 13516   INFO    global  src/cryptonote_core/cryptonote_core.cpp:416     Loading blockchain from folder C:\ProgramData\solo\lmdb ...
2019-05-18 22:24:27.976 13516   INFO    global  src/cryptonote_core/cryptonote_core.cpp:514     Loading checkpoints
2019-05-18 22:24:27.978 13516   INFO    global  src/daemon/core.h:79    Core initialized OK
2019-05-18 22:24:27.978 13516   INFO    global  src/daemon/rpc.h:74     Starting core RPC server...
2019-05-18 22:24:27.979 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:79     core RPC server started ok
2019-05-18 22:24:27.999 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78     Starting p2p net loop...
2019-05-18 22:24:29.001 [P2P7]  INFO    global  src/cryptonote_core/cryptonote_core.cpp:1494
**********************************************************************
The daemon will start synchronizing with the network. This may take a long time to complete.

You can set the level of process detailization through "set_log " command,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).

Use the "help" command to see the list of available commands.
Use "help " to see a command's documentation.
**********************************************************************

2019-05-18 22:24:29.506 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [46.72.106.45:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390209 [Your node is 7411 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:33.847 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390209 [Your node is 7411 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:39.534 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390210 [Your node is 7412 blocks (1 days) behind]
SYNCHRONIZATION started
2019-05-18 22:24:42.264 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:311     [221.219.179.84:22423 OUT] Sync data returned a new top block candidate: 382798 -> 390210 [Your node is 7412 blocks (1 days) behind]
SYNCHRONIZATION started