librelist archives

« back to archive

Geoserver OWS fail

Geoserver OWS fail

From:
Jude Mwenda
Date:
2011-05-19 @ 08:20
Hi,
Maps are not loading. I get the following when i download the WMS 1.1.1
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
ServiceExceptionReport SYSTEM "

http://ec2-67-202-9-183.compute-1.amazonaws.com:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
<ServiceExceptionReport version="1.1.1" >   <ServiceException>
      Translator error
Translator error
null
</ServiceException></ServiceExceptionReport>

On checking the geoserver error log, attached is what i see.
http://dpaste.de/2SMw/

Re: [geonode] Geoserver OWS fail

From:
David Winslow
Date:
2011-05-19 @ 10:38
This sort of error indicates a missing configuration in GeoServer (as in,
GeoServer failed to automatically configure a layer you uploaded.)

Here is a script I use when this problem develops in GeoNode sites that I
maintain.  It generates a lot of noise but if you look for the properties
that are listed only once or a few times instead of for each layer you
should be able to find the culprit.  https://gist.github.com/891080

Judging from the stack trace it looks like the latlon_bbox (and probably
also the projection) are the missing fields, not sure which layer.

--
David Winslow
OpenGeo -  http://opengeo.org/

On Thu, May 19, 2011 at 4:20 AM, Jude Mwenda <jude@upande.com> wrote:

> Hi,
> Maps are not loading. I get the following when i download the WMS 1.1.1
> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
> ServiceExceptionReport SYSTEM "
> 
http://ec2-67-202-9-183.compute-1.amazonaws.com:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
> <ServiceExceptionReport version="1.1.1" >   <ServiceException>
>       Translator error
> Translator error
> null
> </ServiceException></ServiceExceptionReport>
>
> On checking the geoserver error log, attached is what i see.
> http://dpaste.de/2SMw/
>

Re: [geonode] Geoserver OWS fail

From:
Jude Mwenda
Date:
2011-05-19 @ 11:37
Thanks let me give it a try.

2011/5/19 David Winslow <dwinslow@opengeo.org>

> This sort of error indicates a missing configuration in GeoServer (as in,
> GeoServer failed to automatically configure a layer you uploaded.)
>
> Here is a script I use when this problem develops in GeoNode sites that I
> maintain.  It generates a lot of noise but if you look for the properties
> that are listed only once or a few times instead of for each layer you
> should be able to find the culprit.  https://gist.github.com/891080
>
> Judging from the stack trace it looks like the latlon_bbox (and probably
> also the projection) are the missing fields, not sure which layer.
>
> --
> David Winslow
> OpenGeo -  http://opengeo.org/
>
> On Thu, May 19, 2011 at 4:20 AM, Jude Mwenda <jude@upande.com> wrote:
>
>> Hi,
>> Maps are not loading. I get the following when i download the WMS 1.1.1
>> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
>> ServiceExceptionReport SYSTEM "
>> 
http://ec2-67-202-9-183.compute-1.amazonaws.com:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
>> <ServiceExceptionReport version="1.1.1" >   <ServiceException>
>>       Translator error
>> Translator error
>> null
>> </ServiceException></ServiceExceptionReport>
>>
>> On checking the geoserver error log, attached is what i see.
>> http://dpaste.de/2SMw/
>>
>
>

Re: [geonode] Geoserver OWS fail

From:
Jude Mwenda
Date:
2011-05-20 @ 09:09
Hi,
I did run the script, i presume the layers with NONE as the ones that are
brining the issue and those need to be removed?

regards

2011/5/19 Jude Mwenda <jude@upande.com>

> Thanks let me give it a try.
>
>
> 2011/5/19 David Winslow <dwinslow@opengeo.org>
>
>> This sort of error indicates a missing configuration in GeoServer (as in,
>> GeoServer failed to automatically configure a layer you uploaded.)
>>
>> Here is a script I use when this problem develops in GeoNode sites that I
>> maintain.  It generates a lot of noise but if you look for the properties
>> that are listed only once or a few times instead of for each layer you
>> should be able to find the culprit.  https://gist.github.com/891080
>>
>> Judging from the stack trace it looks like the latlon_bbox (and probably
>> also the projection) are the missing fields, not sure which layer.
>>
>> --
>> David Winslow
>> OpenGeo -  http://opengeo.org/
>>
>> On Thu, May 19, 2011 at 4:20 AM, Jude Mwenda <jude@upande.com> wrote:
>>
>>> Hi,
>>> Maps are not loading. I get the following when i download the WMS 1.1.1
>>> <?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE
>>> ServiceExceptionReport SYSTEM "
>>> 
http://ec2-67-202-9-183.compute-1.amazonaws.com:80/geoserver-geonode-dev/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd">
>>> <ServiceExceptionReport version="1.1.1" >   <ServiceException>
>>>       Translator error
>>> Translator error
>>> null
>>> </ServiceException></ServiceExceptionReport>
>>>
>>> On checking the geoserver error log, attached is what i see.
>>> http://dpaste.de/2SMw/
>>>
>>
>>
>