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

Translation not updated.

Can you try to set IE as default browser for a quick test please?

Dia

Still getting that message with RC2.  Win 7 x64 Chrome Browser default.

Sorry if this is a little OT, but if I just pull from master am I getting your RC?  If so, its working great for me :-)

The fee is Sum(inputs) - Sum(outputs). Drop some coins on the floor and a miner will pick 'em up.

ERROR: CTxMemPool::accept() : not enough fees

I'm assuming this is the error that I'm getting. Is this expected behavior? How does one include fees in a raw transaction?

Thanks for the Qt commendation, wumpus and I'm very happy to hear such things as we put some efforts into making the Qt GUI better / cleaner / more polished . I really love his RPC console, too and I'm glad I could help him improving that beast a little ^^.

Dia

It seems to me that the RPC server currently entirely ignores the fact that can be limited via e.g. -onlynet="IPv4" which should never use IPv6 for anything then, right?

Dia

This is a great progress that you guys did in the 0.7 version.
You don't see a progress at the first sight, but the extra RPC commands and the built-in console - for me, just paradise. And it will be so easy to explain to my mom how to use it, so she doesn't have to keep her wallet on the same pc where my father watches porn, pressing yes at every button...
The idea witn some bitcoind.exe, that she had to run from a command prompt... she did not like it.
But a built in RPC console - just genius!
And I must say switching to Qt really seems to have been a good idea, after all.

Thanks.

Consensus is the RPC-doesn't-work-if-you-disable-IpV6 bug is serious enough to hold up the 0.7.0 final release.

So the plan will be: get a fix for that bug and release/test a 0.7.0rc3.

Install.  I'm installing RC2 as we speak and will give it a go.

Do you use portable Zip or installation? Only the installation will update the file associations for bitcoin URIs, which could also cause errors.

Dia

I'm on RC1, I'll check RC2 as soon as I can get back to that machine.

debug.log might tell you why it is being rejected. Some reasons it might be rejected:

+ You're re-using an input that has already been spent.
+ Sum(outputs) is greater than Sum(inputs)
+ signrawtransaction was unable to sign all of the inputs (it did not report "complete" : true )

By the way: be EXTREMELY careful with the raw transactions API. You can easily forget to include a change output and create transactions with huge fees; test your code thoroughly on testnet before putting it into production.

I tried this with RC2 on my Win7 x64 machine and it works like a charm. I have one instance running and sitting in the tray. Clicking a bitcoin URI leads to opening the client and no warning, as expected. Are you really sure you are using 0.7RC2, can you verify please?

Dia

Consistently getting a "TX rejected (code -22)" message when trying using sendrawtransaction. I believe I'm following all the steps properly. (createrawtransaction, signrawtransaction, sendrawtransaction)

Using the rpc console in Win7x64.

Same result using bitcoind.

If I click a link in windows to trigger the URI handling, but already have the client running, it whines about not getting the lock on the data directory.  This would seem to be that its trying to launch a second instance vs reusing the already running instance.  

Try commenting out the entire line

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(
                    static_cast(&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

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