Topic: [∞ YH] solo.ckpool.org 1% fee solo mining USA/DE 251 blocks solved! - page 430. (Read 1514501 times)

Sorry guys next one gonna be mine. 

Hope it'll be me

Must be just about time for someone to find one...

Well the Avalon that Bitwitt won over on Kano pool found a block.

https://bitcointalksearch.org/topic/m.10433228

I will do and let you know.
mtr is realy nice, did't know it before, verry usefull.

I always use > netstat -tupan to check the connections.

Thank you for mtr!

I installed it and this is a report:

root@officerasp:/home/xxxxxxxx# mtr --report -w solo.ckpool.org
HOST: officerasp                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- FRITZBOX                                          0.0%    10    1.3   1.7   1.3   4.2   0.9
  2.|-- rdsl-krlh-de80.nw.mediaways.net                   0.0%    10   45.5  42.5  41.0  45.5   1.2
  3.|-- xmws-krlh-de02-chan-20.nw.mediaways.net           0.0%    10   40.7  40.9  39.7  43.0   0.9
  4.|-- xe-1-0-0-0.0002.dbrx.01.kae.de.net.telefonica.de  0.0%    10   40.2  51.8  39.1 143.3  32.2
  5.|-- rmwc-zuri-ch01-so-2-1-0-0.nw.mediaways.net        0.0%    10   56.2  55.2  52.0  57.1   1.6
  6.|-- 10gigabitethernet1-2.core1.zrh1.he.net            0.0%    10   65.0  59.1  53.9  65.7   4.7
  7.|-- 10ge10-1.core1.par2.he.net                        0.0%    10   74.6  74.4  71.2  80.2   3.3
  8.|-- 10ge15-1.core1.ash1.he.net                        0.0%    10  155.2 153.1 139.8 200.2  17.4
  9.|-- 100ge15-1.core1.lax1.he.net                       0.0%    10  197.4 202.0 197.4 209.7   4.0
 10.|-- 100ge15-1.core1.sjc2.he.net                       0.0%    10  207.3 210.0 207.0 218.7   3.6
 11.|-- 10ge3-2.core3.fmt2.he.net                         0.0%    10  225.2 213.7 206.7 225.2   5.6
 12.|-- router3-fmt.linode.com                           10.0%    10  211.0 209.0 205.5 212.1   2.1
 13.|-- li773-180.members.linode.com                     10.0%    10  208.6 208.5 206.5 211.5   1.4

looks ok for me? what do you think?

Usually this is packet loss somewhere in the routing between you and the server, so it's not your fault or the pool's fault. If you're on linux/*nix you can check the quality of your routing at any time with mtr. If a hop has packet loss of up to 10% that's ok but anything 20% or more is likely a problem. This is the command:

  Hi ck,
I see the interuption live, i have two cgminer running.
One is on a Raspi with Debian and your cgminer with a Jalapeno and on my work pc
running xp i got a Antminer 2 with cgminer. Both reported the same.
I am in germany, so maybe the link to your server was simply interupted.
The internet connection was ok.
Never mind, it was a time of 2 min. and i just want to let you know, no complain.
I had this before, but i never see it live, as i am working and not constantly monitoring the miner.
In that case i saw it and i wrote the message. 2 min. later it was reastablished and i edit my Posting.

Anyway, Thank you for the Pool and your work!

"[2015-02-11 21:52:22] Accepted 0001702f BES 0  pool 0 Diff 45.6k/1k" Go block eruptor!

Congrats!

Sorry, it was my fault the BTC address was set to the password. I changed it to the username and now it works. 

Good luck! Damn shame that 50TH isn't even that much these days.



Provider has already responded and they have had zero issues. The fact that 2 different users had issues means that perhaps the internet routing in their part of the world was where the problem was. Anyway everything's fine at the pool, server and datacentre.

Good luck!  Luck is hiding somewhere, I hope you find it.  I distribute my hashrate over solo.CKPool, Eligius, BTC Guild and Kano and they haven't been very lucky lately... :-/

taking a shot at it. 50th


http://solo.ckpool.org/users/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

Sheesh, save some blocks for us! 

Server and pool still seems fine. I've opened a ticket for the upstream provider.

I just tried to connect and no dice, seems the issue may not be on the miners end. I use a block eruptor as a default load for my charging PSU. 

Guess I'll load Bitcoin-core until things get ironed out, no sense in having 333Mh/s online and not pointing it at the network. 

Nothing wrong at the pool end, but probably immediately upstream maybe at the data centre?  I didn't get any notification of any issues but that doesn't mean it didn't happen.

Mine failed over too.  Don't know for how long though.