Bitcoin Forum
October 19, 2021, 06:38:59 AM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3] 4 5 6 7 »  All
  Print  
Author Topic: Bitcoin Core 0.9.2.1 has been released  (Read 27395 times)
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1010



View Profile
June 21, 2014, 03:11:24 PM
Last edit: June 21, 2014, 03:39:18 PM by Meuh6879
 #41

I have a other issue/problem ... the application crash without message.
This morning, i have noticed that my mining device don't "work" (in pause mode).

I open my windows xp 32 bits machine ... and remark in DEBUG LOG (baretail display) that it have stopped (without warning in DEBUG log) at 5h A.M.



rollback to 0.9.1, sorry ... a random crash (without DEBUG log) is not possible for me.
i have opened the webtemp display to view a specific problem on RAM or CPU at this time (5h A.M.) but nothing append at this time (and all other service on this machine work like usually).



i use bitcoin-qt on this machine since november 2013.




Code:
2014-06-21 03:54:37 ProcessBlock: ACCEPTED
2014-06-21 03:55:03 CreateNewBlock(): total size 107736
2014-06-21 03:57:00 CreateNewBlock(): total size 132404
2014-06-21 03:58:58 CreateNewBlock(): total size 164441
2014-06-21 04:01:54 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:02:03 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:02:26 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:04:43 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2073, them=99.99.255.24:8333, peer=99.99.255.24:8333
2014-06-21 04:04:43 Added time data, samples 35, offset +0 (+0 minutes)
2014-06-21 04:04:43 nTimeOffset = -6  (+0 minutes)
2014-06-21 04:04:55 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:04:56 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:04:56 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:04:57 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:00 receive version message: /Satoshi:0.9.99/: version 70002, blocks=306941, us=90.26.172.230:2092, them=82.116.203.240:8333, peer=82.116.203.240:8333
2014-06-21 04:05:00 Added time data, samples 36, offset +12 (+0 minutes)
2014-06-21 04:05:01 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:01 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2099, them=82.197.197.31:8333, peer=82.197.197.31:8333
2014-06-21 04:05:01 Added time data, samples 37, offset -3 (+0 minutes)
2014-06-21 04:05:01 nTimeOffset = -6  (+0 minutes)
2014-06-21 04:05:02 CreateNewBlock(): total size 208346
2014-06-21 04:05:02 receive version message: /Satoshi:0.8.1/: version 70001, blocks=306941, us=90.26.172.230:2101, them=94.22.32.78:8333, peer=94.22.32.78:8333
2014-06-21 04:05:02 Added time data, samples 38, offset +17 (+0 minutes)
2014-06-21 04:05:03 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2102, them=208.12.95.26:8333, peer=208.12.95.26:8333
2014-06-21 04:05:03 Added time data, samples 39, offset -1 (+0 minutes)
2014-06-21 04:05:03 nTimeOffset = -6  (+0 minutes)
2014-06-21 04:05:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:05:48 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:52 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:52 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:52 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:05:54 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2125, them=85.229.149.25:8333, peer=85.229.149.25:8333
2014-06-21 04:05:54 Added time data, samples 40, offset -5 (+0 minutes)
2014-06-21 04:06:00 socket recv error Une connexion existante a dû être fermée par l'hôte distant.  (10054)
2014-06-21 04:06:17 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2132, them=203.173.198.201:8333, peer=203.173.198.201:8333
2014-06-21 04:06:17 Added time data, samples 41, offset -7 (+0 minutes)
2014-06-21 04:06:17 nTimeOffset = -6  (+0 minutes)
2014-06-21 04:06:17 receive version message: /Satoshi:0.9.1/: version 70002, blocks=306941, us=90.26.172.230:2133, them=83.249.70.190:8333, peer=83.249.70.190:8333
2014-06-21 04:06:17 Added time data, samples 42, offset -6 (+0 minutes)
2014-06-21 04:07:02 CreateNewBlock(): total size 247221
2014-06-21 04:09:02 CreateNewBlock(): total size 360540
2014-06-21 04:11:01 CreateNewBlock(): total size 432115
2014-06-21 04:11:02 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:12:59 CreateNewBlock(): total size 457872
2014-06-21 04:14:56 CreateNewBlock(): total size 485485
2014-06-21 04:15:05 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:16:53 CreateNewBlock(): total size 536924
2014-06-21 04:18:19 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:18:51 CreateNewBlock(): total size 609177
2014-06-21 04:19:24 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:20:48 CreateNewBlock(): total size 631525
2014-06-21 04:22:44 CreateNewBlock(): total size 648390
2014-06-21 04:24:40 CreateNewBlock(): total size 660919
2014-06-21 04:26:36 CreateNewBlock(): total size 677023
2014-06-21 04:28:32 CreateNewBlock(): total size 693739
2014-06-21 04:30:28 CreateNewBlock(): total size 718895
2014-06-21 04:32:25 CreateNewBlock(): total size 731157
2014-06-21 04:34:20 CreateNewBlock(): total size 749534
2014-06-21 04:36:15 CreateNewBlock(): total size 748553
2014-06-21 04:38:10 CreateNewBlock(): total size 743536
2014-06-21 04:39:56 UpdateTip: new best=00000000000000001d04fcaf5f53ad36075fd2cb2eae5740729ec239a0e3bcf2  height=306942  log2_work=79.289893  tx=41104386  date=2014-06-21 04:39:38 progress=0.999999
2014-06-21 04:39:56 ProcessBlock: ACCEPTED
2014-06-21 04:40:06 CreateNewBlock(): total size 593925
2014-06-21 04:42:00 CreateNewBlock(): total size 625596
2014-06-21 04:43:56 CreateNewBlock(): total size 671496
2014-06-21 04:45:51 CreateNewBlock(): total size 688831
2014-06-21 04:47:46 CreateNewBlock(): total size 703732
2014-06-21 04:48:25 ERROR: CheckTransaction() : vin empty
2014-06-21 04:48:25 ERROR: AcceptToMemoryPool: : CheckTransaction failed
2014-06-21 04:48:25 Misbehaving: 94.22.32.78:8333 (0 -> 10)
2014-06-21 04:49:41 CreateNewBlock(): total size 744545
2014-06-21 04:51:36 CreateNewBlock(): total size 738235
2014-06-21 04:53:32 CreateNewBlock(): total size 746756
2014-06-21 04:54:04 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-06-21 04:55:27 CreateNewBlock(): total size 749744
2014-06-21 04:56:38 UpdateTip: new best=00000000000000003b233da34621205e50b15a4016ba441418bb73c7c9eb621e  height=306943  log2_work=79.290006  tx=41104991  date=2014-06-21 04:56:04 progress=0.999999
2014-06-21 04:56:38 ProcessBlock: ACCEPTED
2014-06-21 04:57:23 CreateNewBlock(): total size 483143
2014-06-21 04:59:17 CreateNewBlock(): total size 527702
2014-06-21 05:01:13 CreateNewBlock(): total size 569336
2014-06-21 05:01:39 Pre-allocating up to position 0xb00000 in rev00150.dat
2014-06-21 05:01:40 UpdateTip: new best=00000000000000002a42661e62f6d8f809b428671fd3a99340e52e3b276c9d64  height=306944  log2_work=79.290119  tx=41105276  date=2014-06-21 05:00:18 progress=0.999997
2014-06-21 05:01:40 ProcessBlock: ACCEPTED
2014-06-21 05:03:10 CreateNewBlock(): total size 107447
2014-06-21 05:03:24 UpdateTip: new best=00000000000000002878c62b23c8e2dfa3c8061a528a455a06800603d4aa1a31  height=306945  log2_work=79.290232  tx=41105387  date=2014-06-21 05:02:55 progress=0.999999
2014-06-21 05:03:24 ProcessBlock: ACCEPTED
2014-06-21 05:05:06 CreateNewBlock(): total size 85737
2014-06-21 05:07:03 CreateNewBlock(): total size 116525
2014-06-21 05:09:00 CreateNewBlock(): total size 149270
2014-06-21 05:10:35 UpdateTip: new best=000000000000000033168b88d90ae5715c8dd4df44d73bc2f20e30ff7d3ce165  height=306946  log2_work=79.290345  tx=41105648  date=2014-06-21 05:10:00 progress=0.999999
2014-06-21 05:10:35 ProcessBlock: ACCEPTED
2014-06-21 05:10:59 CreateNewBlock(): total size 24875
2014-06-21 05:12:57 CreateNewBlock(): total size 62709
Requesting initialize
Running AppInit2 in thread
2014-06-21 15:00:44



















2014-06-21 15:00:44 Bitcoin version v0.9.2.1-g354c0f3-beta (Thu, 19 Jun 2014 09:51:15 +0200)
2014-06-21 15:00:44 Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
2014-06-21 15:00:44 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2014-06-21 15:00:44 Default data directory C:\Documents and Settings\PC\Application Data\Bitcoin
2014-06-21 15:00:44 Using data directory G:\block-bitcoin
2014-06-21 15:00:44 Using at most 12 connections (2048 file descriptors available)
2014-06-21 15:00:44 Using 2 threads for script verification
2014-06-21 15:00:45 Error: Couldn't open socket for incoming connections (socket returned error Une adresse incompatible avec le protocole demandé a été utilisée.  (10047))
2014-06-21 15:00:45 Bound to 0.0.0.0:8333
2014-06-21 15:00:45 init message: Chargement de l’index des blocs…
2014-06-21 15:00:45 Opening LevelDB in G:\block-bitcoin\blocks\index
2014-06-21 15:00:45 Opened LevelDB successfully
2014-06-21 15:00:45 Opening LevelDB in G:\block-bitcoin\chainstate
2014-06-21 15:00:46 Opened LevelDB successfully
2014-06-21 15:00:52 LoadBlockIndexDB(): last block file = 150
2014-06-21 15:00:52 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=396, size=81503416, heights=306551...306946, time=2014-06-18...2014-06-21)
2014-06-21 15:00:52 LoadBlockIndexDB(): transaction index disabled
2014-06-21 15:00:52 LoadBlockIndexDB(): hashBestChain=000000000000000033168b88d90ae5715c8dd4df44d73bc2f20e30ff7d3ce165 height=306946 date=2014-06-21 05:10:00 progress=0.998525
2014-06-21 15:00:52 init message: Vérification des blocs en cours...
2014-06-21 15:00:52 Verifying last 288 blocks at level 3
2014-06-21 15:04:09 No coin database inconsistencies in last 64 blocks (19029 transactions)
2014-06-21 15:04:09  block index          204156ms
2014-06-21 15:04:09 Wallet disabled!

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

Posts: 1634625539

View Profile Personal Message (Offline)

Ignore
1634625539
Reply with quote  #2

1634625539
Report to moderator
1634625539
Hero Member
*
Offline Offline

Posts: 1634625539

View Profile Personal Message (Offline)

Ignore
1634625539
Reply with quote  #2

1634625539
Report to moderator
1634625539
Hero Member
*
Offline Offline

Posts: 1634625539

View Profile Personal Message (Offline)

Ignore
1634625539
Reply with quote  #2

1634625539
Report to moderator
green65
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
June 21, 2014, 04:20:37 PM
 #42

Can you update the Ubuntu PPA? as its still on 0.9.1.

https://launchpad.net/~bitcoin/+archive/bitcoin
Lauda
Legendary
*
Offline Offline

Activity: 2674
Merit: 2885


Terminated.


View Profile WWW
June 23, 2014, 06:23:51 PM
 #43

Upgrading to this release is recommended.

Is there a classification of importance/urgency levels about upgrading to new releases?
Or is it just a matter between recommended and mandatory?

Ty in advance.

I'm wondering that as well. If it's not that urgent I don't want to upgrade.

"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
😼 Bitcoin Core (onion)
sarmadkhalid45
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile WWW
June 23, 2014, 06:50:27 PM
 #44

Really The Good news.....
haploid23
Legendary
*
Offline Offline

Activity: 812
Merit: 1002



View Profile WWW
June 24, 2014, 01:56:53 AM
 #45

I'm wondering if this is an urgent upgrade as well. I'm currently using 0.8.6 and it works fine. Any real need to upgrade to this recent version? I'd really like to just have a core client that is a set-and-forget software rather than one that needs constant updating every few weeks. Currently using MS Windows if that matters at all.

wedgy2k
Sr. Member
****
Offline Offline

Activity: 329
Merit: 251



View Profile
June 24, 2014, 06:44:19 AM
 #46

Hi, I may roll back from 0.9.2.1

I find that app becomes unresponsive on OSX 10.9.3 and requires restarting (despite the notification centre alerts - alerting fine despite the app being in a hung state)
The previous version, I was able to leave it on for days with no issue.




Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1010



View Profile
June 24, 2014, 03:06:16 PM
 #47

I'm wondering if this is an urgent upgrade as well. I'm currently using 0.8.6 and it works fine.

0.9.1 work fine, too ... no crashs, no freezes and potential more filters for dust/ip ban and other network pollution.
0.9.2.1 crash randomly without notice message.
sed
Hero Member
*****
Offline Offline

Activity: 532
Merit: 500


View Profile
June 24, 2014, 08:11:30 PM
 #48

The backwards compatibility with older linux distros looks great.  However, if this is the upgrade that contains the fix for the openssl dependencies, then shouldn't this be a *major* bugfix release?  Or maybe there's some other problem with openssl you were referring to.
joeblack
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
June 25, 2014, 12:47:15 AM
 #49

Im getting the following error on Centos 6.5 X86_64 fully updated, any ideas ?

$ bitcoin-qt
bitcoin-qt: symbol lookup error: bitcoin-qt: undefined symbol: _ZN10QTextCodec11validCodecsEv
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
June 25, 2014, 02:00:08 AM
 #50

The backwards compatibility with older linux distros looks great.  However, if this is the upgrade that contains the fix for the openssl dependencies, then shouldn't this be a *major* bugfix release?  Or maybe there's some other problem with openssl you were referring to.

openssl was fixed earlier: https://bitcointalk.org/index.php?topic=562409.0


For those wondering whether to upgrade from x.x.x, have a look here and see if it concerns you. https://bitcoin.org/en/version-history

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
June 27, 2014, 08:12:24 PM
 #51


I don't think this will help a lot, esp. since I don't see anything special in the logs, but here goes anyway...

Windows XP: Within Armory bitcoind 9.2.1 crashes, whereas 0.9.1 runs fine.


OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
cech4204a
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250

12CDKyxPyL5Rj28ed2yz5czJf3Dr2ZvEYw


View Profile WWW
June 27, 2014, 08:14:42 PM
 #52

Since i use MultiBit wallet i don't need that shity Bitcoin Core on my PC with 21 GB of data. Thanks to the guy that made MultiBit. And to be honest i don't trust it since the last problem i had in that software (couldn't recover my wallet backup on it, balance was allways 0, while blockchain showed that addys in that wallet still have money on them).

Bitcoin is DEAD
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1010



View Profile
June 27, 2014, 09:11:59 PM
 #53

thanks to not post on a wrong thread... with an "alternate" software that it don't help the bitcoin network.
multibit work because you have bitcoin-core nodes available to connect on it...
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


https://web.archive.org/web/*/nogleg.com


View Profile WWW
June 28, 2014, 12:14:07 PM
 #54

What does the 'score' in getnetworkinfo signify? ... or better, is there some sort of measure to quantify what you see as a 'score'?
sed
Hero Member
*****
Offline Offline

Activity: 532
Merit: 500


View Profile
June 28, 2014, 07:56:51 PM
 #55

Since i use MultiBit wallet i don't need that shity Bitcoin Core on my PC with 21 GB of data. Thanks to the guy that made MultiBit. And to be honest i don't trust it since the last problem i had in that software (couldn't recover my wallet backup on it, balance was allways 0, while blockchain showed that addys in that wallet still have money on them).

I switched to multibit as well because of the fact that my little computer couldn't really keep up with downloading the whole blockchain.  However, now there's a thread saying that multibit has a lot of issues with losing coins.  I've never had it happen to me but I'm a bit worried by it.

Finally, what about my question about openssl?
fa
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
July 02, 2014, 06:02:18 AM
 #56

Good news. Updating app...
Seldar
Sr. Member
****
Offline Offline

Activity: 334
Merit: 250


View Profile
July 02, 2014, 07:48:08 PM
 #57

Since i use MultiBit wallet i don't need that shity Bitcoin Core on my PC with 21 GB of data. Thanks to the guy that made MultiBit. And to be honest i don't trust it since the last problem i had in that software (couldn't recover my wallet backup on it, balance was allways 0, while blockchain showed that addys in that wallet still have money on them).

Bitcoin Core is perhaps a shity thing, but how could you do bitcoin transactions without nodes... and nodes are Bitcoin Core...
Could you think more thoroughly before saying that Bitcoin Core is shit?

Sorry for my bad english Smiley
Meuh6879
Legendary
*
Offline Offline

Activity: 1512
Merit: 1010



View Profile
July 03, 2014, 05:44:34 PM
 #58

I have a other issue/problem ... the application crash without message.
This morning, i have noticed that my mining device don't "work" (in pause mode).

I open my windows xp 32 bits machine ... and remark in DEBUG LOG (baretail display) that it have stopped (without warning in DEBUG log) at 5h A.M.

i have re-try an other time ... and now, after 48h, no crash.
perhaps the increase of deployed 0.9.2.1 ?  ( https://getaddr.bitnodes.io/dashboard/ )
khuram8494
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
July 05, 2014, 02:05:41 PM
 #59

oh good news thanks Smiley
happyflylong
Sr. Member
****
Offline Offline

Activity: 288
Merit: 250


View Profile
July 06, 2014, 01:25:28 AM
 #60

Finding so many people work hard on bitcoin core,  I feel more confidence with Bitcoin.

I am very glad to see this!
Thank you,  all these core developers!
Bitcoin will go to success!
Pages: « 1 2 [3] 4 5 6 7 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!