ProductName:Mac OS X
App shows starting screen and hangs, never shows anything.
Thanks for trying dbKoda and I'm sorry it is not working for you yet. Normally we would ask for a support bundle from the product, but since the product is not starting it would be easiest for us if you collected one manually. The instructions are here: https://dbkoda.useresponse.com/knowledge-base/article/how-do-i-generate-a-support-bundle , but very quickly for MacOs, you download and run this file: https://github.com/SouthbankSoftware/dbkoda/blob/master/supportBundle.sh. This copies up some data from our log and configuration directory. If you email the tar.gz file to us we'll take a look at it.
Another thing you could try - ideally after sending the support bundle - is to remove the contents of the ~/.dbKoda directory. If we have a corrupted configuration that is where it will be..
I do not have ~/.dbKoda directory, it was not created. And your support sh could be improved because in the absence of this directory it tried to pack my entire home directory, not nice.
Good point Konstantin, I added directory existence checks to the script at https://github.com/SouthbankSoftware/dbkoda/blob/master/supportBundle.sh.
Although the .dbKoda directory does not exist, I would still like to see if any log files were written to ~/Library/Application\ Support/dbKoda/logs. This might help us understand why the product is not initialising. The support bundle script will include these files as well as the .dbKoda files.
We don't have any open support cases with this symptom, so it's hard to speculate on what is happening without further information. If there are no log files I'd also be curious to know if you can view the "dev tools" output by hitting command option I or from the Development/Toggle Dev Tools menu.
Finally if you wouldn't mind just confirming that you are running dbKoda from the latest production DMG file or if you have build from source, or are running from a nightly build.
Again, my sincere apologies for the inconvenience and we really appreciate your assistance in diagnosing this issue.
Oops, I was looking at different mac. So, here is my log
Konstantins-Mac-Pro:~ kgignatyev$ cat ~/Library/Application\ Support/dbKoda/logs/2017-11-11.controller.log
2017-11-11T17:53:11-08:00 - error: Error: Command failed: bash -lc 'which mongo'
mkdir: /.rbenv/shims: Permission denied
mkdir: /.rbenv/versions: Permission denied
at checkExecSyncError (child_process.js:493:13)
at execSync (child_process.js:533:13)
at childProcess.(anonymous function) (ELECTRON_ASAR.js:685:22)
at loadConfig (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:103:55)
at loadConfigFromYamlFile (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:143:5)
at loadCommands (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:173:16)
at Object.<anonymous> (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:208:14)
at Object.<anonymous> (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:214:3)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Object.<anonymous> (/Applications/dbKoda.app/Contents/Resources/app.asar/node_modules/@southbanksoftware/dbkoda-controller/lib/config.js:209:1)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
2017-11-11T17:53:11-08:00 - info: resolve command paths mongoCmd=null, mongoVersionCmd=null, mongodumpCmd=null, mongorestoreCmd=null, mongoimportCmd=null, mongoexportCmd=null, drillCmd=null, showWelcomePageAtStart=true, telemetryEnabled=null
2017-11-11T17:53:11-08:00 - notice: dbKoda Controller is ready at localhost:3030
2017-11-11T17:54:02-08:00 - error: Error: Command failed: bash -lc 'which mongo'
2017-11-11T17:54:02-08:00 - info: resolve command paths mongoCmd=null, mongoVersionCmd=null, mongodumpCmd=null, mongorestoreCmd=null, mongoimportCmd=null, mongoexportCmd=null, drillCmd=null, showWelcomePageAtStart=true, telemetryEnabled=null
2017-11-11T17:54:03-08:00 - notice: dbKoda Controller is ready at localhost:3030
2017-11-11T17:56:12-08:00 - error: Error: Command failed: bash -lc 'which mongo'
2017-11-11T17:56:12-08:00 - info: resolve command paths mongoCmd=null, mongoVersionCmd=null, mongodumpCmd=null, mongorestoreCmd=null, mongoimportCmd=null, mongoexportCmd=null, drillCmd=null, showWelcomePageAtStart=true, telemetryEnabled=null
2017-11-11T17:56:13-08:00 - notice: dbKoda Controller is ready at localhost:3030
Of course user does not have permissions to create files in the root /.
We are pretty sure that the 'mkdir: /.rbenv/shims: Permission denied' errors are coming from rvm commands inside your .bash_profile. We load the .bash_profile when we are running the 'which' command, but unfortunately $HOME does not resolve from within Electron sessions () so we don't always get the complete picture. The mkdir permission errors can probably be ignored.
If as you say you were looking on a different mac, we'd like to be 100% sure that we have all the logs (there is usually an 'app' log as well as a 'controller' log) and also be 100% sure that we have contents of the .dbKoda directory. Best way to get all this is to run the supportBundle script which I PROMISE will not try to bundle up your home directory any more :-)
To get the updated support bundle script:
curl https://raw.githubusercontent.com/SouthbankSoftware/dbkoda/master/supportBundle.sh >supportBundle.sh
then just run that as a bash script.
Hopefully we'll then be able to get to the bottom of this.
Comments have been locked on this page!