Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slasher: PROCESS can be beacon-chain or validator. #5735

Closed
ncsolar opened this issue May 4, 2020 · 2 comments · Fixed by #5747
Closed

Slasher: PROCESS can be beacon-chain or validator. #5735

ncsolar opened this issue May 4, 2020 · 2 comments · Fixed by #5747

Comments

@ncsolar
Copy link

ncsolar commented May 4, 2020

🐞 Bug Report

Description

When I try the command ./prysm.sh slasher i get errors

Has this worked before in a previous version?

Yes, the previous version in which this bug was not present was

🔬 Minimal Reproduction

When i run the command ./prysm.sh slasher

🔥 Error


Latest Prysm version is v1.0.0-alpha.6.
Beacon chain is up to date.
Validator is up to date.
Usage: ./prysm.sh PROCESS FLAGS.
PROCESS can be beacon-chain or validator.
Starting Prysm slasher 
./prysm.sh: line 131: process: unbound variable

🌍 Your Environment

Operating System:

  

PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
  

What version of Prysm are you running? (Which release)

  
v1.0.0-alpha.6.
  

Anything else relevant (validator index / public key)?

@ncsolar
Copy link
Author

ncsolar commented May 4, 2020

Update the error went away after deleting slasher.db

@farazdagi
Copy link
Contributor

farazdagi commented May 5, 2020

I suppose the issue is not that much with slasher.db but with incorrect argument (typo, prbly?) passed to process. If you type ./prysm.sh foo-bar you will get the error. #5747 should fix the issue or properly reporting when invalid process name is provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants