Version 0.7.0 release candidate 3 ready for testing - page 3.

jgarzik

legendary

Activity: 1596

Merit: 1100

Quote from: keystroke on September 09, 2012, 10:29:04 AM

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.

keystroke

hero member

Activity: 900

Merit: 1014

advocate of a cryptographic attack on the globe

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.

Diapolo

hero member

Activity: 772

Merit: 500

Quote from: zvs on September 09, 2012, 04:32:10 AM

Quote from: Diapolo on September 09, 2012, 04:08:50 AM

@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

zvs

legendary

Activity: 1680

Merit: 1000

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

Quote from: Diapolo on September 09, 2012, 04:08:50 AM

@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

Activity: 772

Merit: 500

@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

zvs

legendary

Activity: 1680

Merit: 1000

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

Quote from: flatfly on September 08, 2012, 02:44:54 AM

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.

Severian

sr. member

Activity: 476

Merit: 250

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

flatfly

legendary

Activity: 1092

Merit: 1016

760930

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

wumpus

hero member

Activity: 812

Merit: 1022

No Maps for These Territories

Quote from: slothbag on September 08, 2012, 01:41:42 AM

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.

slothbag

sr. member

Activity: 369

Merit: 250

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.

keystroke

hero member

Activity: 900

Merit: 1014

advocate of a cryptographic attack on the globe

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!

Gavin Andresen

legendary

Activity: 1652

Merit: 2301

Chief Scientist

Quote from: slothbag on September 07, 2012, 05:12:57 AM

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...

Diapolo

hero member

Activity: 772

Merit: 500

Quote from: Meni Rosenfeld on September 06, 2012, 04:46:46 PM

Is it possible to update the translations?

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

Dia

slothbag

sr. member

Activity: 369

Merit: 250

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.

Meni Rosenfeld

donator

Activity: 2058

Merit: 1054

Is it possible to update the translations?

jgarzik

legendary

Activity: 1596

Merit: 1100

Quote from: keystroke on September 06, 2012, 04:19:27 PM

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..

keystroke

hero member

Activity: 900

Merit: 1014

advocate of a cryptographic attack on the globe

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

Gavin Andresen

legendary

Activity: 1652

Merit: 2301

Chief Scientist

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=

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

Topic: Version 0.7.0 release candidate 3 ready for testing - page 3. (Read 9831 times)