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

Bisq doesn't operate on remote NAS devices over SMBFS #5761

Closed
gregturn opened this issue Oct 17, 2021 · 4 comments
Closed

Bisq doesn't operate on remote NAS devices over SMBFS #5761

gregturn opened this issue Oct 17, 2021 · 4 comments

Comments

@gregturn
Copy link

Description

Bisq works great on my local Mac. But when I move my wallet to a remote RAID-based NAS (over SMBFS), it can't launch properly and thus fails to get started.

Version

1.7.4

Steps to reproduce

  1. Install latest version of Bisq.
  2. Set up an alternative location for the wallet.
$ mount 

//zzz@remote-nas-storage-unit._smb._tcp.local/Bisq on /Volumes/Bisq (smbfs, nodev, nosuid, quarantine, mounted by zzz)
  1. Launch Bisq but with an alternative command.
/Volumes/Bisq/Bisq.app/Contents/MacOS/Bisq --appDataDir=/Volumes/Bisq/BisqData

Expected behaviour

I expected Bisq to come up just fine. In fact, it does if I let Bisq use the default path of ~/Library/Application Support/Bisq.

Actual behaviour

Bisq fails to launch. It complains about a potentially corrupted SPV file. But in truth, it appears to need to do some form of low level locking on the SPV file, which for some reason, the NAS in it's configuration is unable to do.

And so it throws this stack trace:

Oct-16 21:08:29.682 [JavaFX Application Thread] ERROR b.core.btc.setup.WalletsSetup: Service failure from state: STARTING; failure={} java.io.IOException: org.bitcoinj.store.BlockStoreException: java.io.IOException: Operation not supported
	at bisq.core.btc.setup.WalletConfig.startUp(WalletConfig.java:352)
	at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:62)
	at com.google.common.util.concurrent.Callables$4.run(Callables.java:119)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.bitcoinj.store.BlockStoreException: java.io.IOException: Operation not supported
	at org.bitcoinj.store.SPVBlockStore.<init>(SPVBlockStore.java:159)
	at org.bitcoinj.store.SPVBlockStore.<init>(SPVBlockStore.java:91)
	at bisq.core.btc.setup.WalletConfig.startUp(WalletConfig.java:289)
	... 3 common frames omitted
Caused by: java.io.IOException: Operation not supported
	at java.base/sun.nio.ch.FileDispatcherImpl.lock0(Native Method)
	at java.base/sun.nio.ch.FileDispatcherImpl.lock(Unknown Source)
	at java.base/sun.nio.ch.FileChannelImpl.tryLock(Unknown Source)
	at java.base/java.nio.channels.FileChannel.tryLock(Unknown Source)
	at org.bitcoinj.store.SPVBlockStore.<init>(SPVBlockStore.java:133)
	... 5 common frames omitted

Device or machine

I'm doing this on MacOS Big Sur. The NAS runs ext4, which is standard Linux. But the partition is smbfs, nodev, nosuid, quarantine.

Additional info

I need this because running Bisq (Tor-based tech) directly on my machine violates security policy. By running everything off of my NAS, I can continue using Bisq. Hopefully, there is some easy adjustment to the code that may make it operational.

@boring-cyborg
Copy link

boring-cyborg bot commented Oct 17, 2021

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@rex4539
Copy link
Contributor

rex4539 commented Oct 30, 2021

Perhaps using a symlink pointing to your NAS but keeping the symlink in the default path.

Something like ln -s ~/Library/Application Support/Bisq /Volumes/Bisq/BisqData

@stale
Copy link

stale bot commented Apr 16, 2022

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 stale bot added the was:dropped label Apr 16, 2022
@stale
Copy link

stale bot commented Apr 28, 2022

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

@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants