[GeoNode-users] problems connect refused when upload shapefiles in geonode
SILVIA GAMERO
gamerinsky at gmail.com
Thu Feb 22 12:10:31 PST 2018
Thanks for your time,
On Thu, Feb 22, 2018 at 11:38 AM, Alessio Fabiani
<alessio.fabiani at geo-solutions.it> wrote:
> Uhm, interesting.
> Could be maybe an issue with some logging stuff. It's a bit difficult to
> debug without being able to reproduce the issue.
>
> I'll try to have a look at the methods above and see if something pops up
> into my mind.
>
> Regards,
>
> Alessio Fabiani
>
> ==
> GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
> for more information.
> ==
>
> Ing. Alessio Fabiani
>
> @alfa7691
> Founder/Technical Lead
>
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
> file/s allegato/i sono da considerarsi strettamente riservate. Il loro
> utilizzo è consentito esclusivamente al destinatario del messaggio, per le
> finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio
> senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
> via e-mail e di procedere alla distruzione del messaggio stesso,
> cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo
> anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per
> finalità diverse, costituisce comportamento contrario ai principi dettati
> dal D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender does
> not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
>
> 2018-02-22 18:31 GMT+01:00 SILVIA GAMERO <gamerinsky at gmail.com>:
>>
>> Hi, Alessio check the data set, I have tried several data sets that
>> apparently are fine and all of them with utf-8, in addition to making
>> the change you mentioned in the previous mail.
>>
>> Also change the regional configuration of the server too, for my case
>> es_SV.iso88591
>>
>> But it shows the following error now:
>>
>>
>> [22/Feb/2018 11:11:53] "GET /upload/progress HTTP/1.1" 200 17
>> Traceback (most recent call last):
>> File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
>> msg = self.format(record)
>> File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
>> return fmt.format(record)
>> File "/usr/lib64/python2.7/logging/__init__.py", line 464, in format
>> record.message = record.getMessage()
>> Archivo "/usr/lib64/python2.7/logging/__init__.py", línea 328, en
>> getMessage
>> msg = msg% self.args
>> UnicodeDecodeError: el códec 'ascii' no puede decodificar el byte 0xf3
>> en la posición 24: el ordinal no está dentro del rango (128)
>> Registrado desde el archivo helpers.py, línea 369
>> Traceback (última llamada más reciente):
>> Archivo "/usr/lib64/python2.7/logging/__init__.py", línea 851, en emitir
>> msg = self.format (registro )
>> Archivo "/usr/lib64/python2.7/logging/__init__.py", línea 724, en
>> formato
>> return fmt.format (registro)
>> Archivo "/usr/lib64/python2.7/logging/__init__.py", línea 467, en
>> formato
>> s = self._fmt% record .__ dict__
>>
>>
>>
>> Thanks,
>>
>>
>>
>>
>>
>>
>> TypeError: coaccionando un Unicode: necesita cadena o buffer,
>> GeoNodeException encontrado
>> [22 / Feb / 2018 11:11:54] "POST / capas / carga HTTP / 1.1" 500 49478
>>
>>
>> 2018-02-22 9:07 GMT-06:00 Alessio Fabiani
>> <alessio.fabiani at geo-solutions.it>:
>> > Hi Silvia,
>> > I guess the original error is on the dataset, most probably your
>> > shapefile
>> > (or whatever) contains non-ASCII characters and GeoServer/JVM runs
>> > without
>> > the correct encoding.
>> >
>> > I kindly suggest to pre-process your data and make sure all letters are
>> > printable.
>> >
>> > To fix the Python error you are pointing on the logs below, try to
>> > change
>> > the the line 174 of file
>> > "/opt/apps/geonode/geonode/geonode/layers/views.py"
>> >
>> > from
>> >
>> > out['errors'] = str(error)
>> >
>> > to
>> >
>> > out['errors'] = unicode(error, 'utf-8').encode('utf-8')
>> >
>> >
>> >
>> > Regards,
>> >
>> > Alessio Fabiani
>> >
>> > ==
>> > GeoServer Professional Services from the experts! Visit
>> > http://goo.gl/it488V
>> > for more information.
>> > ==
>> >
>> > Ing. Alessio Fabiani
>> >
>> > @alfa7691
>> > Founder/Technical Lead
>> >
>> >
>> > GeoSolutions S.A.S.
>> > Via di Montramito 3/A
>> > 55054 Massarosa (LU)
>> > Italy
>> > phone: +39 0584 962313
>> > fax: +39 0584 1660272
>> > mob: +39 331 6233686
>> >
>> > http://www.geo-solutions.it
>> > http://twitter.com/geosolutions_it
>> >
>> > -------------------------------------------------------
>> >
>> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>> >
>> > Le informazioni contenute in questo messaggio di posta elettronica e/o
>> > nel/i
>> > file/s allegato/i sono da considerarsi strettamente riservate. Il loro
>> > utilizzo è consentito esclusivamente al destinatario del messaggio, per
>> > le
>> > finalità indicate nel messaggio stesso. Qualora riceviate questo
>> > messaggio
>> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene
>> > notizia
>> > via e-mail e di procedere alla distruzione del messaggio stesso,
>> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> > divulgarlo
>> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo
>> > per
>> > finalità diverse, costituisce comportamento contrario ai principi
>> > dettati
>> > dal D.Lgs. 196/2003.
>> >
>> > The information in this message and/or attachments, is intended solely
>> > for
>> > the attention and use of the named addressee(s) and may be confidential
>> > or
>> > proprietary in nature or covered by the provisions of privacy act
>> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> > Code).Any use not in accord with its purpose, any disclosure,
>> > reproduction,
>> > copying, distribution, or either dissemination, either whole or partial,
>> > is
>> > strictly forbidden except previous formal approval of the named
>> > addressee(s). If you are not the intended recipient, please contact
>> > immediately the sender by telephone, fax or e-mail and delete the
>> > information in this message that has been received in error. The sender
>> > does
>> > not give any warranty or accept liability as the content, accuracy or
>> > completeness of sent messages and accepts no responsibility for changes
>> > made after they were sent or for other risks which arise as a result of
>> > e-mail transmission, viruses, etc.
>> >
>> >
>> > 2018-02-22 15:52 GMT+01:00 SILVIA GAMERO <gamerinsky at gmail.com>:
>> >>
>> >> Thanks toni, at this time, it does not show that error, but it shows
>> >> another when wanting to upload the layer.
>> >> I have read that it is related to the regional configuration, and that
>> >> it would be easier to solve it on the server, but I do not know what
>> >> would be the best configuration in this case.
>> >>
>> >> I have this configuration in my server:
>> >>
>> >> System Locale: LANG=es_SV.UTF-8
>> >> VC Keymap: latam
>> >> X11 Layout: latam
>> >>
>> >> Although when uploading the layer select UTF-8, it always gives an
>> >> error.
>> >>
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
>> >> msg = self.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
>> >> return fmt.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 464, in format
>> >> record.message = record.getMessage()
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 328, in
>> >> getMessage
>> >> msg = msg % self.args
>> >> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
>> >> 24: ordinal not in range(128)
>> >> Logged from file helpers.py, line 369
>> >> Traceback (most recent call last):
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
>> >> msg = self.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
>> >> return fmt.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 467, in format
>> >> s = self._fmt % record.__dict__
>> >> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in
>> >> position 22: ordinal not in range(128)
>> >> Logged from file views.py, line 172
>> >> Internal Server Error: /layers/upload
>> >> Traceback (most recent call last):
>> >> File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py",
>> >> line 132, in get_response
>> >> response = wrapped_callback(request, *callback_args,
>> >> **callback_kwargs)
>> >> File
>> >> "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py",
>> >> line 22, in _wrapped_view
>> >> return view_func(request, *args, **kwargs)
>> >> File "/opt/apps/geonode/geonode/geonode/layers/views.py", line 174,
>> >> in layer_upload
>> >> out['errors'] = str(error)
>> >> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in
>> >> position 22: ordinal not in range(128)
>> >>
>> >> 2018-02-22 4:10 GMT-06:00 Toni Schönbuchner
>> >> <toni.schoenbuchner at csgis.de>:
>> >> > Hi Alessio,
>> >> >
>> >> > great ! thanks for clarification! As I understood Silvia´s question
>> >> > the
>> >> > upload of Layers is not
>> >> > working. Means there might (still) be some misconfiguration. Let´s
>> >> > see
>> >> > what
>> >> > Silvia says.
>> >> >
>> >> > cheers,
>> >> >
>> >> > Toni
>> >> >
>> >> > -----------------------------------------------
>> >> > CSGIS
>> >> >
>> >> > -----------------------------------------------
>> >> > Kolonnadenstraße 1
>> >> > 04109 Leipzig
>> >> > -----------------------------------------------
>> >> > Mobil +49/ (0) 176 6680 3198
>> >> > Tel +49/ (0) 341 24 04 738
>> >> > Fax +49/ (0) 341 24 04 73
>> >> > Web http://csgis.de
>> >> > -----------------------------------------------
>> >> >
>> >> > Hinweis gemäß § 33 BDSG
>> >> > Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument
>> >> > ist
>> >> > ausschließlich für den
>> >> > Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls Sie
>> >> > diese
>> >> > E-Mail versehentlich
>> >> > erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und
>> >> > löschen
>> >> > Sie diese Nachricht
>> >> > von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung,
>> >> > Vervielfältigung, Veränderung,
>> >> > Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.
>> >> >
>> >> > Am 22.02.2018 um 10:06 schrieb Alessio Fabiani
>> >> > <alessio.fabiani at geo-solutions.it>:
>> >> >
>> >> > Dear Toni and Silvia,
>> >> >
>> >> > do not worry for that message. It is caused by the GeoServer
>> >> > notification
>> >> > plugin trying to reach the messaging server.
>> >> >
>> >> > It is not a real error. Just a too much verbose logging from
>> >> > GeoServer
>> >> > (which must be improved of course). However that is not an error and
>> >> > does
>> >> > not prevent GeoServer to work normally with the standard
>> >> > configuration.
>> >> >
>> >> > Regards,
>> >> > Alessio Fabiani
>> >> > ==
>> >> > GeoServer Professional Services from the experts! Visit
>> >> > http://goo.gl/it488V
>> >> > for more information.
>> >> > ==
>> >> >
>> >> > Ing. Alessio Fabiani
>> >> > @alfa7691
>> >> > Founder/Technical Lead
>> >> >
>> >> > GeoSolutions S.A.S.
>> >> > Via di Montramito 3/A
>> >> > 55054 Massarosa (LU)
>> >> > Italy
>> >> > phone: +39 0584 962313
>> >> > fax: +39 0584 1660272
>> >> > mob: +39 331 6233686
>> >> >
>> >> > http://www.geo-solutions.it
>> >> > http://twitter.com/geosolutions_it
>> >> >
>> >> > -------------------------------------------------------
>> >> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>> >> > Le informazioni contenute in questo messaggio di posta elettronica
>> >> > e/o
>> >> > nel/i
>> >> > file/s allegato/i sono da considerarsi strettamente riservate. Il
>> >> > loro
>> >> > utilizzo è consentito esclusivamente al destinatario del messaggio,
>> >> > per
>> >> > le
>> >> > finalità indicate nel messaggio stesso. Qualora riceviate questo
>> >> > messaggio
>> >> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene
>> >> > notizia
>> >> > via e-mail e di procedere alla distruzione del messaggio stesso,
>> >> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> >> > divulgarlo
>> >> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>> >> > utilizzarlo
>> >> > per
>> >> > finalità diverse, costituisce comportamento contrario ai principi
>> >> > dettati
>> >> > dal D.Lgs. 196/2003.
>> >> >
>> >> > The information in this message and/or attachments, is intended
>> >> > solely
>> >> > for
>> >> > the attention and use of the named addressee(s) and may be
>> >> > confidential
>> >> > or
>> >> > proprietary in nature or covered by the provisions of privacy act
>> >> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data
>> >> > Protection
>> >> > Code).Any use not in accord with its purpose, any disclosure,
>> >> > reproduction,
>> >> > copying, distribution, or either dissemination, either whole or
>> >> > partial,
>> >> > is
>> >> > strictly forbidden except previous formal approval of the named
>> >> > addressee(s). If you are not the intended recipient, please contact
>> >> > immediately the sender by telephone, fax or e-mail and delete the
>> >> > information in this message that has been received in error. The
>> >> > sender
>> >> > does
>> >> > not give any warranty or accept liability as the content, accuracy or
>> >> > completeness of sent messages and accepts no responsibility for
>> >> > changes
>> >> > made after they were sent or for other risks which arise as a result
>> >> > of
>> >> > e-mail transmission, viruses, etc.
>> >> >
>> >> > 2018-02-21 18:07 GMT+01:00 Toni Schönbuchner
>> >> > <toni.schoenbuchner at csgis.de>:
>> >> >>
>> >> >> Dear Silvia,
>> >> >>
>> >> >> if according to the manual I have made the indicated changes, at
>> >> >> least
>> >> >> in
>> >> >> the connection configuration of postgres and local_settings.
>> >> >>
>> >> >>
>> >> >> I just gone through your mail and logs again. I would have bet that
>> >> >> your
>> >> >> geoserver is down.
>> >> >> Unfortunately I´m unfamiliar with installation on centos7. My guess
>> >> >> is
>> >> >> that something is misconfigured
>> >> >> with auth between geonode and geoserver. We should check that
>> >> >> everything
>> >> >> is setup correctly.
>> >> >>
>> >> >> This gist shows a working local_settings.py for geonode2.6:
>> >> >> https://gist.github.com/t-book/0da94fce8c88a1e31dc9f14f99e2aa1b
>> >> >> Please compare it with your settings.
>> >> >> I´ve marked the parts where you should take special care of with (
>> >> >> !!!
>> >> >> ).
>> >> >> ( Replace the credentials and IP regarding your setup. )
>> >> >>
>> >> >> Next visit geoserver admin GUI and navigate to security
>> >> >> „authentification“. Here click
>> >> >> the geonode-oauth2 link. Compare the URL configuration with the one
>> >> >> I´ve
>> >> >> posted as image in the gist (link above).
>> >> >> It shows you where to set the server IP and where localhost.
>> >> >>
>> >> >> Last but not least go to
>> >> >> geonode admin -> applications -> GeoServer
>> >> >>
>> >> >> and check your IP and secret etc as well.
>> >> >> (Image posted under gist as well)
>> >> >>
>> >> >> If all this does not help something else blocks your connection …
>> >> >> like
>> >> >> iptables etc.
>> >> >> But this is really hard to guess.
>> >> >>
>> >> >> Hope this helps a bit to get you started.
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Toni
>> >> >>
>> >> >> -----------------------------------------------
>> >> >> CSGIS
>> >> >>
>> >> >> -----------------------------------------------
>> >> >> Kolonnadenstraße 1
>> >> >> 04109 Leipzig
>> >> >> -----------------------------------------------
>> >> >> Mobil +49/ (0) 176 6680 3198
>> >> >> Tel +49/ (0) 341 24 04 738
>> >> >> Fax +49/ (0) 341 24 04 73
>> >> >> Web http://csgis.de
>> >> >> -----------------------------------------------
>> >> >>
>> >> >> Hinweis gemäß § 33 BDSG
>> >> >> Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument
>> >> >> ist
>> >> >> ausschließlich für den
>> >> >> Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls
>> >> >> Sie
>> >> >> diese E-Mail versehentlich
>> >> >> erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und
>> >> >> löschen Sie diese Nachricht
>> >> >> von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung,
>> >> >> Vervielfältigung, Veränderung,
>> >> >> Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.
>> >> >>
>> >> >> Am 21.02.2018 um 16:06 schrieb SILVIA GAMERO <gamerinsky at gmail.com>:
>> >> >>
>> >> >> Toni, thanks for your help
>> >> >> Geoserver is responding correctly, and if I have restarted tomcat
>> >> >> without
>> >> >> any improvement.
>> >> >>
>> >> >> It is obvious that you can not connect, but I can not know what
>> >> >> configuration I should modify, if according to the manual I have
>> >> >> made
>> >> >> the
>> >> >> indicated changes, at least in the connection configuration of
>> >> >> postgres
>> >> >> and
>> >> >> local_settings.
>> >> >>
>> >> >> 2018-02-21 08:12:45,115 ERROR [common.sender] - Conexión rehusada
>> >> >> (Connection refused)
>> >> >> java.net.ConnectException: Conexión rehusada (Connection refused)
>> >> >> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>> >> >> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> >> >> at java.net.Socket.connect(Socket.java:589)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.SocketFrameHandlerFactory.create(SocketFrameHandlerFactory.java:50)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:60)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:99)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:900)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:859)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:817)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:954)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.sender.RabbitMQSender.initialize(RabbitMQSender.java:79)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.sender.RabbitMQSender.send(RabbitMQSender.java:98)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.DefaultNotificationProcessor.process(DefaultNotificationProcessor.java:39)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.MessageProcessor$WorkerThread.run(MessageProcessor.java:79)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> >> >> at java.lang.Thread.run(Thread.java:748)
>> >> >>
>> >> >> Do you have any idea?
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> geonode-users mailing list
>> >> >> geonode-users at lists.osgeo.org
>> >> >> https://lists.osgeo.org/mailman/listinfo/geonode-users
>> >> >>
>> >> >
>> >> >
>> >
>> >
>>
>> On Thu, Feb 22, 2018 at 9:07 AM, Alessio Fabiani
>> <alessio.fabiani at geo-solutions.it> wrote:
>> > Hi Silvia,
>> > I guess the original error is on the dataset, most probably your
>> > shapefile
>> > (or whatever) contains non-ASCII characters and GeoServer/JVM runs
>> > without
>> > the correct encoding.
>> >
>> > I kindly suggest to pre-process your data and make sure all letters are
>> > printable.
>> >
>> > To fix the Python error you are pointing on the logs below, try to
>> > change
>> > the the line 174 of file
>> > "/opt/apps/geonode/geonode/geonode/layers/views.py"
>> >
>> > from
>> >
>> > out['errors'] = str(error)
>> >
>> > to
>> >
>> > out['errors'] = unicode(error, 'utf-8').encode('utf-8')
>> >
>> >
>> >
>> > Regards,
>> >
>> > Alessio Fabiani
>> >
>> > ==
>> > GeoServer Professional Services from the experts! Visit
>> > http://goo.gl/it488V
>> > for more information.
>> > ==
>> >
>> > Ing. Alessio Fabiani
>> >
>> > @alfa7691
>> > Founder/Technical Lead
>> >
>> >
>> > GeoSolutions S.A.S.
>> > Via di Montramito 3/A
>> > 55054 Massarosa (LU)
>> > Italy
>> > phone: +39 0584 962313
>> > fax: +39 0584 1660272
>> > mob: +39 331 6233686
>> >
>> > http://www.geo-solutions.it
>> > http://twitter.com/geosolutions_it
>> >
>> > -------------------------------------------------------
>> >
>> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>> >
>> > Le informazioni contenute in questo messaggio di posta elettronica e/o
>> > nel/i
>> > file/s allegato/i sono da considerarsi strettamente riservate. Il loro
>> > utilizzo è consentito esclusivamente al destinatario del messaggio, per
>> > le
>> > finalità indicate nel messaggio stesso. Qualora riceviate questo
>> > messaggio
>> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene
>> > notizia
>> > via e-mail e di procedere alla distruzione del messaggio stesso,
>> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> > divulgarlo
>> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo
>> > per
>> > finalità diverse, costituisce comportamento contrario ai principi
>> > dettati
>> > dal D.Lgs. 196/2003.
>> >
>> > The information in this message and/or attachments, is intended solely
>> > for
>> > the attention and use of the named addressee(s) and may be confidential
>> > or
>> > proprietary in nature or covered by the provisions of privacy act
>> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> > Code).Any use not in accord with its purpose, any disclosure,
>> > reproduction,
>> > copying, distribution, or either dissemination, either whole or partial,
>> > is
>> > strictly forbidden except previous formal approval of the named
>> > addressee(s). If you are not the intended recipient, please contact
>> > immediately the sender by telephone, fax or e-mail and delete the
>> > information in this message that has been received in error. The sender
>> > does
>> > not give any warranty or accept liability as the content, accuracy or
>> > completeness of sent messages and accepts no responsibility for changes
>> > made after they were sent or for other risks which arise as a result of
>> > e-mail transmission, viruses, etc.
>> >
>> >
>> > 2018-02-22 15:52 GMT+01:00 SILVIA GAMERO <gamerinsky at gmail.com>:
>> >>
>> >> Thanks toni, at this time, it does not show that error, but it shows
>> >> another when wanting to upload the layer.
>> >> I have read that it is related to the regional configuration, and that
>> >> it would be easier to solve it on the server, but I do not know what
>> >> would be the best configuration in this case.
>> >>
>> >> I have this configuration in my server:
>> >>
>> >> System Locale: LANG=es_SV.UTF-8
>> >> VC Keymap: latam
>> >> X11 Layout: latam
>> >>
>> >> Although when uploading the layer select UTF-8, it always gives an
>> >> error.
>> >>
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
>> >> msg = self.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
>> >> return fmt.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 464, in format
>> >> record.message = record.getMessage()
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 328, in
>> >> getMessage
>> >> msg = msg % self.args
>> >> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
>> >> 24: ordinal not in range(128)
>> >> Logged from file helpers.py, line 369
>> >> Traceback (most recent call last):
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit
>> >> msg = self.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format
>> >> return fmt.format(record)
>> >> File "/usr/lib64/python2.7/logging/__init__.py", line 467, in format
>> >> s = self._fmt % record.__dict__
>> >> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in
>> >> position 22: ordinal not in range(128)
>> >> Logged from file views.py, line 172
>> >> Internal Server Error: /layers/upload
>> >> Traceback (most recent call last):
>> >> File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py",
>> >> line 132, in get_response
>> >> response = wrapped_callback(request, *callback_args,
>> >> **callback_kwargs)
>> >> File
>> >> "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py",
>> >> line 22, in _wrapped_view
>> >> return view_func(request, *args, **kwargs)
>> >> File "/opt/apps/geonode/geonode/geonode/layers/views.py", line 174,
>> >> in layer_upload
>> >> out['errors'] = str(error)
>> >> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in
>> >> position 22: ordinal not in range(128)
>> >>
>> >> 2018-02-22 4:10 GMT-06:00 Toni Schönbuchner
>> >> <toni.schoenbuchner at csgis.de>:
>> >> > Hi Alessio,
>> >> >
>> >> > great ! thanks for clarification! As I understood Silvia´s question
>> >> > the
>> >> > upload of Layers is not
>> >> > working. Means there might (still) be some misconfiguration. Let´s
>> >> > see
>> >> > what
>> >> > Silvia says.
>> >> >
>> >> > cheers,
>> >> >
>> >> > Toni
>> >> >
>> >> > -----------------------------------------------
>> >> > CSGIS
>> >> >
>> >> > -----------------------------------------------
>> >> > Kolonnadenstraße 1
>> >> > 04109 Leipzig
>> >> > -----------------------------------------------
>> >> > Mobil +49/ (0) 176 6680 3198
>> >> > Tel +49/ (0) 341 24 04 738
>> >> > Fax +49/ (0) 341 24 04 73
>> >> > Web http://csgis.de
>> >> > -----------------------------------------------
>> >> >
>> >> > Hinweis gemäß § 33 BDSG
>> >> > Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument
>> >> > ist
>> >> > ausschließlich für den
>> >> > Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls Sie
>> >> > diese
>> >> > E-Mail versehentlich
>> >> > erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und
>> >> > löschen
>> >> > Sie diese Nachricht
>> >> > von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung,
>> >> > Vervielfältigung, Veränderung,
>> >> > Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.
>> >> >
>> >> > Am 22.02.2018 um 10:06 schrieb Alessio Fabiani
>> >> > <alessio.fabiani at geo-solutions.it>:
>> >> >
>> >> > Dear Toni and Silvia,
>> >> >
>> >> > do not worry for that message. It is caused by the GeoServer
>> >> > notification
>> >> > plugin trying to reach the messaging server.
>> >> >
>> >> > It is not a real error. Just a too much verbose logging from
>> >> > GeoServer
>> >> > (which must be improved of course). However that is not an error and
>> >> > does
>> >> > not prevent GeoServer to work normally with the standard
>> >> > configuration.
>> >> >
>> >> > Regards,
>> >> > Alessio Fabiani
>> >> > ==
>> >> > GeoServer Professional Services from the experts! Visit
>> >> > http://goo.gl/it488V
>> >> > for more information.
>> >> > ==
>> >> >
>> >> > Ing. Alessio Fabiani
>> >> > @alfa7691
>> >> > Founder/Technical Lead
>> >> >
>> >> > GeoSolutions S.A.S.
>> >> > Via di Montramito 3/A
>> >> > 55054 Massarosa (LU)
>> >> > Italy
>> >> > phone: +39 0584 962313
>> >> > fax: +39 0584 1660272
>> >> > mob: +39 331 6233686
>> >> >
>> >> > http://www.geo-solutions.it
>> >> > http://twitter.com/geosolutions_it
>> >> >
>> >> > -------------------------------------------------------
>> >> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>> >> > Le informazioni contenute in questo messaggio di posta elettronica
>> >> > e/o
>> >> > nel/i
>> >> > file/s allegato/i sono da considerarsi strettamente riservate. Il
>> >> > loro
>> >> > utilizzo è consentito esclusivamente al destinatario del messaggio,
>> >> > per
>> >> > le
>> >> > finalità indicate nel messaggio stesso. Qualora riceviate questo
>> >> > messaggio
>> >> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene
>> >> > notizia
>> >> > via e-mail e di procedere alla distruzione del messaggio stesso,
>> >> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> >> > divulgarlo
>> >> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>> >> > utilizzarlo
>> >> > per
>> >> > finalità diverse, costituisce comportamento contrario ai principi
>> >> > dettati
>> >> > dal D.Lgs. 196/2003.
>> >> >
>> >> > The information in this message and/or attachments, is intended
>> >> > solely
>> >> > for
>> >> > the attention and use of the named addressee(s) and may be
>> >> > confidential
>> >> > or
>> >> > proprietary in nature or covered by the provisions of privacy act
>> >> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data
>> >> > Protection
>> >> > Code).Any use not in accord with its purpose, any disclosure,
>> >> > reproduction,
>> >> > copying, distribution, or either dissemination, either whole or
>> >> > partial,
>> >> > is
>> >> > strictly forbidden except previous formal approval of the named
>> >> > addressee(s). If you are not the intended recipient, please contact
>> >> > immediately the sender by telephone, fax or e-mail and delete the
>> >> > information in this message that has been received in error. The
>> >> > sender
>> >> > does
>> >> > not give any warranty or accept liability as the content, accuracy or
>> >> > completeness of sent messages and accepts no responsibility for
>> >> > changes
>> >> > made after they were sent or for other risks which arise as a result
>> >> > of
>> >> > e-mail transmission, viruses, etc.
>> >> >
>> >> > 2018-02-21 18:07 GMT+01:00 Toni Schönbuchner
>> >> > <toni.schoenbuchner at csgis.de>:
>> >> >>
>> >> >> Dear Silvia,
>> >> >>
>> >> >> if according to the manual I have made the indicated changes, at
>> >> >> least
>> >> >> in
>> >> >> the connection configuration of postgres and local_settings.
>> >> >>
>> >> >>
>> >> >> I just gone through your mail and logs again. I would have bet that
>> >> >> your
>> >> >> geoserver is down.
>> >> >> Unfortunately I´m unfamiliar with installation on centos7. My guess
>> >> >> is
>> >> >> that something is misconfigured
>> >> >> with auth between geonode and geoserver. We should check that
>> >> >> everything
>> >> >> is setup correctly.
>> >> >>
>> >> >> This gist shows a working local_settings.py for geonode2.6:
>> >> >> https://gist.github.com/t-book/0da94fce8c88a1e31dc9f14f99e2aa1b
>> >> >> Please compare it with your settings.
>> >> >> I´ve marked the parts where you should take special care of with (
>> >> >> !!!
>> >> >> ).
>> >> >> ( Replace the credentials and IP regarding your setup. )
>> >> >>
>> >> >> Next visit geoserver admin GUI and navigate to security
>> >> >> „authentification“. Here click
>> >> >> the geonode-oauth2 link. Compare the URL configuration with the one
>> >> >> I´ve
>> >> >> posted as image in the gist (link above).
>> >> >> It shows you where to set the server IP and where localhost.
>> >> >>
>> >> >> Last but not least go to
>> >> >> geonode admin -> applications -> GeoServer
>> >> >>
>> >> >> and check your IP and secret etc as well.
>> >> >> (Image posted under gist as well)
>> >> >>
>> >> >> If all this does not help something else blocks your connection …
>> >> >> like
>> >> >> iptables etc.
>> >> >> But this is really hard to guess.
>> >> >>
>> >> >> Hope this helps a bit to get you started.
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Toni
>> >> >>
>> >> >> -----------------------------------------------
>> >> >> CSGIS
>> >> >>
>> >> >> -----------------------------------------------
>> >> >> Kolonnadenstraße 1
>> >> >> 04109 Leipzig
>> >> >> -----------------------------------------------
>> >> >> Mobil +49/ (0) 176 6680 3198
>> >> >> Tel +49/ (0) 341 24 04 738
>> >> >> Fax +49/ (0) 341 24 04 73
>> >> >> Web http://csgis.de
>> >> >> -----------------------------------------------
>> >> >>
>> >> >> Hinweis gemäß § 33 BDSG
>> >> >> Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument
>> >> >> ist
>> >> >> ausschließlich für den
>> >> >> Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls
>> >> >> Sie
>> >> >> diese E-Mail versehentlich
>> >> >> erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und
>> >> >> löschen Sie diese Nachricht
>> >> >> von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung,
>> >> >> Vervielfältigung, Veränderung,
>> >> >> Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.
>> >> >>
>> >> >> Am 21.02.2018 um 16:06 schrieb SILVIA GAMERO <gamerinsky at gmail.com>:
>> >> >>
>> >> >> Toni, thanks for your help
>> >> >> Geoserver is responding correctly, and if I have restarted tomcat
>> >> >> without
>> >> >> any improvement.
>> >> >>
>> >> >> It is obvious that you can not connect, but I can not know what
>> >> >> configuration I should modify, if according to the manual I have
>> >> >> made
>> >> >> the
>> >> >> indicated changes, at least in the connection configuration of
>> >> >> postgres
>> >> >> and
>> >> >> local_settings.
>> >> >>
>> >> >> 2018-02-21 08:12:45,115 ERROR [common.sender] - Conexión rehusada
>> >> >> (Connection refused)
>> >> >> java.net.ConnectException: Conexión rehusada (Connection refused)
>> >> >> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>> >> >> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> >> >> at java.net.Socket.connect(Socket.java:589)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.SocketFrameHandlerFactory.create(SocketFrameHandlerFactory.java:50)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:60)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:99)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:900)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:859)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:817)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:954)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.sender.RabbitMQSender.initialize(RabbitMQSender.java:79)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.sender.RabbitMQSender.send(RabbitMQSender.java:98)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.common.DefaultNotificationProcessor.process(DefaultNotificationProcessor.java:39)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> org.geoserver.notification.MessageProcessor$WorkerThread.run(MessageProcessor.java:79)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> >> >> at
>> >> >>
>> >> >>
>> >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> >> >> at java.lang.Thread.run(Thread.java:748)
>> >> >>
>> >> >> Do you have any idea?
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> geonode-users mailing list
>> >> >> geonode-users at lists.osgeo.org
>> >> >> https://lists.osgeo.org/mailman/listinfo/geonode-users
>> >> >>
>> >> >
>> >> >
>> >
>> >
>
>
More information about the geonode-users
mailing list