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

mount failed on MacOS High Sierra #631

Closed
wello007 opened this Issue Jan 22, 2018 · 10 comments

Comments

Projects
None yet
7 participants
@wello007
Copy link

wello007 commented Jan 22, 2018

I am using MacOS High Sierra 10.13.3

I'm running Cryptomator in version: 1.3.2

I am not able to mount the drive anymore, the vault is unlocked but not mounted and can’t be used.

21:34:37.548 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.3.2 on Mac OS X 10.13.3 (x86_64)
21:34:38.145 [JavaFX Application Thread] INFO  o.c.launcher.MainApplication - JavaFX application started.
21:34:38.263 [JavaFX Application Thread] WARN  o.c.c.settings.SettingsJsonAdapter - Unsupported vault setting found in JSON: useIpv6
21:34:38.264 [JavaFX Application Thread] INFO  o.c.common.settings.SettingsProvider - Settings loaded from /Users/waliddib/Library/Application Support/Cryptomator/settings.json
21:34:38.312 [JavaFX Application Thread] INFO  org.cryptomator.jni.JniModule - loaded libMacFunctions.dylib
21:34:38.695 [JavaFX Application Thread] INFO  org.eclipse.jetty.util.log - Logging initialized @1645ms to org.eclipse.jetty.util.log.Slf4jLog
21:34:38.749 [JavaFX Application Thread] INFO  o.c.frontend.webdav.WebDavServer - Binding server socket to localhost:42428
21:34:38.785 [JavaFX Application Thread] INFO  o.e.jetty.server.AbstractConnector - Started ServerConnector@29aef30c{HTTP/1.1,[http/1.1]}{localhost:42428}
21:34:40.189 [pool-4-thread-1] INFO  o.c.ui.controllers.WelcomeController - Current version: 1.3.2, lastest version: 1.3.2
21:34:45.522 [pool-4-thread-1] INFO  org.eclipse.jetty.server.Server - jetty-9.4.7.v20170914
21:34:45.829 [pool-4-thread-1] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@498bc017{/,null,AVAILABLE}
21:34:45.830 [pool-4-thread-1] INFO  org.eclipse.jetty.server.Server - Started @8779ms
21:34:45.830 [pool-4-thread-1] INFO  o.c.frontend.webdav.WebDavServer - WebDavServer started.
21:34:46.373 [pool-4-thread-1] INFO  org.eclipse.jetty.server.session - DefaultSessionIdManager workerName=node0
21:34:46.374 [pool-4-thread-1] INFO  org.eclipse.jetty.server.session - No SessionScavenger set, using defaults
21:34:46.382 [pool-4-thread-1] INFO  org.eclipse.jetty.server.session - Scavenging every 600000ms
21:34:46.549 [pool-4-thread-1] INFO  o.a.j.w.server.AbstractWebdavServlet - authenticate-header = Basic realm="Jackrabbit Webdav Server"
21:34:46.551 [pool-4-thread-1] INFO  o.a.j.w.server.AbstractWebdavServlet - csrf-protection = null
21:34:46.552 [pool-4-thread-1] INFO  o.a.j.w.server.AbstractWebdavServlet - createAbsoluteURI = true
21:34:46.552 [pool-4-thread-1] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@193e6a1f{/Cjv5AJtvS2AH/Documents,null,AVAILABLE}
21:34:46.553 [pool-4-thread-1] INFO  o.c.f.w.s.WebDavServletController - WebDavServlet started: /Cjv5AJtvS2AH/Documents
21:34:47.107 [pool-4-thread-1] INFO  o.c.f.w.s.WebDavServletController - Mounting http://localhost:42428/Cjv5AJtvS2AH/Documents using org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter
21:35:21.170 [AppKit Thread] ERROR o.c.u.controllers.UnlockedController - Mount failed.
org.cryptomator.frontend.webdav.mount.ProcessUtil$CommandTimeoutException: Command timed out.
	at org.cryptomator.frontend.webdav.mount.ProcessUtil.waitFor(ProcessUtil.java:68)
	at org.cryptomator.frontend.webdav.mount.ProcessUtil.startAndWaitFor(ProcessUtil.java:48)
	at org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter.mount(MacAppleScriptMounter.java:60)
	at org.cryptomator.frontend.webdav.servlet.WebDavServletController.mount(WebDavServletController.java:102)
	at org.cryptomator.ui.model.Vault.mount(Vault.java:140)
	at org.cryptomator.ui.controllers.UnlockedController.lambda$mountVault$1(UnlockedController.java:164)
	at org.cryptomator.ui.util.AsyncTaskService.lambda$asyncTaskOf$0(AsyncTaskService.java:43)
	at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$null$6(AsyncTaskService.java:106)
	at org.cryptomator.ui.util.AsyncTaskService.logExceptions(AsyncTaskService.java:135)
	at org.cryptomator.ui.util.AsyncTaskService.access$100(AsyncTaskService.java:24)
	at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$run$7(AsyncTaskService.java:104)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

walid 2018-01-22 at 9 40 36 pm

@saesh

This comment has been minimized.

Copy link

saesh commented Jan 23, 2018

I am on macOS High Sierra 10.13.2 with cryptomator 1.3.2 and cannot mount a drive as well, with this error:

org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Unexpected mount result:
	at org.cryptomator.frontend.webdav.mount.MacAppleScriptMounter.mount(MacAppleScriptMounter.java:52)
	at org.cryptomator.frontend.webdav.servlet.WebDavServletController.mount(WebDavServletController.java:102)
	at org.cryptomator.ui.model.Vault.mount(Vault.java:140)
	at org.cryptomator.ui.controllers.UnlockedController.lambda$mountVault$1(UnlockedController.java:164)
	at org.cryptomator.ui.util.AsyncTaskService.lambda$asyncTaskOf$0(AsyncTaskService.java:43)
	at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$null$6(AsyncTaskService.java:106)
	at org.cryptomator.ui.util.AsyncTaskService.logExceptions(AsyncTaskService.java:135)
	at org.cryptomator.ui.util.AsyncTaskService.access$100(AsyncTaskService.java:24)
	at org.cryptomator.ui.util.AsyncTaskService$AsyncTaskImpl.lambda$run$7(AsyncTaskService.java:104)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
@t0rv1c

This comment has been minimized.

Copy link

t0rv1c commented Jan 25, 2018

Same here. Hi @tobihagemann and @overheadhunter , it looks like this started recently. Could it be the latest Java update 8 161?

@github-peter

This comment has been minimized.

Copy link

github-peter commented Jan 27, 2018

Upgraded macOS High Sierra today, to version 10.13.3. This problem occurred for me too after the update, it worked properly before the update. Using Cryptomator version 1.3.2 (1046).

@tobihagemann

This comment has been minimized.

Copy link
Member

tobihagemann commented Jan 29, 2018

I'm unable to confirm the bug. I'm also at macOS 10.13.3. The Java runtime installed at system-level shouldn't have any influence on the bundled Java runtime inside Cryptomator (which is using Java 8u152).

I think @wello007 and @saesh are having different issues. One is failing due to a timeout (we've recently increased the timeout from 5 seconds to 30 seconds but it looks like that it doesn't matter how long the timeout actually is) and the other one is failing due to an unexpected mount result (and it looks like the result is empty).

For a better understanding what the MacAppleScriptMounter is doing: As the name says, Cryptomator uses AppleScript to mount the WebDAV drive. It's basically like if you'd call the following in Terminal:

/usr/bin/osascript -e "mount volume \"http://localhost:42427/<vault_id>/<vault_name>\""

You can use the "Copy WebDAV URL" function in Cryptomator for the exact URL. This command doesn't seem to do its job in @saesh's case.

Let's say the command worked and the result of it was file Foo:. After that, Cryptomator verifies that the mounted drive exists:

/usr/bin/osascript -e "tell application \"Finder\" to repeat while not (\"Foo:\" exists)" -e "delay 0.1" -e "end repeat"

This seems to run into a timeout in @wello007's case.

Unfortunately, I don't know why this happens in either of your cases. Maybe you can try out these commands in Terminal yourself and see if there is any difference. There shouldn't be because that's basically what Cryptomator is doing but maybe there's more output (with other error messages).

@saesh

This comment has been minimized.

Copy link

saesh commented Jan 29, 2018

@tobihagemann Thanks for your feedback. I tried the command

/usr/bin/osascript -e "mount volume \"http://localhost:42427/<vault_id>/<vault_name>\""

and it executed without error (not output, return code 0).

I see some weird behavior with Finder and the WebDAV shared directory, I believe. I could not make a clear picture but, this is what I observed:

  • automatic mounting and revealing of the vault fails
  • after I enter the command manually, I cannot access the vault from the Finder, but via Terminal (ls -al /Volumes/<vault_name>) and actually work with the files
  • in another try, I could see the files in the Finder after clicking the <vault_name> in the shared folder view of the Finder (I could not reproduce this again)
@pgolebiowski

This comment has been minimized.

Copy link

pgolebiowski commented Mar 1, 2018

This probably could be solved with FUSE support. I have found this blog post: https://cryptomator.org/blog/2018/01/07/roadmap_en.html. @tobihagemann, could you please share if the roadmap is still valid? Thanks!

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Apr 6, 2018

Today we released our first beta of 1.4.0, which brings FUSE support to macOS and Linux.

Please retest this issue with FUSE enabled and report your findings in this thread.


If you experience any new issues, please report them and tell us what software version (including macOS version, involved applications, etc) you're using.

⚠️ This is a beta version! Make backups and don't use this version for production data. ⚠️

@saesh

This comment has been minimized.

Copy link

saesh commented Apr 7, 2018

Thanks for the update @overheadhunter. Will test the beta. 👌

@stale

This comment has been minimized.

Copy link

stale bot commented Jun 17, 2018

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 state:stale label Jun 17, 2018

@no-response no-response bot closed this Jun 17, 2018

@no-response

This comment has been minimized.

Copy link

no-response bot commented Jun 17, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@overheadhunter overheadhunter added this to the 1.4.0 milestone Jun 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment