bitcoin-qt crashing - help required

[Aesopspots]

It would be great to get help please.

I had been trying to verify blocks which were long since rebuilt, because i had neglected to run the client. I struggled to get it going again after various crashes and using Time Machine to help me out.

Having run Bitcoin-qt on my Macbook now for over a week, and seen steady rebuilding going on, today i had what i think was an external electrical problem and my Mac switched off. It's okay again, in fact automatically rebooted. However Bitcoin-qt would not start up again. I have tried all the previous remedies incl. time machine backups, although I turned this off once things started again before to speed it all up! so had nothing to restore except the .app, and to no avail I get different crash reports, if I try to run the old original version that had been working ok until today (0.8.5) - it reports:

Process:         Bitcoin-Qt [1041]
Path:            /Applications/zNET/internet/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
Identifier:      org.bitcoinfoundation.Bitcoin-Qt
Version:         0.8.5 (0.8.5)
Code Type:       X86 (Native)
Parent Process:  launchd [169]

Date/Time:       2015-04-07 17:35:25.708 +0100
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          532770 sec
Crashes Since Last Report:           49
Per-App Interval Since Last Report:  1123463 sec
Per-App Crashes Since Last Report:   25
Anonymous UUID:                      FAD8C0E0-FC01-48A3-BCDD-2C5E51DB3FEF

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  5

Application Specific Information:
Assertion failed: (pindexFirst), function GetNextWorkRequired, file src/main.cpp, line 1138.


 
   If i try to use the most recent version I get a different report.

Is there any obvious solution anyone can identify, and help me with?

Thank you.

[GoingAround]

Old version is not compatible with new version 0.10. Please use latest version of the bitcoin-core available and redownload the blockchain

For latest version: https://bitcoin.org/en/download

[shorena]

Old version is not compatible with new version 0.10. Please use latest version of the bitcoin-core available and redownload the blockchain

For latest version: https://bitcoin.org/en/download

Versions before 0.10. will have problems with the blockchain data stored out of order and thus might need to redownload the blockchain. Not sure if you meant that when you said "not compatible". 0.8.5. will certainly work with 0.10.0 clients over the network.


@OP It still makes sense to run the latest version. Check if the log files[1] reveal anything that might help.

[1] https://en.bitcoin.it/wiki/Data_directory#Mac

[GoingAround]

Old version is not compatible with new version 0.10. Please use latest version of the bitcoin-core available and redownload the blockchain

For latest version: https://bitcoin.org/en/download

Versions before 0.10. will have problems with the blockchain data stored out of order and thus might need to redownload the blockchain. Not sure if you meant that when you said "not compatible". 0.8.5. will certainly work with 0.10.0 clients over the network.


@OP It still makes sense to run the latest version. Check if the log files[1] reveal anything that might help.

[1] https://en.bitcoin.it/wiki/Data_directory#Mac

Yes that what i meant, thanks for clarifying.

[Aesopspots]

 Thank you for responding.

I tried to update the old bitcoin-qt, and installed the latest version, following instruction merely to drop the app into applications replacing the old  app. Here is the crash out put for the newest version:


Process:         Bitcoin-Qt [1912]
Path:            /Applications/zNET/internet/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
Identifier:      org.bitcoinfoundation.Bitcoin-Qt
Version:         0.10.0 (0.10.0)
Code Type:       X86-64 (Native)
Parent Process:  launchd [169]

Date/Time:       2015-04-07 19:10:18.205 +0100
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          538466 sec
Crashes Since Last Report:           67
Per-App Interval Since Last Report:  131 sec
Per-App Crashes Since Last Report:   12
Anonymous UUID:                      FAD8C0E0-FC01-48A3-BCDD-2C5E51DB3FEF

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Crashed Thread:  4  QThread

Thread 0:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib                0x00007fff82ce9d7a mach_msg_trap + 10
1   libSystem.B.dylib                0x00007fff82cea3ed mach_msg + 59
2   com.apple.CoreFoundation         0x00007fff8383f902 __CFRunLoopRun + 1698
3   com.apple.CoreFoundation         0x00007fff8383ed8f CFRunLoopRunSpecific + 575
4   com.apple.HIToolbox              0x00007fff800317ee RunCurrentEventLoopInMode + 333
5   com.apple.HIToolbox              0x00007fff800315f3 ReceiveNextEventCommon + 310
6   com.apple.HIToolbox              0x00007fff800314ac BlockUntilNextEventMatchingListInMode + 59
7   com.apple.AppKit                 0x00007fff84d9beb2 _DPSNextEvent + 708
8   com.apple.AppKit       



....etc etc etc

[shorena]

Thank you for responding.

I tried to update the old bitcoin-qt, and installed the latest version, following instruction merely to drop the app into applications replacing the old  app. Here is the crash out put for the newest version:
-snip report-

I have no clue what your OS wants to say with that, besides "well it crashed". Please check the bitcoin log files.

[tspacepilot]

Thank you for responding.

I tried to update the old bitcoin-qt, and installed the latest version, following instruction merely to drop the app into applications replacing the old  app. Here is the crash out put for the newest version:
-snip report-

I have no clue what your OS wants to say with that, besides "well it crashed". Please check the bitcoin log files.

SIGSEGV is "segmentation fault" it means that the program tried to access a memory location that doesn't exist.  <http://en.cppreference.com/w/c/program/SIG_types>

However, I think you're right that the OP should start with some higher level debugging.  OP, can you find the debug.log file and other logs (I don't recall their names) in your ~/.bitcoin directory?

[Aesopspots]

From the debug.log file:





2015-04-07 20:10:14 Bitcoin version v0.10.0 (2015-02-13 09:55:11 +0100)
2015-04-07 20:10:14 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2015-04-07 20:10:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-04-07 20:10:14 Default data directory /Users/a/Library/Application Support/Bitcoin
2015-04-07 20:10:14 Using data directory /Users/a/Library/Application Support/Bitcoin
2015-04-07 20:10:14 Using config file /Users/a/Library/Application Support/Bitcoin/bitcoin.conf
2015-04-07 20:10:14 Using at most 125 connections (2560 file descriptors available)
2015-04-07 20:10:14 Using 2 threads for script verification
2015-04-07 20:10:14 Using wallet wallet.dat
2015-04-07 20:10:14 init message: Verifying wallet...
2015-04-07 20:10:14 CDBEnv::Open : LogDir=/Users/a/Library/Application Support/Bitcoin/database ErrorFile=/Users/a/Library/Application Support/Bitcoin/db.log
2015-04-07 20:10:17 Bound to [::]:8333
2015-04-07 20:10:17 Bound to 0.0.0.0:8333
2015-04-07 20:10:17 init message: Loading block index...
2015-04-07 20:10:17 Opening LevelDB in /Users/a/Library/Application Support/Bitcoin/blocks/index
2015-04-07 20:10:17 Opened LevelDB successfully
2015-04-07 20:10:17 Opening LevelDB in /Users/a/Library/Application Support/Bitcoin/chainstate
2015-04-07 20:10:18 Opened LevelDB successfully
 




Crash report (top part)

Process:         Bitcoin-Qt [2936]
Path:            /Applications/zNET/internet/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt
Identifier:      org.bitcoinfoundation.Bitcoin-Qt
Version:         0.10.0 (0.10.0)
Code Type:       X86-64 (Native)
Parent Process:  launchd [169]

Date/Time:       2015-04-07 21:10:22.580 +0100
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Interval Since Last Report:          545680 sec
Crashes Since Last Report:           81
Per-App Interval Since Last Report:  162 sec
Per-App Crashes Since Last Report:   13
Anonymous UUID:                      FAD8C0E0-FC01-48A3-BCDD-2C5E51DB3FEF

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Crashed Thread:  4  QThread

[cr1776]

If you have a seg fault, it would make me ask a few questions:
1. How much RAM (memory) do you have?
2. How much space is left on the drive?  (e.g. if you are running out of disk space, VM may not be working)
3. Is there a reason you are still running OS X 10.6.8?  The latest release was summer 2011, so it is not getting security updates.  Depending on which Mac you have, you might consider going to OS X 10.9.x (or even OS X 10.10).
4. I am pretty sure that Bitcoin 0.10.0 was only tested on OS X 10.7 through OS X 10.10, so that COULD be an issue.
5. Finally, which processor are you running? (or perhaps easier, which Mac "Model Identifier" in System info  e.g. MacBook3,1  or Macbook 5,2 are you running?)  I ask this because bitcoin 0.10.0 was also only tested on OS X with 64 bit processors, so that too could be an issue.
6. If for some reason you can't upgrade to OS X 10.9 or 10.10 and are really stuck at 10.6.8, that may change the suggestions.

[Aesopspots]

I'm using here a Macbook 2,1, running 10.6.8 that cannot be updated any further.
The processor is a 2GHz Intel core duo from around 2007/8.
The memory, 2 GB 677 Mhz SDRAM. 
Boot ROM Version:   MB21.00A5.B07

Of the 120Gb HDD I have 21.5Gb remaining space.

This morning before the crash Bitcoin-Qt had another 36 weeks of the blockchain to verify.

I had tried previously to run .10 but it failed to open as now, so I went back through Time machine and managed to restart in .8, and it was running for 1-2 weeks 24-7, occasionally with a successful shut down and restart, with a DU scan in between.

[tspacepilot]

Why not go ahead and look in those debug.log files to see if there are clues in there?  oyo's point about VM is interesting, are you running it in a VM or on your OSX machine?  I thought the latter, but perhaps it's worth it to ask.

[cr1776]

I'm using here a Macbook 2,1, running 10.6.8 that cannot be updated any further.
The processor is a 2GHz Intel core duo from around 2007/8.
The memory, 2 GB 677 Mhz SDRAM. 
Boot ROM Version:   MB21.00A5.B07

Of the 120Gb HDD I have 21.5Gb remaining space.

This morning before the crash Bitcoin-Qt had another 36 weeks of the blockchain to verify.

I had tried previously to run .10 but it failed to open as now, so I went back through Time machine and managed to restart in .8, and it was running for 1-2 weeks 24-7, occasionally with a successful shut down and restart, with a DU scan in between.

I don't think you want to be running 0.10.0 then.  The 64 bit vs 32 bit and not tested with 10.6.8 is sufficient reason to avoid it.  I'd use the version you were using, 0.8.5.  2GB with VM should be okay.

You could try re downloading a known good copy of 0.8.5 and see if that helps.  If not it might come down to using the torrent, and then resyncing the whole thing.

[Aesopspots]

I'll try to download another copy of  0.8.5, since i think I can no longer get the working one i found in.

I'm using my Macbook for all this, no VM, but had possibly corrupted something, prior to it all working these past 2 weeks, which of course raises doubts about problems from having tried to direct everything to an external hdd. i tried to methods at that time in Terminal, one worried me since it created a .sh app that I hope I erased all trace of, before getting things going again. Clearing all I could from my Mac, I thought the 40-50gb hdd space would be enough, for the whole blockchain history, now i'm near 20gb I'm worried still this might have been part of the problem.

I saved backups of the wallet.dat and blockchain, 20-30gb of data. Hopefully if it runs again on a new installation of 0.8.5, I can drop that info back, should I have to go as far again to erase the lot from the actual to get it working again.

Having been moving things about (in part to save my data as best I can), I have just seen that I have a bitcoin folder in Applications Support both on the HDD, and under Users. They are both different. I clearly need to sort this out now. Can I get anyone's confirmation of exactly where it should be?

I'm got a little lost last time in why the folders and files were quite different in 0.10 than in 0.8.5.

Thanks for reassuring me cr1776 that 0.8.5 is best for my ageing machine. I thought that much was true last time I had problems.

And to all other support and suggestions.

[shorena]

I'm using here a Macbook 2,1, running 10.6.8 that cannot be updated any further.
The processor is a 2GHz Intel core duo from around 2007/8.
The memory, 2 GB 677 Mhz SDRAM. 
Boot ROM Version:   MB21.00A5.B07

Of the 120Gb HDD I have 21.5Gb remaining space.

This morning before the crash Bitcoin-Qt had another 36 weeks of the blockchain to verify.

I had tried previously to run .10 but it failed to open as now, so I went back through Time machine and managed to restart in .8, and it was running for 1-2 weeks 24-7, occasionally with a successful shut down and restart, with a DU scan in between.

I don't think you want to be running 0.10.0 then.  The 64 bit vs 32 bit and not tested with 10.6.8 is sufficient reason to avoid it.  I'd use the version you were using, 0.8.5.  2GB with VM should be okay.

You could try re downloading a known good copy of 0.8.5 and see if that helps.  If not it might come down to using the torrent, and then resyncing the whole thing.

I would have thought 10.6.8 is 64 bit already, looks like its good I stay away from Mac advice

Feel free to use one of these nodes for syncing, it probably is fast as it gets. Start bitcoin core with -connect=IP, not sure how exactly youd do that on a Mac.

Code:

last updated 2015.03.11
-----------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]    -  speed      - info/stats page[2] - testnet
-----------------------------------------------------------------------------------------------------
185.45.192.129      - Amsterdam, NL, EU    - anon        - 1000 mbit/s - /node.php[3]       - yes
84.200.34.113       - Freinsheim, DE, EU   - Newar       - 1000 mbit/s - yes                - no
5.9.90.133          - Falkenstein, DE, EU  - zvs         -  500 mbit/s - no                 - no
94.23.146.127       - NL, EU               - Mitchełł[6] -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena     -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue        -  100 mbit/s - no                 - no
23.92.214.123  [5]  - Rochester, USA       - Newar       -  100 mbit/s - no                 - no
-----------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[4] be down!!
-----------------------------------------------------------------------------------------------------
all up
-----------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[5] Runs BTCD (alternative full node implementation with GO)
[6] I dont want you search for those ł's on your keyboard, have a link
    https://bitcointalk.org/index.php?action=profile;u=113670

[cr1776]

I would have thought 10.6.8 is 64 bit already, looks like its good I stay away from Mac advice

10.6.8 is (was) both 32 bit and 64 bit.  The main problem is that the Macbook2,1 was a late 2006/mid 2007 machine and so 2-3 years before 10.6 (Aug 2009) and so defaults to a 32 bit kernel.  10.6.8 was released in July 2011, so that was even later.  I think that the machine isn't even capable of a 64 bit kernel (one generation too early) so while the OS can do it, the computer can't.

0.10.0 was only tested on 10.7+ with 64 bit.  Given that (iirc) the kernel is only 32 bit, I think that was the issue with 0.10.0 on that machine.

By the way, I think you can go to 10.7 on the Macbook2,1 (not that it would make a lot of difference).

I think the steps he is trying - reinstalling bitcoin and trying to redownload the blockchain are a good start.  

[tspacepilot]

I would have thought 10.6.8 is 64 bit already, looks like its good I stay away from Mac advice

10.6.8 is (was) both 32 bit and 64 bit.  The main problem is that the Macbook2,1 was a late 2006/mid 2007 machine and so 2-3 years before 10.6 (Aug 2009) and so defaults to a 32 bit kernel.  10.6.8 was released in July 2011, so that was even later.  I think that the machine isn't even capable of a 64 bit kernel (one generation too early) so while the OS can do it, the computer can't.

0.10.0 was only tested on 10.7+ with 64 bit.  Given that (iirc) the kernel is only 32 bit, I think that was the issue with 0.10.0 on that machine.

By the way, I think you can go to 10.7 on the Macbook2,1 (not that it would make a lot of difference).

I think the steps he is trying - reinstalling bitcoin and trying to redownload the blockchain are a good start.  

Indeed, and what's more, if he were running the wrong executable format on the wrong arch it wouldn't result in a sigsegv, it would simply fail to run and say "wrong executable format" (or that's what has happened to me when I tried to run 64bit binaries on a 32bit machine).