hi - We stopped plotting as we have 10 x 14TB WD external plus 10 toshiba N300 sata 8TB x internal hardrives full too.
The time to win has been stating 1 month - however - we have not received any chia at all for 3 months now or since we stopped plotting. I am just asking for advice as thinking of just wrapping it up and selling drives second hand really as feel electric element is ridiculous for not gaining anything.
We started about 8 months ago and have only ever received a total of 6 chia? Not what I expected.
When you check Poisson distribution, that 3x delay is rather not a big deal. I know, it is frustrating, but nothing you can do about it, potentially bad luck (I also should have won few block, but just hit one).
Having said that, in addition to what @Bones said, are your checking your responses? Are they (virtually) all below 5 secs? If you are member of some pool, did you check how many stalled partials they report? (Just by browsing some pools, I saw that a lot of people have around 20% bad (stalled) replies. Unfortunately, those pool owners don’t give rat’s asses about it, thus hurting farmers, and their pools.)
I am having similar issues! It’s very disheartening! I have a 300 TiB farm. Estimated time to win is currently 26 days. I haven’t won in 75 days. I’ve checked my lookup times and everything seems ok. I can’t find any problems in my logs except a line about pool.garden not being able to connect or something. I’m still earning from space pool, so I’m guessing my node is working correctly. Lookup times are below 1 sec.
Take a look at that video, and download that Excel document. Again, having 2x or 3x delay is rather normal. That expected time is just 50% probability of winning a block (i.e., getting your head rather than tail when doing just one coin toss).
I understand some delay… But come on. 3x delay? If the estimated time to win is gonna be 3x or greater wrong, they should just remove it all the way. Not really any point in having it on there if you can’t use it as a guide… Am I wrong? I am pooling, so the pain is not really that great, but I’d be PISSED if I was solo! That would mean I had around 7 grand sunk into this with zero earnings in 3 months! I mean come on… That’s nonsense. I just think that the estimated time to win is extremely misleading, and should be removed all together. That’s all I was getting at. I knew going into this that this could happen. It is the sole reason that I switched to the pooling protocol. Read way too many horror stories of the same thing happening to other people. I’m interested to see how high I can get the day count actually.
In simple terms, you can look at your winnings as coin tosses. One such coin toss is 2x your estimated time to win (ETW). So, your second coin toss ends at 4x your ETW. So, with your 3x delay, you are still on your second coin toss.
Just watch that video, run that Excel with your data. That is just math, not sentiments.
Are you or @Bones any good at deciphering the logs? I have a couple of questions. About my farmer response times. Is this the line I should be looking at to get my farmer response times?
2021-10-31T13:46:25.196 full_node chia.full_node.full_node: INFO Added unfinished_block 66074ca4ee2230080e4de3d9946562d8bbfc43f7c95dfdf2e4fcde6663722fa5, not farmed by us, SP: 4 farmer response time: 12.1260, Pool pk xch1hh570r0ffh2yzt4rln9jq0uadvfuvd5kam9dayymjernf5x2kqwsv8nma5, validation time: 0.5177 seconds, cost: 3973930068, percent full: 36.127%
or should I be looking at
2021-10-31T13:46:05.204 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming 155e421836... Found 0 proofs. Time: 0.00719 s. Total 516 plots
Also, one more question if I may. What is up with this SSL error when trying to connect to other nodes? Could this be causing me issues? It doesn’t seem to have this error every time it tries to connect to a node. It’s kind of sporadic.
2021-10-31T13:46:10.934 full_node full_node_server : INFO Cannot connect to host 90.174.132.53:8444 ssl:<ssl.SSLContext object at 0x7fb125e9bc40> [Connect call failed ('90.174.132.53', 8444)]
And below is my full log if any of you guys feel like taking a look at it to see if you can identify any issues that I need to address. I thought I had it up and running pretty smoothly. Sorry to hijack the thread also. Didn’t mean to do that.
Ok. Thanks. The line that I used for the validation time was actually a really low one. Those times can get up much higher on my setup. Also, I have multiple harvesters connecting to this node. I guess it doesn’t show the times for those, but they all seem within expectation.
I feel you. I went 4th of July to Nov 18 with no wins on 19-20 days TTW. Then I hit three times a in week. Mean reversion will happen, just wait for it.
2021-10-31T20:57:48.518 harvester chia.harvester.harvester: INFO 4 plots were eligible for farming b596d9650b… Found 0 proofs. Time: 0.95833 s. Total 1242 plots
2021-10-31T20:58:02.582 full_node chia.full_node.full_node_store: INFO Don’t have rc hash 3ae9aebf7fb751c01f6f9b7f1335d5b7b3ee86eebb7873c34c4ac55bcbaa7593. caching signage point 57.
2021-10-31T20:58:02.608 full_node chia.full_node.full_node_store: INFO Don’t have rc hash 3ae9aebf7fb751c01f6f9b7f1335d5b7b3ee86eebb7873c34c4ac55bcbaa7593. caching signage point 58.
2021-10-31T20:58:02.633 full_node chia.full_node.full_node_store: INFO Don’t have rc hash 3ae9aebf7fb751c01f6f9b7f1335d5b7b3ee86eebb7873c34c4ac55bcbaa7593. caching signage point 59.
2021-10-31T20:58:02.656 full_node chia.full_node.full_node_store: INFO Don’t have rc hash 3ae9aebf7fb751c01f6f9b7f1335d5b7b3ee86eebb7873c34c4ac55bcbaa7593. caching signage point 60.
2021-10-31T20:58:02.680 full_node chia.full_node.full_node_store: INFO Don’t have rc hash 3ae9aebf7fb751c01f6f9b7f1335d5b7b3ee86eebb7873c34c4ac55bcbaa7593. caching signage point 61.
2021-10-31T20:58:04.626 full_node chia.full_node.full_node_store: INFO Don’t have challenge hash fd485399912a4eb45d945466e4c4f09ffe55681653c57c1342701be114e46cb9, caching EOS
2021-10-31T20:58:04.628 full_node chia.full_node.full_node: INFO End of slot not added CC challenge b596d9650bf608148f9175616a5b2a0a2e4097da64cfe57ad101ab00edfe1f4e
2021-10-31T20:58:04.693 full_node chia.full_node.full_node_store: INFO Don’t have challenge hash fd485399912a4eb45d945466e4c4f09ffe55681653c57c1342701be114e46cb9, caching EOS
2021-10-31T20:58:04.694 full_node chia.full_node.full_node: INFO End of slot not added CC challenge b596d9650bf608148f9175616a5b2a0a2e4097da64cfe57ad101ab00edfe1f4e
2021-10-31T20:58:04.696 full_node chia.full_node.full_node_store: INFO Don’t have challenge hash fd485399912a4eb45d945466e4c4f09ffe55681653c57c1342701be114e46cb9, caching EOS
Getting other errors also???
