zope
[Arriba] [Todas las Listas]

Re: [Zope] ZEO manageUndo No laborable - DisconnectedError

To: Sebastian Tänzer <st@xxxxxxxxxx>,zope@xxxxxxxx
Subject: Re: [Zope] ZEO manageUndo No laborable - DisconnectedError
From: "Niels Dettenbach (Syndicat IT & Internet)" <nd@xxxxxxxxxxxx>
Date: Wed, 06 May 2015 07:42:51 +0200
Delivered-to: zope@xxxxxxxx
Delivery-date: Wed, 06 May 2015 01:49:14 -0400
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=syndicat.com; s=x; h=Message-ID:To:Date:From:Subject:Content-Type:Content-Transfer-Encoding:MIME-Version:References:In-Reply-To; bh=tLnkYAX6T9/BfakNmbVkg4CmAdV8JVEJdCFCLkXIEGo=; b=xZkEKwalJxsx9X38ueiMHW1WNPmL92ffM/TC7YF6Nap8VO0lYSbPyvOBx/KJZfkAxBiFZc4cFgVky4synvKPDz3nggWZaoH2v9LPF148jyR4w3znCUimSoLlhI73n6Aoh4oAds62WJ9fD4/G0wS3POjD3ychovbDhOtiFE+qMY0=;
Envelope-to: traductor@xxxxxxxxxxx
In-reply-to: <204528C4-5FA1-41F4-89A4-3C24385386BA@taenzer.me>
List-archive: <http://mail.zope.org/pipermail/zope/>
List-help: <mailto:zope-request@zope.org?subject=help>
List-id: Users of the Z Object Publishing Environment <zope.zope.org>
List-post: <mailto:zope@zope.org>
List-subscribe: <https://mail.zope.org/mailman/listinfo/zope>, <mailto:zope-request@zope.org?subject=subscribe>
List-unsubscribe: <https://mail.zope.org/mailman/options/zope>, <mailto:zope-request@zope.org?subject=unsubscribe>
References: <204528C4-5FA1-41F4-89A4-3C24385386BA@taenzer.me>
Sender: "Zope" <zope-bounces@xxxxxxxx>
Soy 6. *Mai 2015 01:24:50 *MESZ, *schrieb "Sebastian *Tänzer" <st@xxxxxxxxxx>:
>2015-05-06 01:16:46 AVISO *ZEO.*zrpc (19205) CW: el error que conecta a ('::1',
>9999): *ECONNREFUSED
>2015-05-06 01:16:46 *INFO *ZEO.*ClientStorage *zeostorage Probando
>conexión <*ManagedClientConnection ('127.0.0.1', 9999)>
>2015-05-06 01:16:46 *INFO *ZEO.*zrpc.Conexión('*C') (127.0.0.1:9999)
*hmm,

justo un tiro pequeño en la oscuridad: Incluso si esto "tendría que" trabajar demasiado - por qué el cliente intenta conectar el *IPv4 dirección de *loopback y el error da el *IPv6 de él atrás?

Probaría a *eleminate esto si posible y traer *Zope abajo a *IPv4 completamente, porque hay todavía muchas bibliotecas de software y aplicaciones alrededor de (incluso algún *underlying *os partes) cuáles no son bien probado con *IPv6.

Si esto soluciona vuestro *prob - ninguna idea...


*hth Un poco.
*cheerioh,


*Niels.
-- 
*Niels *Dettenbach
*Syndicat LO & Internet
*http://www.syndicat.com
_______________________________________________
*Zope *maillist  -  Zope@xxxxxxxx
*https://correo.*zope.*org/*mailman/*listinfo/*zope
**   #Ninguno correos de cruz o HTML *encoding!  **
(Listas relacionadas -
 *https://correo.*zope.*org/*mailman/*listinfo/*zope-Anunciar
 *https://correo.*zope.*org/*mailman/*listinfo/*zope-*dev )
Am 6. Mai 2015 01:24:50 MESZ, schrieb "Sebastian Tänzer" <st@xxxxxxxxxx>:
>2015-05-06 01:16:46 WARNING ZEO.zrpc (19205) CW: error connecting to
>('::1', 9999): ECONNREFUSED
>2015-05-06 01:16:46 INFO ZEO.ClientStorage zeostorage Testing
>connection <ManagedClientConnection ('127.0.0.1', 9999)>
>2015-05-06 01:16:46 INFO ZEO.zrpc.Connection('C') (127.0.0.1:9999)
hmm,

just a small shot in the dark: Even if this "should" work too - why the client tries to connect the IPv4 address of loopback and the error gives the IPv6 of it back?

I would try to eleminate this if possible and bring Zope down to IPv4 completely, because there are still many software libraries and applications around (even some underlying os parts) which are not well tested with IPv6.

If this solves your prob - no idea...


hth a bit.
cheerioh,


Niels.
-- 
Niels Dettenbach
Syndicat IT & Internet
http://www.syndicat.com
_______________________________________________
Zope maillist  -  Zope@xxxxxxxx
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )
<Anterior por Tema] Tema Actual [Siguiente por Tema>