Most of the time farming status is not synced or not connected to peers

I cant seem to figure out why my setup keeps displaying this…

Farming status: Not synced or not connected to peers

I from time to time see it switch to,

Farming status: Farming

But most of the time its not sync’d

Current Blockchain Status: Not Synced.
Peak height:               280490
Time:                      Fri May 14 2021 16:20:58 America
Height:                    280490

This Height keeps incrementing. I dont know if this is by design? Am I not farming while its Syncing?

3 Likes

Farming status: Not synced or not connected to peers
Total chia farmed: 2.0
User transaction fees: 0.0
Block rewards: 2.0
Last height farmed: 273726
Plot count: 21
Total size of plots: 2.079 TiB
Estimated network space: 4808.511 PiB
Expected time to win: 1 year and 2 months
Note: log into your key using ‘chia wallet show’ to see rewards for each key

Re installed the application, It was farming for a bit then stopped again.

I see this popping up from time to time in the logs…

2021-05-14T19:10:03.786 harvester chia.harvester.harvester: INFO 0 plots were eligible for farming

But I in spurts.

I can confirm port 8444 open externally.

1 Like

So the problem is that you are sometimes disconnected? But otherwise you can farm fine most of the time? For how long and how often are you not synced, can you describe the schedule? Or the opposite, when and how often are you synced?

Looks as is I am syncing for several spurts. But now I have had any messages about eligible plots for almost 30 minutes. Had several before here and there.

2021-05-14T19:07:51.881 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:07:51.893 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:08:52.056 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:02.455 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:02.468 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:02.473 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:02.483 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:25.367 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:25.378 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:35.815 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:35.826 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:35.835 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:35.841 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:09:35.847 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:03.778 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:03.786 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:34.198 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:39.966 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:39.978 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:39.991 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:39.994 harvester chia.harvester.harvester: INFO     0 plots were eligible for
2021-05-14T19:10:55.754 harvester chia.harvester.harvester: INFO     0 plots were eligible for

Stopped at 19:10 and havent seen one since.

FYI @yamen I’ve formatted your logs. Do have a look out for the </> button in the toolbar to help make things readable. :+1:

I have yet to master posting logs. But I can honestly say its not due to a lack of trying. Thank you.

I have another PC at another location (Different Internet connection) and I am getting same issue. It farms for a while then stops. One machine is linux the other is Windows.

Something not right, Just dont know if its me or not me…

The Windows PC just says “Not Synced” in red. Yet says connected next to it.

And as I was typing this it went to Synced again… Two different locations two different machines same similar issue.

Not sure if the same issue - I’ve been farming with a Raspberry Pi 4 (that includes running the full node on it) and since some time earlier this week it’s been having terrible keeping up with the network. Flopping between synced and not synced, but even when synced the challenges came in late or were missed. And yes I’m on 1.1.5 since it came out. Today I’ve given up and moved farming to my PC, and that manages to stay synced.

The Pi had similar problems when transactions went live. The transaction volume was just too high to keep up. There’s been code optimizations since then, and after the initial flurry the Pi was able again to keep up. But perhaps in recent days the transaction volume has picked up, and now it’s too much again. Could be caused by additional exchanges opening.

There are some recommendations to lower the peer count so that the full node doesn’t need to process so much, but then it’s more likely to have no good peers that are actually synced. On my PC with 100 peers, I see less than half the peers are on the current height.

Check if your chia_full_node process consistently uses more than 100% CPU. I think in this case the machine is simply not fast enough to keep up with the network. I fear the chia software is still too unoptimized to reliably run a full node on a lower spec machine.

1 Like

I agree to an extend, I think it has something to do with to high of network transactions.

My linux machine is a Docker. System is fairly robust. It should be able to handle it. The windows machines is fully dedicated to Chia… Should have no issues at all.

Sure enough it’s not synced again on both machines.

Looks like there are several similar issues brought up on GitHub, So its a wider spread issue. Kind of a bummer.

1 Like

Can you link to the issues? That’d be helpful.

&

Are the most active ones.

1 Like

I had this issue. I quickly solved it by opening port 8444 on my router. You can check with Open Port Check Tool - Test Port Forwarding on Your Router (yougetsignal.com) using your public IP

Ya earlier in the post i stated that i confirmed port 8444 is open.

I have been experiencing intermittent sync lately as well. The issue seemed to have started after the 1.1.4hotfix, but I don’t know if it is related. The keybase support channel indicates this is a common issue and there is hope that the next update will help.

Manually adding the local introducer seems to have helped on my end, but I don’t know if it is fully resolved. Resolving Sync Issues Port 8444 · Chia-Network/chia-blockchain Wiki · GitHub

In addition to the logs, I have begun to keep an eye on connections as well. Even with the introducer my peer count is low (<10)
chia show -c | grep FULL_NODE

Hope you get things sorted out on your end, this is a frustrating situation for many at the moment.

Ya earlier in my post I stated that I confirmed port 8444 is open externally.

Is it possible to clarify about which IP port 8444 should be open for? I’m behind a GCNAT. 8444 is open when my external address matches my remote address, but closed when I use my Pi’s IPv4 as my remote address. Should this setup be fine? My Pi won’t sync, but things work fine on my PC. Both are connected to the same network. chia-blockchain v1.1.7