[XMR] Monero - A secure, private, untraceable cryptocurrency

[Its About Sharing]

I've been searching and can't find a solution here. Anyone have any idea as to why upon synching I get the below errors?
In particular, why is there "ric" after the /Users/ directory? I'm on a Mac and that is not my user name, so the /Users/ric directory does not exist.
(I've removed the wallet.bin file and restarted everything, new seed and all generated, but this didn't seem to help.)
I started by double clicking on bitmonerod and then once synched, simplewallet, which were downloaded from Github. (I was unable to install via the command line instructions.)

Thanks
IAS

Code:

2014-Jun-15 14:54:28.481185 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:55:35.798590 [P2P3][87.246.145.171:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.316479 [P2P4][134.249.161.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.389800 [P2P3][113.190.13.120:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.459267 [P2P3][86.25.118.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:40.417736 [P2P4][101.164.234.118:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:43.603074 [P2P6][184.190.220.14:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:56:01.198940 [P2P0][199.188.178.180:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:57:51.320218 [P2P6][sock 15] Some problems at write: Broken pipe:32
2014-Jun-15 14:58:49.917326 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:59:13.308392 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:13.420894 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.102139 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.102228 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.109085 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.109163 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.375326 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.375418 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.460551 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.460639 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.461740 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.461798 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:32.024017 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:32.043524 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:42.239133 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:42.260234 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:515 [88.193.177.21:18080 OUT]Failed to do_send
2014-Jun-15 14:59:45.678970 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:45.679094 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()

[lecristoph]

I've been searching and can't find a solution here. Anyone have any idea as to why upon synching I get the below errors?
In particular, why is there "ric" after the /Users/ directory? I'm on a Mac and that is not my user name, so the /Users/ric directory does not exist.
(I've removed the wallet.bin file and restarted everything, new seed and all generated, but this didn't seem to help.)
I started by double clicking on bitmonerod and then once synched, simplewallet, which were downloaded from Github. (I was unable to install via the command line instructions.)

Thanks
IAS

Code:

2014-Jun-15 14:54:28.481185 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:55:35.798590 [P2P3][87.246.145.171:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.316479 [P2P4][134.249.161.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.389800 [P2P3][113.190.13.120:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:37.459267 [P2P3][86.25.118.21:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:40.417736 [P2P4][101.164.234.118:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:55:43.603074 [P2P6][184.190.220.14:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:56:01.198940 [P2P0][199.188.178.180:18080 OUT] SYNCHRONIZED OK
2014-Jun-15 14:57:51.320218 [P2P6][sock 15] Some problems at write: Broken pipe:32
2014-Jun-15 14:58:49.917326 [P2P8][sock 22] Some problems at write: Broken pipe:32
2014-Jun-15 14:59:13.308392 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:13.420894 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.102139 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.102228 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.109085 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.109163 [P2P0]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:14.375326 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:14.375418 [P2P4]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.460551 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.460639 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:15.461740 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:15.461798 [P2P1]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:32.024017 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:32.043524 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()
2014-Jun-15 14:59:42.239133 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:42.260234 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:515 [88.193.177.21:18080 OUT]Failed to do_send
2014-Jun-15 14:59:45.678970 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/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-15 14:59:45.679094 [P2P5]ERROR /Users/ric/Desktop/Temp/bitmonero-core/contrib/epee/include/net/levin_protocol_handler_async.h:638 [88.193.177.21:18080 OUT]Failed to do_send()

I get the same error, but for me it's "tom" instead of ric... the mystery thickens...

[equipoise]

^It's OK, but if you see huge amount of those it's best to restart the daemon.

[From Above]

<3 Monero forever

[meccoin4me]

realy like the coin and the whole concept , but i am busy with it now for two days , i create 2 wallets (simplewallet and gui)  start mining it and buyed some .

still  2 days after retrying to withdraw from bittrex and waiting for miningearnings i have still 2 empty wallets , it 's a little frustrating

but i am a noob in this whole world and for sure in this coin ,but still trying and waiting till all works

great coin again

but happy to have some on an exchange

[beavis4ever]

realy like the coin and the whole concept , but i am busy with it now for two days , i create 2 wallets (simplewallet and gui)  start mining it and buyed some .

still  2 days after retrying to withdraw from bittrex and waiting for miningearnings i have still 2 empty wallets , it 's a little frustrating

but i am a noob in this whole world and for sure in this coin ,but still trying and waiting till all works

great coin again

but happy to have some on an exchange

Apparently the exchanges are having issues because they were using too low of a transaction fee.  Bittrex support told me they were already updated to the mandatory code but didn't notice the change in the tx fee from May 29th.  I find it hard to believe though.  Doesn't the daemon set the tx fee minimum?

[sammy007]

realy like the coin and the whole concept , but i am busy with it now for two days , i create 2 wallets (simplewallet and gui)  start mining it and buyed some .

still  2 days after retrying to withdraw from bittrex and waiting for miningearnings i have still 2 empty wallets , it 's a little frustrating

but i am a noob in this whole world and for sure in this coin ,but still trying and waiting till all works

great coin again

but happy to have some on an exchange

Apparently the exchanges are having issues because they were using too low of a transaction fee.  Bittrex support told me they were already updated to the mandatory code but didn't notice the change in the tx fee from May 29th.  I find it hard to believe though.  Doesn't the daemon set the tx fee minimum?

Exchanges MUST do some job, track latest changes in coins they listing, unfortunately they are too relaxed adding bunches of scam/shit coins every day. They got into the habit of monkey job listing copycats, stuck with supporting this pipeline.

[surfer43]

Apparently the exchanges are having issues because they were using too low of a transaction fee.  Bittrex support told me they were already updated to the mandatory code but didn't notice the change in the tx fee from May 29th.  I find it hard to believe though.  Doesn't the daemon set the tx fee minimum?

Indeed, but the transactions they send can include any fee. Those are accepted by the wallet and rejected by the daemon if the transaction fee is below 0.005 XMR.

[equipoise]

^The exchanges have some problems, because they were using the old code with smaller fees and their transactions will be included only by the miners also using the old code. Those changes are 16 days old and most of the miners changed their code on 30th of May and just a few miners (and one of the pools?!) are using this old code. The miners using the old code are mining blocks with little to no reward (~0.3 XMR for a mined block?!). This problem started about 30th of May for the exchanges and I wrote them back then to update, but they are little slow with such small issues. Their transactions somehow got mined till now, but it's getting more and more unlikely and their transactions are stuck in the mempool (will be mined or will get eventually returned back to their wallets sooner or later). The exchanges are finally working on the problem and the devs are helping them in #monero-dev. This will be fixed sooner or later and we should receive our XMR.

About the exchanges "didn't notice the change in the tx fee from May 29th":

05/30/2014 Me: "Yes, finally it did. Did you upgraded bitmonerod to the final version? There is a higher tax in the new daemon and it seems your transactions are not propagated and accepted from the network. Thank you."
05/30/2014 Bittrex support: "We have no upgraded yet... I'll make sure to add that to the list."

[parker928]

Price is increasing. I regret I didn't buy more at 0.0025 I always make same mistakes.

you are a nice guy, i like you

you are sad you missed cheap xmr but you don't come on here and fud, instead you admit your mistake and learn from it. Thanks for not being a troll about it. send me your xmr address and ill send you a few xmr

[beavis4ever]

^The exchanges have some problems, because they were using the old code with smaller fees and their transactions will be included only by the miners also using the old code. Those changes are 16 days old and most of the miners changed their code on 30th of May and just a few miners (and one of the pools?!) are using this old code. The miners using the old code are mining blocks with little to no reward (~0.3 XMR for a mined block?!). This problem started about 30th of May for the exchanges and I wrote them back then to update, but they are little slow with such small issues. Their transactions somehow got mined till now, but it's getting more and more unlikely and their transactions are stuck in the mempool (will be mined or will get eventually returned back to their wallets sooner or later). The exchanges are finally working on the problem and the devs are helping them in #monero-dev. This will be fixed sooner or later and we should receive our XMR.

About the exchanges "didn't notice the change in the tx fee from May 29th":

05/30/2014 Me: "Yes, finally it did. Did you upgraded bitmonerod to the final version? There is a higher tax in the new daemon and it seems your transactions are not propagated and accepted from the network. Thank you."
05/30/2014 Bittrex support: "We have no upgraded yet... I'll make sure to add that to the list."

Then Mr. Richie Lai is either a liar or ill informed.

Me Yesterday at 20:15

Thank you. Is there an ETA on when either my coins will be showing up in my wallet or you refund them to my account? Here is the announcement from Bitcointalk:

"May 29 - Mandatory upgrade to 0.8.8 to fix an overly aggressive block size penalty. Please do not send funds using the older version of the wallet software, as it will use the incorrect fee, and your transaction will take several days to either arrive or fall out the mempool.

Seems you guys are a few weeks behind.


Richie Lai Today at 04:11

Yeah , we've had the upgrade for a while, but the txfee change wasn't something we caught. We've been working with the devs on this all night. Hoping to get this resolved soon.

Thanks for your patience and understanding.
Richie

[matthewh3]

Whenever I run the deamon on *buntu 13.10 my DNS goes down for every browser.  As soon as I stop the deamon all my browsers start working again.

[equipoise]

Then Mr. Richie Lai is either a liar or ill informed.

He should be very busy with the support. After reading that my ticket is resolved and my question about the daemon update he might just skip the rest of my message and didn't noticed the transaction fee changes...

[uvt9]

I've been searching and can't find a solution here. Anyone have any idea as to why upon synching I get the below errors?
In particular, why is there "ric" after the /Users/ directory? I'm on a Mac and that is not my user name, so the /Users/ric directory does not exist.
(I've removed the wallet.bin file and restarted everything, new seed and all generated, but this didn't seem to help.)
I started by double clicking on bitmonerod and then once synched, simplewallet, which were downloaded from Github. (I was unable to install via the command line instructions.)

I have similar error on Windows, from official Windows binaries:

Code:

[P2P4]ERROR c:\users\tom\documents\github\bitmonero\contrib\epee\include\serialization\keyvalue_serialization_overloads.h:153 size in blob 1720 not have not zero modulo for sizeof(value_type) = 24

'tom' is not a username in my PC. It seems there is a bug while compiling these binaries.

Another annoying error pop up quite frequently:

Code:

[P2P3][sock 768] Some problems at write: An established connection was aborted by the software in your host machine:10053

bitmonerod is now consuming a lot of bandwidth.

I didn't have these problems with old version, i don't understand why new version get worse than old.

[Crypto_Man1212]

Hey guys im new to the community, is the anon working or is it in development like darkcoin.

[uvt9]

Hey guys im new to the community, is the anon working or is it in development like darkcoin.

Anon has been fully functional since day 0, and of course ring signature is much more superior than what darkcoin is developing.

[sk00t3r]

Another annoying error pop up quite frequently:

Code:

[P2P3][sock 768] Some problems at write: An established connection was aborted by the software in your host machine:10053

bitmonerod is now consuming a lot of bandwidth.

I didn't have these problems with old version, i don't understand why new version get worse than old.

Same exact issues here as well.

[binaryFate]

^The exchanges have some problems, because they were using the old code with smaller fees and their transactions will be included only by the miners also using the old code. Those changes are 16 days old and most of the miners changed their code on 30th of May and just a few miners (and one of the pools?!) are using this old code. The miners using the old code are mining blocks with little to no reward (~0.3 XMR for a mined block?!). This problem started about 30th of May for the exchanges and I wrote them back then to update, but they are little slow with such small issues. Their transactions somehow got mined till now, but it's getting more and more unlikely and their transactions are stuck in the mempool (will be mined or will get eventually returned back to their wallets sooner or later). The exchanges are finally working on the problem and the devs are helping them in #monero-dev. This will be fixed sooner or later and we should receive our XMR.

About the exchanges "didn't notice the change in the tx fee from May 29th":

05/30/2014 Me: "Yes, finally it did. Did you upgraded bitmonerod to the final version? There is a higher tax in the new daemon and it seems your transactions are not propagated and accepted from the network. Thank you."
05/30/2014 Bittrex support: "We have no upgraded yet... I'll make sure to add that to the list."

I bet poloniex is in the same boat, and that is the problem with my withdrawal:

Yesterday I've withdrawn some XMR from Poloniex. The transaction was listed as "COMPLETE" quickly. However today, when checking my wallet (and after refresh), the funds are not there. And indeed the tx id that poloniex shows for this tx is unknown on http://monerochain.info.

I just opened a ticket, but I wonder if somebody else encountered this?

They escalated my ticket, but still didn't solve it.

[parker928]

Hey guys im new to the community, is the anon working or is it in development like darkcoin.

It was always working. It never stopped. In fact, you can control the level of anonymity by varying the "mixin count".

[LeroyJenkens]

^The exchanges have some problems, because they were using the old code with smaller fees and their transactions will be included only by the miners also using the old code. Those changes are 16 days old and most of the miners changed their code on 30th of May and just a few miners (and one of the pools?!) are using this old code. The miners using the old code are mining blocks with little to no reward (~0.3 XMR for a mined block?!). This problem started about 30th of May for the exchanges and I wrote them back then to update, but they are little slow with such small issues. Their transactions somehow got mined till now, but it's getting more and more unlikely and their transactions are stuck in the mempool (will be mined or will get eventually returned back to their wallets sooner or later). The exchanges are finally working on the problem and the devs are helping them in #monero-dev. This will be fixed sooner or later and we should receive our XMR.

About the exchanges "didn't notice the change in the tx fee from May 29th":

05/30/2014 Me: "Yes, finally it did. Did you upgraded bitmonerod to the final version? There is a higher tax in the new daemon and it seems your transactions are not propagated and accepted from the network. Thank you."
05/30/2014 Bittrex support: "We have no upgraded yet... I'll make sure to add that to the list."

I bet poloniex is in the same boat, and that is the problem with my withdrawal:

Yesterday I've withdrawn some XMR from Poloniex. The transaction was listed as "COMPLETE" quickly. However today, when checking my wallet (and after refresh), the funds are not there. And indeed the tx id that poloniex shows for this tx is unknown on http://monerochain.info.

I just opened a ticket, but I wonder if somebody else encountered this?

They escalated my ticket, but still didn't solve it.

I had the same problem. I filed the ticket yesterday. It was escalated but still no payment.