Quote from: shawn2025 on March 01, 2015, 05:01:50 AM

Quote from: Evil-Dragon on February 28, 2015, 09:03:01 PM

Quote from: rocoro on February 28, 2015, 08:53:28 PM

Quote from: shawn2025 on February 28, 2015, 08:00:41 PM

Quote from: dooglus on February 28, 2015, 08:40:32 AM

Quote from: shawn2025 on February 28, 2015, 06:39:42 AM

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.

Hope this helps. Thanks for everything!

/s/

Same thing was happening to me on a previous version (1.4.7 i think) and the 0 weight was also showing.
I haven't seen it happen to me again yet on this latest version.. but I'll watch for it.

It can stay red for up to one minute, i've seen it myself. When you hover over it says 'Not staking because you don't have mature coins'

It doesn't appear to affect staking in the long run, i always just put it down to new blocks being generated and that it was a normal thing.

I have the debug switch on at the moment so i'll try and upload the debug.log next time i see it happen.

I think I caught a red patch in the debug log. This is the point where it was red and then normalized:

ERROR: AcceptToMemoryPool : ConnectInputs failed 275b33ea6daf21907648b93235e33942d63c759c139efe8135f9e88a02aec89f
ERROR: ConnectInputs() : afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e prev tx already used at (nFile=1, nBlockPos=319403622, nTxPos=319404329)
ERROR: AcceptToMemoryPool : ConnectInputs failed afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e
ERROR: ConnectInputs() : 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7 prev tx already used at (nFile=1, nBlockPos=342165995, nTxPos=342168405)
ERROR: AcceptToMemoryPool : ConnectInputs failed 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7
ERROR: ConnectInputs() : 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62 prev tx already used at (nFile=1, nBlockPos=342323040, nTxPos=342323537)
ERROR: AcceptToMemoryPool : ConnectInputs failed 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62
ERROR: ConnectInputs() : 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1 prev tx already used at (nFile=1, nBlockPos=342592588, nTxPos=342593400)
ERROR: AcceptToMemoryPool : ConnectInputs failed 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1
stake took 0s
stake took 0s
stake took 0s
stake took 0s
SetBestChain: new best=c4f00cb1bd10f1465095c98ace135a9cde9beff8f28f92469835487faf060c35 height=360756 trust=16799287784950803720 blocktrust=156701501658267 date=03/01/15 04:48:48
ProcessBlock: ACCEPTED
stake took 0s
SetBestChain: new best=8e2c754fd4bcadb59b715244d7f885f2059120b7d862f0b0e29f1c01e929a9c7 height=360757 trust=16799443607527302960 blocktrust=155822576499240 date=03/01/15 04:49:20
ProcessBlock: ACCEPTED
stake took 0s
SetBestChain: new best=8aec101da5519366c1b71c094f9ddf4d213860433299fd918f89ef03b83a62d6 height=360758 trust=16799598557078531095 blocktrust=154949551228135 date=03/01/15 04:49:36
ProcessBlock: ACCEPTED

Any update on why this happens ? Mine seemed to stay red longer this morning
Edit: also seems to be happening more frequently (icon turning red)

Edit #2: Restarted wallet and symptom seems to have mysteriously disappeared (for now?)