Unable to restore wallet from seed phrase.

[gordonbrice]

Tried to restore my wallet from the seed phrase and got the attached error. Also attached the log file.

bisq.log

[ManfredKarrer]

Do you have the lastest Bisq version?

[gordonbrice]

Yes, I have the latest version. I was able to restore from backup and do Alt+J to recover my private keys. BTW, my wallet was password protected and I was able to do this without entering a password. This seems like a security hole.

…

-Regards Gordon

On Sun, Jan 27, 2019 at 9:55 PM Manfred Karrer ***@***.***> wrote: Do you have the lastest Bisq version? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACJn92EtW85Xf8k7R4nbRk2BbH41ehBtks5vHmacgaJpZM4aU4vF> .

[ManfredKarrer]

When you restore from seed the pw protection is removed.

[Mycelial1]

I've also got the same error.

I have the latest version.

[ghost]

@Mycelial1

• what is your OS ?
• do you have an AntiVirus AV running ?

[Mycelial1]

I'm using windows and there's no antivirus software running that I know of. I tried to restore a wallet from generated from a different wallet app (copay). Is that 'restore' function different than 'import' wallet?

…

On Sat, Feb 9, 2019, 5:36 AM Harry MacFinned ***@***.***> wrote: @Mycelial1 <https://github.com/Mycelial1> - what is your OS ? - do you have an AntiVirus AV running ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AhVOWmExu7yQ__gdJOeCNRnL8ykNGL4rks5vLqSngaJpZM4aU4vF> .

[ghost]

@Mycelial1 wrote:

Is that 'restore' function different than 'import' wallet?

My understanding is that it is the same restore function.
But restoring means restoring from a Bisq wallet (primary usage)
while importing means restoring from a non-Bisq wallet.

This will only work with compatible wallets, ie BIP44 format wallet, which is the format used by Bisq.
(see https://bisq.community/t/import-bitcoin-qt-wallet-to-bisq-or-another/4709)

However, I think this is to use only carefully.
The warning says "only for emergency cases".

[psyantyst]

I got the same error on Bisq v0.9.3. My wallet was backed up around Bisq version v0.5.1. The log file says:

[JavaFX Application Thread] ERROR b.c.b.s.WalletsSetup: Service failure from state: STARTING; failure={} java.io.IOException: org.bitcoinj.store.BlockStoreException: java.nio.channels.OverlappingFileLockException
	at bisq.core.btc.setup.WalletConfig.startUp(WalletConfig.java:492)
	at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:62)
	at com.google.common.util.concurrent.Callables$4.run(Callables.java:122)
	at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: org.bitcoinj.store.BlockStoreException: java.nio.channels.OverlappingFileLockException
	at org.bitcoinj.store.SPVBlockStore.<init>(SPVBlockStore.java:133)
	at bisq.core.btc.setup.WalletConfig.provideBlockStore(WalletConfig.java:329)
	at bisq.core.btc.setup.WalletConfig.startUp(WalletConfig.java:404)
	... 3 common frames omitted
Caused by: java.nio.channels.OverlappingFileLockException: null
	at java.base/sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255)
	at java.base/sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152)
	at java.base/sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:1191)
	at java.base/java.nio.channels.FileChannel.tryLock(FileChannel.java:1160)
	at org.bitcoinj.store.SPVBlockStore.<init>(SPVBlockStore.java:106)
	... 5 common frames omitted

[oscarguindzberg]

@psyantyst Your issue is described here #2402 and should be fixed once #2403 is merged.

@gordonbrice @Mycelial1 You seem to have a different problem, but I still suggest to double check if the problem is still there once #2403 is merged.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.