background

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Buy bitcoins anywhere in the world at localbitcoins.com

Buy Monero at local Monero

Trade BTC for Monero at AgoraDesk

Use Anonymous Ads
Use Anonymous Ads

Graphs vs payouts vs accepted and rate

edited January 2014 in General
A little confused about how these things interact.

I've got a miner that averages about 7 Gh/s, and it runs constantly except for a few hours on Wednesday mornings when my computer reboots and I have to log in to start it (but that is resolved in the latest MacMiner version).

Looking at the p2pool graph, my (17VfvJ…) blue lines spike up to the ~7Gh/s range as expected, but routinely drop back down to zero for big chunks. For example right now, nearly half of my 'week' chart is zero.

I don't even have a chart for today, even though I'm at 7Gh/s with 49228 accepted and 313 rejected.

On the payout side, I've gotten payouts on Dec 25, 26, 29, 30, Jan 4, 5, and 16th. Back in November and December the payouts were coming like every other day, but in January they've way slowed down. 

Is this all expected based on the current difficulty level, or is their something wrong with my set up?

Comments

  • edited January 2014
    Hey, there's something not right in those long periods without work, it looks like a connectivity problem or it's mining on a backup pool? Sorry to say but that's probably been affecting your income, it looks as though you weren't mining on the node between the 5th and the 12th :S

     It is harder on P2Pool at lower speeds, the developer keeps adjusting it to try to keep it easier and there were an especially tough couple of weeks lately with difficulty increases, so if you're having trouble with P2Pool it might be an idea to try http://FabulousPanda.triplemining.com/ instead which is a more conventional pool than P2Pool and it has a lower difficulty. I hope you've had lucky returns so far!
  • Hmm, I'll give triplemining a shot.

    I've got a constant high speed (fios) connection so connectivity shouldn't be an issue.

    My backups / pools were set to the defaults, I just do 'save & start' after each macminer update and accept what's there.
  • Sounds like you're using best practices, I'm afraid I can't say why you kept disconnecting from the pool, please let me know how it goes from here on!
  • Okay, how do I troubleshoot this?

    I've got the two pools set up (fabulous panda…9332 and eu2.triplemining.com:8344) both with the correct user/pass.

    MacMiner's FPGA window is showing stuff was happening all day today - Accepted 10064, Detected 67, 7.00Gh, and it isn't 'hung' on that, the log window is scrolling new "Accepted <hex> BFL 0h pool 2…" lines every couple seconds.

    The fab.panda graph shows no activity since before noon today. The triple mining page shows my last submission was 7 hours ago.

    What is 'pool 2' - I only have 2 pools configured, and early in the startup sequence they are referred to as Pool 0 and Pool 1

  • Can you please go to the miner settings panel - edit config manually and check that the pool info there is as you would expect?
  • I completely removed the fabulous panda one in case it was causing issues. I now have only triple mining ones. 

    {
    "pools" : [
    {
    "user" : "Myuser_myworker",
    "pass" : "mypass"
    },
    {
    "user" : "Myuser_myworker",
    "pass" : "mypass"
    },
    {
    "user" : "Myuser_myworker",
    "pass" : "mypass"
    },
    {
    "user" : "Myuser_myworker",
    "pass" : "mypass"
    }
    ],

    "kernel-path" : "/Applications/MacMiner.app/Contents/Resources/bfgminer/bin"
    }

    (with the correct user/pass of course)

    Last night I even switched down to only having one of the stratum one to eliminate as many moving parts as possible.

    They work for awhile, and then they 'stop working'. 'Stop working' is a weird state where the 'accepted/rejected' numbers go up but no work is recorded per the pool website.

    My general network connectivity is fine, I am able to stream movies, surf the web, ping these domain names all with no problem through this entire period.

    I woke up this morning, checked my MacMiner window, it was continuing to update - then went to my triple chart and it looked like this: http://i.imgur.com/yxX01Wd.png

    The first chunk of work is when I got home and restarted MacMiner, then went to dinner. The second chunk of work is when I was restarted it (stop/start button) before going to bed - then sometime around midnight it stopped submitting results again.



  • Thanks for ruling the pool out, please try this version not yet released 


    It disallows API Control for bfgminer so if someone has access to your network and is sending pool change commands that can't happen any more
  • Okay, just started that version up. I'll keep an eye on my charts - it seems like an hour is as good as it gets, so it shouldn't be hard to detect a change in behavior. 
  • Been running a couple hours now. I won't know for sure if that resolved the problem until the morning.

    It is a reasonable theory though. I was running this on my server which is on the DMZ. I had no idea at all that mining would have opened up any listening ports, so it never crossed my mind that I should be paying attention to that.

    I am on a DHCP address, but it generally stays stable unless there is a power outage longer than the fios battery backup.
  • Ooh, is there any particular reason you're running the machine in the DMZ? You should get behind a firewall if possible, even with this version, which still allows people to read your config and stats just not change settings so on the DMZ you'd still be broadcasting the fact that you're mining. I should update the reference with a security section!
  • Well that must have been the problem, because it successfully ran all night long.

    I was going to put the miner on my main machine but the thing is just wayyyy too loud. Stuck it on the server down in the basement where it can't be heard. The server is in my router's dmz because it runs a ton of services across many many ports. It is relying on Apple's app-based firewall and I must have clicked 'okay' to a dialog letting this have access without thinking. 

    When I get home maybe I'll explicitly block MacMiner in Apple's firewall. And my testing of Little Snitch on my desktop has gone well, so I'll get that installed on the server now too.
  • Ah, I guess because it's a server it has a unique IP or FQDN? That's probably how it got caught. MacMiner needs to be able to access your pool server but I definitely recommend Little Snitch for control over exactly what it's connecting to. The only thing to keep in mind is that it'll ask you once for the triple mining FQDN when you start mining and then after about a day it tries to reconnect to a different IP for the same pool and that one needs to be allowed by Little Snitch too - that cost me a few hours mining!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file