[Problem] Error at shutdown, check the debug.log file

Fakhoury

legendary

Activity: 1386

Merit: 1027

Permabull Bitcoin Investor

Quote from: achow101 on October 20, 2016, 08:49:24 PM

Quote from: Fakhoury on October 20, 2016, 08:46:32 PM

Thanks for your input, could you please tell me more (from your word/expreience) what is -salvagewallet and what does it do ?

Thank you

-salvagewallet does exactly what the name suggests, it attempt to salvage a corrupted wallet. That means that Bitcoin Core will try to read the wallet and recover as many keys as it can from that wallet.

I didn't forget to thank you achow101, and I wanted to PM you to thank you so much because you've always been there for ME exactly whenever I need any help with Core.

I'm sorry if my thanks came late, but I never forgot it.

Thank you so much my friend and from the bottom of my heart, I wish you all the best.

I will leave the thread open for you if you wish to reply or to lock it, the issue is solved as I've had a good copy of the chain, I've used it and it synced well and everything went well

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: Fakhoury on October 20, 2016, 08:46:32 PM

Thanks for your input, could you please tell me more (from your word/expreience) what is -salvagewallet and what does it do ?

Thank you

-salvagewallet does exactly what the name suggests, it attempt to salvage a corrupted wallet. That means that Bitcoin Core will try to read the wallet and recover as many keys as it can from that wallet.

Fakhoury

legendary

Activity: 1386

Merit: 1027

Permabull Bitcoin Investor

Quote from: longbob72 on October 20, 2016, 02:54:22 PM

Quote from: Fakhoury on October 20, 2016, 02:19:32 PM

Quote from: longbob72 on October 20, 2016, 02:15:51 PM

~~Looks a lot like the problem in this thread~~ On second read, no it's not that similar. I'd try reindexing first and see if it works (start core with -reindex), if not then it's a hardware problem.

No other solution beside re-indexing ?

If your problem is corrupted blocks then reindex or deleting all the corrupted block files and redownloading them are the only solutions. If it's a hardisk problem then you have to move them to other hardisk.
If it's a wallet.dat corruption (found that here) then run core with -salvagewallet.

Thanks for your input, could you please tell me more (from your word/expreience) what is -salvagewallet and what does it do ?

Thank you

longbob72

hero member

Activity: 574

Merit: 503

V2h5IGFyZSB5b3UgcmVhZGluZyB0aGlzPw==

Quote from: Fakhoury on October 20, 2016, 02:19:32 PM

Quote from: longbob72 on October 20, 2016, 02:15:51 PM

~~Looks a lot like the problem in this thread~~ On second read, no it's not that similar. I'd try reindexing first and see if it works (start core with -reindex), if not then it's a hardware problem.

No other solution beside re-indexing ?

If your problem is corrupted blocks then reindex or deleting all the corrupted block files and redownloading them are the only solutions. If it's a hardisk problem then you have to move them to other hardisk.
If it's a wallet.dat corruption (found that here) then run core with -salvagewallet.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Post the contents of the db.log file.

Fakhoury

legendary

Activity: 1386

Merit: 1027

Permabull Bitcoin Investor

Quote from: longbob72 on October 20, 2016, 02:15:51 PM

~~Looks a lot like the problem in this thread~~ On second read, no it's not that similar. I'd try reindexing first and see if it works (start core with -reindex), if not then it's a hardware problem.

No other solution beside re-indexing ?

longbob72

hero member

Activity: 574

Merit: 503

V2h5IGFyZSB5b3UgcmVhZGluZyB0aGlzPw==

~~Looks a lot like the problem in this thread~~ On second read, no it's not that similar. I'd try reindexing first and see if it works (start core with -reindex), if not then it's a hardware problem.

Fakhoury

legendary

Activity: 1386

Merit: 1027

Permabull Bitcoin Investor

Hello again,

Well, I've solved the issue on here (https://bitcointalksearch.org/topic/problem-sent-balance-showing-still-as-unsent-1656197).

But after solving it and each time I close the client, I get this error.

And each time I start the client, re-scanning takes place.

Part of the debug file, I'm running Bitcoin Core 0.12.1 btw.

Code:

2016-10-20 18:07:28 tor: Thread interrupt
2016-10-20 18:07:28 torcontrol thread exit
2016-10-20 18:07:28 scheduler thread interrupt
2016-10-20 18:07:28 opencon thread interrupt
2016-10-20 18:07:28 addcon thread interrupt
2016-10-20 18:07:28 msghand thread interrupt
2016-10-20 18:07:28 net thread interrupt
2016-10-20 18:07:28 Shutdown: In progress...
2016-10-20 18:07:28 StopNode()
2016-10-20 18:07:28 *** System error while flushing: CDB: Error -30974, can't open database
2016-10-20 18:07:56 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2016-10-20 18:07:56 Shutdown: done

Thanks in advance and have a great day.

Topic: [Problem] Error at shutdown, check the debug.log file (Read 966 times)