Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

ParaValidator has been disputed while client upgrade #6041

Closed
base1217 opened this issue Sep 22, 2022 · 2 comments
Closed

ParaValidator has been disputed while client upgrade #6041

base1217 opened this issue Sep 22, 2022 · 2 comments
Assignees
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.
Milestone

Comments

@base1217
Copy link

base1217 commented Sep 22, 2022

One of our validator has been disputed exact at same time when we were upgrading client.

Bellow some details:
12:22 - 12:25 UTC We were upgrading client from 0.9.28 to 0.9.29

Validator:15qomv8YFTpHrbiJKicP4oXfxRDyG4XEHZH7jdfJScnw2xnV
Event: ParasDisputes (https://polkadot.subscan.io/extrinsic/12059266-1)
Epoch: 5051
Block:12059266

Upgrade was by ansible, task steps:

  1. stop node through systemd(SIGTERM)
  2. Download and replace new version
  3. Safe start(will start if finalized block grew up at least 3 in 30 seconds)

Setup:
VM instance hosted in GCP - instance_type: c2d-highcpu-8, min_cpu_platform: "AMD Milan"
DB: RocksDB, pruned
PVF execution time <= 1s 100%

Events before stop:

2022-09-15 12:22:01 Detected invalid candidate as an approval checker. reason=ExecutionError("ambiguous worker death") candidate_hash=0xa2cfd2254a71c3d5e218d51cb7bb4e310d381049916350a7adabe5bcd4545972 para_id=Id(2030) traceID=216414003027371284759400717824118443569

2022-09-15 12:22:01 subsystem exited with error subsystem="approval-voting-subsystem" err=FromOrigin { origin: "approval-voting", source: Generated(TaskSpawn("get-approval-signatures")) }

2022-09-15 12:22:01 failed to send an execute request worker_pid=719645 validation_code_hash=0x5fb733293d5dc16e5a7c3daa1d504f0518fb0e3d1556f12be497df4d40030db4 error=Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }

@eskimor
Copy link
Member

eskimor commented Sep 22, 2022

Thank you very much - we are looking into it!

@eskimor eskimor added the T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes. label Sep 22, 2022
@eskimor eskimor self-assigned this Sep 22, 2022
@eskimor eskimor added this to the slashing milestone Sep 23, 2022
@eskimor
Copy link
Member

eskimor commented Nov 9, 2022

Fixed by: #6195

@eskimor eskimor closed this as completed Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T5-parachains_protocol This PR/Issue is related to Parachains features and protocol changes.
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants