Cant start plotting

Support
1

Pulsar built from latest available sources. After sync finished node just dies with error.

Starting node ...
Node started successfully!
 ◟  [00:11:30] 100% [█████████████████████████████████████████████████████████████] (462250/462250) 669.35bps, Initial syncing is completed! Syncing will continue in the background..., ETA: 00:00:00
Starting farmer ...
Farmer started successfully!
Initial plotting for farm: #0 (/node/subspace_farms)
 ◠  [00:00:00] 0% [                                                                                                                                  ] (0 B/419.10 GiB) 0 B/s, plotting, ETA: 00:00:00
The application panicked (crashed).
Message:  A Tokio 1.x context was found, but it is being shutdown.
Location: /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.34.0/src/runtime/time/entry.rs:556

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Error:
   0: waiting on farmer failed
   1: solution subscription crashed
   2: parallel block stream couldn't be processed
   3: couldn't get rewards, votes and author info
   4: error in stream encountered in try_fold step
   5: Failed to decode events
   6: Could not decode `EventRecord::phase`:
   6:   Could not decode `Phase`, variant doesn't exist
   6:
   7: Could not decode `Phase`, variant doesn't exist

Location:
   src/utils.rs:327

Suggestion: If you think this is a bug, please submit it to our forums: https://forum.autonomys.xyz
2 Likes
2

I’m having a similar issue - anyone have a suggestion?

3

@Parth any idea what could be happening here? Would you like an issue raised?

4

This is the error I keep getting:

Initial plotting for farm: #0 (/root/.local/share/pulsar/farms)
[00:00:00] 100% [████████████████████████████████████████] (1.86 GiB/1.86 GiB) Initial plotting finished!

The application panicked (crashed).
Message: A Tokio 1.x context was found, but it is being shutdown.
Location: /home/ubuntu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.34.0/src/runtime/time/entry.rs:556

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Error:
0: waiting on farmer failed
1: solution subscription crashed
2: parallel block stream couldn’t be processed
3: couldn’t get rewards, votes and author info
4: error in stream encountered in try_fold step
5: Failed to decode events
6: Could not decode EventRecord::phase:
6: Could not decode Phase, variant doesn’t exist
6:
7: Could not decode Phase, variant doesn’t exist

Location:
src/utils.rs:327

Suggestion: If you think this is a bug, please submit it to our forums: https://forum.autonomys.xyz

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
root@vmi1542944:~#

5

I have the same error when running the latest plusar client

6

subspce
subspce1425×78 3.59 KB

is this normal?

7

I will take a look. Can you tell me for which network this error is encountered? (i.e Local, DevNet or Gemini3g)?

8

@ydanila90 Also, you mentioned that you have built the pulsar client from latest available sources. Just to confirm, does this mean you compiled pulsar from the source? If yes, Can you send me the commands as well as the source code commit for subspace, subspace-sdk and pulsar?

If no, Can you tell me which version of Pulsar this is? You can take a look at release description, you downloaded binary from.

9

It was built from latest available commit for that moment 0a215289fc6c77a04b6b152d8c6a77aad0904fd2

All comand from your github

cargo build
cargo build --release
cargo install --path .

After wipe all, init and farm

Topic not correct - “Cant start faming”.

10

Can you try with latest commit?
f1702c7d63256dfb55910dfe3d164a7cb1472b69

11

I’m using the latest commit but I still get that error too. On Gemini 3G.

12

Same error after sync finished.

13

I have a similar error today 8th Jan 2024. Fresh install using v 0.7.2 (downloaded yesterday) as shown below…

root@vmi1290023:/usr/local/bin# ./subspace-cli init

/\ \ /\ \ /\ \/\ \ /\ \__ /\ \ \ \,\L\_\ __ __\ \ \____ ____ _____ __ ___ __\ \ \ \ __\ \ ,\ __ __ __ ___ _ \ \ /’
/_ \ /\ /\ \ \ '\ /',__\/\ '__\ /‘\ /'___\ /'__\ \ , \ /'__\ \ / /\ /\ /\ \ / \/\'\ \ , <
/\ \L\ \ \ _\ \ \ \L\ /_, \ \ \L\ \/\ \L\.\_/\ \__//\ __/\ \ \\ /\ /\ \ _\ \ _/ _/ /\ \L\ \ \ / \ \ \\ \ _\ _/ \ _,//_/\ \ ,/\ _/._\ _\ _\ _\ _\ _\ _\ _x/’\ _/\ _\ \ _\ _
//// // // \ \ / //////// /////___/ // //// // // ////
\ _
//

version: 0.7.2

Configuration creation process has started…
Do you have an existing farmer/reward address? [y/n]: y
Enter your farmer/reward address: stAA8jNbFzmDY7qYAtwDepcvQFG8cibf4Xh5PnNUos7GBYKhD
Enter your node name to be identified on the network(defaults to root, press enter to use the default): stewfar
Specify a path for storing farm files (press enter to use the default: "/root/.local/share/pulsar/farms"):
Specify a path for storing node files (press enter to use the default: "/root/.local/share/pulsar/node"):
Specify a farm size (defaults to 2.0 GB, press enter to use the default):
Specify the chain to farm. Available options are: [Gemini3g, Dev, DevNet].
Defaults to Gemini3g, press enter to use the default:
Configuration has been generated at /root/.config/pulsar
Ready for lift off! Run the follow command to begin:
"./subspace-cli" farm
root@vmi1290023:/usr/local/bin# ./subspace-cli farm
Starting node …
Node started successfully!
◟ [1d 03:46:40] 100% [█████████████████████████████████] (1014223/1014223) 10.14bps, Initial syncing is completed! Syncing will continue in the background…, ETA: 00:00:00 Starting farmer …
Farmer started successfully!
Initial plotting for farm: #0 (/root/.local/share/pulsar/farms)

The application panicked (crashed).
Message: A Tokio 1.x context was found, but it is being shutdown.
Location: /home/ubuntu/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.34.0/src/runtime/time/entry.rs:556

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Error:
0: waiting on farmer failed
1: solution subscription crashed
2: parallel block stream couldn’t be processed
3: couldn’t get rewards, votes and author info
4: error in stream encountered in try_fold step
5: Failed to decode events
6: Could not decode EventRecord::phase:
6: Could not decode Phase, variant doesn’t exist
6:
7: Could not decode Phase, variant doesn’t exist

Location:
src/utils.rs:327

Suggestion: If you think this is a bug, please submit it to our forums: https://forum.autonomys.xyz

I have looked into the farms folder and this is my ls-ltr output…

root@vmi1290023:~/.local/share/pulsar/farms# ls -ltr
total 1950932
-rw-r–r-- 1 root root 33 Jan 8 22:03 identity.bin
-rw-r–r-- 1 root root 252 Jan 8 22:03 single_disk_farm.json
-rw-r–r-- 1 root root 1179692 Jan 8 22:03 metadata.bin
-rw-r–r-- 1 root root 1056896064 Jan 8 22:03 plot.bin
-rw-r–r-- 1 root root 939645952 Jan 8 22:04 piece_cache.bin

My node was registered and showing up on Gemini3g network:
https://telemetry.subspace.network/#list/0x418040fc282f5e5ddd432c46d05297636f6f75ce68d66499ff4cbda69ccd180b

My diskspace is at 72% so enough disk space for the node.

Can anyone please assist?

Thanks
Stewart

14

Please upgrade to pulsar v0.7.4 which fixes this issue as well as general fix with syncing.