accounts: unlock multiple accounts fails #1785
Comments
obscuren
changed the title
* lines with leading space are ommitted from history * exit processed even with whitespace around * all whitespace lines (not only empty ones) are ignored add 7 missing commands to admin api autocomplete registrar: methods now return proper error if reg addresses are not set. fixes #1457 rpc/console: fix personal.newAccount() regression. Now all comms accept interactive password registrar: add registrar tests for errors crypto: catch AES decryption error on presale wallet import + fix error msg format. fixes #1580 CLI: improve error message when starting a second instance of geth. fixes #1564 cli/accounts: unlock multiple accounts. fixes #1785 * make unlocking multiple accounts work with inline <() fd * passwdfile now correctly read only once * improve logs * fix CLI help text for unlocking fix regression with docRoot / admin API * docRoot/jspath passed to rpc/api ParseApis, which passes onto adminApi * docRoot field for JS console in order to pass when RPC is (re)started * improve flag desc for jspath common/docserver: catch http errors from response fix rpc/api tests common/natspec: fix end to end test (skipped because takes 8s) registrar: fix major regression: * deploy registrars on frontier * register HashsReg and UrlHint in GlobalRegistrar. * set all 3 contract addresses in code * zero out addresses first in tests
|
I believe this has already been fixed in #1840 |
|
Closing if supposedly fixed. Please reopen if it's not the case. Also note, an upcoming PR will change the account list to comma separated values instead of space separated ones. This is a general move towards eliminating whitespace from within CLI arguments as they cause significant pains when passing through different environments (e.g. bash -> go -> docker -> bash). |
|
Sorry for my late reply! Just tried it now and it's still not working in version |
|
I'll take a look |
|
I'm also seeing this with geth 1.3.5 - trying to unlock more than one account via |
|
Hello guys, Help! |
* Added new flags for http timeouts * Update cmd/utils/flags.go Co-authored-by: piersy <pierspowlesland@gmail.com> * Update cmd/utils/flags.go Co-authored-by: piersy <pierspowlesland@gmail.com> * Update cmd/utils/flags.go Co-authored-by: piersy <pierspowlesland@gmail.com> * Do not duplicate default timeout variables * Normalice default timeout values to seconds * Update eth/protocols/snap/sync.go Revert message Co-authored-by: piersy <pierspowlesland@gmail.com> Co-authored-by: Gaston Ponti <pontigaston@gmail.com>
When trying to use
--unlock="0 1"geth fails with the message:Fatal: Unlock account failed 'Decryption failed: MAC mismatch'. The first account is unlocked and the messageAccount '0' unlockedis printed.It's important to note that
unlock="0"ANDunlock="1"both works! Also, if you invert the order ("1 0" instead of "0 1"), it printsAccount '1' unlockedand then fails to unlock second account with same message. So, the problem is clearly related to unlock multiple accounts and problem always happens on second account.The text was updated successfully, but these errors were encountered: