Recurring User 'None' Error Geofence/Geoserver

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Recurring User 'None' Error Geofence/Geoserver

Tweedle
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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Paolo Corti
I am getting exactly the same error, using master and GeoServer 2.13-SNAPSHOT
In the stack I also see "Could not retrieve GeoFence Rules count."
best
Paolo
On Fri, Oct 12, 2018 at 1:11 PM Michael Fedak <[hidden email]> wrote:

>
> 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
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/geonode-users



--
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti
_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
Also happens when I try sync_geofence:

('Unexpected error:', <type 'exceptions.RuntimeError'>)
perm_spec is {u'users': {u'AnonymousUser': [u'view_resourcebase', u'download_resourcebase'], u'lprca': [u'view_resourcebase', u'download_resourcebase', u'change_resourcebase_metadata', u'change_resourcebase', u'delete_resourcebase', u'change_resourcebase_permissions', u'publish_resourcebase', u'change_layer_data', u'change_layer_style']}, u'groups': {u'anonymous': [u'view_resourcebase', u'download_resourcebase']}}

Interestingly enough; fix_geofence_rules fails for all of the layers where sync_geofence works. 




On Fri, Oct 12, 2018 at 3:12 PM Paolo Corti <[hidden email]> wrote:
I am getting exactly the same error, using master and GeoServer 2.13-SNAPSHOT
In the stack I also see "Could not retrieve GeoFence Rules count."
best
Paolo
On Fri, Oct 12, 2018 at 1:11 PM Michael Fedak <[hidden email]> wrote:
>
> 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
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/geonode-users



--
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
And also getting an error (Error updating permissions) when trying to add groups to layer permissions; although the permission change is still successful.  

On Fri, Oct 12, 2018 at 6:02 PM Michael Fedak <[hidden email]> wrote:
Also happens when I try sync_geofence:

('Unexpected error:', <type 'exceptions.RuntimeError'>)
perm_spec is {u'users': {u'AnonymousUser': [u'view_resourcebase', u'download_resourcebase'], u'lprca': [u'view_resourcebase', u'download_resourcebase', u'change_resourcebase_metadata', u'change_resourcebase', u'delete_resourcebase', u'change_resourcebase_permissions', u'publish_resourcebase', u'change_layer_data', u'change_layer_style']}, u'groups': {u'anonymous': [u'view_resourcebase', u'download_resourcebase']}}

Interestingly enough; fix_geofence_rules fails for all of the layers where sync_geofence works. 




On Fri, Oct 12, 2018 at 3:12 PM Paolo Corti <[hidden email]> wrote:
I am getting exactly the same error, using master and GeoServer 2.13-SNAPSHOT
In the stack I also see "Could not retrieve GeoFence Rules count."
best
Paolo
On Fri, Oct 12, 2018 at 1:11 PM Michael Fedak <[hidden email]> wrote:
>
> 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
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/geonode-users



--
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
And finally, document uploads throws an error but the upload is still successful.  

On Fri, Oct 12, 2018 at 6:23 PM Michael Fedak <[hidden email]> wrote:
And also getting an error (Error updating permissions) when trying to add groups to layer permissions; although the permission change is still successful.  

On Fri, Oct 12, 2018 at 6:02 PM Michael Fedak <[hidden email]> wrote:
Also happens when I try sync_geofence:

('Unexpected error:', <type 'exceptions.RuntimeError'>)
perm_spec is {u'users': {u'AnonymousUser': [u'view_resourcebase', u'download_resourcebase'], u'lprca': [u'view_resourcebase', u'download_resourcebase', u'change_resourcebase_metadata', u'change_resourcebase', u'delete_resourcebase', u'change_resourcebase_permissions', u'publish_resourcebase', u'change_layer_data', u'change_layer_style']}, u'groups': {u'anonymous': [u'view_resourcebase', u'download_resourcebase']}}

Interestingly enough; fix_geofence_rules fails for all of the layers where sync_geofence works. 




On Fri, Oct 12, 2018 at 3:12 PM Paolo Corti <[hidden email]> wrote:
I am getting exactly the same error, using master and GeoServer 2.13-SNAPSHOT
In the stack I also see "Could not retrieve GeoFence Rules count."
best
Paolo
On Fri, Oct 12, 2018 at 1:11 PM Michael Fedak <[hidden email]> wrote:
>
> 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
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/geonode-users



--
Paolo Corti
Geospatial software developer
web: http://www.paolocorti.net
twitter: @capooti
skype: capooti

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
In reply to this post by Tweedle
Which version of GeoNode you installed and how? Master (aka 2.10) works only with geoserver 2.14+ 

2.8.x and below DO NOT WORK with geoserver 2.14+ but only with 2.13 and below.

Il ven 12 ott 2018, 19:11 Michael Fedak <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
Using geonode 2.8.x off the 2.8.x branch current to today. Geoserver is 2.12.2. installed on Ubuntu 16.04 in a virtualenv. 

On Fri, Oct 12, 2018, 7:40 PM Alessio Fabiani <[hidden email]> wrote:
Which version of GeoNode you installed and how? Master (aka 2.10) works only with geoserver 2.14+ 

2.8.x and below DO NOT WORK with geoserver 2.14+ but only with 2.13 and below.

Il ven 12 ott 2018, 19:11 Michael Fedak <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
In reply to this post by Tweedle
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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
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 <[hidden email]> wrote:
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
 @mikefedak I've just run another test by adding first some layers manually to GeoServer and then launching "updatelayers". This time I also have got an error, but it is related to another cause.

`Duplicate Rule Rule[id:null pri:150 srv:WPS ws:geonode l:relief_san_andres acc:ALLOW]`

I'll open a separate issue for that. I'm also assuming this might happen only with management commands since there isn't such check on the logic.

In order to avoid introducing more overhead, my idea is just to relax the check by just skipping duplicated rules.

I'm going to push a tentative fix and ask you to make another try.


Il giorno lun 15 ott 2018 alle ore 16:13 Michael Fedak <[hidden email]> 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 <[hidden email]> wrote:
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Alessio Fabiani
In reply to this post by Tweedle
This should fix the duplicated rules issue when running the management commands



Il giorno lun 15 ott 2018 alle ore 16:13 Michael Fedak <[hidden email]> 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 <[hidden email]> wrote:
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
I confirm that this fixes the management commands. 

On Mon, Oct 15, 2018 at 10:41 AM Alessio Fabiani <[hidden email]> wrote:
This should fix the duplicated rules issue when running the management commands



Il giorno lun 15 ott 2018 alle ore 16:13 Michael Fedak <[hidden email]> 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 <[hidden email]> wrote:
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
Reply | Threaded
Open this post in threaded view
|

Re: Recurring User 'None' Error Geofence/Geoserver

Tweedle
Now the only error I have remaining is around superuser logins for geoserver. 

If I try using the link from geonode, I get the following error. But if I use the 'authorize' link on the geoserver page the login occurs as intended. Logout seems to work perfectly after being logged in. 

2018-10-15 14:59:46,763 DEBUG [geoserver.security] - Bad credentials
org.springframework.security.authentication.BadCredentialsException: Bad credentials
at org.springframework.security.authentication.dao.DaoAuthenticationProvider.additionalAuthenticationChecks(DaoAuthenticationProvider.java:98)
at org.springframework.security.authentication.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:165)
at org.geoserver.security.auth.UsernamePasswordAuthenticationProvider.authenticate(UsernamePasswordAuthenticationProvider.java:78)
at org.geoserver.security.GeoServerAuthenticationProvider.authenticate(GeoServerAuthenticationProvider.java:54)
at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:167)
at org.geoserver.security.GeoServerSecurityManager.checkForDefaultAdminPassword(GeoServerSecurityManager.java:1440)
at org.geoserver.security.web.SecurityHomePageContentProvider$SecurityWarningsPanel.<init>(SecurityHomePageContentProvider.java:117)
at org.geoserver.security.web.SecurityHomePageContentProvider.getPageBodyComponent(SecurityHomePageContentProvider.java:44)
at org.geoserver.web.GeoServerHomePage$1.populateItem(GeoServerHomePage.java:133)
at org.apache.wicket.markup.html.list.ListView.onPopulate(ListView.java:523)
at org.apache.wicket.markup.repeater.AbstractRepeater.onBeforeRender(AbstractRepeater.java:124)
at org.apache.wicket.Component.internalBeforeRender(Component.java:950)
at org.apache.wicket.Component.beforeRender(Component.java:1018)
at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1836)
at org.apache.wicket.Component.onBeforeRender(Component.java:3916)
at org.apache.wicket.Page.onBeforeRender(Page.java:801)
at org.apache.wicket.Component.internalBeforeRender(Component.java:950)
at org.apache.wicket.Component.beforeRender(Component.java:1018)
at org.apache.wicket.Component.internalPrepareForRender(Component.java:2236)
at org.apache.wicket.Page.internalPrepareForRender(Page.java:242)
at org.apache.wicket.Component.render(Component.java:2325)
at org.apache.wicket.Page.renderPage(Page.java:1018)
at org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
at org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
at org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:157)
at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:174)
at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:963)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.filters.CorsFilter.handleNonCORS(CorsFilter.java:414)
at org.apache.catalina.filters.CorsFilter.doFilter(CorsFilter.java:169)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:26)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:69)
at org.geoserver.flow.controller.IpBlacklistFilter.doFilter(IpBlacklistFilter.java:89)
at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:66)
at org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:73)
at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:66)
at org.geoserver.monitor.MonitorFilter.doFilter(MonitorFilter.java:83)
at org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:66)
at org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:41)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:37)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:316)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:126)
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:90)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
at org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
at org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.filter.GeoServerAnonymousAuthenticationFilter.doFilter(GeoServerAnonymousAuthenticationFilter.java:51)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:205)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
at org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
at org.geoserver.security.filter.GeoServerUserNamePasswordAuthenticationFilter.doFilter(GeoServerUserNamePasswordAuthenticationFilter.java:112)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
at org.springframework.security.web.authentication.rememberme.RememberMeAuthenticationFilter.doFilter(RememberMeAuthenticationFilter.java:157)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
at org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.oauth2.GeoServerOAuthAuthenticationFilter.doFilter(GeoServerOAuthAuthenticationFilter.java:172)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:70)
at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:91)
at org.geoserver.security.filter.GeoServerSecurityContextPersistenceFilter$1.doFilter(GeoServerSecurityContextPersistenceFilter.java:52)
at org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:74)
at org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:91)
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:213)
at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:176)
at org.geoserver.security.GeoServerSecurityFilterChainProxy.doFilter(GeoServerSecurityFilterChainProxy.java:141)
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:262)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:90)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.SessionDebugFilter.doFilter(SessionDebugFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.geoserver.filters.FlushSafeFilter.doFilter(FlushSafeFilter.java:42)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:197)
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:651)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:500)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:754)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1376)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
2018-10-15 14:59:46,764 DEBUG [auth.GeoFenceAuthenticationProvider] - Auth request with org.springframework.security.authentication.UsernamePasswordAuthenticationToken@58b33e84: Principal: admin; Credentials: [PROTECTED]; Authenticated: false; Details: null; Not granted any authorities
2018-10-15 14:59:46,764 DEBUG [geofence.cache] - Loading user 'admin'
2018-10-15 14:59:46,765 WARN [geofence.cache] - org.geoserver.geofence.cache.CachedRuleReader$NoAuthException: Can't auth user [admin]
2018-10-15 14:59:46,765 DEBUG [auth.GeoFenceAuthenticationProvider] - Default admin credentials NOT authenticated -- probably a frontend check

On Mon, Oct 15, 2018 at 10:54 AM Michael Fedak <[hidden email]> wrote:
I confirm that this fixes the management commands. 

On Mon, Oct 15, 2018 at 10:41 AM Alessio Fabiani <[hidden email]> wrote:
This should fix the duplicated rules issue when running the management commands



Il giorno lun 15 ott 2018 alle ore 16:13 Michael Fedak <[hidden email]> 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 <[hidden email]> wrote:
Hi Michael,
thanks very much for helping on test.

I've finally figured out where the problem was. Fix available here


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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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@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@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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users

_______________________________________________
geonode-users mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geonode-users
12