[GeoNode-devel] Thumbnail update fails
Francesco Bartoli
xbartolone at gmail.com
Mon Aug 29 06:54:30 PDT 2016
Just notice such build has a special security provider for the authentication from django https://github.com/GeoNode/geoserver-geonode-ext
Francesco
Il giorno 29/ago/2016, alle ore 15:44, Guillaume Sueur <no-reply at neogeo-online.net> ha scritto:
> I'm gonna try with
> http://build.geonode.org/geoserver/latest/geoserver.war and see what
> happens.
> Thanks for your kind advices
>
> Guillaume
> Le 29/08/2016 à 15:40, Francesco Bartoli a écrit :
>> Maybe you can try with the official stable version 2.9.1 of geoserver
>> just making the operations manually with curl and see if the problem is
>> still happening careless of geonode.
>>
>> Regards,
>> Francesco
>>
>> Il giorno 29/ago/2016, alle ore 15:32, Simone Dalmasso
>> <simone.dalmasso at gmail.com <mailto:simone.dalmasso at gmail.com>> ha scritto:
>>
>>> Indeed is strange. Try to delete geoserver and the war file and run
>>> paver setup again. Let's see how it goes with a new one. (save your
>>> data dir if needed)
>>>
>>> 2016-08-29 15:28 GMT+02:00 Guillaume Sueur <no-reply at neogeo-online.net
>>> <mailto:no-reply at neogeo-online.net>>:
>>>
>>> Hi again,
>>>
>>> It's really weird. It seems that the printing module is correctly
>>> activated (geoserver/pdf/info.json sends some content,
>>> corresponding to
>>> the correct config.yaml file).
>>> But it's like the bindings with the REST API is not done. On another
>>> instance, if I request
>>> localhost:8080/geoserver/rest/printng/render.png
>>> I have an empty PNG in return. On this one, I keep having this
>>> damn 405
>>> error, just because it is not recognized by the REST API I guess.
>>>
>>> Any clue here ? Maybe I should ask the Geoserver mailing list. It's
>>> always hard to guess with these cross-software / configuration
>>> problems.
>>>
>>> Best regards
>>>
>>> Guillaume
>>>
>>>
>>> Le 29/08/2016 à 14:06, Simone Dalmasso a écrit :
>>>> And if you open that url in your browser you get a 405 too?
>>>>
>>>> In the layer detail page a 405 on /rest/styles is expected and is the
>>>> correct behavior. But not more than one.
>>>>
>>>> 2016-08-29 13:52 GMT+02:00 Guillaume Sueur <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>
>>>> <mailto:no-reply at neogeo-online.net
>>> <mailto:no-reply at neogeo-online.net>>>:
>>>>
>>>> Hi, thanks for your reply,
>>>>
>>>> Nothing shows up in the log, even in developer logging mode.
>>>> Anyway, what is strange is that I get a 405 error (method not allowed)
>>>> and not a 401 (authentication needed). The requested URL is correct
>>>> though... :
>>>>
>>>> http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180
>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180>
>>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180
>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=*************************&height=180>>
>>>>
>>>> (auth account and realm are correct too).
>>>>
>>>> Best regards
>>>>
>>>> Guillaume
>>>>
>>>> Le 29/08/2016 à 13:37, Simone Dalmasso a écrit :
>>>>> Hi, try to take a look at the geoserver logs to see if there is a
>>>>> problem with authenticating with geonode or a missing permission
>>>> (but I
>>>>> don't think). It may just be a small misconfiguration in geoserver.
>>>>>
>>>>> Hope this helps
>>>>>
>>>> http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse
>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse>
>>>> .org%2Cguillaume%2Ccatch22&height=180
>>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse
>>> <http://localhost:8080/geoserver/rest/printng/render.png?width=240&auth=geonode.aua-toulouse>
>>>> .org%2Cguillaume%2Ccatch22&height=180>
>>>>> 2016-08-29 12:23 GMT+02:00 Guillaume Sueur
>>>> <no-reply at neogeo-online.net <mailto:no-reply at neogeo-online.net>
>>> <mailto:no-reply at neogeo-online.net
>>> <mailto:no-reply at neogeo-online.net>>
>>>>> <mailto:no-reply at neogeo-online.net
>>> <mailto:no-reply at neogeo-online.net>
>>>> <mailto:no-reply at neogeo-online.net
>>> <mailto:no-reply at neogeo-online.net>>>>:
>>>>>
>>>>> Hi list,
>>>>>
>>>>> I am experiencing a weird problem with geonode and
>>> geoserver
>>>> rest API.
>>>>> Here is the story. I have a bunch of layers in
>>> Geoserver, and
>>>> I can
>>>>> updatelayers from Geonode without any problem, having the
>>>> thumbnails
>>>>> correctly created in uploaded/thumbs directory, and
>>> correctly
>>>> set to
>>>>> www-data ownership afterwards to avoid any problem when
>>>> updating from
>>>>> the web interface.
>>>>>
>>>>> Then, if I use the "Define Thumbnail" button from the
>>> Layer
>>>> Edit Window,
>>>>> an empty image is created over the previously created
>>>> thumbnail. I dig a
>>>>> bit into the code trying to locate the issue. It seems it
>>>> comes from
>>>>> geoserver api which replies to the request emitted in
>>>>> geoserver/helpers.py on line 1687 with :
>>>>>
>>>>> Thumbnail created : {'date': 'Mon, 29 Aug 2016
>>> 10:19:56 GMT',
>>>> 'status':
>>>>> '405', 'content-length': '0'
>>>>> , 'allow': 'GET', 'server':
>>> 'Noelios-Restlet-Engine/1.0..8'}
>>>>>
>>>>> which means that the Method Not allowed error wasn't
>>> caught back
>>>>> correctly by geonode who continued the process and
>>> wrote the empty
>>>>> content to a new file.
>>>>>
>>>>> I just don't understand why I received this 405 HTTP
>>> error in this
>>>>> situation, that I have seen working well on other Geonode
>>>> Instances.
>>>>>
>>>>> I've made the installation following the custom
>>> installation
>>>> guide last
>>>>> week, so I guess with some fresh github code.
>>>>>
>>>>> Any clue ?
>>>>>
>>>>> Best regards
>>>>>
>>>>> Guillaume
>>>>> _______________________________________________
>>>>> geonode-devel mailing list
>>>>> geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>
>>>> <mailto:geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>>
>>>> <mailto:geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>
>>>> <mailto:geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>>>
>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>
>>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Simone
>>>> _______________________________________________
>>>> geonode-devel mailing list
>>>> geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>
>>> <mailto:geonode-devel at lists.osgeo.org
>>> <mailto:geonode-devel at lists.osgeo.org>>
>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>
>>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>> <http://lists.osgeo.org/mailman/listinfo/geonode-devel>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Simone
>>>
>>>
>>>
>>>
>>> --
>>> Simone
>>> _______________________________________________
>>> geonode-devel mailing list
>>> geonode-devel at lists.osgeo.org <mailto:geonode-devel at lists.osgeo.org>
>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20160829/cc7b2e89/attachment.html>
More information about the geonode-devel
mailing list