ah - i forgot to do that step.....i'm running tp32 now to see if that works, but i'll fix that issue on master.
On Wed, Feb 28, 2018 at 10:41 AM, Robert Dale <[email protected]> wrote: > Could it be that 'bin/gremlin.sh' is linked to a specific version? Does > this have to be updated every release? > > $ ll gremlin-console/bin/gremlin.sh > gremlin-console/bin/gremlin.sh -> > ../target/apache-tinkerpop-gremlin-console-3.3.2-SNAPSHOT-standalone/bin/ > gremlin.sh > > Robert Dale > > On Wed, Feb 28, 2018 at 10:37 AM, Robert Dale <[email protected]> wrote: > > > I got it too. tp32: good. tp33: good. master: bad. > > > > Robert Dale > > > > On Wed, Feb 28, 2018 at 10:20 AM, Stephen Mallette <[email protected] > > > > wrote: > > > >> I'm having no success generating docs with Docker. On master i'm > currently > >> getting: > >> > >> Starting namenodes on [localhost] > >> localhost: Warning: Permanently added 'localhost' (ECDSA) to the list of > >> known hosts. > >> localhost: starting namenode, logging to > >> /usr/local/lib/hadoop-2.7.2/logs/hadoop-root-namenode-61cfd8f63c77.out > >> localhost: Warning: Permanently added 'localhost' (ECDSA) to the list of > >> known hosts. > >> localhost: starting datanode, logging to > >> /usr/local/lib/hadoop-2.7.2/logs/hadoop-root-datanode-61cfd8f63c77.out > >> Starting secondary namenodes [0.0.0.0] > >> 0.0.0.0: Warning: Permanently added '0.0.0.0' (ECDSA) to the list of > >> known > >> hosts. > >> 0.0.0.0: starting secondarynamenode, logging to > >> /usr/local/lib/hadoop-2.7.2/logs/hadoop-root-secondarynameno > >> de-61cfd8f63c77.out > >> starting yarn daemons > >> starting resourcemanager, logging to > >> /usr/local/lib/hadoop-2.7.2/logs/yarn-root-resourcemanager- > >> 61cfd8f63c77.out > >> localhost: Warning: Permanently added 'localhost' (ECDSA) to the list of > >> known hosts. > >> localhost: starting nodemanager, logging to > >> /usr/local/lib/hadoop-2.7.2/logs/yarn-root-nodemanager-61cfd8f63c77.out > >> Gremlin REPL is not available. Cannot preprocess AsciiDoc files. > >> Untagged: tinkerpop:build-1519830232 > >> > >> On that particular run, I'd just deleted all my Docker images (including > >> the linux image) and it still failed. Any clues as to what might be > wrong? > >> am i the only person with a problem here? > >> > > > > >
