Gemini 3c pre-release testing - how do i know plotting is working?

Hello, I have installed the jan-27 pre-release and configured a node and farmer. The farmer is able to connect to the node, I can see so in the node’s stdout.

The farmer does not post anything to the stdout to indicate it’s actually plotting. What am I missing? The farmer’s stdout just stays at

[srv_subspace@node-9 subspace]$ ./farmer.sh |grep -v "Couldn't get a piece from DSN. Retrying" 2023-01-27T19:08:52.405380Z INFO subspace_farmer::utils: Increase file limit from soft to hard (limit is 1048576) 2023-01-27T19:08:52.405529Z INFO subspace_farmer::commands::farm: Connecting to node RPC at ws://127.0.0.1:62401 2023-01-27T19:08:52.406839Z INFO subspace_farmer::commands::farm::dsn: Record cache DB configured. piece_cache_db_path="/sub/dbs/disk01//piece_cache_db" piece_cache_size=65536 provider_cache_db_path="/sub/dbs/disk01//provider_cache_db" provider_cache_size=655360 2023-01-27T19:08:52.407453Z INFO subspace_networking::behavior::provider_storage::providers: New record cache initialized. path="/sub/dbs/disk01//provider_cache_db" 2023-01-27T19:08:52.407774Z INFO subspace_farmer::utils::farmer_piece_cache: New local piece cache initialized. 2023-01-27T19:08:52.407983Z INFO subspace_networking::create: DSN instance configured. allow_non_global_addresses_in_dht=false peer_id=..... 2023-01-27T19:08:52.409891Z INFO subspace_farmer::commands::farm: Connecting to node RPC at ws://127.0.0.1:62401 2023-01-27T19:08:52.449034Z INFO subspace_farmer::single_disk_plot: Subscribing to slot info notifications 2023-01-27T19:08:52.449041Z INFO subspace_farmer::reward_signing: Subscribing to reward signing notifications

The farmer’s command

name=“s99-0001”
base_path=“/sub/dbs/disk01/$name/”
farm_path=“/sub/plots/disk01/$name/”
mkdir -p “$base_path”
mkdir -p “$farm_path”

cmd="./target/production/subspace-farmer
–base-path $base_path
–farm path=$farm_path,size=700G
farm
–node-rpc-url ws://127.0.0.1:12999
–listen-on /ip4/0.0.0.0/tcp/15999
–reward-address …
–disable-private-ips
"

1 Like

Hours later, the plot file has not been written to, not even accessed at all. I have mounted the drive with access time enabled.

[srv_subspace@pnode-12 subspace]$ stat /sub/plots/disk01/s99-0001/plot.bin File: /sub/plots/disk01/s99-0001/plot.bin Size: 699979005952 Blocks: 1367146640 IO Block: 4096 regular file Device: 8,0 Inode: 51717 Links: 1 Access: (0644/-rw-r--r--) Uid: (30333/srv_subspace) Gid: ( 9998/ farming) Context: unconfined_u:object_r:unlabeled_t:s0 Access: 2023-01-27 13:55:55.388089375 -0500 Modify: 2023-01-27 13:55:55.380089370 -0500 Change: 2023-01-27 13:55:55.388089375 -0500 Birth: 2023-01-27 13:41:50.591525474 -0500

[srv_subspace@pnode-12 subspace]$ ls -lh /sub/plots/disk01/s99-0001/ total 653G -rw-r--r--. 1 srv_subspace farming 33 Jan 27 13:41 identity.bin -rw-r--r--. 1 srv_subspace farming 1011M Jan 27 13:41 metadata.bin -rw-r--r--. 1 srv_subspace farming 652G Jan 27 13:55 plot.bin -rw-r--r--. 1 srv_subspace farming 271 Jan 27 13:41 single_disk_plot.json

I also encountered the same problem as you

1 Like

I have been watching the plot file and creating sha256 checksums with days in between of what looked like successful node/farming… How come the plot file doesn’t change?

[srv_subspace@pnode-12 subspace]$ sha256sum /sub/plots/disk01/s99-0001/plot.bin
fa25e4067ef8a4103fdcc843fcddfb4697e2423e1c90fee7e286d15164f072f7 /sub/plots/disk01/s99-0001/plot.bin

3 days of farming in between… Has not changed the plot file at all…

[srv_subspace@pnode-12 subspace]$ sha256sum /sub/plots/disk01/s99-0001/plot.bin
fa25e4067ef8a4103fdcc843fcddfb4697e2423e1c90fee7e286d15164f072f7 /sub/plots/disk01/s99-0001/plot.bin

2 days of farming plus upgrade to gemini-3c-2023-feb-20… Has not changed the plot file at all…

[srv_subspace@pnode-12 subspace]$ sha256sum /sub/plots/disk01/s99-0001/plot.bin
fa25e4067ef8a4103fdcc843fcddfb4697e2423e1c90fee7e286d15164f072f7 /sub/plots/disk01/s99-0001/plot.bin

2 days of farming but the plot file still has not changed.

sha256sum /sub/plots/disk01/s99-0001/plot.bin
fa25e4067ef8a4103fdcc843fcddfb4697e2423e1c90fee7e286d15164f072f7 /sub/plots/disk01/s99-0001/plot.bin

How can I confirm plotting is working?

The issue has been resolved as of Allow DNS records in DSN by nazar-pc · Pull Request #1185 · subspace/subspace · GitHub