Recon failure

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Recon failure

Daniel Johnson
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I discovered on Tuesday that keyserver.progman.us was not syncing, and
was about a thousand keys behind the network.  The logs indicated this
had been a problem for several days.  In the course of looking at it I
pulled a D'oh and screwed up the DBs.

It just finished recreating its databases ("build" "cleandb" and
"pbuild") from a fresh (Wednesday) dump on ftp.prato.linux.it, and
already I see this:

2005-09-16 23:26:20 Recon partner: <ADDR_INET 213.141.80.20:11370>
2005-09-16 23:26:20 Initiating reconciliation
2005-09-16 23:26:20 Marshalling: Config
2005-09-16 23:27:05 <recon as client> callback timed out.

Now I think we'd have to agree the databases are as fresh as they
come.  I'm running a recently-built copy of 1.0.10.  I've examined
all of my peers, and they appear to be set up for two-way syncing.

- From looking at the code, I think this Config refers to comparing
configuration with the peer.  Yet, I doubt that all of my peers are
having config problems right now.  :(

Assistance would be greatly appreciated.

[And if this PGP sig fails: I think I've got it traced to
  Thunderbird.  Sorry.]

Daniel Johnson
[hidden email]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDK5vB6vGcUBY+ge8RAtDkAJwOyQ3sJo355jiJSptITYhTfAO69ACg+EVU
g+W2ddGv2var3PLc4noAcAg=
=Sf6N
-----END PGP SIGNATURE-----


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: Recon failure

Daniel Johnson
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

*tap* *tap* This thing on?  Hello?

keyserver.progman.us is still not syncing properly.  Requests from
pks.aaiedu.hr seem to work though, and have kept me basically up
to date.  If not for that, I'd have to down SKS (nobody wants to
use an out-of-sync server).

Could anyone at least post log entries related to my system?
Preferably with a high debuglevel set...

Daniel Johnson
[hidden email]

Example error:
2005-09-22 19:53:53 Recon partner: <ADDR_INET 193.196.36.4:11370>
2005-09-22 19:53:53 Initiating reconciliation
2005-09-22 19:53:53 Marshalling: Config
2005-09-22 19:53:53 <recon as client> error in callback.: End_of_file

Example success:
2005-09-22 19:49:44 Recon partner: <ADDR_INET 161.53.2.67:11370>
2005-09-22 19:49:44 Initiating reconciliation
2005-09-22 19:49:44 Marshalling: Config
2005-09-22 19:49:45 Unmarshalling: Config
2005-09-22 19:49:45 Unmarshalling: ReconRqst_Poly()
2005-09-22 19:49:45 Marshalling: Elements(len:0)
2005-09-22 19:49:45 Unmarshalling: Flush
2005-09-22 19:49:45 Flush occured
2005-09-22 19:49:45 Unmarshalling: Done
2005-09-22 19:49:45 Done received
2005-09-22 19:49:45 Reconciliation complete
2005-09-22 19:49:45 Hashes recovered from <ADDR_INET 161.53.2.67:11371>
2005-09-22 19:49:45     1213EC2158605E869CC3FC0F592097E2
2005-09-22 19:49:45     515E6CAB16D518A6E7D6A781F8365C81
2005-09-22 19:49:45     73A19017AEEA6C8E1C0DA56169FD69A6
2005-09-22 19:49:45     E42DEB08A16C67831DEE71320D3770AB
2005-09-22 19:49:45 Disabling gossip
2005-09-22 19:49:46 Requesting 4 missing keys from <ADDR_INET
     161.53.2.67:11371>, starting with 1213EC2158605E869CC3FC0F592097E2
2005-09-22 19:49:47 4 keys received
2005-09-22 19:49:47 Marshalling: KeyStrings: 4 keystrings
2005-09-22 19:49:47 Unmarshalling: Ack: 0
2005-09-22 19:49:47 Marshalling: LogQuery: (5000,1127435578.242713)
2005-09-22 19:49:48 Unmarshalling: LogResp: 4 events
2005-09-22 19:49:48 setting synctime to 1127436587.476195
2005-09-22 19:49:48 Added 4 hash-updates. Caught up to 1127436587.476195
2005-09-22 19:49:48 Enabling gossip

Example success #2:
2005-09-22 19:53:06 Beginning recon as server, client: <ADDR_INET
       161.53.2.67:64492>
2005-09-22 19:53:06 Joining reconciliation
2005-09-22 19:53:06 Marshalling: Config
2005-09-22 19:53:06 Unmarshalling: Config
2005-09-22 19:53:06 Marshalling: ReconRqst_Poly()
2005-09-22 19:53:06 Queue length: 1
2005-09-22 19:53:06 Operation would have blocked
2005-09-22 19:53:06 Marshalling: Flush
2005-09-22 19:53:06 Queue length: 2
2005-09-22 19:53:06 Operation would have blocked
2005-09-22 19:53:07 Unmarshalling: Elements(len:0)
2005-09-22 19:53:07 Marshalling: Done
2005-09-22 19:53:07 Reconciliation complete
2005-09-22 19:53:07 No hashes recovered from <ADDR_INET
            161.53.2.67:11371>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDM19c6vGcUBY+ge8RAhNLAJ90WMW5KEHxBWsKX4rA72s3/gTOWQCg7Jmq
+G85Ss6OstFfegHIoCVky/M=
=z26U
-----END PGP SIGNATURE-----


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: Recon failure

Jason Harris
On Thu, Sep 22, 2005 at 08:50:43PM -0500, Daniel Johnson wrote:

> keyserver.progman.us is still not syncing properly.  Requests from
> pks.aaiedu.hr seem to work though, and have kept me basically up
> to date.  If not for that, I'd have to down SKS (nobody wants to
> use an out-of-sync server).

How often is your IP address changing?  Ask your other peers to add
a cron entry like this:

  # keep up with ...'s dynamic IP
  0 * * * * touch /.../sks/membership > /dev/null

for hourly updates.

--
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
[hidden email] _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

attachment0 (322 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: Recon failure

Daniel Johnson
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Harris wrote:
 > How often is your IP address changing?  Ask your other peers to
 > add a cron entry like this:
 >
 >   # keep up with ...'s dynamic IP
 >   0 * * * * touch /.../sks/membership > /dev/null
 >
 > for hourly updates.

My address is usually quite stable, I've had occasions where I held an
IP for two months.  The last change was on the 19th when I replaced
the UPS.

According to the wiki, SKS versions higher than 1.0.7 (at least)
reload their membership file automatically every few hours.  Since
most of the network is at least 1.0.9 (according to
sks_network_today.png), and the oldest is 1.0.6 (keyserver.hadiko.de)
I don't think that this is the issue.  That said, I've still got a
similar entry in my crontab from when I first installed SKS.  :)

I was chatting with a friend about this (okay, I was venting) and he
brought up a good question: Has the filter set been changed?  I
don't recall seeing anything about adding on to yminsky.dedup and
yminsky.merge.

Good news: Peered with ice.mudshark.org, and syncing appears to work.
Between mudshark and aaiedu I'm staying in sync.

Daniel Johnson
[hidden email]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDNaqG6vGcUBY+ge8RArz2AKC/oBgbrAF/40dwYdoP76goJ9LBoQCgprXU
aIfbwgAcBjonX9EH4oktPl0=
=Vc/O
-----END PGP SIGNATURE-----


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: Recon failure

Yaron Minsky
The DNS theory does so far seem like the best one.  I think a filter mismatch would end up with a different error.  It would be ideal to get the logs from the other side, since that might clear up why the other side is terminating the connection.  Without that information, it's a little hard to debug what's going on.

Yaron

On 9/24/05, Daniel Johnson <[hidden email]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Harris wrote:
> How often is your IP address changing?  Ask your other peers to
> add a cron entry like this:
>
>   # keep up with ...'s dynamic IP
>   0 * * * * touch /.../sks/membership > /dev/null
>
> for hourly updates.

My address is usually quite stable, I've had occasions where I held an
IP for two months.  The last change was on the 19th when I replaced
the UPS.

According to the wiki, SKS versions higher than 1.0.7 (at least)
reload their membership file automatically every few hours.  Since
most of the network is at least 1.0.9 (according to
sks_network_today.png), and the oldest is 1.0.6 (keyserver.hadiko.de)
I don't think that this is the issue.  That said, I've still got a
similar entry in my crontab from when I first installed SKS.  :)

I was chatting with a friend about this (okay, I was venting) and he
brought up a good question: Has the filter set been changed?  I
don't recall seeing anything about adding on to yminsky.dedup and
yminsky.merge.

Good news: Peered with ice.mudshark.org , and syncing appears to work.
Between mudshark and aaiedu I'm staying in sync.

Daniel Johnson
[hidden email]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDNaqG6vGcUBY+ge8RArz2AKC/oBgbrAF/40dwYdoP76goJ9LBoQCgprXU
aIfbwgAcBjonX9EH4oktPl0=
=Vc/O
-----END PGP SIGNATURE-----


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: Re: Recon failure

Jason Harris
In reply to this post by Daniel Johnson
On Sat, Sep 24, 2005 at 02:36:05PM -0500, Daniel Johnson wrote:
> Jason Harris wrote:

> > How often is your IP address changing?  Ask your other peers to
> > add a cron entry like this:
> >
> >   # keep up with ...'s dynamic IP
> >   0 * * * * touch /.../sks/membership > /dev/null
> >
> > for hourly updates.
>
> My address is usually quite stable, I've had occasions where I held an
> IP for two months.  The last change was on the 19th when I replaced
> the UPS.
>
> According to the wiki, SKS versions higher than 1.0.7 (at least)
> reload their membership file automatically every few hours.  Since
The 6 hour updates weren't enough to keep keyserver.sascha.silbe.org
in sync.

--
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
[hidden email] _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

attachment0 (322 bytes) Download Attachment