 Show Posts
|
|
Pages: [1] 2 »
|
I see this in my wallet log: 2018-Jun-29 15:51:28.792382 [P2P6][96.59.239.119:19733 OUT]Sync data returned a new top block candidate: 147142 -> 144447 [Your node is 2695 blocks (7 days) ahead]
SYNCHRONIZATION started Is this a known problem or have I done something wrong? I got the wallet from github and compiled few weeks ago. |
|
|
|
Already wasted months mining and holding Sumokoin. They are not worth anything now. It's ASIC only. Nobody's interested.
Sad true... |
|
|
|
I noticed my wallet isn't syncing. I did new git clone, compiled, removed old lmdb and ran the daemon but it's stack here, never starts the sync: 2018-04-16 12:18:53.478 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1282 **********************************************************************
2018-04-16 12:18:53.478 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1283 Last scheduled hard fork time shows a daemon update is needed now.
2018-04-16 12:18:53.478 [P2P1] WARN global src/cryptonote_core/cryptonote_core.cpp:1284 **********************************************************************
2018-04-16 12:18:53.507 [P2P1] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid DeroPulse DNS checkpoint records were received
I set log level to 2 and see: 2018-04-16 12:44:45.188 [P2P4] WARN net.p2p src/p2p/net_node.inl:777 [85.217.170.245:18090 OUT] COMMAND_HANDSHAKE invoke failed. (-4, LEVIN_ERROR_CONNECTION_TIMEDOUT)
2018-04-16 12:44:45.188 [P2P7] WARN net.p2p src/p2p/net_node.inl:826 [85.217.170.245:18090 OUT] COMMAND_HANDSHAKE Failed
2018-04-16 12:44:45.188 [P2P7] INFO net.p2p src/p2p/net_node.inl:1003 [85.217.170.245:18090 OUT] Failed to HANDSHAKE with peer 85.217.170.245:18090
2018-04-16 12:44:45.188 [P2P7] WARN net.p2p src/p2p/net_node.inl:1224 Failed to connect to any of seed peers, continuing without seeds
2018-04-16 12:44:46.189 [P2P4] DEBUG net.p2p src/p2p/net_node.inl:1351 STARTED PEERLIST IDLE HANDSHAKE
2018-04-16 12:44:46.189 [P2P4] DEBUG net.p2p src/p2p/net_node.inl:1366 FINISHED PEERLIST IDLE HANDSHAKE
2018-04-16 12:44:46.710 [P2P3] INFO net.p2p src/p2p/net_node.inl:1818 [85.217.171.11:18090 eef6295d-fac7-dc21-b738-918b41dafabe OUT] CLOSE CONNECTION
2018-04-16 12:44:46.710 [P2P3] INFO net.p2p src/p2p/connection_basic.cpp:172 Destructing connection p2p#66 to 85.217.171.11
2018-04-16 12:44:47.189 [P2P2] DEBUG net.p2p src/p2p/net_node.inl:884 Random connection index=6(x=14, max_index=20)
2018-04-16 12:44:47.189 [P2P2] INFO net.p2p src/p2p/net_node.inl:1166 Considering connecting (out) to peer: 066f766b826d4fdb 213.169.75.114:18090
2018-04-16 12:44:47.189 [P2P2] DEBUG net.p2p src/p2p/net_node.inl:1181 Selected peer: 066f766b826d4fdb 213.169.75.114:18090[peer_list=1] last_seen: d10.h21.m28.s35
2018-04-16 12:44:47.189 [P2P2] DEBUG net.p2p src/p2p/net_node.inl:974 Connecting to 213.169.75.114:18090(peer_type=1, last_seen: d10.h21.m28.s35)...
2018-04-16 12:44:47.189 [P2P2] INFO net.p2p src/p2p/connection_basic.cpp:164 Spawned connection p2p#88 to 0.0.0.0 currently we have sockets count:23
2018-04-16 12:44:47.189 [P2P2] INFO net contrib/epee/include/net/abstract_tcp_server2.inl:85 test, connection constructor set m_connection_type=2
2018-04-16 12:44:47.189 [P2P2] DEBUG net contrib/epee/include/net/abstract_tcp_server2.inl:962 connections_ size now 22
2018-04-16 12:44:47.217 [P2P2] INFO net.p2p src/p2p/net_node.inl:990 [0.0.0.0:0 OUT] Connect failed to 213.169.75.114:18090
2018-04-16 12:44:47.217 [P2P2] INFO net.p2p src/p2p/net_node.inl:1184 Handshake failed
Should I use some other(which one?) peers? |
|
|
|
Hi,
Mining on old 280x GPU rig.
Earlier I've got almost 500h from one card.
But now with SRBminer get <400h.
Is it normal?
I haven't read last few pages here on Sumo forum so I am not fully up-to-date but started mining today again with xmr-stak 2.4.2 version and I see my cards perform much worse. I used to get 2.7kH/s with my rig, now only 1.9kH/s which I guess is the result of latest changes in the code so I guess it's normal. I played with the intensity values in config but going too high(above 700) the cards don't mine at all. At least the network hashrate seems to have been quite low for the last few days, which is why switched back to SUMO. |
|
|
|
I am not on telegram. Can I download up-to-date blockchain from somewhere and sync from there?
Or any other hints?
It would be faster for you to just sync the blockchain using the wallet software. The blockchain is quite small right now, I would recommend just syncing the normal way. That's what I am doing but normal sync(./ombred) doesn't finish. Make sure you are using the latest code. I got ombred stuck on block height 21299 too, but stopping it and starting again helped. Okay, compiled latest ombre from github and syncing continues. Thanks. |
|
|
|
I am not on telegram. Can I download up-to-date blockchain from somewhere and sync from there?
Or any other hints?
It would be faster for you to just sync the blockchain using the wallet software. The blockchain is quite small right now, I would recommend just syncing the normal way. That's what I am doing but normal sync(./ombred) doesn't finish. |
|
|
|
hmm, freshly compiled wallet, started syncing and got: 2018-Mar-22 15:08:29.670570 [P2P3][104.200.137.40:19743 OUT]Sync data returned a new top block candidate: 21299 -> 25140 [Your node is 3841 blocks (2 days) behind] SYNCHRONIZATION started
2018-Mar-22 15:08:35.329433 [P2P8][69.85.85.37:19743 OUT]Sync data returned a new top block candidate: 21299 -> 25140 [Your node is 3841 blocks (2 days) behind] SYNCHRONIZATION started
same problem also after removal of .ombre/lmdb/ and restarting the daemon. Any help on this? Due to some.l weird event the network Forked 2 days ago. Just let daemon sync until it reaches the new top hight. If you still have problems please join our telegram. We can help you more there. thanks for the answer. I let it run over night but nothing happened: 2018-Mar-23 04:14:23.159549 [P2P5][139.194.72.157:19743 OUT]Sync data returned a new top block candidate: 21299 -> 24829 [Your node is 3530 blocks (2 days) behind] SYNCHRONIZATION started
2018-Mar-23 04:14:24.191322 [P2P1]IP 58.164.13.190 blocked.
2018-Mar-23 04:14:59.949521 [P2P2][139.194.72.157:19743 OUT]Sync data returned a new top block candidate: 21299 -> 24901 [Your node is 3602 blocks (2 days) behind] SYNCHRONIZATION started
I am not on telegram. Can I download up-to-date blockchain from somewhere and sync from there? Or any other hints? |
|
|
|
hmm, freshly compiled wallet, started syncing and got: 2018-Mar-22 15:08:29.670570 [P2P3][104.200.137.40:19743 OUT]Sync data returned a new top block candidate: 21299 -> 25140 [Your node is 3841 blocks (2 days) behind] SYNCHRONIZATION started
2018-Mar-22 15:08:35.329433 [P2P8][69.85.85.37:19743 OUT]Sync data returned a new top block candidate: 21299 -> 25140 [Your node is 3841 blocks (2 days) behind] SYNCHRONIZATION started
same problem also after removal of .ombre/lmdb/ and restarting the daemon. Any help on this? |
|
|
|
|
Wow, the hashrate is 91.83 MH/s at this very moment, that is insane, given the current SUMO price...
I think we'll soon see some dumps. Nicehash gotta pay its electricity bills, right?!
|
|
|
|
|
In my case, my miners seem to working just fine, I didn't see any connections problems.
However the official pool has been having issues for the last couple of days to display
my stats and payment history. It keeps searching for my address and then times out.
It occasionally display the stats, but most of the time it doesn't, I regularly check the pool
during the day. Do we know the root cause or are devs still investigating it?
It's not a big deal, I receive the payments, but would be nice to have that fixed.
|
|
|
|
I seem to be having problem with official pool http://pool.dero.live/The search field of my address keeps searching and never returns, then prints "Connection error" but is still searching. Is it only me or also somebody else experiencing this? |
|
|
|
SUMO is over and slowly dying, I don't think that SUMO will ever be relevant again. Fact is that SUMO has nothing new to offer, just because their dev team is so small. SUMO literally doesn't do anything new, they just add some "extra" features, cmon
Just my opinion.
What do have other coins to offer? |
|
|
|
Mining on the official pool for the past day and now its saying my IP is banned? Has this happened to anyone else?
Yep, for setting too low of a difficulty for your hashrate. Difficulty should be in the range of 10-30x your hashrate (e.g. - 7000 to 21000 for 700 H/s) and can be set by appending the value to your DERO address with a period, e.g., <address>.<difficulty> Does setting a firm hashrate have any benefit? You aren't setting a firm hashrate - that depends entirely on the capability of your miner - rather, you are setting a fixed share difficulty so that - hopefully! - you will find shares in a reasonably predictable and consistent amount of time. Like anything else there are tradeoffs involved: the lower the share difficulty the less valuable each share is, and the more of an impact ping time has on your earnings (because ping time becomes a significant percentage of the time to find each share). Conversely, too high a difficulty means you might still be trying to solve a share for a block that someone else found, rendering your share "stale" (ie, worthless). If you don't set a fixed difficulty - and a lot of pools won't let you because it is misused or abused - then the pool will employ a singularly useless variable difficulty strategy that, in my experience at least, tends to result in spending a lot of time at ridiculously high difficulties for my hashrate (e.g. - 100001 for 440 H/s, when 8000 would be more appropriate). Note that the format I gave earlier for setting a fixed difficulty does not apply to all pools; some require appending it to your address with a "+" while others require a ":" so make sure you check the pool's "getting started" section rather than solely rely on what some random dude on the internet says. Ups, I meant difficulty, not hashrate. Thanks for explanation. |
|
|
|
Mining on the official pool for the past day and now its saying my IP is banned? Has this happened to anyone else?
Yep, for setting too low of a difficulty for your hashrate. Difficulty should be in the range of 10-30x your hashrate (e.g. - 7000 to 21000 for 700 H/s) and can be set by appending the value to your DERO address with a period, e.g., <address>.<difficulty> Does setting a firm hashrate have any benefit? |
|
|
|
Just for curiosity, How many people still holding your sumokoin in this bitcoin selling off trend???
Holding. Waiting for $50-100. |
|
|
|
|
I would have thought the diff goes down with such a price drop but despite that it's still high.
But it also looks like someone with massive hash power is manipulating? It jumps up and down
in intervals, there's not a steady hashrate, at least that's what I've observed.
Anyway, I am holding everything I mined in the beginning no matter what.
SUMO go go go!
|
|
|
|
|
Is the official? pool 185.106.122.31/bitcedi down?
I got it from bitcedi dot org.
Otherwise I can't find a pool with bigger hashrate.
|
|
|
|
There seems to be a problem with http://[Suspicious link removed]/ pool?
I am getting timeouts my miners can't connect.
The pool is bxcpool dot tk |
|
|
|
|
There seems to be a problem with http://[Suspicious link removed]/ pool?
I am getting timeouts my miners can't connect.
|
|
|
|
I am using SumoEasyMiner.
I am using HP 15-bw033WM, Windows 10, AMD A12-9720 Quad Core Processor, 8GB Memory, AMD Radeon R7 GPU.
and getting hash rate of 30 H/s.
But I am not seeing any thing earned on my wallet. Am I missing something?
My wallet is 100% synchronized.
You might want to use xmr-stak miner which gives higher hashrate https://github.com/fireice-uk/xmr-stak-amd/releases https://github.com/fireice-uk/xmr-stak-cpu/releases30H/s is basically nothing. With current difficulty and your hw it will take a bit to earn something, and also what pool you're mining on, look at pending balance what you got there. |
|
|
|
|
