|
xorxor
|
 |
June 04, 2013, 10:40:44 AM |
|
looks stable last few hours.
I have one question:
with introduction of 1% fee , can API be now available for everyone?
I believe people looking just at API not loging in and using web will more likely decrase than increase server use.
|
fuck deeponion, fuck bitcoincash, all glory to one BITCOIN
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
|
|
|
|
|
|
badalien
|
|
June 04, 2013, 03:36:17 PM |
|
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.
|
|
|
|
|
|
badalien
|
|
June 04, 2013, 03:56:20 PM |
|
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. |
|
|
|
|
DrHaribo
Legendary
 Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
|
June 04, 2013, 07:24:31 PM |
|
with introduction of 1% fee , can API be now available for everyone?
I believe people looking just at API not loging in and using web will more likely decrase than increase server use.
The API perk will become cheaper and some new perks will be added as soon as I have time. 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. Not sure what happened there. Was cgminer still showing a normal hashrate? Were proofs of work still being accepted? |
|
|
|
|
badalien
|
|
June 04, 2013, 09:17:44 PM |
|
my miner is now i a normal state, no problems visible, very curious, i will observe this the next days.
|
|
|
|
|
BitAddict
Legendary
Offline
Activity: 1190
Merit: 1001
|
|
June 04, 2013, 09:33:44 PM |
|
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.
|
|
|
|
|
|
badalien
|
|
June 04, 2013, 09:42:18 PM |
|
cgminer has with an special configuration an similar effect. The USB Asics will not work with 670 mhs, i think its a driver issue.
|
|
|
|
|
BitAddict
Legendary
Offline
Activity: 1190
Merit: 1001
|
|
June 04, 2013, 09:45:40 PM |
|
cgminer has with an special configuration an similar effect. The USB Asics will not work with 670 mhs, i think its a driver issue.
Thanks for the answer. But it detect the Mh/s correctly when you start 2013.06.04 [23:44] Icarus (COM8): Command response 7 ms, hash rate 336,0 Mhps. |
|
|
|
|
DrHaribo
Legendary
Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
|
June 04, 2013, 09:51:01 PM |
|
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.
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. |
|
|
|
|
xorxor
|
|
June 05, 2013, 09:40:22 AM
Last edit: June 05, 2013, 10:24:17 AM by xorxor |
|
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.
|
fuck deeponion, fuck bitcoincash, all glory to one BITCOIN
|
|
|
|
badalien
|
|
June 05, 2013, 10:08:27 AM |
|
i can confirm this.
|
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
June 05, 2013, 10:16:40 AM |
|
i can confirm this.
Happened to me about 45 mins ago.. 5:30 ET. M |
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me! |
|
|
DrHaribo
Legendary
Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
|
June 05, 2013, 02:52:31 PM |
|
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.
|
|
|
|
veleten
Legendary
Offline
Activity: 1960
Merit: 1102
|
|
June 05, 2013, 04:16:19 PM |
|
+185 % difficulty next 5 days !
gg
|
|
|
|
rammy2k2
Legendary
Offline
Activity: 1778
Merit: 1002
|
|
June 05, 2013, 04:54:22 PM |
|
do u plan to accept blades to mine on your pool anytime soon ? looks like no one can mine with blades on your pool
|
|
|
|
|
DrHaribo
Legendary
Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
|
June 05, 2013, 05:09:15 PM |
|
do u plan to accept blades to mine on your pool anytime soon ? looks like no one can mine with blades on your pool
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? |
|
|
|
|
davidspitzer
|
|
June 05, 2013, 05:10:53 PM |
|
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
|
|
|
|
|
DrHaribo
Legendary
Offline
Activity: 2716
Merit: 1034
Bitminter.com Operator
|
|
June 05, 2013, 05:23:58 PM |
|
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
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. |
|
|
|
matt4054
Legendary
Offline
Activity: 1708
Merit: 1011
BitcoinQueue.com
|
|
June 05, 2013, 11:03:40 PM |
|
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.
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  |
|
|
|
|
rammy2k2
Legendary
Offline
Activity: 1778
Merit: 1002
|
|
June 06, 2013, 09:59:52 AM |
|
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.
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 have stratum proxy running in my comp, blade working on ALL other pools but here  |
|
|
|
|
|
