Execution issues about joern

[juhakivekas]

With latest do you mean the head of the dev branch? That one shouldn't be using neo4j anymore, and should run without all the old components that the master branch needs. The freshest development version should run without problems on an up-to-date debian with java 1.8 or newer (that's how I run it).

[mozark24]

@juhakivekas. I was working from the branch listed "latest" in the docs when I got these errors, which used Neo4j. But before posting I had also tried the dev version and hit different issues (w/ Java 1.8). This was on Ubuntu 16.04.

BUT I was eventually able to get Joern working with the dev branch when I swapped to Debian Jessie. There were a few places in the docs that are in need of changing (gremlin commands are out of date), but I was able to string it together to finally give me an basic gremlin query. Thank you for the response.

[juhakivekas]

I have a PR for those parts of the docs (#160), but it seems like the repo isn’t being kept up to date very much as the maintainer seems to be working on something new and slightly different.

I went through a few cycles of wanting to give up when setting up joren a month ago too, so I understand your confusion :)

[mozark24]

Ugg... I want to like this project but I had to reboot and now I can't get the server working again. It just freezes at the cmd line with no output. Can I ask what settings your octopus-server.sh has for memory? not sure if its related but worth a try.

[juhakivekas]

The server starting and being quiet on the command line is the expected behavior. Try running joern-import on some archive and you'll see the debug logging in the terminal your server is running in. If nothing gets printed, then there's a problem that I haven't had yet.