[0Th]Ozcoin Pooled Mining |DGM 1%|Stratum+VarDiff port 80|NEW CN mining|

[wazoo42]

Has anybody else had trouble with stratum.ozco.in in the past few hours? I have 4 miners and all of them are idle b/c they report it as dead.

[1713981668]

1713981668

[1713981668]

1713981668

[1713981668]

1713981668

[1713981668]

1713981668

[crazyates]

Has anybody else had trouble with stratum.ozco.in in the past few hours? I have 4 miners and all of them are idle b/c they report it as dead.

I got quite a few idle email notifications yesterday, even tho my miner never went down. Now today, CGMiner is reporting it as dead as well.

I really hope you have some backup pool set up, either a different Ozcoin node or another pool. Yes?

[wazoo42]

I have http://us.ozco.in:8331 set as a backup, but that does not appear to work either and my 2nd backup (bitcoinpool) no longer exists. Any suggestions for a backup ozco pool or a different pool?

[crazyates]

I have http://us.ozco.in:8331 set as a backup, but that does not appear to work either and my 2nd backup (bitcoinpool) no longer exists. Any suggestions for a backup ozco pool or a different pool?

Yep those 8331 ports shouldn't be working anymore. They've shut off the old GW protocols. Ozcoin has 4 nodes now:

stratum.ozco.in:3333
us.ozco.in:3333
au.ozco.in:3333
eustratum.ozco.in:3333

Pinging them, it seems that stratum.ozco.in and au.ozco.in share the same IP, so it looks like it's really only 3 right now. As for pool strategy, keeping 2-3 Ozcoin nodes and then 1-2 other pools would keep you very well protected from downtime.

[os2sam]

Has anybody else had trouble with stratum.ozco.in in the past few hours? I have 4 miners and all of them are idle b/c they report it as dead.

Yep, last couple days.

[Graet]

au.ozco server is offline currently, it's dns is pointed to stratum.ozco, there are routing issues with the datacentre stratum.ozco is located in, we have contacted both hosts and hope to have issues resolved today
sorry for the inconvenience
Graet

[Blaksmith]

All mining nodes have been updated with new changes that will help with bandwidth issues that have cropped up since ASIC's have hit the mining world hard.  These changes should also help with fewer "Lost xx shares due to stratum disconnect on pool x" messages.  If your internet has issues, it will not fix that issue.

Changes are:
Dynamic difficulty setting of -1 will now load in your last difficulty that your miner was working at when it logs in.
Manually setting a difficulty of an ASIC miner too low, will force it to a dynamic difficulty.  This does not set your difficulty on the web site!  Once your miner has settled on a good number, please set it in your worker's page.

[yxt]

miner up and running @eustratum but shown as offline?

[Graet]

miner up and running @eustratum but shown as offline?

Yeah mining node has lost communication with DB server, shares are being cached and will be counted when comms resumes.
sorry for the inconvenience

[yxt]

no problem, thx for the fast answer

You are doing a great job

[Graet]

thanks

eustratum/DB connection fixed, shares currently counting

[os2sam]

Changes are:
Dynamic difficulty setting of -1 will now load in your last difficulty that your miner was working at when it logs in.
Manually setting a difficulty of an ASIC miner too low, will force it to a dynamic difficulty.  This does not set your difficulty on the web site!  Once your miner has settled on a good number, please set it in your worker's page.

My Jalapeno was dynamically changed to a diff 31.  That seems a tad bit high for a Jalapeno, doesn't it?
Sam

[aneutronic]

New guy here and not sure if this is normal. I just received my avalon last week and have had it mining here about 5 days. I've been getting worker idle notifications the past 2 days but the miner hasn't skipped a beat other than the resets I've done after trying changes. About the same time the stats are reporting a hash rate of about half of what cgminer shows (as far as I can estimate due to the stats delay).

My efficiency also seems low compared to others (~99%), should this always be at 100% and what settings affect it?

I know it depends on pool luck and up time but what is a reasonable daily earnings to expect from a batch 3 avalon at the current difficulty?

[kano]

At 37Mil diff, 80GH/s would expect 1.07594397 BTC a day, then subtract pool fees.
If you are more or less than 80GH/s simply multiply it - so that's up to just now.

But, yeah, it just hit an all time new record of 51M diff ... so with the new diff it's now:
80GH/s would expect 0.79181761 BTC a day, then subtract pool fees.

My calculator:
http://tradebtc.net/bitcalc.php

[aneutronic]

Nice calculator, thanks.

That's quite a bump on difficulty today. It's going to be tough to break even on this thing if all the new asics deliver on time.   

[Graet]

Updates to stratum mining nodes underway completed
stratum will need to be restarted on each mining node

[crazyates]

I got an idle worker notification for both my workers, and both the widget and the website show my hashrate as 0, but CGMiner is still reporting the pool as up and is still submitting shares. Any issues noticed on the pool end?

[Graet]

I got an idle worker notification for both my workers, and both the widget and the website show my hashrate as 0, but CGMiner is still reporting the pool as up and is still submitting shares. Any issues noticed on the pool end?

no issues with pool
issue with kansas datacentre (the one that att drilled holes thru the cables other day) had a couple of small downtimes - we think they are finishing up repairs - tho they didnt contact us to warn of downtime :/
the only affect this has is take a bitcoind we rely on for site stats offline - we are looking at duplicating this bitcoind so dc issues like this dont affect us in future
sorry for any inconvenience

[crazyates]

I got an idle worker notification for both my workers, and both the widget and the website show my hashrate as 0, but CGMiner is still reporting the pool as up and is still submitting shares. Any issues noticed on the pool end?

no issues with pool
issue with kansas datacentre (the one that att drilled holes thru the cables other day) had a couple of small downtimes - we think they are finishing up repairs - tho they didnt contact us to warn of downtime :/
the only affect this has is take a bitcoind we rely on for site stats offline - we are looking at duplicating this bitcoind so dc issues like this dont affect us in future
sorry for any inconvenience

No worries. Thanks for the explanation!

[Graet]

Updated all the bitcoinds today

Pool hashrate gradually climbing - welcome to new miners