keyservers MIA

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

keyservers MIA

Peter Palfrader-2
Hi,

while going over my membership file I noticed that a lot of keyservers I
added over the time appear to have vanished.  If you sync only or mostly
against the keyservers below you should probably try to find a few more
additional peers.

The following keyservers from my membership file appear to be no longer
functional (I did not check any servers not in my membership file!):

- keyserver.aarg.net (bogus DNS)
- sks.keyserver.penguin.de (Connection refused)
- backup.lk.keyserver.penguin.de (No route to host)
- thedungeon.dnsalias.net (unknown host)
- sks.dnsalias.net (Connection timed out)
- keyserver.bu.edu (Connection timed out)
- keys.se.linux.org (No route to host)
- keyserver.fabbione.net (Connection refused)
- keyserver.sane.net (Connection timed out)
- pgp.ael.be (No route to host)
- misterl.net (Connection refused)
- www.linux-geeks.de (Connection refused)
- gnupg.jccc.net (unknown host)
- keys.kadath.com.ar (bogus DNS)
- pgp.cns.ualberta.ca (Connection refused)
- elephant.finux.org (Connection refused)
- keyserver.afoyi.com (unknown host)
- pgp.hpc.unm.edu (Connection refused)
- pgp.uni-mainz.de (Connection refused)
- keyserver-sks.kjsl.com:21370 (Connection refused)

Additionally, keyserver.kjsl.com has bounced my syncmails for weeks (now
with "mail looks back to myself").

Also pgpkeys.pca.dfn.de doesn't work for me, but apparently for others.
I just get a connect and then the connection is immiediately dropped -
looks like async config or broken tcpwrappers.


As always, if you want to sync with me, just add
'keyserver.noreply.org 11370' to your membership file and drop me a
mail.

Cheers,
Peter

[The relevant admins have been bcced.  Some of you I mailed before,
sorry for the duplicate.]
--
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/


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

Re: keyservers MIA

Fabio M. Di Nitto-3
Peter Palfrader wrote:
> Hi,
>

> - keyserver.fabbione.net (Connection refused)

The server did crash and i didn't notice. Thanks. It's up again now.

Fabio

--
I'm going to make him an offer he can't refuse.


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

Re: keyservers MIA

Christoph Martin
In reply to this post by Peter Palfrader-2
Hi,

Peter Palfrader schrieb:
> Hi,
>
> The following keyservers from my membership file appear to be no longer
> functional (I did not check any servers not in my membership file!):
>
> - pgp.uni-mainz.de (Connection refused)

I am working on the recovery. My sks crashed during my holiday on July
9th with a database error:

Fatal database error: Bdb.DBError("fatal region error detected; run
recovery")

Recovery is not working:

# db4.1_recover -vech .
db_recover: Finding last valid log LSN: file: 1436 offset 1264017
db_recover: Recovery starting from [1436][28]
db_recover: txnid 80000007 commit record found, already on commit list
db_recover: Recovery function for LSN 1436 1258581 failed on backward pass
db_recover: PANIC: Invalid argument
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: Database handles open during environment close
db_recover: dbenv->close: Invalid argument

I did not find a solution for it.

Can anybody help?

Christoph

--
============================================================================
Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany
 Internet-Mail:  [hidden email]
  Telefon: +49-6131-3926337
      Fax: +49-6131-3922856


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

signature.asc (260 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: keyservers MIA

Peter Palfrader-2
On Thu, 27 Jul 2006, Christoph Martin wrote:

> > - pgp.uni-mainz.de (Connection refused)
>
> I am working on the recovery. My sks crashed during my holiday on July
> 9th with a database error:

Ok, readding to membership file.

> Fatal database error: Bdb.DBError("fatal region error detected; run
> recovery")
>
> Recovery is not working:
>
> # db4.1_recover -vech .
[..]
> db_recover: dbenv->close: Invalid argument
>
> I did not find a solution for it.

Fastest solution is probably to just build a new db from scratch.  Peter
Pramberger has uptodate keydumps.

ftp://ftp.pramberger.at/services/keyserver/keydump/

Cheers,
Peter
--
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/


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

Re: keyservers MIA

Chris Kuethe-2
In reply to this post by Peter Palfrader-2
On Thu, 27 Jul 2006, Peter Palfrader wrote:

> Hi,
>
> while going over my membership file I noticed that a lot of keyservers I
> added over the time appear to have vanished.  If you sync only or mostly
> against the keyservers below you should probably try to find a few more
> additional peers.
>
> The following keyservers from my membership file appear to be no longer
> functional (I did not check any servers not in my membership file!):
>
> - pgp.cns.ualberta.ca (Connection refused)

D'oh. I'm not sure why this machine got rebooted without me being told.
As for the latency in doing something about it... that's my overeager
procmail filtering.

Also, I'd prefer it if people started to refer to it as pgp.srv.ualberta.ca
.cns is a leftover cname from when I was running it on my workstation.

CK

--
Chris Kuethe, GCIA: Secure Systems Specialist - U of A AICT
       office: 157 General Services Bldg.    +1.780.492.8135
               chris.kuethe@[pyxis.cns.]ualberta.ca

      GDB has a 'break' feature; why doesn't it have 'fix' too?


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