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

parity build from master branch not work when use POA,No valid password for the consensus signer! #11521

Closed
passionofvc opened this issue Feb 26, 2020 · 1 comment · Fixed by #11524
Labels
F2-bug 🐞 The client fails to follow expected behavior. P5-sometimesoon 🌲 Issue is worth doing soon. Q3-medium A fair chunk of work, not necessarily very hard but not trivial either

Comments

@passionofvc
Copy link

Hey ! I can not use parity build from master to run below POA node, it always show
password not right even the password is OK,and the problem is build from master branch.
When I build from https://github.com/OpenEthereum/open-ethereum/archive/v2.7.2.tar.gz
it can run and start node normally, so Why master branch not work, or may be a latent bug?
The POA node script is from https://wiki.parity.io/Validator-Set-Tutorial-Overview

  • Parity Ethereum version: v2.8.0
    build from master branch source

  • reproduce step

$ git clone https://github.com/OpenEthereum/open-ethereum.git
$ cd OpenEthereum
$ cargo build --release --features final

# the parity created ok
$ ls -ltr target/release/
合計 136388
drwxrwxr-x.   2        6  2月 26 12:32 incremental
drwxrwxr-x.   2        6  2月 26 12:32 examples
drwxrwxr-x. 104     8192  2月 26 12:32 build
-rw-rw-r--.   2 94330720  2月 26 14:06 libparity_ethereum.rlib
-rwxrwxr-x.   2 45135480  2月 26 14:15 parity
drwxrwxr-x.   2    73728  2月 26 14:15 deps
-rw-rw-r--.   1    36792  2月 26 14:15 libparity_ethereum.d
-rw-rw-r--.   1    36819  2月 26 14:15 parity.d

$ git branch
* master

#OS
$ uname -a
Linux pb-app-01 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ ./parity  --version
Parity Ethereum Client.
  version Parity-Ethereum/v2.8.0-nightly-cd70180-20200225/x86_64-unknown-linux-gnu/rustc1.41.0
Copyright 2015-2020 Parity Technologies (UK) Ltd.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

By Wood/Paronyan/Kotewicz/Drwi?ga/Volf/Greeff
   Habermeier/Czaban/Gotchac/Redman/Nikolsky
   Schoedon/Tang/Adolfsson/Silva/Palm/Hirsz et al.

$ git clone https://github.com/Tbaut/Validator-set-tutorial.git
$ cd ~/Validator-set-tutorial/Full-setup
$bash start.sh
Loading config file from ./node0.toml
2020-02-26 18:56:19  Running AuRa with a single validator implies instant finality. Use a database?
2020-02-26 18:56:19  Starting Parity-Ethereum/v2.8.0-nightly-cd70180-20200225/x86_64-unknown-linux-gnu/rustc1.41.0
2020-02-26 18:56:19  Keys path node0/keys/Validator-set-tutorial
2020-02-26 18:56:19  DB path node0/chains/Validator-set-tutorial/db/fef38a67cfcd0963
2020-02-26 18:56:19  State DB configuration: fast
2020-02-26 18:56:19  Operating mode: active
No valid password for the consensus signer 0xa292…d64a. Make sure valid password is present in files passed using `--password` or in the configuration file.
@niklasad1
Copy link
Collaborator

@passionofvc

Thank you for reporting this, it is very surprising to me that 2.7.2 and master have different behavior because the functionality has not been changed AFAIK.

I have successfully reproduced this behavior.

@niklasad1 niklasad1 added F2-bug 🐞 The client fails to follow expected behavior. P5-sometimesoon 🌲 Issue is worth doing soon. Q3-medium A fair chunk of work, not necessarily very hard but not trivial either labels Feb 26, 2020
niklasad1 added a commit that referenced this issue Feb 26, 2020
Fixes #11521, caused by switching to `upstream rust-secp256k1`
ordian pushed a commit that referenced this issue Feb 27, 2020
* [EngineSigner]: don't sign message only zeroes

Fixes #11521, caused by switching to `upstream rust-secp256k1`

* address grumbles

* forgot formatting change
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. P5-sometimesoon 🌲 Issue is worth doing soon. Q3-medium A fair chunk of work, not necessarily very hard but not trivial either
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants