bitmonerod is spewing stuff like this every 10s or so:

ERROR   {8} {p1} 2016-05-28 15:25:07.443042 [abstract_tcp_server2.inl+512 ::do_send_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), shutting down connection
ERROR   {8} {p1} 2016-05-28 15:25:34.447733 [abstract_tcp_server2.inl+512 ::do_send_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), shutting down connection
ERROR   {4} {p1} 2016-05-28 15:26:14.299694 [abstract_tcp_server2.inl+512 ::do_send_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), shutting down connection
ERROR   {8} {p1} 2016-05-28 15:26:46.632806 [abstract_tcp_server2.inl+512 ::do_send_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), shutting down connection
ERROR   {6} {p1} 2016-05-28 15:27:16.128294 [abstract_tcp_server2.inl+512 ::do_send_chunk] send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(1000), shutting down connection

Indeed there are - thanks.  Not really satisfactory, though.

I'm getting the following errors trying to "make release" with v0.9.4 (as tagged in git) on Debian 8.

How can I proceed from here?

Is buildability on common platforms not really an objective for Monero?

Linking CXX executable unit_tests
/home/foo/bitmonero/src/wallet/wallet2.cpp: In member function ‘load_keys’:
/home/foo/bitmonero/src/wallet/wallet2.cpp:1062:74: warning: ‘field_store_tx_info’ may be used uninitialized in this function [-Wmaybe-uninitialized]
                    || (field_store_tx_info_found && (field_store_tx_info != 0));
                                                                          ^
/home/foo/bitmonero/src/wallet/wallet2.cpp:1060:5: note: ‘field_store_tx_info’ was declared here
     GET_FIELD_FROM_JSON_RETURN_ON_ERROR(json, store_tx_info, int, Int, false);
     ^
/home/foo/bitmonero/src/wallet/wallet2.cpp:1061:74: warning: ‘field_store_tx_keys’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     m_store_tx_info = (field_store_tx_keys_found && (field_store_tx_keys != 0))
                                                                          ^
/home/foo/bitmonero/src/wallet/wallet2.cpp:1059:5: note: ‘field_store_tx_keys’ was declared here
     GET_FIELD_FROM_JSON_RETURN_ON_ERROR(json, store_tx_keys, int, Int, false);
     ^
/tmp/cc4V2Hqv.ltrans2.ltrans.o: In function `(anonymous namespace)::BlockchainDBTest_RetrieveBlockData_Test<cryptonote::BlockchainLMDB>::TestBody()':
cc4V2Hqv.ltrans2.o:(.text+0x1e293): warning: the use of `tmpnam' is dangerous, better use `mkstemp'
/tmp/cc4V2Hqv.ltrans3.ltrans.o: In function `unbound_supported_algorithms_Test::TestBody()':
cc4V2Hqv.ltrans3.o:(.text+0xb210): undefined reference to `dnskey_algo_id_is_supported'
cc4V2Hqv.ltrans3.o:(.text+0xb2cf): undefined reference to `dnskey_algo_id_is_supported'
cc4V2Hqv.ltrans3.o:(.text+0xb36e): undefined reference to `dnskey_algo_id_is_supported'
cc4V2Hqv.ltrans3.o:(.text+0xb396): undefined reference to `dnskey_algo_id_is_supported'
collect2: error: ld returned 1 exit status
tests/unit_tests/CMakeFiles/unit_tests.dir/build.make:694: recipe for target 'tests/unit_tests/unit_tests' failed
make[3]: *** [tests/unit_tests/unit_tests] Error 1
make[3]: Leaving directory '/home/foo/bitmonero/build/release'
CMakeFiles/Makefile2:1873: recipe for target 'tests/unit_tests/CMakeFiles/unit_tests.dir/all' failed
make[2]: *** [tests/unit_tests/CMakeFiles/unit_tests.dir/all] Error 2
make[2]: Leaving directory '/home/foo/bitmonero/build/release'
Makefile:127: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/foo/bitmonero/build/release'
Makefile:51: recipe for target 'release' failed
make: *** [release] Error 2

Yes.


I get this is the case in theory, but it's just not progressing / catching up.


Ubuntu 14.10, bitmonero v0.8.8.6 compiled from source.

my bitmonerod is stuck.  When I run it, I get this message (block 498962 was about 12h ago according to some explorer web site):

2015-Mar-30 23:43:03.008517 Net service bound to 0.0.0.0:18080
2015-Mar-30 23:43:03.008635 Attempting to add IGD port mapping.
2015-Mar-30 23:43:07.018928 No IGD was found.
2015-Mar-30 23:43:07.019128 P2p server initialized OK
2015-Mar-30 23:43:07.019602 Initializing core rpc server...
2015-Mar-30 23:43:07.020388 Binding on 127.0.0.1:18081
2015-Mar-30 23:43:07.020847 Core rpc server initialized OK on port: 18081
2015-Mar-30 23:43:07.021003 Initializing core...
2015-Mar-30 23:43:07.030683 Loading blockchain...
2015-Mar-30 23:43:44.327441 Blockchain initialized. last block: 498962, d0.h9.m24.s51 time ago, current difficulty: 918680635

Additionally, when I run simplewallet, it says "Starting refresh" then hangs for ages and then says:

Error: refresh failed: no connection to daemon. Please, make sure daemon is running. Blocks received: 0

I don't really want to start again and download the whole blockchain.  Can anyone help with troubleshooting these issues?

What's all this about 24 words.  It's 25 on my system.

thanks for this.

Thanks.  I was familiar with the concept of an OOM killer.  I'm a newb at Monero, not Unix / Linux.  So I was really asking if bitmonerod was expected to be a memory hog.


Holy shit, it keeps the **whole blockchain** in memory!  This software is even more primitive than I thought.

I didn't have any swap as I didn't want to wear out my laptop's SSD.  I've now added a 2TB USB3 disk as encrypted swap while I'm playing with Monero.

I know there's a way to do it, as I once did it with an old account.

I've just looked through the settings loads of times under "PROFILE" for a way to set the length of time I stay logged in, and can't find it.

I just got up and went to check sync progress for my first ever Monero sync.

The xterm in which I had launched monerod in the foreground had the following output at the end:

2015-Mar-29 06:43:34.867898 [P2P3][46.166.188.212:14630 INC]Sync data returned unknown top block: 354494 -> 496973 [142479 blocks (98 days) behind] 
SYNCHRONIZATION started
Killed

So I look in syslog and find a load of stuff about being out of memory:

Mar 29 06:44:04 rosti kernel: [12411960.385984]  [<ffffffff8216d68d>] out_of_memory+0x4cd/0x510
Mar 29 06:44:04 rosti kernel: [12411960.386247] Out of memory: Kill process 7956 (bitmonerod) score 641 or sacrifice child
Mar 29 06:44:04 rosti kernel: [12411960.386249] Killed process 7956 (bitmonerod) total-vm:6039844kB, anon-rss:5153036kB, file-rss:0kB

This is on my workstation with 8 GiB RAM.  Is this a known issue?

Also occasionally, instead of someone asking that, they will just think to themselves "so it depends on other transactions being present in each block", and go away feeling uneasy about the design of the whole thing.

In other words, not a "simplification" to be encouraged.

Please could someone help with some questions I have.  I'm just getting started with XMR.

When a wallet is described at https://moneroeconomy.com/news/choose-your-wallet as doing "remote node", what is this more analogous to: a bitcoin wallet which uses the RPC interface and believes the results, or an SPV bitcoin client?  I don't know if the SPV concept maps over into Monero.  But is it possible to have a wallet mode of operation with Monero where just block headers and our own transactions are verified?

My bitmonerod is currently downloading the blockchain and it's going to take a while.  If there was an SPV-alike mode available so I could get on and have a play with balances and sending transactions, that would be great.

Could someone expand a bit on minimum fees, differentiating between any minimum in the protocol for the tx to be valid, amount set by commonly used client(s), and amount required by widely-used mining software.

Unless the situation is very different from bitcoin, these are three different things.  With Bitcoin, the protocol minimum is zero, most miners require X (has changed a few times in reference code, some miners still accept zero-fees), and reference client typically sends Y (has also changed, not at same time as X).