You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening the FusionDB Server application via the Dock from /Applications, you are initially presented with the launcher config dialog. Upon clicking save the Dialog disappears and nothing seems to happen. Instead, at that point launcher.stage2.sh should have been executed to show the Menu Icon and start the server.
However, if you instead run /Applications/FusionDB\ Server.app/Contents/MacOS/fdb-JavaAppLauncher from the Terminal.app then FusionDB Server starts fine. This can be used as a temporary workaround.
Why it does not run from the Dock, but does run from the command line is somewhat of a mystery. At the moment we have two lines of investigation:
Perhaps the launcher.stage2.sh is somehow not permitted to be run from the Dock. It is a Bash script, that is executed from LauncherWrapper.java via a ProcessBuilder. Does directly trying to execute a .sh script when not already inside a Terminal.app perhaps not work?
The Launcher's config dialog when clicking save, writes a bunch of files inside of /Applications/FusionDB Server.app. Directly, after a fresh install of the App from the DMG to /Applications, we can see that the codesign utility reports this:
codesign --verify --deep --verbose=8 /Applications/FusionDB\ Server.app
/Applications/FusionDB Server.app: valid on disk
/Applications/FusionDB Server.app: satisfies its Designated Requirement
However, after first launching from the Dock and clicking Save in the launcher's config dialog, we see that the codesign utility reports this:
When opening the
FusionDB Serverapplication via the Dock from /Applications, you are initially presented with the launcher config dialog. Upon clicking save the Dialog disappears and nothing seems to happen. Instead, at that pointlauncher.stage2.shshould have been executed to show the Menu Icon and start the server.However, if you instead run
/Applications/FusionDB\ Server.app/Contents/MacOS/fdb-JavaAppLauncherfrom the Terminal.app then FusionDB Server starts fine. This can be used as a temporary workaround.Why it does not run from the Dock, but does run from the command line is somewhat of a mystery. At the moment we have two lines of investigation:
Perhaps the
launcher.stage2.shis somehow not permitted to be run from the Dock. It is a Bash script, that is executed fromLauncherWrapper.javavia aProcessBuilder. Does directly trying to execute a.shscript when not already inside a Terminal.app perhaps not work?The Launcher's config dialog when clicking save, writes a bunch of files inside of
/Applications/FusionDB Server.app. Directly, after a fresh install of the App from the DMG to/Applications, we can see that thecodesignutility reports this:However, after first launching from the Dock and clicking Save in the launcher's config dialog, we see that the codesign utility reports this:
We also see that
/Applications/FusionDB Server.app/Contents/Resources/logs/exist.logcontains only this:The text was updated successfully, but these errors were encountered: