Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1825. (Read 4671114 times)

can anyone confirm this with mintpal?

I would be shocked if MintPal added MRO. They wouldn't add Nxt when Nxt got first place votes for a mile, once they realized they actually had to modify the api since it wasn't a bitcoin clone. Nxt offered its own developers for help, but MintPal was too lazy.

I think this is one reason why the price is being pumped at the moment.

Those daemon errors are not uncommon, its all to do with it commmunicating with other peers.

The send_que_size is more than... error is because the daemon tries to shove more data at a remote peer than it is supposed to in a session

The connection closed by remote host is someone else's daemon disconnecting you for some reason


You can usually ignore them, but if you are getting loads at the same time it can end up only talking to one or two peers and getting out of sync. Even so thats not a major problem unless you are running a pool.

Can someone explain these errors in the daemon?  It goes on forever in red text except for the bolded which is white.  Before I was mostly getting the bolded error.

2014-Jun-14 13:46:44.564557 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:46:44.570561 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:46:44.577566 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:46:44.588574 [P2P8]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:08.950807 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:10.594970 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:47:10.602976 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:10.609980 [P2P1]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:12.034988 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:12.041993 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [24.8.142.47:18080 O
UT]Failed to do_send()
2014-Jun-14 13:47:12.047997 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:12.056004 [P2P3]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:638 [81.155.65.215:18080
 OUT]Failed to do_send()
2014-Jun-14 13:47:17.557895 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:47:42.866797 [P2P3][sock 2288] Some problems at write: An existin
g connection was forcibly closed by the remote host:10054
2014-Jun-14 13:48:02.277528 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:515 [24.8.142.47:18080 O
UT]Failed to do_send
2014-Jun-14 13:48:02.289536 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than
 ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
2014-Jun-14 13:48:02.297542 [P2P2]ERROR c:\temp\monero\git\bitmonero-master-x64\
contrib\epee\include\net\levin_protocol_handler_async.h:515 [81.155.65.215:18080
 OUT]Failed to do_send

So I set mixin to 0 and sent .5 XMR. I refreshed and tried another .5 and couldnt sent it. I tried .3 and couldnt. I cant even send .1 XMR
I give up. If this isn't fixed, this coin has no future.

set mixin to 0 and send smaller amounts, eg 0.5 MRO

I have a transfer from Bitrex to my wallet that never arrived currently.  It was for a much greater amount than yours though.  I have a ticket open, but so far all I heard was they show them as sent.  Yet the txid isn't found in the blockchain.  txid 7c626ba76a822e0e474303b7fe7b80a79ccb90464cc1e1818a7ee0a1f2d01bbd if anyone can help.  I was wondering if anyone else was having problems with Bitrex.

I seriously think the error size limit bug is on purpose. Keeps people from dumping the coins.
I have 137 XMR in my wallet, i can't even send 1 XMR to the exchange...
So...What to do?

The poll at agx.io features Monero! Spread the word and get out the vote!

- The Austin Global Team

Find us at:
agx.io
reddit.com/r/AustinGlobalExchange/
twitter.com/AustinGlobalX
austinglobal.tumblr.com

Who cares.  BTC had a botnet problem.  So did Litecoin.  Hashrate is also going up because of yet another miner enhancement.  There is also a GPU miner out there now which hashes on parity with a good CPU, allowing more to get into the XMR mining game.  I doubt it's profitable for them at the moment but I'm sure quite a few of them see longer term potential in this coin and plan on holding instead of dumping. I'm sure eventually someone will figure out how to increase the GPU miner efficiency on top of that.  Eventually the botnets will take their stolen power elsewhere.  

5 till 10 min. ago , tanx for the fast reply

It might take a little while before the transaction is confirmed on the blockchain.  How long ago did you request the withdrawals?

Hello all , i am totally new to this coin and after a lot of reading i new have two wallets , the simplewallet and the crptonotewallet ( i am a noob i guess) , i buyed some coins on bittrex and try to send some little amounts , new i now it was to little because i send 0,1 ,minus de trans.fee they sent less then the 0.1 that is neccesary so new i try to sent 0.5 to my cryptonotewallet but it also did not arrive , is it possible that it takes some time before the coins came in my wallet?

please some help , tanx anyway

SimpleWallet refresh SOOOO DAMMNNN SLLOOOOW =/

<3 Monero.  This coin has endless potential, but the software definitely has a ways to go.  Oh well, gives a few more months to collect XMR before the crowds start flocking when there is a pretty/integrated/fast GUI wallet.

We're waiting on zone117x to do it, if anyone is skilled with node.js, they can also implement it.

https://github.com/zone117x/node-cryptonote-pool/issues/12

Fix should do this this:
1.) keep track of all shares on the server and distribute reward per block for contribution internally
2.) allow the user to request manual payout or set auto payout threshold
3.) allow only payments in increments of 0.1 (because of the denomination code); do not allow payments smaller than 0.1

In the meantime, all smaller miners are recommended not to mine at moneropool.com or moneropool.org, as mining there will produce lots of dust if your HR is low.

There are already several open source, non official GUIs available. For the official one, fluffypony stated on reddit that we might have to wait few more months. Dev team is focusing on more important work to improve stability of network.
http://www.reddit.com/r/Monero/comments/283f49/do_anyone_know_when_we_will_get_a_moneroqt_wallet/ci7856u


The transaction size limit only happened with small miners who received to many dust from pools. Normal users (like me) has no problem, i can transfer thousands of coins in one transaction smoothly.

Apparently the pool software need some fix, i don't know who is doing it.

What's the minimum number of coins you can send?

yes but it has always been the case, what i was wondering is what made you aware of all this? it would be useful to know in order to attract more people into MRO:)