Bitcoin Forum
December 09, 2016, 05:55:24 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 [4] 5 »  All
  Print  
Author Topic: Version 0.6.0 released  (Read 9554 times)
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
April 05, 2012, 09:56:36 PM
 #61

The blockchain download speed is soo much faster now!

<3

1481306124
Hero Member
*
Offline Offline

Posts: 1481306124

View Profile Personal Message (Offline)

Ignore
1481306124
Reply with quote  #2

1481306124
Report to moderator
1481306124
Hero Member
*
Offline Offline

Posts: 1481306124

View Profile Personal Message (Offline)

Ignore
1481306124
Reply with quote  #2

1481306124
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481306124
Hero Member
*
Offline Offline

Posts: 1481306124

View Profile Personal Message (Offline)

Ignore
1481306124
Reply with quote  #2

1481306124
Report to moderator
SkRRJyTC
Legendary
*
Offline Offline

Activity: 966


View Profile
April 05, 2012, 10:40:09 PM
 #62

The devs have been begging for beta testers for a while now.

How would I begin to get involved with this?
ThiagoCMC
Legendary
*
Offline Offline

Activity: 1190


฿itcoin: Currency of Resistance!


View Profile WWW
April 05, 2012, 11:27:17 PM
 #63

Any issues upgrading or can I just install and open w/o loss?

What I've done:

1- Stop your Bitcoin <0.5.3;
2- Copy your wallet;
3- remove (or move it away) the "old" blockchain (i.e. mv ~/.bitcoin/ ~/_bitcoin-0.5.3-backup);
4- create a empty dir (i.e. mkdir ~/.bitcoin/);
5- copy the wallet.dat from the backup to ~/.bitcoin;
6- start Bitcoin 0.6.0.

Mercado Forex acessível para todos os Brasileiros que tenham Bitcoins! Cadastre-se hoje mesmo! Bastar acessar aqui: https://1broker.com/m/r.php?i=8879
dlb76
Newbie
*
Offline Offline

Activity: 19


View Profile
April 06, 2012, 01:17:28 AM
 #64

updated to 0.6.0.6-beta
Thanks for QR codes!
GideonGono
Sr. Member
****
Offline Offline

Activity: 398


Long Live The FED


View Profile WWW
April 06, 2012, 05:43:25 AM
 #65

Thanks to all the contributors to this release!!

jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 06, 2012, 09:24:56 PM
 #66

Please file bug reports on the github issue tracker. Include enough information so we can reproduce the problem (what platform? what seems to cause the problem? etc) and it might get fixed.

Another crash happened today, same platform etc.

This time it ran with -printtoconsole (no -debug).  The scrollback buffer is filled with hundreds of

Code:
received getdata for: tx 7680e65403ab1b258887

.. then:

Code:
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
trying connection 81.176.229.178:8333 lastseen=-2.5hrs
connect() failed after select(): Connection refused
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
askfor tx 263d4ec0b5712e6e1b47   0
sending getdata: tx 263d4ec0b5712e6e1b47
trying connection 141.106.36.16:8333 lastseen=-3.9hrs
connect() failed after select(): Connection refused
received getdata for: tx 7680e65403ab1b258887
askfor tx 263d4ec0b5712e6e1b47   1333717043000000
askfor tx 263d4ec0b5712e6e1b47   1333717163000000
askfor tx 263d4ec0b5712e6e1b47   1333717283000000
askfor tx 263d4ec0b5712e6e1b47   1333717403000000
askfor tx 263d4ec0b5712e6e1b47   1333717523000000
askfor tx 263d4ec0b5712e6e1b47   1333717643000000
askfor tx 263d4ec0b5712e6e1b47   1333717763000000
askfor tx 263d4ec0b5712e6e1b47   1333717883000000
askfor tx 263d4ec0b5712e6e1b47   1333718003000000
askfor tx 263d4ec0b5712e6e1b47   1333718123000000
AcceptToMemoryPoolUnchecked(): size 22
AcceptToMemoryPool(): accepted 263d4ec0b5
received getdata for: tx 7680e65403ab1b258887
received getdata for: tx 7680e65403ab1b258887
trying connection 69.119.102.53:8333 lastseen=-2.9hrs
sending getdata: tx 35f44d3defc623e850d4
received getdata for: tx 89c54bace5d7221fb8e2
ERROR: AcceptToMemoryPool() : not enough fees
received getdata for: tx 7680e65403ab1b258887
Added 1 addresses from 74.58.231.130: 3415 tried, 8183 new
Added 1 addresses from 95.211.10.8: 3415 tried, 8183 new
received getdata for: tx 7680e65403ab1b258887
askfor tx fee32af70d821d823ba6   0
sending getdata: tx fee32af70d821d823ba6
askfor tx fee32af70d821d823ba6   1333717046000000
askfor tx fee32af70d821d823ba6   1333717166000000
askfor tx fee32af70d821d823ba6   1333717286000000
askfor tx fee32af70d821d823ba6   1333717406000000
askfor tx fee32af70d821d823ba6   1333717526000000
AcceptToMemoryPoolUnchecked(): size 23
AcceptToMemoryPool(): accepted fee32af70d
received getdata for: tx fee32af70d821d823ba6
Added 1 addresses from 91.95.240.5: 3415 tried, 8183 new
Added 1 addresses from 68.38.31.2: 3415 tried, 8183 new
askfor tx a817688a1f0463c40287   0
sending getdata: tx a817688a1f0463c40287
askfor tx a817688a1f0463c40287   1333717048000000
askfor tx a817688a1f0463c40287   1333717168000000
connection timeout  
askfor tx a817688a1f0463c40287   1333717288000000
accepted connection 147.133.197.3:64460
askfor tx a817688a1f0463c40287   1333717408000000
askfor tx a817688a1f0463c40287   1333717528000000
askfor tx a817688a1f0463c40287   1333717648000000
AcceptToMemoryPoolUnchecked(): size 24
AcceptToMemoryPool(): accepted a817688a1f
version message: version 32300, blocks=174516
trying connection 83.101.77.156:8333 lastseen=-3.7hrs
connect() failed after select(): Connection refused
received getdata for: tx a817688a1f0463c40287
received getdata for: tx a817688a1f0463c40287
askfor tx 9258e72d561e900d9f43   0
sending getdata: tx 9258e72d561e900d9f43
AcceptToMemoryPoolUnchecked(): size 25
AcceptToMemoryPool(): accepted 9258e72d56
received getdata for: tx 8d0bb79790fb657abcf5
trying connection 80.109.36.181:8333 lastseen=-2.1hrs
connect() failed after select(): Connection refused
trying connection 75.71.123.118:8333 lastseen=-2.8hrs
askfor tx 92422eb05a06de269337   0
sending getdata: tx 92422eb05a06de269337
askfor tx 92422eb05a06de269337   1333717051000000
askfor tx 92422eb05a06de269337   1333717171000000
askfor tx 92422eb05a06de269337   1333717291000000
askfor tx 92422eb05a06de269337   1333717411000000
askfor tx 92422eb05a06de269337   1333717531000000
askfor tx 92422eb05a06de269337   1333717651000000
askfor tx 92422eb05a06de269337   1333717771000000
askfor tx 92422eb05a06de269337   1333717891000000
askfor tx 92422eb05a06de269337   1333718011000000
askfor tx 92422eb05a06de269337   1333718131000000
askfor tx 92422eb05a06de269337   1333718251000000
askfor tx 92422eb05a06de269337   1333718371000000
AcceptToMemoryPoolUnchecked(): size 26
AcceptToMemoryPool(): accepted 92422eb05a
askfor tx 4119e666abec78284fa8   0
sending getdata: tx 4119e666abec78284fa8
askfor tx 4119e666abec78284fa8   1333717053000000
askfor tx 1c7736165bd767d36f81   0
sending getdata: tx 1c7736165bd767d36f81
AcceptToMemoryPoolUnchecked(): size 27
AcceptToMemoryPool(): accepted 4119e666ab
AcceptToMemoryPoolUnchecked(): size 28
AcceptToMemoryPool(): accepted 1c7736165b
Added 1 addresses from 128.211.220.133: 3415 tried, 8181 new
connection timeout  
trying connection 85.134.121.91:8333 lastseen=-2.7hrs
received getdata for: tx bc7df6ba49c3f73c67b5
received getdata for: tx 0824d52714585ec7b346
Added 1 addresses from 174.29.73.225: 3415 tried, 8180 new
askfor tx 4c999081f337a76825bb   0
sending getdata: tx 4c999081f337a76825bb
askfor tx 4c999081f337a76825bb   1333717059000000
askfor tx 4c999081f337a76825bb   1333717179000000
askfor tx 4c999081f337a76825bb   1333717299000000
askfor tx 4c999081f337a76825bb   1333717419000000
askfor tx 4c999081f337a76825bb   1333717539000000
askfor tx 4c999081f337a76825bb   1333717659000000
askfor tx 4c999081f337a76825bb   1333717779000000
askfor tx 4c999081f337a76825bb   1333717899000000
askfor tx 4c999081f337a76825bb   1333718019000000
AcceptToMemoryPoolUnchecked(): size 29
AcceptToMemoryPool(): accepted 4c999081f3
Added 1 addresses from 58.38.114.57: 3415 tried, 8180 new
Added 1 addresses from 86.171.229.45: 3415 tried, 8179 new
connection timeout  
trying connection 24.199.159.83:8333 lastseen=-3.6hrs
Added 1 addresses from 71.125.32.246: 3415 tried, 8178 new
Added 1 addresses from 131.93.72.31: 3415 tried, 8179 new
connection timeout  
Added 1 addresses from 76.117.220.29: 3415 tried, 8177 new
trying connection 78.159.58.51:8333 lastseen=-3.5hrs
connected 78.159.58.51:8333
Added time data, samples 200, offset -17 (+0 minutes)
Moving 78.159.58.51:8333 to tried
version message: version 32300, blocks=174521
trying connection 95.27.140.103:8333 lastseen=-3.3hrs
Added 8 addresses from 78.159.58.51: 3415 tried, 8170 new
connection timeout  
Added 1 addresses from 98.182.22.232: 3415 tried, 8168 new
trying connection 194.226.8.27:8333 lastseen=-2.1hrs
received getdata for: block 0000000000000504f773
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
socket closed
disconnecting node 109.75.176.70:8333

...

Code:
Added 1 addresses from 76.117.220.29: 3415 tried, 8128 new
accepted connection 86.47.17.210:10890
Added time data, samples 200, offset -4 (+0 minutes)
Added 86.47.17.210:8333 from 86.47.17.210: 3415 tried, 8127 new
Moving 86.47.17.210:8333 to tried
version message: version 60000, blocks=167425
connection timeout  
trying connection 117.22.50.36:8333 lastseen=-2.2hrs
connected 117.22.50.36:8333
trying connection 84.232.230.105:8333 lastseen=-2.0hrs
connect() failed after select(): Connection refused
trying connection 82.170.160.25:8333 lastseen=-2.1hrs
getblocks 166650 to 000000000000027f4096 limit 500
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed

.. and now I get literally hundreds of this:

Code:
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed

.. after which it continues like this:

Code:
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
  getblocks stopping at limit 167149 00000000000003251788 (40500 bytes)
received getdata for: tx 1b356369085657c7ace4
received getdata for: tx 8c50e82b2748528264cf
received getdata for: tx 2198ff40554b152b1a79
received getdata for: tx 828a38228f1721fece77
received getdata for: tx d4a4a2a23faebe9f6e62
received getdata for: tx 227eb66590575d626827
received getdata for: tx f3bc2efde58857ee9e66
received getdata for: tx 905f4ec6f080f66ffd0e
received getdata for: tx cc2fa59268afb6437f27
received getdata for: tx 8204e14270077c5cbf76
received getdata for: tx 5a3e47b43ce378aad707
received getdata for: tx 09a5d50c49714bafeaf8
received getdata for: tx 89c99876c87ccddea130
received getdata for: tx 16b0eedcbe030dc75129
received getdata for: block 0000000000000706fb4a
ERROR: CBlock::ReadFromDisk() : OpenBlockFile failed
received getdata for: tx a26d8f23d50b8ede2221
Added 1 addresses from 213.151.89.23: 3416 tried, 8123 new
connection timeout
socket closed
disconnecting node 68.12.223.12:8333
trying connection 77.93.86.5:8333 lastseen=-9.3hrs
connect() failed after select(): No route to host
trying connection 92.30.18.217:8333 lastseen=-2.7hrs
Added 1 addresses from 24.84.96.223: 3416 tried, 8119 new
Added 1 addresses from 68.53.153.158: 3416 tried, 8120 new
Added 1 addresses from 216.150.78.34: 3416 tried, 8120 new
connection timeout
trying connection 78.42.219.156:8333 lastseen=-2.2hrs
connected 78.42.219.156:8333
trying connection 86.93.165.82:8333 lastseen=-3.2hrs
askfor tx cc18e6dd56b2ac029bb1   0
sending getdata: tx cc18e6dd56b2ac029bb1
askfor tx cc18e6dd56b2ac029bb1   1333717155000000
askfor tx cc18e6dd56b2ac029bb1   1333717275000000
received getdata for: tx 7112939b80c44093c5cc
askfor tx cc18e6dd56b2ac029bb1   1333717395000000
askfor tx cc18e6dd56b2ac029bb1   1333717515000000
ERROR: CTransaction::ReadFromDisk() : OpenBlockFile failed
ERROR: FetchInputs() : cc18e6dd56 ReadFromDisk prev tx 803d7f1f5d failed
ERROR: AcceptToMemoryPool() : FetchInputs failed cc18e6dd56
storing orphan tx cc18e6dd56
Added 1 addresses from 90.214.173.163: 3416 tried, 8115 new
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx a26d8f23d50b8ede2221
connection timeout  
received getdata for: tx ddb63a21608ada6d5a1d
trying connection 89.223.38.207:8333 lastseen=-4.3hrs
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx a26d8f23d50b8ede2221
received getdata for: tx 4febb23f86ab4a0d6cc4
Added 1 addresses from 68.53.153.158: 3416 tried, 8105 new
connection timeout  
trying connection 99.244.62.156:8333 lastseen=-4.0hrs
connected 99.244.62.156:8333
Added 1 addresses from 173.238.168.52: 3416 tried, 8106 new
Added 1 addresses from 192.75.95.253: 3416 tried, 8107 new
trying connection 90.129.138.126:8333 lastseen=-2.3hrs
trying connection 216.160.91.91:8333 lastseen=-4.5hrs
trying connection 75.94.171.54:8333 lastseen=-3.4hrs
trying connection 68.207.196.134:8333 lastseen=-2.2hrs
trying connection 80.199.31.74:8333 lastseen=-2.4hrs
trying connection 12.189.154.66:8333 lastseen=-3.1hrs
trying connection 188.47.5.13:8333 lastseen=-2.0hrs
trying connection 46.146.1.200:8333 lastseen=-2.8hrs
trying connection 74.60.78.73:8333 lastseen=-3.2hrs
trying connection 98.222.154.122:8333 lastseen=-2.8hrs
trying connection 77.255.5.179:8333 lastseen=-3.2hrs
socket recv error 110
disconnecting node 109.246.254.188:8333
trying connection 81.151.216.26:8333 lastseen=-4.3hrs
socket closed
disconnecting node 84.73.221.49:8333
terminate called after throwing an instance of 'DbRunRecoveryException'
  what():  DbEnv::txn_checkpoint: DB_RUNRECOVERY: Fatal error, run database recovery
Aborted

.. and here bitcoind is dead.  No more messages, nor a stackdump either.  Resultcode is 134.

I got the same behaviour on two different boxes.


The earliest abnormal behaviour I could find in the scrollback buffer is transaction 7680e65403ab1b258887 (dont know if this identifier is meaningful after bitcoind has shutdown?).  Then there is that sole "OpenBlockFile failed", which shortly extends into hundreds of the same error which take down all dependent operations very quickly.

This happened around 7pm CET this afternoon.

If necessary, I think I have full -debug -printtoconsole logs on the other box (not limited by scrollback buffer size).  Let me know if you need them and I will recover them for you.

Edit: added code tags
rjk
Sr. Member
****
Offline Offline

Activity: 420


1ngldh


View Profile
April 06, 2012, 09:38:08 PM
 #67

Look to me like it could be either disk corruption or someone flooding your node with an invalid tx. I think you mentioned that you have already blown away the block database once, but if you haven't that would be something to try.

Mining Rig Extraordinaire - the Trenton BPX6806 18-slot PCIe backplane [PICS] Dead project is dead, all hail the coming of the mighty ASIC!
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 06, 2012, 09:38:36 PM
 #68

Another good one:

...

Code:
version message: version 40000, blocks=174571
04/06/12 21:31:23 received: verack (0 bytes)
04/06/12 21:31:23 received: block (7123 bytes)
received block 00000000000008506c9e
SetBestChain: new best=00000000000008506c9e  height=174572  work=286071818980138056873
ProcessBlock: ACCEPTED
04/06/12 21:31:23 received: inv (37 bytes)
  got inventory: tx 2218b46d9523b7a39653  new
askfor tx 2218b46d9523b7a39653   0
sending getdata: tx 2218b46d9523b7a39653
04/06/12 21:31:23 sending: getdata (37 bytes)
04/06/12 21:31:23 received: block (7123 bytes)
received block 00000000000008506c9e
ERROR: ProcessBlock() : already have block 174572 00000000000008506c9e
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: addr (31 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 received: inv (37 bytes)
  got inventory: block 00000000000008506c9e  have
askfor block 00000000000008506c9e   0
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 sending: inv (37 bytes)
04/06/12 21:31:23 received: tx (620 bytes)
Rate limit dFreeCount: 728.562 => 1348.56
AcceptToMemoryPoolUnchecked(): size 5
AcceptToMemoryPool(): accepted 2218b46d95
04/06/12 21:31:24 received: inv (37 bytes)
  got inventory: block 00000000000008506c9e  have
askfor block 00000000000008506c9e   1333747883000000
04/06/12 21:31:24 sending: inv (37 bytes)
04/06/12 21:31:24 sending: inv (37 bytes)
04/06/12 21:31:24 received: inv (37 bytes)
  got inventory: tx 2218b46d9523b7a39653  have
04/06/12 21:31:24 sending: inv (37 bytes)
04/06/12 21:31:24 sending: inv (37 bytes)
04/06/12 21:31:24 sending: inv (37 bytes)
04/06/12 21:31:25 received: inv (37 bytes)
  got inventory: tx 2218b46d9523b7a39653  have
04/06/12 21:31:26 sending: inv (37 bytes)
04/06/12 21:31:26 Flushing wallet.dat
Flushed wallet.dat 19ms
04/06/12 21:31:26 sending: inv (37 bytes)
04/06/12 21:31:26 sending: inv (37 bytes)
04/06/12 21:31:26 received: addr (5851 bytes)
Segmentation fault  

The returncode is 139 at this point.

Note how at one point is sais received block 00000000000008506c9e, then it sais error, already have 00000000000008506c9e.  Then shortly after it sais ask for block 00000000000008506c9e and shortly after it just segfaults.

Edit: added code tags
paraipan
Legendary
*
Offline Offline

Activity: 924


Firstbits: 1pirata


View Profile WWW
April 06, 2012, 09:42:54 PM
 #69

interesting...

Quote
askfor tx 263d4ec0b5712e6e1b47   1333717043000000

Quote
askfor block 00000000000008506c9e   1333747883000000

BTCitcoin: An Idea Worth Saving - Q&A with bitcoins on rugatu.com - Check my rep
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 06, 2012, 09:44:26 PM
 #70

Look to me like it could be either disk corruption or someone flooding your node with an invalid tx. I think you mentioned that you have already blown away the block database once, but if you haven't that would be something to try.

Disk corruption is not likely.  The two boxes have different hardware, different blockdevs, even different filesystems.

Wipe database, yes I did this already.

About your other suspicion:  flood with invalid tx -> crash == DoS attack vector.

The goold old 3.xx branch was rock stable, and now we are FORCED to use software which has less than a week of testing (and many obvious problems already visible).
rjk
Sr. Member
****
Offline Offline

Activity: 420


1ngldh


View Profile
April 06, 2012, 09:49:04 PM
 #71

About your other suspicion:  flood with invalid tx -> crash == DoS attack vector.
Some similar tx flood DoS attack vectors were recently closed, but it is entirely possible that more remain, or that the patch has opened a different vector. It will be interesting to find out the cause of this crashing.

BTW, I believe that Luke-jr has posted backports of 0.5.x, if that interests you.

Mining Rig Extraordinaire - the Trenton BPX6806 18-slot PCIe backplane [PICS] Dead project is dead, all hail the coming of the mighty ASIC!
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 06, 2012, 10:00:00 PM
 #72

What about this one:

Bitcoin version 0.6.0.99-beta
Default data directory /home/USERNAME/.bitcoin
Loading addresses...
dbenv.open strLogDir=/home/USERNAME/.bitcoin/database strErrorFile=/home/USERNAME/.bitcoin/db.log


************************
EXCEPTION: NSt8ios_base7failureE
CDataStream::read() : end of data
bitcoin in AppInit()

Result code is 134 and it repeats like this until I delete addr.adt

Apparently addr.dat can also be filled with "poisonous data" from remote.  Good way to take offline your competitors.
Gavin Andresen
Legendary
*
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
April 07, 2012, 12:02:44 AM
 #73

Is anybody else seeing anything like what jetmine is seeing?  Anybody else running CentOS 5.6?  Did you compile from source or are you using the binaries we compiled?

My 0.6 nodes running on Ubuntu 11 have been rock solid.

The "CBlock::ReadFromDisk() : OpenBlockFile failed" is very odd, that should never happen.  You aren't running with a -datadir on a network drive or something are you?

RE: filling addr.dat:  that is one of the denial-of-service attacks fixed by the 0.6 release.

How often do you get the chance to work on a potentially world-changing project?
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218


Gerald Davis


View Profile
April 07, 2012, 02:49:52 AM
 #74

Nope but not using Centos.  Have 3 copies running 1 on Win7 and 2 on Debian.  They support a farm running p2pool.  Haven't had a single crash on any instance.
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
April 07, 2012, 08:28:58 AM
 #75

run it in gdb, and use the "bt" command when a segfault occurs.  Make sure to enable thread tracing, if that is not default / built in.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 07, 2012, 11:58:51 AM
 #76

Did you compile from source or are you using the binaries we compiled?

The "CBlock::ReadFromDisk() : OpenBlockFile failed" is very odd, that should never happen.  You aren't running with a -datadir on a network drive or something are you?

Compiled from source.

The datadir is on the local disk (LVM volume on the same physical disk as the OS).

run it in gdb, and use the "bt" command when a segfault occurs.  Make sure to enable thread tracing, if that is not default / built in.

Thanks, I will do that.  One doubt though.  How can I enable thread tracing, or check whether it is enabled by default?  Google tells me to use ptrace instead of gdb for thread tracing, but I suspect this is not what you want me to do.
BlackEye
Newbie
*
Offline Offline

Activity: 17


View Profile
April 07, 2012, 03:33:46 PM
 #77

I've been running the released 0.6.0.6-beta Windows version for a few days without issue.  This morning I see that it had crashed.

Code:
AcceptToMemoryPoolUnchecked(): size 165
AcceptToMemoryPool(): accepted 6782e85f04
askfor tx 6aa3f5bd2139496e20ca   0
sending getdata: tx 6aa3f5bd2139496e20ca
askfor tx 6aa3f5bd2139496e20ca   1333775791000000
AcceptToMemoryPoolUnchecked(): size 166
AcceptToMemoryPool(): accepted 6aa3f5bd21
askfor tx 69c0e4718003450f04d7   0
sending getdata: tx 69c0e4718003450f04d7
askfor tx 69c0e4718003450f04d7   1333775793000000
AcceptToMemoryPoolUnchecked(): size 167
AcceptToMemoryPool(): accepted 69c0e47180
Added 1 addresses from 216.245.210.212: 45 tried, 12819 new
Added 1 addresses from 208.118.235.153: 45 tried, 12820 new


************************
EXCEPTION: St9bad_alloc       
std::bad_alloc
C:\path\to\bitcoin\bitcoin-qt.exe in ThreadDumpAddress()


1CLJbMgYsaRUbcN2LwQDx2WkG3NJJ2KyJr
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 08, 2012, 09:56:35 AM
 #78

RE: filling addr.dat:  that is one of the denial-of-service attacks fixed by the 0.6 release.

I am running both 0.6.0 release and the master from Apr-03 (which is shortly afterwards).  Yet I get these addr.dat errors.  There must be another bug to fix in addr.dat

Today I got two other crashes, one of them in gdb.  I will post it in a separate post, so that my point about addr.dat doesnt get drowned.
jetmine
Jr. Member
*
Offline Offline

Activity: 53


View Profile
April 08, 2012, 10:05:27 AM
 #79

run it in gdb, and use the "bt" command when a segfault occurs.  Make sure to enable thread tracing, if that is not default / built in.

Ok, so this is a crash with v0.6.0 release at around 6am today.  I still dont know how to enable thread tracing, so I hope it was just enable by default (?).


The backbuffer of -debug -printtoconsole looks quite normal:

Code:
Added 1 addresses from 91.154.226.179: 3470 tried, 11409 new
04/08/12 04:06:56 sending: addr (31 bytes)
04/08/12 04:06:57 received: addr (31 bytes)
04/08/12 04:06:57 sending: addr (31 bytes)
04/08/12 04:06:59 sending: addr (31 bytes)
04/08/12 04:07:00 sending: addr (31 bytes)
04/08/12 04:07:00 sending: addr (31 bytes)
04/08/12 04:07:01 sending: addr (31 bytes)
04/08/12 04:07:03 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  new
askfor tx 46003e4d1f5d3985d710   0
sending getdata: tx 46003e4d1f5d3985d710
04/08/12 04:07:03 sending: getdata (37 bytes)
04/08/12 04:07:03 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  new
askfor tx 46003e4d1f5d3985d710   1333858023000000
04/08/12 04:07:03 received: tx (258 bytes)
Rate limit dFreeCount: 13149.2 => 13407.2
AcceptToMemoryPoolUnchecked(): size 132
AcceptToMemoryPool(): accepted 46003e4d1f
04/08/12 04:07:03 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:03 sending: inv (37 bytes)
04/08/12 04:07:03 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:03 sending: inv (37 bytes)
04/08/12 04:07:04 sending: inv (37 bytes)
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 sending: inv (37 bytes)
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 sending: inv (37 bytes)
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 sending: inv (37 bytes)
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:04 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:05 sending: inv (37 bytes)
04/08/12 04:07:05 sending: inv (37 bytes)
04/08/12 04:07:05 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:05 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:05 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:05 sending: inv (37 bytes)
04/08/12 04:07:06 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:06 sending: inv (37 bytes)
04/08/12 04:07:07 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:10 received: inv (37 bytes)
  got inventory: tx 46003e4d1f5d3985d710  have
04/08/12 04:07:12 received: addr (31 bytes)
04/08/12 04:07:12 sending: addr (31 bytes)
04/08/12 04:07:16 sending: addr (31 bytes)
04/08/12 04:07:17 received: addr (31 bytes)
04/08/12 04:07:18 sending: addr (31 bytes)
04/08/12 04:07:19 received: addr (31 bytes)
*** glibc detected *** /home/btc/bitcoind: free(): invalid next size (fast): 0x0000000000d9ffa0 ***

Now comes a dump that was made automatically.  It looks similar to what I mentioned that had happened already once to me:

Code:
======= Backtrace: =========
[0x7f346b]
[0x7f7516]
[0x40f013]
[0x40f2d8]
[0x40e0ee]
[0x40e3dc]
[0x46d2b4]
[0x470620]
[0x48e435]
[0x48e645]
[0x751edd]
[0x810329]
======= Memory map: ========
00400000-0099b000 r-xp 00000000 fd:02 181991                             /home/USERNAME/bitcoind
00b9a000-00bab000 rwxp 0059a000 fd:02 181991                             /home/USERNAME/bitcoind
00bab000-038dc000 rwxp 00bab000 00:00 0
038dc000-038dd000 rwxp 038dc000 00:00 0
038dd000-04cb9000 rwxp 038dd000 00:00 0
40000000-40001000 ---p 40000000 00:00 0
40001000-40a01000 rwxp 40001000 00:00 0
40a01000-40a02000 ---p 40a01000 00:00 0
40a02000-41402000 rwxp 40a02000 00:00 0
41402000-41403000 ---p 41402000 00:00 0
41403000-41e03000 rwxp 41403000 00:00 0
41e03000-41e04000 ---p 41e03000 00:00 0
41e04000-42804000 rwxp 41e04000 00:00 0
42804000-42805000 ---p 42804000 00:00 0
42805000-43205000 rwxp 42805000 00:00 0
43205000-43206000 ---p 43205000 00:00 0
43206000-43c06000 rwxp 43206000 00:00 0
43c06000-43c07000 ---p 43c06000 00:00 0
43c07000-44607000 rwxp 43c07000 00:00 0
44607000-44608000 ---p 44607000 00:00 0
44608000-45008000 rwxp 44608000 00:00 0
45008000-45009000 ---p 45008000 00:00 0
45009000-45a09000 rwxp 45009000 00:00 0
2aaaaaaab000-2aaaaaaae000 r-xp 2aaaaaaab000 00:00 0                      [vdso]
2aaaaaaae000-2aaaae07c000 r-xp 00000000 fd:00 4475090                    /usr/lib/locale/locale-archive
2aaaae07c000-2aaaae083000 r-xs 00000000 fd:00 8786                       /usr/lib64/gconv/gconv-modules.cache
2aaaae083000-2aaaae085000 rwxp 2aaaae083000 00:00 0
2aaaae085000-2aaaae08b000 rwxs 00000000 fd:02 37965938                   /home/USERNAME/.bitcoin/__db.001
2aaaae08b000-2aaaae281000 rwxs 00000000 fd:02 37965939                   /home/USERNAME/.bitcoin/__db.002
2aaaae281000-2aaab01c3000 rwxs 00000000 fd:02 37965940                   /home/USERNAME/.bitcoin/__db.003
2aaab01c3000-2aaab02e3000 rwxs 00000000 fd:02 37965941                   /home/USERNAME/.bitcoin/__db.004
2aaab02e3000-2aaab08e9000 rwxs 00000000 fd:02 37965942                   /home/USERNAME/.bitcoin/__db.005
2aaab08e9000-2aaab08f5000 rwxs 00000000 fd:02 37965943                   /home/USERNAME/.bitcoin/__db.006
2aaab08fb000-2aaab0905000 r-xp 00000000 09:01 130597                     /lib64/libnss_files-2.5.so
2aaab0905000-2aaab0b04000 ---p 0000a000 09:01 130597                     /lib64/libnss_files-2.5.so
2aaab0b04000-2aaab0b05000 r-xp 00009000 09:01 130597                     /lib64/libnss_files-2.5.so
2aaab0b05000-2aaab0b06000 rwxp 0000a000 09:01 130597                     /lib64/libnss_files-2.5.so
2aaab0b06000-2aaab0c53000 r-xp 00000000 09:01 130565                     /lib64/libc-2.5.so
2aaab0c53000-2aaab0e53000 ---p 0014d000 09:01 130565                     /lib64/libc-2.5.so
2aaab0e53000-2aaab0e57000 r-xp 0014d000 09:01 130565                     /lib64/libc-2.5.so
2aaab0e57000-2aaab0e58000 rwxp 00151000 09:01 130565                     /lib64/libc-2.5.so
2aaab0e58000-2aaab0e5d000 rwxp 2aaab0e58000 00:00 0
2aaab0e5d000-2aaab0e79000 r-xp 00000000 09:01 130587                     /lib64/ld-2.5.so
2aaab0e79000-2aaab1079000 ---p 0001c000 09:01 130587                     /lib64/ld-2.5.so
2aaab1079000-2aaab107a000 r-xp 0001c000 09:01 130587                     /lib64/ld-2.5.so
2aaab107a000-2aaab107b000 rwxp 0001d000 09:01 130587                     /lib64/ld-2.5.so
2aaab107b000-2aaab117b000 rwxp 2aaab107b000 00:00 0
2aaab117b000-2aaab117f000 r-xp 00000000 09:01 130596                     /lib64/libnss_dns-2.5.so
2aaab117f000-2aaab137e000 ---p 00004000 09:01 130596                     /lib64/libnss_dns-2.5.so
2aaab137e000-2aaab137f000 r-xp 00003000 09:01 130596                     /lib64/libnss_dns-2.5.so
2aaab137f000-2aaab1380000 rwxp 00004000 09:01 130596                     /lib64/libnss_dns-2.5.so
2aaab1380000-2aaab1391000 r-xp 00000000 09:01 130606                     /lib64/libresolv-2.5.so
2aaab1391000-2aaab1591000 ---p 00011000 09:01 130606                     /lib64/libresolv-2.5.so
2aaab1591000-2aaab1592000 r-xp 00011000 09:01 130606                     /lib64/libresolv-2.5.so
2aaab1592000-2aaab1593000 rwxp 00012000 09:01 130606                     /lib64/libresolv-2.5.so
2aaab1593000-2aaab1595000 rwxp 2aaab1593000 00:00 0
2aaab2117000-2aaab272f000 rwxp 2aaab2117000 00:00 0
2aaab4000000-2aaab5e3d000 rwxp 2aaab4000000 00:00 0
2aaab5e3d000-2aaab8000000 ---p 2aaab5e3d000 00:00 0
7ffffffea000-7ffffffff000 rwxp 7ffffffe9000 00:00 0                      [stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0                  [vsyscall]

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x43c05940 (LWP 1393)]
0x000000000082ce95 in raise ()

When I use the bt command, I get this:

Code:
#0  0x000000000082ce95 in raise ()
#1  0x00000000007cfb10 in abort ()
#2  0x00000000007eaaeb in __libc_message ()
#3  0x00000000007f346b in _int_free ()
#4  0x00000000007f7516 in free ()
#5  0x000000000040f013 in erase (this=0xbab918, __first=<value optimized out>, __last=...)
    at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/ext/new_allocator.h:94
#6  std::_Rb_tree<CNetAddr, std::pair<CNetAddr const, int>, std::_Select1st<std::pair<CNetAddr const, int> >, std::less<CNetAddr>, std::allocator<std::pair<CNetAddr const, int> > >::erase (this=0xbab918, __first=<value optimized out>, __last=...)
    at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_tree.h:1281
#7  0x000000000040f2d8 in std::_Rb_tree<CNetAddr, std::pair<CNetAddr const, int>, std::_Select1st<std::pair<CNetAddr const, int> >, std::less<CNetAddr>, std::allocator<std::pair<CNetAddr const, int> > >::erase (this=0xbab918, __x=<value optimized out>)
    at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_tree.h:1215
#8  0x000000000040e0ee in erase (this=0xbab8a0, nUBucket=<value optimized out>)
    at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/stl_map.h:461
#9  CAddrMan::ShrinkNew (this=0xbab8a0, nUBucket=<value optimized out>) at addrman.cpp:181
#10 0x000000000040e3dc in CAddrMan::Add_ (this=0xbab8a0, addr=<value optimized out>, source=<value optimized out>, nTimePenalty=<value optimized out>)
    at addrman.cpp:346
#11 0x000000000046d2b4 in ProcessMessage (pfrom=0x2aaab4bb0450, strCommand=..., vRecv=...) at addrman.h:433
#12 0x0000000000470620 in ProcessMessages (pfrom=0x2aaab4bb0450) at main.cpp:2767
#13 0x000000000048e435 in ThreadMessageHandler2 (parg=<value optimized out>) at net.cpp:1516
#14 0x000000000048e645 in ThreadMessageHandler (parg=0x0) at net.cpp:1481
#15 0x0000000000751edd in start_thread ()
#16 0x0000000000810329 in clone ()

I have to leave for a few hours, but will keep the debugger open.  If there are any commands that can extract more useful information from it, please post here and I will run them on it tonight.

Edit: Added code tags (good idea).  BTW, the box is still up, for if anyone wants to see the output of another gdb command, memory dump, etc.
Red Emerald
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
April 08, 2012, 05:50:40 PM
 #80

jetmine. You should really put those giant posts inside code blocks

Code:
Like this

Pages: « 1 2 3 [4] 5 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!