Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 209. (Read 837101 times)

There are many users connected with Stratum proxy right now without problems. Except that they send my server an error if it asks them which software/version they are running and that's spamming my logs a bit. That appears to be a bug in recent versions of the stratum proxy.

Are you seeing any errors? Maybe you just have the names/password wrong? Or you are not using the correct hostname and port: host mint.bitminter.com and port 3333

i have stratum proxy running in my comp, blade working on ALL other pools but here

The reason is quite simple: Blades do not support Stratum at all, they are supposed to be used with a (local) stratum proxy. So this is not BitMinter specific. I had success using the Blade with getwork and diff=8 on another pool, but it was purely experimental. Running the stratum proxy seems the reasonable thing to do. Same goes for mining on BitMinter of course

I think that's likely to be because of the network issues earlier today. Looks like the client was delayed in getting more work and in sending in proofs of work it had found. Then the network cleared up but there had been a block change and the proofs of work were stale.

I am receiving 8 Jalapenos tomorrow so I was test driving your Beta Client with my Current FPGA Singles - I was getting a lot of work rejects as follows - Any thoughts

2013.06.05 [10:02] FPGA device detected on COM6: BitFORCE v1.0
2013.06.05 [10:02] Difficulty is now 15605633
2013.06.05 [10:03]  BitFORCE (COM13) ERROR: BitFORCE (COM13) ran out of work. Idling...
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:03]  Work rejected. Server says: Stale proof of work
2013.06.05 [10:07]  BitFORCE (COM8) ERROR: ZFX command timed out. Retries: 0
2013.06.05 [10:07]  BitFORCE (COM8) ERROR: Extraneous data received: NO-NONCE
2013.06.05 [10:08]  BitFORCE (COM4) ERROR: ZFX command timed out. Retries: 0
2013.06.05 [10:08]  BitFORCE (COM4) ERROR: Extraneous data received: NO-NONCE
2013.06.05 [10:09]  Work rejected. Server says: Stale proof of work

There is a lot of blade hashpower in the pool already.

It does look like the blades can't mine directly in the pool, but it works through Stratum proxy. I don't know what the reason is, I don't have a blade to test with and I don't have any technical data on them whatsoever. I'm guessing their Stratum implementation is a little sensitive. Perhaps the server asking them what their software/version is causes them to disconnect. Perhaps it's something else.

Are you getting an error message that might help?

do u plan to accept blades to mine on your pool anytime soon ? looks like no one can mine with blades on your pool

+185 % difficulty  next 5 days !
gg

Yes, it looks like there was some sort of problem. There was 20% packet loss for a while. But the traffic wasn't that high. Likely an issue at the data center.

Happened to me about 45 mins ago.. 5:30 ET. 

M

i can confirm this.

ddos?

keeps going to backup pool and back. web is up but shows 0Mh miners and 0.00Th pool for some time, than everything goes back.

The hashrate is estimated based on an Icarus with 2x FPGA splitting the nonce range between them. That doesn't get the correct hashrate with the Block Erupter. I'll have this fixed in a future version.

Thanks for the answer. But it detect the Mh/s correctly when you start

cgminer has with an special configuration an similar effect. The USB Asics will not work with 670 mhs, i think its a driver issue.

I'm trying here for first time with the Bitminer client.

Is it normal that all 5 USB Asicminer are hashing at ~670Mh/s each one... when they're supposed to run at 336Mh/s. Program failure?

I'm going to DC them and reboot.

my miner is now i a normal state, no problems visible, very curious, i will observe this the next days.

The API perk will become cheaper and some new perks will be added as soon as I have time.


Not sure what happened there. Was cgminer still showing a normal hashrate? Were proofs of work still being accepted?

after restart the miner all seems to be ok.  
Edit: i mine since some month on differnt pools, but on bitminter is the cashout for my lite miner very good, so i see smallest problems and wondering about the problem from today.

my worker sees no 0 mhs on my bitminter account, but my cgminera see 7,3 ghs. Anything goes wrong at the moment. The problem occures until 1200 UTC.