| Re: [geogig-dev] Loading of GeoGig repositories fails after restart of Geoserver |
Hi Erik, We have checked the permissions on files in the lib folder and they all have the same settings. We have then restarted the GeoServer and reproduced the issue. The GeoServer logs generated after restart are attached in the compressed file TomCat_logs.2017-07-14.abc. After detachment the file extension should be changed to .zip. I will by the end of this day start a vacation over the next three weeks J So I would ask you to include my colleague Morten Storm (email: ms@xxxxxxxxxx) in emails following this one. Best regards
Fra: geogig-dev-bounces@xxxxxxxxxxxxxxxx [mailto:geogig-dev-bounces@xxxxxxxxxxxxxxxx] På vegne af Erik Merkle Erik, I don't have access to a Windows Server 2012 or 2008 system, but I have tried on Windows 7 with the same GeoServer 2.10.0 you have (same commit and build date), and the 1.1.1 plugin from here: https://github.com/locationtech/geogig/releases/download/v1.1.1/geoserver-2.10.x-geogig-plugin.zip. I was able to create RocksDB backed repos with that combination fine. The only thing I had to do was remove the postgresql-9.4.1211.jar as the plugin is bundled with the newer 42.1.1 version. I tried to reproduce the problem, but the only way I can get a NoClassDefFound exception is if the rocksdbjni jarfile is missing, as Gabriel said. Either version should work (4.13.4 or 4.13.5). Erik Merkle On Thu, Jul 13, 2017 at 4:56 AM, Erik Martinsen <ema@xxxxxxxxxx> wrote: Hi Gabriel and Erik, Thank you for your replies. From our side we have tested different things in order to have the GeoGig GeoServer 2.10 plugin working: · Ensuring that only one JAR file is present of the ones where geogig is part of the file naming. · Tried to use rocksdbjni-4.13.5.jar instead of the rocskdbjni-4.13.4.jar delivered with the zip file. · Upgrading the Java installation on the server from 1.8.0_72-b15 to 1.8.0_131-b11. However we are still not able to create file based GeoGig repositories. We know we earlier got the plugin to work on a Windows Server 2012 and are now trying to obtain the same on a Windows Server 2008. But since it is a server delivered by our customer it will be difficult for us to upgrade regarding OS server version. Best regards
Fra: geogig-dev-bounces@xxxxxxxxxxxxxxxx [mailto:geogig-dev-bounces@xxxxxxxxxxxxxxxx] På vegne af Gabriel Roldan
It looks like the missing jar is rocksdbjni-4.13.5.jar It definitely is in the geoserver-2.10.x-geogig-plugin.zip archive. May you have accidentally removed it from geoserver's WEB-INF/lib? On Wed, Jul 12, 2017 at 12:21 PM, Erik Merkle <emerkle@xxxxxxxxxxxxxxxx> wrote: Erik, That error is strange as it would normally indicate either a missing JAR, or multiple class definitions on the classpath. I'll try to reproduce this on my end. Could you double check that, when using this plugin: you only have 1 JAR file for each of the "geogig" jars. I'm wondering if you might have older GeoGig jar files mixed with the 1.1.1 release versions. For example, you should only have: geogig-rocksdb-1.1.1.jar and not have: geogig-rocksdb-1.1-SNAPSHOT.jar or any of the RC release candidate versions: geogig-rocksdb-1.1.1-RC1.jar, geogig-rocksdb-1.1.1-RC2.jar, geogig-rocksdb-1.1.1-RC3.jar, or geogig-rocksdb-1.1.1-RC4.jar If you only have one jar, the issue should be easy to reproduce on my end. For now, I've created an issue ticket here to track it: Thanks for reporting the issue, - Erik Merkle On Wed, Jul 12, 2017 at 8:49 AM, Erik Martinsen <ema@xxxxxxxxxx> wrote: Hi Erik, We have now tried to install the build of the GeoServer 2.10 plugin provided in your link on a GeoServer with the following information:
GeoServer 2.10 is installed on a Tomcat server with the following configuration:
We have removed the PostgreSQL driver postgresql-9.4.1211.jar before installing the GeoServer 2.10 plugin. The GeoGig menu items in the left side loads as expected after restarting the GeoServer but when we try to create a file based GeoGig repository we get an error of this kind “Could not initialize class org.rocksdb.RocksDB” (further information is included in the attached file java_errors.txt). We have also tried to install the GeoServer 2.10 plugin from this link: https://github.com/locationtech/geogig/releases/download/v1.1.1/geoserver-2.10.x-geogig-plugin.zip but unfortunately with the same result. Do you know the cause of this issue or a workaround? Best regards
Fra: geogig-dev-bounces@xxxxxxxxxxxxxxxx [mailto:geogig-dev-bounces@xxxxxxxxxxxxxxxx] På vegne af Erik Merkle
Erik, The latest GeoServer 2.10 plugin build is here: Be aware, there is an updated PostgreSQL driver bundled in the plugin (version 42.1.1) and it will conflict with the PostgreSQL driver that comes with GeoServer 2.10. If you chose to use the nightly plugin build, you will have to remove the older PostgreSQL driver currently in your GeoServer install (likely postgresql-9.4.1211.jar). Regards, Erik Merkle On Thu, Jun 29, 2017 at 12:46 AM, Erik Martinsen <ema@xxxxxxxxxx> wrote: Hi Gabriel, Thank you for the information. Is it possible for you to provide a similar link to the latest build of the GeoServer 2.10 plugin? Or do you know when this plugin will be released in final mode? We have yesterday tested the build we can download from this link https://github.com/locationtech/geogig/releases/download/v1.1.1-RC1/geoserver-2.10-SNAPSHOT-geogig-plugin.zip . It solves some of our problems but we still cannot load the GeoGig repositories after restart of the GeoServer. Best regards
Fra: geogig-dev-bounces@xxxxxxxxxxxxxxxx [mailto:geogig-dev-bounces@xxxxxxxxxxxxxxxx] På vegne af Gabriel Roldan
Hello, just a heads that this bug has been fixed and will be released with 1.1.1. while we wait for 1.1.1 final to come out, you can get the fix from the latest nightly build [1] Cheers, Gabriel On Wed, Jun 21, 2017 at 4:57 AM, Erik Martinsen <ema@xxxxxxxxxx> wrote: Hi Erik, Yes, usually we create the GeoGig repository from the GeoServer UI. But we have now tried to create a repository directly from the GeoGig plugin in QGIS. From QGIS we access the GeoServer using this URL
So the URL to the repository is like in your example: http://server3x2:8082/geoserver/geogig/repos/EMA_REPOS_2/ In QGIS the GeoGig plugin is configured with user name and email:
Even though we create the repository directly from QGIS and GeoGig configured with user name and email the first time we try to add a layer to the repository we get this error:
We have tried to configure globally through command line but we have manually to edit the local repository config file on the server by adding these lines:
The repository then works as expected. After restart of the GeoServer ensuring no QGIS sessions is running that are connected to the repository (so only one single process) the access to the repository from QGIS afterward fails with the following error: 2017-06-21T09:48:13 0 QGIS starter... 2017-06-21T09:48:14 0 Python-understøttelse SLÅET TIL :-) 2017-06-21T09:50:01 0 Application state: QGIS_PREFIX_PATH env var: C:/PROGRA~2/QGIS2~1.18/apps/qgis Prefix: C:/PROGRA~2/QGIS2~1.18/apps/qgis Plugin Path: C:/PROGRA~2/QGIS2~1.18/apps/qgis/plugins Package Data Path: C:/PROGRA~2/QGIS2~1.18/apps/qgis/. Active Theme Name: default Active Theme Path: C:/Users/erik.martinsen/.qgis2///themes\default\icons/ Default Theme Path: :/images/themes/default/ SVG Search Paths: C:/PROGRA~2/QGIS2~1.18/apps/qgis/./svg/ C:/Users/erik.martinsen/.qgis2//svg/ User DB Path: C:/PROGRA~2/QGIS2~1.18/apps/qgis/./resources/qgis.db Auth DB Path: C:/Users/erik.martinsen/.qgis2//qgis-auth.db 2017-06-21T09:50:01 0 QGIS er klar! 2017-06-21T09:50:23 2 An error occurred while fetching repository data! 500 Server Error: for url: http://server3x2:8082/geoserver/geogig/repos/EMA_REPOS_2/ls-tree?path=HEAD&output_format=json&_onlyTrees_=True Best regards
Fra: geogig-dev-bounces@xxxxxxxxxxxxxxxx [mailto:geogig-dev-bounces@xxxxxxxxxxxxxxxx] På vegne af Erik Merkle Hi Erik, C an you clarify a few things for me? It sounds like your GeoGig repository is created via GeoServer, correct? Then you are accessing the repository via QGIS. I'm assuming you are using the GeoGig plugin in QGIS to connect. If so, are you exposing the repository via command line "geogig serve", or are you accessing the repository as exposed via GeoServer (using a URL similar to http://localhost/geoserver/geogig/repos/myRepo)? The error you are seeing may be related to one of a couple of issues that have been raised: The problem with issue #309 is that there are 2 processes trying to access a single RocksDB database at the same time. Currently, the RocksDB integration in GeoGig is such that GeoGig will maintain an exclusive lock on the RocksDB database as long as the repository remains open in a given process. This means that GeoServer can serve out the repository, or "geogig serve" from the command line can serve out the repository, but not both at the same time. I suspect this may be the issue, if you have a QGIS session open and connected to the repository (via geogig serve), and then you try to restart GeoServer, which will try to open the repository as well. If this is not the case, that is you only have a single process accessing the repository, then it may be related to issue #302, or it may be a new issue we have not come across. If you would, could you please reply back and let us know if your issue is being caused by more than one process trying to access the database. If that is not the issue, we can collect more details and open a new ticket in GitHub. Many thanks, Erik Merkle On Tue, Jun 20, 2017 at 12:25 AM, Erik Martinsen <ema@xxxxxxxxxx> wrote: Hi, We are testing GeoGig on a Windows Server 2012R2 with GeoServer 2.10.0. The server is installed with Java version 1.8.0_121. After creating file based GeoGig repositories we access them from QGIS Desktop 2.18.2. From QGIS we can successfully add new layers to the repositories and make layer versioning and merging in master and branches. However after a restart of the GeoServer the repositories fails with an error message of the following type for one and each of them when we try to access them from QGIS: 2017-06-19 13:39:31,954 WARN [geoserver.config] - Error loading GeoGig repository instance for id 5f646e20-aaee-4cd5-8f35-92045ed9c831 java.lang.RuntimeException: org.rocksdb.RocksDBException: × Further details is available from the attached geoserver.log file. After restart of the GeoServer we can create a new repository that will be operating as expected until next time the GeoServer is restarted. Are there some kind of close down or start up procedure for the GeoServer we are not aware of? Best regards
-- Gabriel Roldán
-- Gabriel Roldán
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Attachment:
TomCat_logs.2017-07-14.abc
Description: Binary data
