Mac fag checking in. Running 1.4.10 and smooth sailing so far. Staking and all.
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.
Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?
If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.
You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.
I couldn't find an existing one, so I created a clam.conf and added debug=stake. I'm hoping I did it correctly. I added a screengrab of data flow.
http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight. And then other times it says not staking because I don't have mature coins. But then I stake at least once a day.
I'm sorry, I didn't notice your reply until now.
That screenshot looks like it didn't have "debug=stake" in the clam.conf. Maybe you put the clam.conf in the wrong folder, or didn't restart the client after editing it, or something else...
You can run the client with the -debug=stake flag to achieve the same effect without editing any files. When it's set, the logfile should show a bunch of [STAKE] messages every 16 seconds, like this:
[STAKE] searching for staking opportunity:
2015-03-04 18:33:05 [STAKE] checking 2 output(s)
2015-03-04 18:33:05 [STAKE] check 4b669d099edc650be18f19695fad64057eb5aded6f1a8f0f55f2f47601acfbf3:0 (0.0001 CLAM)
2015-03-04 18:33:05 [STAKE] fail: hash ac18df140e5080e0ed6553d10b31ce2baf675bdb852223c3d6495349f44ba3ae
2015-03-04 18:33:05 [STAKE] > target 43b056b0000000000000000000000000000000000000000000000000
2015-03-04 18:33:05 [STAKE] check 4b669d099edc650be18f19695fad64057eb5aded6f1a8f0f55f2f47601acfbf3:1 (100.9814 CLAM)
2015-03-04 18:33:05 [STAKE] fail: hash ce2be821048a46acc0ea14932bc615758388556abb380c220b48852ee09eb4b5
2015-03-04 18:33:05 [STAKE] > target 412fc60da4b20000000000000000000000000000000000000000000000000
2015-03-04 18:33:05 stake took 0s
That's my two outputs trying but failing to stake yet again.
I'm wondering if your "checking 2 outputs()" count goes down to 0 when the icon goes red, and if so whether the log says anything about it.