[GeoNode-users] problems connect refused when upload shapefiles in geonode

Alessio Fabiani alessio.fabiani at geo-solutions.it
Thu Feb 22 01:06:48 PST 2018

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.


Alessio Fabiani

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Alessio Fabiani

Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39 331 6233686




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
> -----------------------------------------------
> -----------------------------------------------
> Kolonnadenstraße 1
> 04109 Leipzig
> -----------------------------------------------
> Mobil +49/ (0) 176 6680 3198 <+49%20176%2066803198>
> Tel  +49/ (0) 341 24 04 738 <+49%20341%202404738>
> Fax  +49/ (0) 341 24 04 73 <+49%20341%20240473>
> 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.RecoveryAwareAMQConnectionFact
> ory.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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20180222/05bbf593/attachment.html>

More information about the geonode-users mailing list