I noticed that chia.net lists version 1.1.6 as out with release notes, but the download links still lead to the 1.1.5 executable for windows. I haven’t checked my linux machine yet.
Is the file hidden somewhere? I noticed the release notes have a zip of the source code, but I didn’t want to do a dirty hack/replace and mess something up.
Hmm… 1.1.6 no longer shows info in logs about sending signage points to the remote harvesters / receiving farming info from remote harvesters… The harvesters are showing challenges, but usually I can just look at the full node and see that all 4 are responding.
edit: asked in keybase. response: all networking logs are removed from INFO, they are in DEBUG now. sadface.
New farm logs for remote harvesters only available under DEBUG log level:
2021-05-21T05:03:18.071 farmer farmer_server : DEBUG <- new_signage_point from peer c131xxxx 127.0.0.1
2021-05-21T05:03:18.072 farmer farmer_server : DEBUG -> new_signage_point_harvester to peer 192.168.141.211 dcc1xxxx
2021-05-21T05:03:18.072 farmer farmer_server : DEBUG -> new_signage_point_harvester to peer 192.168.141.177 adc2xxxx
2021-05-21T05:03:18.072 farmer farmer_server : DEBUG -> new_signage_point_harvester to peer 192.168.141.138 53adxxxx
2021-05-21T05:03:18.073 farmer farmer_server : DEBUG -> new_signage_point_harvester to peer 192.168.141.134 97faxxxx
2021-05-21T05:03:18.073 farmer farmer_server : DEBUG Time taken to process new_signage_point from c131xxxx is 0.0019631385803222656 seconds
2021-05-21T05:03:18.084 farmer farmer_server : DEBUG <- farming_info from peer 97faxxxx 192.168.141.134
2021-05-21T05:03:18.085 farmer farmer_server : DEBUG Time taken to process farming_info from 97faxxxx is 0.0005400180816650391 seconds
2021-05-21T05:03:18.141 farmer farmer_server : DEBUG <- farming_info from peer adc2xxxx 192.168.141.177
2021-05-21T05:03:18.141 farmer farmer_server : DEBUG Time taken to process farming_info from adc2xxxx is 0.0006067752838134766 seconds
2021-05-21T05:03:18.180 farmer farmer_server : DEBUG <- farming_info from peer 53adxxxx 192.168.141.138
2021-05-21T05:03:18.180 farmer farmer_server : DEBUG Time taken to process farming_info from 53adxxxx is 0.0005393028259277344 seconds
2021-05-21T05:03:18.254 farmer farmer_server : DEBUG <- farming_info from peer dcc1xxxx 192.168.141.211
2021-05-21T05:03:18.254 farmer farmer_server : DEBUG Time taken to process farming_info from dcc1xxxx is 0.0006356239318847656 seconds
Plotting does not require a live Internet connection, many of us use idle or additional machines to run plotting using the same one key that we use on our farmer(Full Node) that is connected to the internet. We then move over the new plots made on the additional machines (the plotters) onto the Full Node. Sorry, did not mean to cause the confusion.
Generally, plotters are lined up with jobs and are in between jobs, so cannot update them without bringing plotting to a complete halt (similar to bringing a conveyor belt production line to a halt). So if the exercise is redundant, many of us might not want to update the plotters… If it is essential to do so, then we will have to…
I have been plotting on a separate machine and copying those plots over to my full node machine. But due to my full node machine refusing to sync, I have not been able to (or do not know how to) confirm that the remotely created plots will actually work with my full node machine.
Is there a command I could run, on my full node machine, to have it test a specific plot so that it will tell me “yay” or “nay” on whether that plot will be given the green light upon eventually syncing?
The command that I use to create the remote plots is:
chia create -t some_ssd_temp_dir -d some_spinning_hard_drive_dir -f some_value -p some_other_value
For the above -f and -p values, I got them from running
chia keys show
…and get the -f value from the “Farmer public key”,
…and get the -p value from the “Pool public key”.
Can you please confirm that I am doing this correctly, and how to have my full node machine verify that the remotely made plots are good?