[solved] Bitcoin core 0.12.1 on ubuntu 16.04 keep crashing

[retek]

My bitcoin core client on my ubuntu 16.04 (on a virtual machine) keep crashing..)

When started, it download some hundred of blocks and then crash.. always.

I try to delete all the data in the config directory, to redownload all the blockchain, but no-way.. it still crash.

Here the log messages about the crash

2016-04-30 14:24:52 *** System error while flushing: CDB: Error -30974, can't open database
2016-04-30 14:24:53 ERROR: ProcessNewBlock: ActivateBestChain failed
2016-04-30 14:24:53 receive version message: /Satoshi:0.11.2/: version 70002, blocks=409580, us=80.181.135.118:51467, peer=9
2016-04-30 14:24:53 tor: Thread interrupt
2016-04-30 14:24:53 addcon thread interrupt
2016-04-30 14:24:53 opencon thread interrupt
2016-04-30 14:24:53 scheduler thread interrupt
2016-04-30 14:24:53 msghand thread interrupt
2016-04-30 14:24:53 torcontrol thread exit
2016-04-30 14:24:53 net thread interrupt
2016-04-30 14:24:53 Shutdown: In progress...
2016-04-30 14:24:53 StopNode()
2016-04-30 14:24:53 *** System error while flushing: CDB: Error -30974, can't open database
2016-04-30 14:24:55 CDBEnv::EnvShutdown: Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2016-04-30 14:24:55 Shutdown: done

Any idea?
Thanks =)

[1713578974]

1713578974

[butt_coin]

I upgraded to 16.04 LTS and a lot of stuff seem to have compatibility issues. You can try to recompile it or go back to 14 or 15 or whatever you were on til they get things sorted out.

[retek]

I upgraded to 16.04 LTS and a lot of stuff seem to have compatibility issues. You can try to recompile it or go back to 14 or 15 or whatever you were on til they get things sorted out.

Thanks for the reply.
I solved this problem using -salvagewallet arg.

Thanks =)

[firetreeactual]

I upgraded to 16.04 LTS and a lot of stuff seem to have compatibility issues. You can try to recompile it or go back to 14 or 15 or whatever you were on til they get things sorted out.

Thanks for the reply.
I solved this problem using -salvagewallet arg.

Thanks =)

I'm going to have to reinstall Linux tomorrow, and I'm going to do a clean install of 16.04 LTS (was running 14LTS)...saw your note here, and wanted to ask if you could be more specific/expansive on "using -salvagewallet arg." I was able to reconstitute my 0.11.1 wallet on Win10 using the backup wallet.dat file from the data drive (I don't store my data files on a system drive).

I'm also figuring to update the Core Client to 0.12.1 from 0.11.1, and so I'm trying to get my troubleshooting resources together before trying it. I've seen info that says there are problems with older data files (ie, 0.11.1) being used by 0.12.1? I've got a backup Win10 drive I use in the meantime.

Thanks for your input.

[achow101]

I'm going to have to reinstall Linux tomorrow, and I'm going to do a clean install of 16.04 LTS (was running 14LTS)...saw your note here, and wanted to ask if you could be more specific/expansive on "using -salvagewallet arg." I was able to reconstitute my 0.11.1 wallet on Win10 using the backup wallet.dat file from the data drive (I don't store my data files on a system drive).

I'm also figuring to update the Core Client to 0.12.1 from 0.11.1, and so I'm trying to get my troubleshooting resources together before trying it. I've seen info that says there are problems with older data files (ie, 0.11.1) being used by 0.12.1? I've got a backup Win10 drive I use in the meantime.

Thanks for your input.

There are usually no problems with older files that are not also experienced by older software. The upgrade is usually smooth and goes without issue.

[firetreeactual]

I'm going to have to reinstall Linux tomorrow, and I'm going to do a clean install of 16.04 LTS (was running 14LTS)...saw your note here, and wanted to ask if you could be more specific/expansive on "using -salvagewallet arg." I was able to reconstitute my 0.11.1 wallet on Win10 using the backup wallet.dat file from the data drive (I don't store my data files on a system drive).

I'm also figuring to update the Core Client to 0.12.1 from 0.11.1, and so I'm trying to get my troubleshooting resources together before trying it. I've seen info that says there are problems with older data files (ie, 0.11.1) being used by 0.12.1? I've got a backup Win10 drive I use in the meantime.

Thanks for your input.

There are usually no problems with older files that are not also experienced by older software. The upgrade is usually smooth and goes without issue.

Thanks, kid...I needed that. 

[achow101]

I'm going to have to reinstall Linux tomorrow, and I'm going to do a clean install of 16.04 LTS (was running 14LTS)...saw your note here, and wanted to ask if you could be more specific/expansive on "using -salvagewallet arg." I was able to reconstitute my 0.11.1 wallet on Win10 using the backup wallet.dat file from the data drive (I don't store my data files on a system drive).

I'm also figuring to update the Core Client to 0.12.1 from 0.11.1, and so I'm trying to get my troubleshooting resources together before trying it. I've seen info that says there are problems with older data files (ie, 0.11.1) being used by 0.12.1? I've got a backup Win10 drive I use in the meantime.

Thanks for your input.

There are usually no problems with older files that are not also experienced by older software. The upgrade is usually smooth and goes without issue.

Thanks, kid...I needed that.  

If you think I am spamming, I am not. I have worked with Bitcoin Core for a long time and in my experience, the upgrade is always smooth. What usually happens when something goes wrong is usually due to either hardware failure or the user being stupid. It has nothing to do with the software itself as the Core Developers are very careful to ensure that the software is backwards compatible and they do stringent testing to ensure that everything works as it should.

I personally have never experienced any such issues with Bitcoin Core or with upgrading the software, and I have done so on multiple operating systems and across OS upgrades.

[retek]

I upgraded to 16.04 LTS and a lot of stuff seem to have compatibility issues. You can try to recompile it or go back to 14 or 15 or whatever you were on til they get things sorted out.

Thanks for the reply.
I solved this problem using -salvagewallet arg.

Thanks =)

I'm going to have to reinstall Linux tomorrow, and I'm going to do a clean install of 16.04 LTS (was running 14LTS)...saw your note here, and wanted to ask if you could be more specific/expansive on "using -salvagewallet arg." I was able to reconstitute my 0.11.1 wallet on Win10 using the backup wallet.dat file from the data drive (I don't store my data files on a system drive).

I'm also figuring to update the Core Client to 0.12.1 from 0.11.1, and so I'm trying to get my troubleshooting resources together before trying it. I've seen info that says there are problems with older data files (ie, 0.11.1) being used by 0.12.1? I've got a backup Win10 drive I use in the meantime.

Thanks for your input.

I used -salvagewallet arg to bitcoin-qt because it was some sort of problem with my wallet.
The problem was there with an older backup with the wallet too... So yes, I can think this was some sort of problem/incompatibility with the software, but of course I can't be sure..

Hope it help =)