[GeoNode-users] Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani alessio.fabiani at gmail.com
Mon Oct 15 07:41:37 PDT 2018


This should fix the duplicated rules issue when running the management
commands

https://github.com/GeoNode/geonode/pull/3988/files


Il giorno lun 15 ott 2018 alle ore 16:13 Michael Fedak <mikefedak at gmail.com>
ha scritto:

> Thank Alessio,
>
> This fixes the problem with documents. However I am still experiencing the
> same problems with layers, I have commented on the pull request. I am also
> having the same issue with superusers not being automatically logged into
> geoserver.
>
> On Mon, Oct 15, 2018 at 4:39 AM Alessio Fabiani <alessio.fabiani at gmail.com>
> wrote:
>
>> Hi Michael,
>> thanks very much for helping on test.
>>
>> I've finally figured out where the problem was. Fix available here
>>
>> https://github.com/GeoNode/geonode/pull/3985
>>
>> I'll merge it as soon as the Travis checks pass. I'll also try to add
>> some specific test cases for this particular issue.
>>
>>
>> Il giorno dom 14 ott 2018 alle ore 21:08 Alessio Fabiani <
>> alessio.fabiani at gmail.com> ha scritto:
>>
>>> Uhm very strange. Tomorrow will do some specific tests on this.
>>> Currently I cannot figure out what the problem could be.
>>>
>>> Il dom 14 ott 2018, 21:03 Michael Fedak <mikefedak at gmail.com> ha
>>> scritto:
>>>
>>>> Ok, fixed; I had my JAVA_OPTS entered incorrectly. Now geoserver
>>>> starts. However, I am experiencing the same issues as before.
>>>>
>>>> On Sun, Oct 14, 2018 at 2:10 PM Michael Fedak <mikefedak at gmail.com>
>>>> wrote:
>>>>
>>>>> Traced it back some more, it seems to be an issue with GWC:
>>>>>
>>>>> Cannot resolve reference to bean 'gwcXmlConfigResourceProvider' while
>>>>> setting constructor argument; nested exception is
>>>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>>>> bean with name 'gwcXmlConfigResourceProvider' defined in URL
>>>>> [jar:file:/opt/apache-tomcat-9.0.1/webapps/geoserver/WEB-INF/lib/gs-gwc-2.13-20181005.133101-833.jar!/geowebcache-core-context.xml]:
>>>>> Bean instantiation via constructor failed; nested exception is
>>>>> org.springframework.beans.BeanInstantiationException: Failed to instantiate
>>>>> [org.geoserver.gwc.config.GeoserverXMLResourceProvider]: Constructor threw
>>>>> exception; nested exception is java.lang.IllegalStateException: Could not
>>>>> create directory.
>>>>>
>>>>> On Sun, Oct 14, 2018 at 1:42 PM Michael Fedak <mikefedak at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Ok, got the war and attempted to deploy it. Tomcat is unable to
>>>>>> deploy it due to an error associated with geotools:
>>>>>>
>>>>>>
>>>>>> Geoserver log:
>>>>>> 2018-10-14 10:24:59,152 TRACE [geotools.factory] - ENTRY
>>>>>> (CRSAuthorityFactory, CRS_AUTHORITY_FACTORY)
>>>>>> 2018-10-14 10:24:59,152 TRACE [geotools.factory] - CHECK
>>>>>> (CRSAuthorityFactory, CRS_AUTHORITY_FACTORY): user provided a Class.
>>>>>> 2018-10-14 10:24:59,152 TRACE [geotools.factory] - CHECK
>>>>>> (CRSAuthorityFactory, CRS_AUTHORITY_FACTORY): consider hint[last]
>>>>>> AbstractEpsgMediator.
>>>>>> 2018-10-14 10:24:59,152 TRACE [geotools.factory] - THROW
>>>>>> (CRSAuthorityFactory, CRS_AUTHORITY_FACTORY): could not find implementation.
>>>>>> 2018-10-14 10:24:59,152 INFO [geotools.util] - Weak collection
>>>>>> cleaner stopped
>>>>>>
>>>>>> Catalina log:
>>>>>>
>>>>>>
>>>>>> 14-Oct-2018 17:21:40.658 SEVERE [http-nio-8080-exec-13]
>>>>>> org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
>>>>>> The web application [geoserver-2.13.x] created a ThreadLocal with key of
>>>>>> type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal at 454bb710])
>>>>>> and a value of type
>>>>>> [org.geotools.referencing.operation.projection.TransverseMercator.Provider]
>>>>>> (value [PROJECTION["Transverse_Mercator"]]) but failed to remove it when
>>>>>> the web application was stopped. Threads are going to be renewed over time
>>>>>> to try and avoid a probable memory leak.
>>>>>> 14-Oct-2018 17:21:40.658 SEVERE [http-nio-8080-exec-13]
>>>>>> org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks
>>>>>> The web application [geoserver-2.13.x] created a ThreadLocal with key of
>>>>>> type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal at 86e380d])
>>>>>> and a value of type [org.geotools.referencing.wkt.Formatter] (value []) but
>>>>>> failed to remove it when the web application was stopped. Threads are going
>>>>>> to be renewed over time to try and avoid a probable memory leak.
>>>>>>
>>>>>>
>>>>>> I will keep trying to troubleshoot this.
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 14, 2018 at 10:02 AM Michael Fedak <mikefedak at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Never mind, found your build server:
>>>>>>> https://build.geo-solutions.it/geonode/geoserver/latest/
>>>>>>>
>>>>>>> On Sun, Oct 14, 2018 at 10:00 AM Michael Fedak <mikefedak at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Ok, I can do that. Is there a place to download the build with the
>>>>>>>> extension since build.geonode.org is down? Or shall I just
>>>>>>>> download vanilla 2.13 and apply the extension myself?
>>>>>>>>
>>>>>>>> On Sun, Oct 14, 2018 at 9:56 AM Alessio Fabiani <
>>>>>>>> alessio.fabiani at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Uhm, most probably a Geoserver issue. From. Geoserver 2.13+
>>>>>>>>> there's a fix to threat void users as * users.
>>>>>>>>> Any chance to try out updating to Geoserver 2.13.x?
>>>>>>>>> You won't have to change anything on the data dir.
>>>>>>>>>
>>>>>>>>> Il ven 12 ott 2018, 19:11 Michael Fedak <mikefedak at gmail.com> ha
>>>>>>>>> scritto:
>>>>>>>>>
>>>>>>>>>> I am using the latest 2.8.x branch with Geoserver 2.12.2 and I
>>>>>>>>>> keep receiving the following error when attempting to run the updatelayers
>>>>>>>>>> command (Below).
>>>>>>>>>>
>>>>>>>>>> I am also having trouble with users not being sync'd with
>>>>>>>>>> geoserver. I have gone through the documentation for security
>>>>>>>>>> configuration, and checked that the geonode role/user apis are accessible
>>>>>>>>>> to geoserver. As far as I can tell, nothing is blocking either geonode from
>>>>>>>>>> reaching geofence or vice-versa.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Traceback (most recent call last):
>>>>>>>>>>   File "manage.py", line 29, in <module>
>>>>>>>>>>     execute_from_command_line(sys.argv)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/gndev/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>>>>>> line 354, in execute_from_command_line
>>>>>>>>>>     utility.execute()
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/gndev/local/lib/python2.7/site-packages/django/core/management/__init__.py",
>>>>>>>>>> line 346, in execute
>>>>>>>>>>     self.fetch_command(subcommand).run_from_argv(self.argv)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/gndev/local/lib/python2.7/site-packages/django/core/management/base.py",
>>>>>>>>>> line 394, in run_from_argv
>>>>>>>>>>     self.execute(*args, **cmd_options)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/gndev/local/lib/python2.7/site-packages/django/core/management/base.py",
>>>>>>>>>> line 445, in execute
>>>>>>>>>>     output = self.handle(*args, **options)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/geonode_dev/geonode/geonode/geoserver/management/commands/updatelayers.py",
>>>>>>>>>> line 124, in handle
>>>>>>>>>>     execute_signals=True)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/geonode_dev/geonode/geonode/geoserver/helpers.py", line 636,
>>>>>>>>>> in gs_slurp
>>>>>>>>>>     layer.set_permissions(perm_spec)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/geonode_dev/geonode/geonode/security/models.py", line 216, in
>>>>>>>>>> set_permissions
>>>>>>>>>>     sync_geofence_with_guardian(self.layer, perms, group=group)
>>>>>>>>>>   File "/home/gnode/geonode_dev/geonode/geonode/decorators.py",
>>>>>>>>>> line 44, in wrapper
>>>>>>>>>>     return func(*args, **kwargs)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/geonode_dev/geonode/geonode/security/utils.py", line 393, in
>>>>>>>>>> sync_geofence_with_guardian
>>>>>>>>>>     _update_geofence_rule(layer.name, layer.workspace, service)
>>>>>>>>>>   File
>>>>>>>>>> "/home/gnode/geonode_dev/geonode/geonode/security/utils.py", line 564, in
>>>>>>>>>> _update_geofence_rule
>>>>>>>>>>     raise RuntimeError(msg)
>>>>>>>>>> Exception: ('Failed to process lprca_ws_boundarywgs84',
>>>>>>>>>> RuntimeError("Could not ADD GeoServer User None Rule for Layer
>>>>>>>>>> u'lprca_ws_boundarywgs84'",))
>>>>>>>>>> _______________________________________________
>>>>>>>>>> geonode-users mailing list
>>>>>>>>>> geonode-users at lists.osgeo.org
>>>>>>>>>> https://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>>>>>>
>>>>>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20181015/739a4c2e/attachment.html>


More information about the geonode-users mailing list