|Re: [geomesa-users] Configuring GeoServer for GeoMesa|
It didn’t look like I had duplicate copies of any jars. Here are all the “slf4j” and “log4j” jar files in the GeoServer WEB-INF/lib:
-rw-r--r--. 1 barnhartr barnhartr 367444 Sep 12 2013 log4j-1.2.14.jar
-rw-r--r--. 1 barnhartr barnhartr 23445 Sep 16 2013 slf4j-api-1.5.8.jar
-rw-r--r--. 1 barnhartr barnhartr 8620 Sep 16 2013 slf4j-log4j12-1.4.2.jar
I tried replacing these with the newer versions from Hadoop 2.4.0’s tomcat WEB-INF/lib (no impact):
-rw-r--r--. 1 barnhartr barnhartr 489884 May 22 09:09 log4j-1.2.17.jar
-rw-r--r--. 1 barnhartr barnhartr 26084 May 22 09:20 slf4j-api-1.7.5.jar
-rw-r--r--. 1 barnhartr barnhartr 8869 May 22 09:20 slf4j-log4j12-1.7.5.jar
I then replaced $GEOSERVER_HOME/lib/log4j-1.2.14.jar with its 1.2.17 version, also with no impact.
You are getting this error “java.lang.NoSuchMethodError: org.slf4j.Logger.isTraceEnabled()Z” which means you have at least 2 copies of the slf4j logger jar deployed for geomesa. GeoServer comes with a log4j-1.2.14 and GeoMesa requires log4j-1.2.17 I believe (at least that is what I deploy with some of my other GeoServer extensions/apps we write).
Check your GeoServer folder WEB-INF/lib for log4j-X.X.X.jar and rename all of them except the one with the highest number. Restart your container (Tomcat, JBoss, etc) and try adding the GeoMesa store again.
Senior Software Engineer
Intelligent Software Solutions, Inc.
Direct (719) 452-7257
I think I’ve gotten past the “missing .jar file” issues, adding the following .jars:
I am continuing with the instruction at http://geomesa.github.io/2014/04/17/geomesa-gdelt-analysis/.
I brought up GeoServer and added a new workspace (name:geomesa,url:www.geomesa.org). That went fine.
Then I tried to register the GeoMesa data store with GeoServer, defining the “geomesa:gdelt” data store as shown in the tutorial. I used all the same connection parameters I used to ingest the GDELT 20140507 data.
However, when I hit “Save” I got the following error on the web-page:
Error creating data store, check the parameters. Error message: Failed to connect to zookeeper (localhost:2181) within 2x zookeeper timeout period 30000
The GeoServer standard-error output a large number of the following errors (presumably one for each failed attempt to connect to ZooKeeper):
272858 [btpool0-7-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket connection established to localhost/127.0.0.1:2181, initiating session
272862 [btpool0-7-SendThread(localhost:2181)] WARN org.apache.zookeeper.ClientCnxn - Session 0x0 for server localhost/127.0.0.1:2181, unexpected error, closing socket connection and attempting reconnect
274761 [btpool0-7-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
However, as far as I can tell, ZooKeeper is running fine and responded to commands such as “echo ruok | nc 127.0.0.1 5111”.
Any ideas what might be going wrong here?
On 05/21/2014 02:00 PM, Barnhart, Bob M. wrote:
Back to the top