by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 14 2017 09:41

    pomadchin on master

    Update README.md (compare)

  • Feb 03 2017 20:24
    pomadchin closed #4
  • Feb 03 2017 20:24
    pomadchin commented #4
  • Feb 03 2017 20:23

    pomadchin on master

    Fix quay.io link Merge pull request #5 from jwal… (compare)

  • Feb 03 2017 20:23
    pomadchin closed #5
  • Feb 03 2017 20:23
    pomadchin commented #5
  • Feb 03 2017 20:10
    jwalgran opened #5
  • Dec 10 2016 21:50
    pomadchin commented #4
  • Dec 10 2016 13:42
    Plippe opened #4
Emilio
@elahrvivaz
i guess so...
Grigory
@pomadchin
Emilio
@elahrvivaz
I'm deleting all the 'latest' tags - that was confusing me haha
from quay.io
Grigory
@pomadchin
Ahahhahaha
Emilio
@elahrvivaz
actually 2.7.3 didn't work either... looks like we have to go to 2.8.4-1.el7
Grigory
@pomadchin
._.
Emilio
@elahrvivaz
gah, I don't get it... if I publish to a new tag, it works, but I can't seem to get it to work with the existing tag
i tried clearing out all my caches and such
Grigory
@pomadchin
hmmmm
mb they have some bug / feature?
Emilio
@elahrvivaz
I think I'll just make a new tag
Grigory
@pomadchin
:+1:
ah
you can delete an old image
and push a new one with the old tag
Emilio
@elahrvivaz
ok let me try that...
is that through quay or through docker commands?
Grigory
@pomadchin
doesnt matter :)
or should not matter
Emilio
@elahrvivaz
hmm, no luck - let me try a new tag just to verify i'm not crazy
i did see it work at one point :P
Emilio
@elahrvivaz
gah, it was pointing to the wrong tag this whole time :/
I never updated the docker-compose files to point to accumulo 1.9.2
Grigory
@pomadchin
hahahaha
okay
:D
it happens
dependent images %)
But I filed to ingest some sample data, use the GeoMesa command line tools
Grigory
@pomadchin
hey @tpolong what errors have you seen? is accumulo up and running?
Tangweilong
@tpolong
[root@localhost geodocker-accumulo-geomesa]# docker exec geodocker-accumulo-geomesa_accumulo-master_1_91c1064f73a9 geomesa ingest -c geomesa.gdelt -C gdelt -f gdelt -s gdelt -u root -p GisPwd /tmp/20170710.export.CSV
rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"geomesa\": executable file not found in $PATH"
It's running
[root@80ee55656ac9 accumulo]# cd /opt/geomesa/bin
[root@80ee55656ac9 bin]# ./geomesa-accumulo ingest -C example-csv -c example -u root -p GisPwd -s example-csv /tmp/20170710.export.CSV
Error: Could not find or load main class .usr.lib.zookeeper.zookeeper.jar
Grigory
@pomadchin
hmmm
probably we need @elahrvivaz powas there
Emilio
@elahrvivaz
@tpolong how did you start it up? did you run cd geodocker-accumulo-geomesa; docker-compose up?
and do you have the latest git commits on master?
I didn't test out ingest after getting it running the other day
Tangweilong
@tpolong
I started it and ran cd geodocker-accumulo-geomesa; docker-compose up
I cloned it from github yesterday
Emilio
@elahrvivaz
ok thanks, let me check it out
Emilio
@elahrvivaz
@tpolong looks like a bug in how the classpath is set up
for now, you can edit this line in geomesa-accumulo:

change

ZOOKEEPER_JAR="$(find -L $ZOOKEEPER_HOME -maxdepth 1 -type f -name *zookeeper*jar)"

to

ZOOKEEPER_JAR="$(find -L $ZOOKEEPER_HOME -maxdepth 1 -type f -name *zookeeper*jar | head -n 1)"
in the zookeeper lib directory there are 2 zookeeper jars (one is a symlink to the other), which is messing up the classpath syntax
I'll fix it in geomesa, but probably we won't have a new image for a week or two
Tangweilong
@tpolong
I changed it and ran it ,still it had a error
ERROR Unable to locate Accumulo instance. Please ensure that $ACCUMULO_HOME is set correctly and/or provide the instance name with the parameter --instance.