Some questions for fellow p2pool users : is anyone using cgminer with p2pool as primary pool and several other fallback pools ?
I ask because I see my cgminer-2.1.1 instances using fallback pools on occasions (on temporary network slowdowns maybe) and it seems they can get stuck for large periods using the fallback pool(s). At least my p2pool node logs exhibit large variations of hashing speed (between ridiculously low rates to near theoretical max hashrate) over large periods (the oscillations seem to span several hours).
All clients are cgminer 2.1.0 and 2.1.1 with similar configuration, I often see 1-difficulty share being submitted. It's probably a cgminer bug but I wonder if anyone saw this kind of log :
15:30:04.698403 Worker submitted share with hash > target:
15:30:04.698579 hash : 474e164967bdceaedb355c9bfcb8f96fadcfc1ad25a2b00cfb148770
15:30:04.698713 target: 578ae00000000000000000000000000000000000000000000000000
Might be a share for a "classic" pool being submitted to p2pool in error (I think 2.0.8 had this kind of problem and believed it to be fixed in 2.1.0).
Anyone can confirm seeing this kind of behavior on cgminer (or another miner supporting fallbacks) ?
I´m using cgminer 2.0.8 with two backup pools. I noticed the same behavior, that the miners spend much time on the backup pools. I m now using only one backup pool and now only about 0,5% of the hashing power goes to the backup pool. I never saw that log of yours here, but sometimes I get "[2012-01-02 17:19:49] Pool 0 not providing work fast enough"
I have another question:
I´m not generating any namecoins.
~/.namecoin/bitcoin.conf has rpcuser, rpcpassword and rpcport set. Im running p2pool like this:
python run_p2pool.py bitcoinRpcUser bitcoinRpcPass --merged-url
http://127.0.0.1:8882/ --merged-userpass namecoinRpcUser:namecoinRpcPass
How can i see if merged mining is working? P2pool sometimes logs:
Got new merged mining work! Difficulty: 409454.724619
So I think it should be working, but namecoind shows no balance or transactions.
Any ideas?
