Just upgrade to 2.10.1 from 2.9.7.
The hanging problem when the connection goes down/unstable seems to be gone under windows. Yay!! It wasn't just stratum, btw, I saw it on my p2pool nodes as well.
However I'm having a problem with it dividing work up across my backup pools. I had to remove one of my p2pool nodes because it was sending work to 3 nodes almost all the time. I'm not sure why 2.9.7 was able to send all 2g/h of work to one node, and now 2.10.1 sends most, but not all of it, there, and the rest to other nodes. Is this intended?
M
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 420. (Read 5805998 times)
December 16, 2012, 07:17:19 PM
December 16, 2012, 06:42:08 PM
Roger those comments, that gives me something to work with. Yes there is no way to reconnect stratum (yet?) and submit shares you were working on last time you were connected unfortunately.
December 16, 2012, 01:40:25 PM
I've noticed two problems with stratum backup pools, that still exist on 2.10.1. The bigger problem is that stratum backup pools can become permanently dead. This is only happening on my rigs with wireless connections, so maybe it's a problem with latency / packet loss? Second problem is that with failover-only disabled, most leaked shares seem to go to my getwork backup pool, even though it's last on the list. I have two stratum backup pools with higher priority than the getwork pool, but they rarely (if ever) get leaked shares. This is only a small matter, since share leakage is very low.
I need to investigate the dead pool issue. I haven't seen it happen myself.As for leaking shares, stratum and gbt pools actually don't leak shares at all with or without failover-only mode. You only get leakage if the primary pool is getwork and you're not in failover only mode.
I think this is probably the same issue that I hit. It seems easy to reproduce. [EDIT: the dead pools issue, that is] I have pools configured as follows (2.10.1-ish build). Pool management is failover, failover only is disabled.
stratum+tcp://us1.eclipsemc.com:3333
stratum+tcp://us2.eclipsemc.com:3333
stratum+tcp://eustratum.ozco.in:3333
http://api.bitcoin.cz:8332 (which upgrades to Stratum anyway)
Steps to reproduce:
1. Ensure you are happily mining on pool 0, with cgminer showing all pools as alive
2. Pull the network connection and wait until cgminer declares all pools dead (may take a few minutes)
3. Restore the network connection. cgminer will declare pool 0 alive and start mining. Pools 1-3 remain dead indefinitely.
roy
December 16, 2012, 11:30:30 AM
I've noticed two problems with stratum backup pools, that still exist on 2.10.1. The bigger problem is that stratum backup pools can become permanently dead. This is only happening on my rigs with wireless connections, so maybe it's a problem with latency / packet loss? Second problem is that with failover-only disabled, most leaked shares seem to go to my getwork backup pool, even though it's last on the list. I have two stratum backup pools with higher priority than the getwork pool, but they rarely (if ever) get leaked shares. This is only a small matter, since share leakage is very low.
I need to investigate the dead pool issue. I haven't seen it happen myself.As for leaking shares, stratum and gbt pools actually don't leak shares at all with or without failover-only mode. You only get leakage if the primary pool is getwork and you're not in failover only mode.
Here's how the shares end up to pool 3, the only getwork pool, when primary pool connection drops:
[2012-12-16 18:14:05] Accepted 0b30f6dd Diff 22/4 GPU 0 pool 0
[2012-12-16 18:14:32] Accepted 1717f2fd Diff 11/4 GPU 0 pool 0
[2012-12-16 18:16:02] Lost 2 shares due to stratum disconnect on pool 0
[2012-12-16 18:16:37] Accepted 481563e1 Diff 3/1 GPU 1 pool 3
[2012-12-16 18:16:52] Accepted 3752b425 Diff 4/1 GPU 0 pool 3
[2012-12-16 18:16:53] Accepted ed86b60d Diff 1/1 GPU 0 pool 3
[2012-12-16 18:17:02] Pool 0 http://mint.bitminter.com:3333 not responding!
[2012-12-16 18:17:02] Switching to http://us1.eclipsemc.com:3333
[2012-12-16 18:17:16] Accepted 33ec2056 Diff 4/1 GPU 1 pool 3
[2012-12-16 18:17:24] Accepted 3c342f03 Diff 4/1 GPU 0 pool 1
Some shares go to pool 3 before cgminer switches to my first backup pool. This also happens during startup, but it's only a share or two.
"Lost 2 shares due to stratum disconnect on pool 0" happens because stratum can't handle disconnects currently, right?
December 16, 2012, 01:53:34 AM
Also, anyone like to respond to this: https://bitcointalksearch.org/topic/mining-protocol-bandwidth-comparison-gbt-stratum-and-getwork-131035
I'm especially interested in the network usage differences between BFGminer and CGMiner when using various protocols?
Stratum on the hostile fork of cgminer uses approximately 100x (?1000x) the bandwidth of stratum on cgminer. I'm especially interested in the network usage differences between BFGminer and CGMiner when using various protocols?
December 16, 2012, 01:42:27 AM
Also, anyone like to respond to this: https://bitcointalksearch.org/topic/mining-protocol-bandwidth-comparison-gbt-stratum-and-getwork-131035
I'm especially interested in the network usage differences between BFGminer and CGMiner when using various protocols?
I'm especially interested in the network usage differences between BFGminer and CGMiner when using various protocols?
December 16, 2012, 01:40:49 AM
i've been running 2.10.1 for over 24 hrs now w/o any issues on win 7. 
Weird, cuz I was having freezing issues of 2.9.7, but now I'm not. Been good for 24 hours now. Next time it freezes, I'll upgrade to the newest. 
December 15, 2012, 10:59:21 PM
i've been running 2.10.1 for over 24 hrs now w/o any issues on win 7.
well it was the main reason for the updated version. Glad to see I finally resolved that annoying bug, and it was as expected deep within libcurl dll for windows managing raw sockets. I fixed one bug but there seem to be numerous others...Going on about 30+ hours now, zero issues. (Win7 x64)
Thanks! December 15, 2012, 06:38:00 PM
i've been running 2.10.1 for over 24 hrs now w/o any issues on win 7.
well it was the main reason for the updated version. Glad to see I finally resolved that annoying bug, and it was as expected deep within libcurl dll for windows managing raw sockets. I fixed one bug but there seem to be numerous others... 
December 15, 2012, 06:35:39 PM
i've been running 2.10.1 for over 24 hrs now w/o any issues on win 7.
December 15, 2012, 04:03:33 PM
I've noticed two problems with stratum backup pools, that still exist on 2.10.1. The bigger problem is that stratum backup pools can become permanently dead. This is only happening on my rigs with wireless connections, so maybe it's a problem with latency / packet loss? Second problem is that with failover-only disabled, most leaked shares seem to go to my getwork backup pool, even though it's last on the list. I have two stratum backup pools with higher priority than the getwork pool, but they rarely (if ever) get leaked shares. This is only a small matter, since share leakage is very low.
I need to investigate the dead pool issue. I haven't seen it happen myself.As for leaking shares, stratum and gbt pools actually don't leak shares at all with or without failover-only mode. You only get leakage if the primary pool is getwork and you're not in failover only mode.
December 15, 2012, 09:37:44 AM
I have tried to run cgminer with scrypt enabled on my windows 7 machine with a 6850hd for fun but cannot get it to run. I followed the tutorial and ended up with:
cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
Make sure you at least have sdk2.6 as well, meaning the one that comes with driver 11.12 or later, and you need MORE SYSTEM RAM to mine ltc.cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
I found out you meant the ACL SDK. I just updated that to 2.8 to no avail
December 15, 2012, 08:21:55 AM
Thanks for the reply. I don't really know what Stratum backup servers are so I think it is unlikely this is the cause (right?). I FYI this crash happens the second after I run the bat file.
Concerning the wireless issues I am on wireless (via an adapter) because there is no clear way to connect my router to my pc without laying the cable all across the living room
When I run the exact same script without the --scrypt it does work (with the litecoin p2ppool) but it runs at 220Mh/s or something so I guess it is not doing anything useful then right? (it is very weird that shares are being accepted though, how can that be?)
Concerning the wireless issues I am on wireless (via an adapter) because there is no clear way to connect my router to my pc without laying the cable all across the living room
When I run the exact same script without the --scrypt it does work (with the litecoin p2ppool) but it runs at 220Mh/s or something so I guess it is not doing anything useful then right? (it is very weird that shares are being accepted though, how can that be?)
December 15, 2012, 07:50:34 AM
I've noticed two problems with stratum backup pools, that still exist on 2.10.1. The bigger problem is that stratum backup pools can become permanently dead. This is only happening on my rigs with wireless connections, so maybe it's a problem with latency / packet loss? Second problem is that with failover-only disabled, most leaked shares seem to go to my getwork backup pool, even though it's last on the list. I have two stratum backup pools with higher priority than the getwork pool, but they rarely (if ever) get leaked shares. This is only a small matter, since share leakage is very low.
December 15, 2012, 07:33:37 AM
Bump. Does anyone have an idea what can cause this? I cannot find any log files anywhere. It merely crashes.
December 14, 2012, 08:15:00 PM
I have tried to run cgminer with scrypt enabled on my windows 7 machine with a 6850hd for fun but cannot get it to run. I followed the tutorial and ended up with:
cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
Make sure you at least have sdk2.6 as well, meaning the one that comes with driver 11.12 or later, and you need MORE SYSTEM RAM to mine ltc.cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
I didn't know how to see which SDK I have but after your comment I updated Catalyst to the latest non-beta version (12.10) and this did not change behaviour.
Note I did not follow this part of the readme (because I am not using a Linux distro):
Code:
Step 1 on linux:
export GPU_MAX_ALLOC_PERCENT=100
If you do not do this, you may find it impossible to scrypt mine. You may find
a value of 40 is enough and increasing this further has little effect.
export GPU_USE_SYNC_OBJECTS=1
may help CPU usage a little as well.
Is anything logged somewhere? It just doesn't work and doesn't give me anything to work with.
December 14, 2012, 08:05:10 PM
I've uploaded some fresh debug builds for windows here for those who want to try and help me get debug information:
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
cgminer.exe caused an Access Violation at location 65722074 Reading from location 65722074.
Registers:
eax=00000000 ebx=0028f570 ecx=747b2e09 edx=00000000 esi=00000002 edi=00000000
eip=771c15de esp=0028f55c ebp=0028faa4 iopl=0 nv up ei pl zr na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
Call stack:
771C15DE ntdll.dll:771C15DE ZwRaiseException
75111A2C kernel32.dll:75111A2C WaitForMultipleObjectsEx
75114220 kernel32.dll:75114220 WaitForMultipleObjects
6248320B pthreadGC2.dll:6248320B pthreadCancelableTimedWait
December 14, 2012, 07:58:27 PM
I have tried to run cgminer with scrypt enabled on my windows 7 machine with a 6850hd for fun but cannot get it to run. I followed the tutorial and ended up with:
cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
Make sure you at least have sdk2.6 as well, meaning the one that comes with driver 11.12 or later, and you need MORE SYSTEM RAM to mine ltc. cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
December 14, 2012, 07:55:32 PM
I have tried to run cgminer with scrypt enabled on my windows 7 machine with a 6850hd for fun but cannot get it to run. I followed the tutorial and ended up with:
cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
cgminer --scrypt -o #somep2ppool# -u myAddress -p x --shaders 960 --intensity 12 --worksize 128 -g 1
but it just crashes. Even: cgminer --scrypt crashes.
Do I need to install/compile some scrypt library or something? (I have been using the windows binaries)
December 14, 2012, 07:45:59 PM
I've uploaded some fresh debug builds for windows here for those who want to try and help me get debug information:
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
http://ck.kolivas.org/apps/cgminer/debug/
These builds have optimisations disabled to hopefully try and get meaningful debug information out of them. It's annoying how hard windows builds are to debug...
Oh and the libcurl dll included in the 2.10.0 archive is already one with the fix from 2.9.7 (even though it's a different size) so there's no point trying a different dll if you are getting crashes.
cgminer.exe caused an Access Violation at location 65722074 Reading from location 65722074.
Registers:
eax=00000000 ebx=0028f570 ecx=747b2e09 edx=00000000 esi=00000002 edi=00000000
eip=771c15de esp=0028f55c ebp=0028faa4 iopl=0 nv up ei pl zr na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
Call stack:
771C15DE ntdll.dll:771C15DE ZwRaiseException
75111A2C kernel32.dll:75111A2C WaitForMultipleObjectsEx
75114220 kernel32.dll:75114220 WaitForMultipleObjects
6248320B pthreadGC2.dll:6248320B pthreadCancelableTimedWait
Jump to: