Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1811. (Read 4671953 times)
Got word from the admin of http://pool.cryptoescrow.eu/ - They are aware of the issue with blocks and are working to get it resolved ASAP.
moneropool.org - getting a Stratum Connection Timed Out and Interrupted.
down again
hmm? Not for me.
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
moneropool.ORG is up not .COM
down again
hmm? Not for me.Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
down again
hmm? Not for me.Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - Cannot connect to mine.moneropool.com port 3334
DevFee: Stratum - Failed to connect, retry in 5sec...
Stratum - Cannot connect to mine.moneropool.com port 3334
Stratum - Failed to connect, retry in 5sec...
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Stratum - connecting to 'mine.moneropool.com' <5.9.25.103> port 3334
Down for me - site loads but no data.
loads fine for me, shows it just hit a block
Down for me - site loads but no data.
down again
hmm? Not for me.
down again
how to solo mine with GPU 
Set up your own pool. If you can't, just solo CPU mine. It's fairly competitive anyway.
Failing all that, at least spread out to smaller pools.
Glad to see this.
yeah,
looks like http://monero.crypto-pool.fr/ is pool to mine with
don't know what's with http://pool.cryptoescrow.eu/, they should find some block, since pool HR went up.
crypto-pool.fr finds at least 1 block/hour with smaller HR then cryptoescrow.eu
weird, at least or really really really bad luck
the only thing that cames to mind its they are keeping the blocks for themselfs looks like http://monero.crypto-pool.fr/ is pool to mine with
don't know what's with http://pool.cryptoescrow.eu/, they should find some block, since pool HR went up.
crypto-pool.fr finds at least 1 block/hour with smaller HR then cryptoescrow.eu
weird, at least or really really really bad luck
with that hash its impossibel not to have a block in 1hour much less 8
Beware monero.crypto-pool.fr... they haven't paid ANYONE in several days. Admin claims he can't figure out the problem and that payments are fine.
how to solo mine with GPU
yeah,
looks like http://monero.crypto-pool.fr/ is pool to mine with
don't know what's with http://pool.cryptoescrow.eu/, they should find some block, since pool HR went up.
crypto-pool.fr finds at least 1 block/hour with smaller HR then cryptoescrow.eu
weird, at least or really really really bad luck
the only thing that cames to mind its they are keeping the blocks for themselfs looks like http://monero.crypto-pool.fr/ is pool to mine with
don't know what's with http://pool.cryptoescrow.eu/, they should find some block, since pool HR went up.
crypto-pool.fr finds at least 1 block/hour with smaller HR then cryptoescrow.eu
weird, at least or really really really bad luck
with that hash its impossibel not to have a block in 1hour much less 8
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
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: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
I get the same error, but for me it's "tom" instead of ric... the mystery thickens...
LOL! Are you serious?
Well, hopefully it is nothing as the other poster said. Have you tried moving coins in and out?
Thx,
IAS
Much mystery...
...such Scooby Doo: tewinget (Tom) built the Windows binaries, and I (Riccardo) built the OS X binaries. Obviously when you execute compiled code you don't have the source code *on your system*, but it has to still be able to reference where the error is occurring. You can safely ignore both those "ABSTRACT_SERVER_SEND_QUE_MAX_COUNT " errors as well as the path it refers to, as that just happened to be the build path at the time:)
How about we put up a bounty to find the person(s) who initiated the DDOS attack on Moneropool.org and exact justice - cut off their fingers - All of them.
Think there is a hidden compliment in there.
Not even hidden.
Nobody attacks an unsuccessful coin.
Now I don't want to be quoted out of context. I never support endorse criminal activity, but in a sense the DDOS of larger pools actually does the coin a service, by encouraging decentralization for a while. Learn your lesson and get the hell off the big pools and spread out or even better solo mine.
Lest we end up like bitcoin. Not a good thing what is happening over there. (The developers of this coin are committed to long term centralization solutions, but they are just that, long term. In the mean time we need preventive measures as well.)
Anyone else having transaction size too big when trying transfer xmr out to an exchange?
For some reason if I have 50xmr I have to send them in 10xmr chunks to get anything to transfer out.
Any ideas?
For some reason if I have 50xmr I have to send them in 10xmr chunks to get anything to transfer out.
Any ideas?
You had received too many dust transactions from pool and this is the reason. We're waiting for more improvement for pool software. At the moment you can try to send your coins by small chunks to new wallet of yours and that new wallet will be fine.
Correct. Other remedy is to swtich to a smaller pool or solo mine. You will get less frequent larger payments so no dust issue.
MRO is this next BTC!
I just sold my house, my wife, and my car. Now you better be right!Too bad about the house and the car. Congrats though.
Good one
MRO is this next BTC!
I just sold my house, my wife, and my car. Now you better be right!Too bad about the house and the car. Congrats though.
Jump to: