Dreamweaver
Member
 Offline
Activity: 104
Merit: 10
Trying to find my way.
|
 |
April 13, 2013, 09:58:29 PM |
|
I tried the expiry flag for CGminer and nothing has changed. I've noticed this same problem only recently, and still nothing seems to work. Is it related to the pool or what? Here's what my batch file looks like: @echo on
ECHO "Example cgminer miner startup file (set your own user and password)"
ECHO.
cgminer.exe -o vircurpool.com:8337 -u Dreamweaver.Test -p HD --worksize 256 --
thread-concurrency 8192 -I 13 --scrypt --expiry 10 EDIT: Whoops! I missed the post regarding the pool's increased hashrate xD I suppose we can disregard this then. |
BTC: 15hfE8dXf13Z1n5WQnpoF24Zr7G8Fv1Ghk
|
|
|
|
|
|
|
|
|
|
The forum was founded in 2009 by Satoshi and Sirius. It replaced a
SourceForge forum.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
dorei
Newbie
Offline
Activity: 19
Merit: 0
|
|
April 14, 2013, 01:37:50 AM |
|
I was too experiencing "time-too-old" errors. Setting expiry didn't seem to fix it.  But when I add -Q 0 to cgminer, "time-too-old" errors almost disappear.  |
|
|
|
|
SuperTramp
Legendary
Offline
Activity: 1073
Merit: 1000
|
 |
April 14, 2013, 07:33:26 AM |
|
Pool up to 35MH/s now  |
|
|
|
rTech
Sr. Member
Offline
Activity: 305
Merit: 250
Trust but confirm!
|
|
April 14, 2013, 05:08:26 PM |
|
LoL i'll mine some MNC for future savings  |
|
|
|
|
|
manface
|
|
April 15, 2013, 03:54:22 AM |
|
I think the pool was going through some growing pains as it went from 10 miners to 80 miners now. Looks like my stale issues have been fixed, but I mostly use Reaper now because it's faster and seems more stable.
|
|
|
|
|
SuperTramp
Legendary
Offline
Activity: 1073
Merit: 1000
|
|
April 15, 2013, 07:36:18 AM |
|
I think the pool was going through some growing pains as it went from 10 miners to 80 miners now. Looks like my stale issues have been fixed, but I mostly use Reaper now because it's faster and seems more stable.
Same here, switched to reaper and things seem to be a bit smoother and a bit higher hash rate too! |
|
|
|
|
manface
|
|
April 17, 2013, 03:20:44 AM |
|
Any word on this pool having a PPS (pay per share) option instead of PPLNS ?
|
|
|
|
|
|
ronaldinho_07
|
|
April 17, 2013, 04:21:24 AM |
|
I was too experiencing "time-too-old" errors. Setting expiry didn't seem to fix it. But when I add -Q 0 to cgminer, "time-too-old" errors almost disappear. same as you why is the pool stale shares so high ? |
|
|
|
|
maunderingcabal
Full Member
Offline
Activity: 154
Merit: 100
Don't dwell in the past, don't dream of the future
|
|
April 17, 2013, 08:22:06 AM |
|
This pool does not work with cgminer. I tried everything. Popped on reaper and pow, accepts.
|
|
|
|
|
vipah (OP)
|
|
May 03, 2013, 01:25:32 AM |
|
Updated main post.
Stratum now supported.
|
|
|
|
|
SuperTramp
Legendary
Offline
Activity: 1073
Merit: 1000
|
|
May 03, 2013, 07:06:13 AM |
|
Updated main post.
Stratum now supported.
NICE !  |
|
|
|
|
baka
|
|
May 03, 2013, 07:09:38 AM |
|
Any news on why in gods name is anyone mining this? Block reward is stupid low compared to first blocks.
|
|
|
|
bratkartoffel
Newbie
Offline
Activity: 20
Merit: 0
|
|
May 13, 2013, 07:58:57 AM |
|
Are there stratum problems? 2013-05-13 09:57:09,990 ERROR proxy # Connection to upstream pool timed out
[2013-05-13 09:57:39] HTTP request failed: Operation timed out after 30015 milliseconds with 0 bytes received
[2013-05-13 09:57:39] submit_upstream_work json_rpc_call failed
[2013-05-13 09:57:39] ...retry after 30 seconds
Got these Messages over and over on all my miners for a few hours now :/ Regards, BK |
|
|
|
|
SuperTramp
Legendary
Offline
Activity: 1073
Merit: 1000
|
|
May 13, 2013, 09:35:33 AM |
|
Are there stratum problems? 2013-05-13 09:57:09,990 ERROR proxy # Connection to upstream pool timed out
[2013-05-13 09:57:39] HTTP request failed: Operation timed out after 30015 milliseconds with 0 bytes received
[2013-05-13 09:57:39] submit_upstream_work json_rpc_call failed
[2013-05-13 09:57:39] ...retry after 30 seconds
Got these Messages over and over on all my miners for a few hours now :/ Regards, BK Vipah had to reboot the pool. Not sure if this is related to what you have going on or not just thought I would pass along the info. |
|
|
|
|
ISAWHIM
|
|
June 09, 2013, 04:16:40 AM
Last edit: June 09, 2013, 07:14:39 PM by ISAWHIM |
|
100% reject rate... What did this actually fix?
Someone in the 3-connections is feeding bad block data. Issue resolved, again, by deleting all the block-data, and reconnecting until I got a good reply from the good server.
You need more main servers participating in the block distribution, and something that allows the bad-block data to be removed and replaced with good data. If it is one of your servers, you may have bad RAM or a bad HD sector... be sure you are using "error correction" switches in your compiles for your servers, which should have error-correction memory and HD ability. (If you are running this off a home-PC... just surrender now.)
Finally it is mining again. Try and try again... I think all the evil has been rooted-out.
|
|
|
|
|
|
