Bitcoin Forum
February 04, 2023, 10:14:35 PM *
News: Latest Bitcoin Core release: 24.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 »  All
  Print  
Author Topic: Version 0.7.0 release candidate 3 ready for testing  (Read 9711 times)
Gavin Andresen (OP)
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2053


Chief Scientist


View Profile WWW
September 06, 2012, 07:59:48 PM
Last edit: September 13, 2012, 06:39:01 PM by Gavin Andresen
 #1

Bitcoin version 0.7.0 release candidate 3 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/test/

Unless another critical bug is found, this should be the final 0.7.0 release.

How to Upgrade
--------------

If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you were running on Linux with a version that might have been compiled
with a different version of Berkeley DB (for example, if you were using an
Ubuntu PPA version), then run the old version again with the -detachdb
argument and shut it down; if you do not, then the new version will not
be able to read the database files and will exit with an error.

Incompatible Changes
--------------------
* Replaced the 'getmemorypool' RPC command with 'getblocktemplate/submitblock'
  and 'getrawmempool' commands.
* Remove deprecated RPC 'getblocknumber'

Bitcoin Improvement Proposals implemented
-----------------------------------------
BIP 22 - 'getblocktemplate', 'submitblock' RPCs
BIP 34 - block version 2, height in coinbase
BIP 35 - 'mempool' message, extended 'getdata' message behavior


Core bitcoin handling and blockchain database
---------------------------------------------
* Reduced CPU usage, by eliminating some redundant hash calculations
* Cache signature verifications, to eliminate redundant signature checks
* Transactions with zero-value outputs are considered non-standard
* Mining: when creating new blocks, sort 'paid' area by fee-per-kb
* Database: better validation of on-disk stored data
* Database: minor optimizations and reliability improvements
* -loadblock=FILE will import an external block file
* Additional DoS (denial-of-service) prevention measures
* New blockchain checkpoint at block 193,000


JSON-RPC API
------------
* Internal HTTP server is now thread-per-connection, rather than
  a single-threaded queue that would stall on network I/O.
* Internal HTTP server supports HTTP/1.1, pipelined requests and
  connection keep-alive.
* Support JSON-RPC 2.0 batches, to encapsulate multiple JSON-RPC requests
  within a single HTTP request.
* IPv6 support
* Added raw transaction API.  See https://gist.github.com/2839617
* Added 'getrawmempool', to list contents of TX memory pool
* Added 'getpeerinfo', to list data about each connected network peer
* Added 'listaddressgroupings' for better coin control
* Rework gettransaction, getblock calls. 'gettransaction' responds for
  non-wallet TXs now.
* Remove deprecated RPC 'getblocknumber'
* Remove superceded RPC 'getmemorypool' (see BIP 22, above)
* listtransactions output now displays "smart" times for transactions,
  and 'blocktime' and 'timereceived' fields were added


P2P networking
--------------
* IPv6 support
* Tor hidden service support (see doc/Tor.txt)
* Attempts to fix "stuck blockchain download" problems
* Replace BDB database "addr.dat" with internally-managed "peers.dat"
  file containing peer address data.
* Lower default send buffer from 10MB to 1MB
* proxy: SOCKS5 by default
* Support connecting by hostnames passed to proxy
* Add -seednode connections, and use this instead of DNS seeds when proxied
* Added -externalip and -discover
* Add -onlynet to connect only to a given network (IPv4, IPv6, or Tor)
* Separate listening sockets, -bind=<addr>


Qt GUI
------
* Add UI RPC console / debug window
* Re-Enable URI handling on Windows, add safety checks and tray-notifications
* Harmonize the use of ellipsis ("...") to be used in menus, but not on buttons
* Add 2 labels to the overviewpage that display Wallet and Transaction status (obsolete or current)
* Extend the optionsdialog (e.g. language selection) and re-work it to a tabbed UI
* Merge sign/verify message into a single window with tabbed UI
* Ensure a changed bitcoin unit immediately updates all GUI elements that use units
* Update QR Code dialog
* Improve error reporting at startup
* Fine-grained UI updates for a much smoother UI during block downloads
* Remove autocorrection of 0/i in addresses in UI
* Reorganize tray icon menu into more logical order
* Persistently poll for balance change when number of blocks changed
* Much better translations
* Override progress bar design on platforms with segmented progress bars to assist with readability
* Added 'immature balance' display on the overview page
* (Windows only): enable ASLR and DEP for bitcoin-qt.exe
* (Windows only): add meta-data to bitcoin-qt.exe (e.g. description)

Internal codebase
-----------------
* Additional unit tests
* Compile warning fixes


Miscellaneous
-------------
* Reopen debug.log upon SIGHUP
* Bash programmable completion for bitcoind(1)
* On supported OS's, each thread is given a useful name

How often do you get the chance to work on a potentially world-changing project?
1675548875
Hero Member
*
Offline Offline

Posts: 1675548875

View Profile Personal Message (Offline)

Ignore
1675548875
Reply with quote  #2

1675548875
Report to moderator
The trust scores you see are subjective; they will change depending on who you have in your trust list.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1675548875
Hero Member
*
Offline Offline

Posts: 1675548875

View Profile Personal Message (Offline)

Ignore
1675548875
Reply with quote  #2

1675548875
Report to moderator
1675548875
Hero Member
*
Offline Offline

Posts: 1675548875

View Profile Personal Message (Offline)

Ignore
1675548875
Reply with quote  #2

1675548875
Report to moderator
1675548875
Hero Member
*
Offline Offline

Posts: 1675548875

View Profile Personal Message (Offline)

Ignore
1675548875
Reply with quote  #2

1675548875
Report to moderator
keystroke
Hero Member
*****
Offline Offline

Activity: 899
Merit: 1007


advocate of a cryptographic attack on the globe


View Profile
September 06, 2012, 09:19:27 PM
 #2

Very nice Gavin! What are the changes between rc1 and rc2?

"The difference between a castle and a prison is only a question of who holds the keys."
jgarzik
Legendary
*
qt
Offline Offline

Activity: 1596
Merit: 1059


View Profile
September 06, 2012, 09:35:31 PM
 #3

Very nice Gavin! What are the changes between rc1 and rc2?

Lots of minor bug fixes.

Git users may view the shortlog with

Code:
$ git shortlog --no-merges v0.7.0rc1..

Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Meni Rosenfeld
Donator
Legendary
*
expert
Offline Offline

Activity: 2058
Merit: 1029



View Profile WWW
September 06, 2012, 09:46:46 PM
 #4

Is it possible to update the translations?

1EofoZNBhWQ3kxfKnvWkhtMns4AivZArhr   |   Who am I?   |   bitcoin-otc WoT
Bitcoil - Exchange bitcoins for ILS (thread)   |   Israel Bitcoin community homepage (thread)
Analysis of Bitcoin Pooled Mining Reward Systems (thread, summary)  |   PureMining - Infinite-term, deterministic mining bond
slothbag
Sr. Member
****
Offline Offline

Activity: 369
Merit: 250



View Profile
September 07, 2012, 10:12:57 AM
 #5

0.7rc1 was running perfectly fine on Windows 7 for the past couple weeks.  Just installed rc2 and it freezes on the splash screen where it says loading block index.

Eventually I get a windows popup asking to kill the process.

Something not right there.

Edit: Eventually it does open. But it never used to say "Program is not responding" during the startup phase before.
Diapolo
Hero Member
*****
Offline Offline

Activity: 769
Merit: 500



View Profile WWW
September 07, 2012, 09:45:35 PM
 #6

Is it possible to update the translations?

That should be done for the final version once more, yes!

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
Gavin Andresen (OP)
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2053


Chief Scientist


View Profile WWW
September 07, 2012, 09:52:12 PM
 #7

0.7rc1 was running perfectly fine on Windows 7 for the past couple weeks.  Just installed rc2 and it freezes on the splash screen where it says loading block index.
....
Edit: Eventually it does open. But it never used to say "Program is not responding" during the startup phase before.
Anybody else having success or failure running rc2 on Windows 7, please let us know...

How often do you get the chance to work on a potentially world-changing project?
keystroke
Hero Member
*****
Offline Offline

Activity: 899
Merit: 1007


advocate of a cryptographic attack on the globe


View Profile
September 08, 2012, 12:02:58 AM
 #8

rc2 is starts fine and downloads the blockchain on Windows 8 aside from the issues with Qt which I mentioned previously. Is there a test plan which should be executed to help testing? Nice work everyone!

"The difference between a castle and a prison is only a question of who holds the keys."
slothbag
Sr. Member
****
Offline Offline

Activity: 369
Merit: 250



View Profile
September 08, 2012, 06:41:42 AM
 #9

I just checked v0.6.3 it appears to behave in the same manor.

If you click on the splash screen while it says "loading block index", the splash screen goes a shade of white and you get the popup saying "application is not responding".

Eventually the application loads.

wumpus
Hero Member
*****
qt
Offline Offline

Activity: 812
Merit: 1019

No Maps for These Territories


View Profile
September 08, 2012, 07:11:05 AM
 #10

If you click on the splash screen while it says "loading block index", the splash screen goes a shade of white and you get the popup saying "application is not responding".
This is nothing new. The initialisation happens in the UI thread, which thus is unable to respond to window system messages for some time between phases, and thus the window system may think it's helpful by showing that message (and/or greying the UI). Changing this is on the (long) TODO list.

Bitcoin Core developer [PGP] Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through FileBackup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.
flatfly
Legendary
*
Offline Offline

Activity: 1022
Merit: 1007


View Profile
September 08, 2012, 07:44:54 AM
Last edit: September 08, 2012, 08:19:34 AM by flatfly
 #11

Hey, I'm getting this error twice while starting bitcoind (0.7.0rc2 beta) on Windows XP. It then exits.

Code:
Error: An error occurred while setting up the RPC port 8332 for listening: open: An address incompatible with the requested protocol was used

(0.6.3 on the other hand, is running fine on this system)


EDIT:

 1. Just to confirm that I made sure that 0.6.3 was NOT running at the same time

 2. Tried to reboot, doesn't help

 3. I'm actually getting another socket-related error first. Log follows.

 4. Tried disabling the firewall, doesn't help

Code:
Bitcoin version v0.7.0rc2-beta (2012-09-05 12:38:37 -0400)
Using OpenSSL version OpenSSL 1.0.1b 26 Apr 2012
Startup time: 09/08/12 08:08:52
Default data directory C:\Documents and Settings\xxx\Application Data\Bitcoin
Used data directory C:\Documents and Settings\xxx\Application Data\Bitcoin
Error: Couldn't open socket for incoming connections (socket returned error 1004
7)
Bound to 0.0.0.0:8333
Loading block index...
dbenv.open LogDir=C:\Documents and Settings\xxx\Application Data\Bitcoin\databa
se ErrorFile=C:\Documents and Settings\xxx\Application Data\Bitcoin\db.log
LoadBlockIndex(): hashBestChain=000000000019d6689c08  height=0  date=01/03/09 18
:15:05
Verifying last 0 blocks at level 1
 block index             172ms
Loading wallet...
nFileVersion = 70002
 wallet                 1328ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
RandAddSeed() 121624 bytes
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
Error: An error occurred while setting up the RPC port 8332 for listening: open:
 An address incompatible with the requested protocol was used
Error: An error occurred while setting up the RPC port 8332 for listening: open:
 An address incompatible with the requested protocol was used
send version message: version 60002, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, pee
r=127.0.0.1:0
ThreadRPCServer exited
Flush(false)
blkindex.dat refcount=0
DNS seeding disabled
ThreadIRCSeed exited
ThreadOpenAddedConnections started
ThreadMessageHandler started
ThreadOpenAddedConnections exited
ThreadSocketHandler started
ThreadOpenConnections started
ThreadMessageHandler exited
ThreadDumpAddress exited
ThreadSocketHandler exited
GetMyExternalIP() received [85.28.98.143] 85.28.98.143:0
GetMyExternalIP() returned 85.28.98.143
AddLocal(85.28.98.143:8333,5)
blkindex.dat checkpoint
blkindex.dat closed
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended             468ms
StopNode()
ThreadOpenConnections exited
Flushed 0 addresses to peers.dat  109ms
Flush(true)
DBFlush(true) ended               0ms
Bitcoin exited

My main BTC/XCP address is 1111127SpvabYpoeDoiz5L7QPkfiSh2Q.
Severian
Sr. Member
****
Offline Offline

Activity: 476
Merit: 250



View Profile
September 08, 2012, 08:07:56 AM
 #12

Running like a champ on OS X Lion, though it appears to have a slightly larger footprint than 0.7.0 rc1 did.
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


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


View Profile WWW
September 08, 2012, 11:30:59 AM
 #13

Hey, I'm getting this error twice while starting bitcoind (0.7.0rc2 beta) on Windows XP. It then exits.

Code:
Error: An error occurred while setting up the RPC port 8332 for listening: open: An address incompatible with the requested protocol was used

(0.6.3 on the other hand, is running fine on this system)


EDIT:

 1. Just to confirm that I made sure that 0.6.3 was NOT running at the same time

 2. Tried to reboot, doesn't help

 3. I'm actually getting another socket-related error first. Log follows.

 4. Tried disabling the firewall, doesn't help

Code:
Bitcoin version v0.7.0rc2-beta (2012-09-05 12:38:37 -0400)
Using OpenSSL version OpenSSL 1.0.1b 26 Apr 2012
Startup time: 09/08/12 08:08:52
Default data directory C:\Documents and Settings\xxx\Application Data\Bitcoin
Used data directory C:\Documents and Settings\xxx\Application Data\Bitcoin
Error: Couldn't open socket for incoming connections (socket returned error 1004
7)
Bound to 0.0.0.0:8333
Loading block index...
dbenv.open LogDir=C:\Documents and Settings\xxx\Application Data\Bitcoin\databa
se ErrorFile=C:\Documents and Settings\xxx\Application Data\Bitcoin\db.log
LoadBlockIndex(): hashBestChain=000000000019d6689c08  height=0  date=01/03/09 18
:15:05
Verifying last 0 blocks at level 1
 block index             172ms
Loading wallet...
nFileVersion = 70002
 wallet                 1328ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
RandAddSeed() 121624 bytes
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
Error: An error occurred while setting up the RPC port 8332 for listening: open:
 An address incompatible with the requested protocol was used
Error: An error occurred while setting up the RPC port 8332 for listening: open:
 An address incompatible with the requested protocol was used
send version message: version 60002, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, pee
r=127.0.0.1:0
ThreadRPCServer exited
Flush(false)
blkindex.dat refcount=0
DNS seeding disabled
ThreadIRCSeed exited
ThreadOpenAddedConnections started
ThreadMessageHandler started
ThreadOpenAddedConnections exited
ThreadSocketHandler started
ThreadOpenConnections started
ThreadMessageHandler exited
ThreadDumpAddress exited
ThreadSocketHandler exited
GetMyExternalIP() received [85.28.98.143] 85.28.98.143:0
GetMyExternalIP() returned 85.28.98.143
AddLocal(85.28.98.143:8333,5)
blkindex.dat checkpoint
blkindex.dat closed
wallet.dat refcount=0
wallet.dat checkpoint
wallet.dat detach
wallet.dat closed
DBFlush(false) ended             468ms
StopNode()
ThreadOpenConnections exited
Flushed 0 addresses to peers.dat  109ms
Flush(true)
DBFlush(true) ended               0ms
Bitcoin exited

I have this problem on one of my ubuntu machines.  To get it to work, it requires editing out some mention of ipv6 in the the bitcoinrpc.cpp file.  

though I believe for me (on ubuntu) I've had to do this on every release from 0.6.3 on up  

see:

Quote
Post by: pooler on July 27, 2012, 01:35:40 PM

As I've already said, I got the same error with the latest bitcoind, and to make it work I had to disable IPv6 and patch bitcoinrpc.cpp.
Commenting out lines 2664 (https://github.com/bitcoin/bitcoin/blob/c1aed4eff468d8152231b7a857c2edd4e10eca80/src/bitcoinrpc.cpp#L2664) to 2681 (https://github.com/bitcoin/bitcoin/blob/c1aed4eff468d8152231b7a857c2edd4e10eca80/src/bitcoinrpc.cpp#L2681) (inclusive) is a quick and (very) dirty fix.

not sure if those lines still match up in 0.7.0 or not, but i know what to edit out by now.

using onlynet and/or disabling ipv6 during compile results in the same error.
Diapolo
Hero Member
*****
Offline Offline

Activity: 769
Merit: 500



View Profile WWW
September 09, 2012, 09:08:50 AM
 #14

@zvs What Operating system causes this? Have you enabled IPv6 in the Windows network settings? Sorry, I saw you are Using Ubuntu and I'm of no big help there ^^.

@Gavin Andresen It would have been very cool, if Lukes translation stuff and my Windows version info patch would be in 0.7 final, but I guess it's too late for that now?

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


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


View Profile WWW
September 09, 2012, 09:32:10 AM
 #15

@zvs What Operating system causes this? Have you enabled IPv6 in the Windows network settings? Sorry, I saw you are Using Ubuntu and I'm of no big help there ^^.

@Gavin Andresen It would have been very cool, if Lukes translation stuff and my Windows version info patch would be in 0.7 final, but I guess it's too late for that now?

Dia
I specifically disabled ipv6 on that machine.... it's not worth the resources on one of the kimsufi atom's (esp. when you get unlucky and get a 1.4 atom)

though, it seems a bit odd that some ipv6 functions cause it to not work, when you disable it
Diapolo
Hero Member
*****
Offline Offline

Activity: 769
Merit: 500



View Profile WWW
September 09, 2012, 09:34:43 AM
 #16

@zvs What Operating system causes this? Have you enabled IPv6 in the Windows network settings? Sorry, I saw you are Using Ubuntu and I'm of no big help there ^^.

@Gavin Andresen It would have been very cool, if Lukes translation stuff and my Windows version info patch would be in 0.7 final, but I guess it's too late for that now?

Dia
I specifically disabled ipv6 on that machine.... it's not worth the resources on one of the kimsufi atom's (esp. when you get unlucky and get a 1.4 atom)

though, it seems a bit odd that some ipv6 functions cause it to not work, when you disable it

I'll try and see what happens, when I tell my NIC to not bind to IPv6 on Win7 and will report back later today.
Of course a disabled IPv6 OS part should not cause IPv6 problems with the client!

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
keystroke
Hero Member
*****
Offline Offline

Activity: 899
Merit: 1007


advocate of a cryptographic attack on the globe


View Profile
September 09, 2012, 03:29:04 PM
 #17

Will the old addr.dat always hang around now that peers.dat has replaced it? I notice peers.dat is much smaller, is this because it is a more efficient internally managed method? Nice work again everyone, if there is any type of formal test plan I am happy to help run it.

PS. I also notice the .lock file is never deleted. Is this normal? Mine was from last year so after closing the client I deleted it and restarted it but it was created again. Normally a lock file exists only when the DB is open, right? I do detach my databases on shutdown.

"The difference between a castle and a prison is only a question of who holds the keys."
jgarzik
Legendary
*
qt
Offline Offline

Activity: 1596
Merit: 1059


View Profile
September 09, 2012, 05:57:37 PM
 #18

Will the old addr.dat always hang around now that peers.dat has replaced it? I notice peers.dat is much smaller, is this because it is a more efficient internally managed method? Nice work again everyone, if there is any type of formal test plan I am happy to help run it.

The old addr.dat is never deleted.  You may wish to swap back to an older version in an emergency.

New users will never see addr.dat, once 0.7 is released.


Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Diapolo
Hero Member
*****
Offline Offline

Activity: 769
Merit: 500



View Profile WWW
September 09, 2012, 06:52:35 PM
 #19

I was not able to produce IPv6 related error messages by just disabling OS IPv6 binding. Can the ones who have problems with that give more details about used OS and their used command-line switches please.

Dia

Liked my former work for Bitcoin Core? Drop me a donation via:
1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x
bitcoin:1PwnvixzVAKnAqp8LCV8iuv7ohzX2pbn5x?label=Diapolo
zvs
Legendary
*
Offline Offline

Activity: 1680
Merit: 1000


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


View Profile WWW
September 10, 2012, 12:05:35 AM
 #20

I was not able to produce IPv6 related error messages by just disabling OS IPv6 binding. Can the ones who have problems with that give more details about used OS and their used command-line switches please.

Dia
well, the documentation seems to suggest that you must enable ipv6 by including USE_IPV6=1, but the build file has USE_IPV6:=1 as default.   i tried changing that to USE_IPV6=- and USE_IPV6=0, still results in same error

that being:

09/09/12 23:28:43 ThreadMessageHandler started
09/09/12 23:28:43 ThreadOpenConnections started
09/09/12 23:28:43 trying connection xxxx lastseen=0.0hrs
09/09/12 23:28:43 ThreadOpenAddedConnections started
09/09/12 23:28:43 ThreadOpenAddedConnections exited
09/09/12 23:28:43 ThreadSocketHandler started
09/09/12 23:28:43 ThreadIRCSeed exited
09/09/12 23:28:43 Error: An error occurred while setting up the RPC port 8332 for listening: Address family not supported by protocol
09/09/12 23:28:43 ThreadRPCServer exited
09/09/12 23:28:43 Flush(false)
09/09/12 23:28:43 blkindex.dat refcount=0
09/09/12 23:28:43 blkindex.dat checkpoint
09/09/12 23:28:43 connected xxxx
09/09/12 23:28:43 send version message: version 60002, blocks=183152, us=0.0.0.0:0, them=xxxx:8333, peer=xxxx:8333
09/09/12 23:28:43 ThreadSocketHandler exited
09/09/12 23:28:43 ThreadMessageHandler exited

to make it work, one must comment out or remove the following in bitcoinrpc.cpp:

        acceptor->open(endpoint.protocol());
        acceptor->set_option(boost::asio::ip::tcp::acceptor::reuse_address(true));

        // Try making the socket dual IPv6/IPv4 (if listening on the "any" address)
        boost::system::error_code v6_only_error;
        acceptor->set_option(boost::asio::ip::v6_only(loopback), v6_only_error);

        acceptor->bind(endpoint);
        acceptor->listen(socket_base::max_connections);

        RPCListen(acceptor, context, fUseSSL);
        // Cancel outstanding listen-requests for this acceptor when shutting down
        StopRequests.connect(signals2::slot<void ()>(
                    static_cast<void (ip::tcp::acceptor::*)()>(&ip::tcp::acceptor::close), acceptor.get())
                .track(acceptor));

        // If dual IPv6/IPv4 failed (or we're opening loopback interfaces only), open IPv4 separately
        if (loopback || v6_only_error)
     

then it does:

09/10/12 00:00:22 ThreadMessageHandler started
09/10/12 00:00:22 ThreadOpenConnections started
09/10/12 00:00:22 trying connection xxxx lastseen=0.0hrs
09/10/12 00:00:22 ThreadOpenAddedConnections started
09/10/12 00:00:22 ThreadOpenAddedConnections exited
09/10/12 00:00:22 ThreadSocketHandler started
09/10/12 00:00:22 ThreadIRCSeed exited
09/10/12 00:00:22 connected xxxx
09/10/12 00:00:22 send version message: version 60002, blocks=183152, us=0.0.0.0:0, them=xxxx:8333, peer=xxxx:8333
09/10/12 00:00:22 Added time data, samples 2, offset -1 (+0 minutes)
09/10/12 00:00:22 Flushed 0 addresses to peers.dat  57ms
09/10/12 00:00:22 receive version message: version 60002, blocks=198073, us=xxxx:44586, them=xxxx:8333, peer=xxxx:8333
09/10/12 00:00:23 received block 0000000000000045a7f8 from xxxx:8333
09/10/12 00:00:23 SetBestChain: new best=0000000000000045a7f8  height=183153  work=345239274296880467532  date=06/05/12 18:48:15
09/10/12 00:00:23 ProcessBlock: ACCEPTED

and so on
Pages: [1] 2 3 »  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!