sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] misc errors and their meanings?


From: Jeff Johnson
Subject: Re: [Sks-devel] misc errors and their meanings?
Date: Fri, 29 Oct 2010 16:55:10 -0400

On Oct 29, 2010, at 4:32 PM, Christoph Anton Mitterer wrote:

> Hi.
> 
> I get several errors which I don't understand:
> 

Caveat: I too did not understand, below are the explanations
I've devised.

> in db.log:
> 1) many like these:
> 2010-10-25 01:50:53 Error fetching key from hash
> 9BC79BCAF20C03977BAD4986AE5A2EA8: Not_found
> 2010-10-25 04:51:48 Error fetching key from hash
> 1602C783D3BBC01EA6882BCC8C087F40: Not_found
> 2010-10-25 04:51:48 Error fetching key from hash
> DB7FCC05B8B531038352BD920811C07C: Not_found
> 2010-10-25 05:27:28 Error fetching key from hash
> 63F992DC43065DC8CD6577152F939CA7: Not_found
> 2010-10-25 05:27:28 Error fetching key from hash
> 6D18637BE544356DDD17464C93938FD3: Not_found
> 2010-10-25 06:20:45 Error fetching key from hash
> 722F0BE97A662518253A377E35FC99FE: Not_found
> What are they?
> 

I believe most of these follow an update which DEL'd some keys.
So ins some sense, the "error" (sic) is just a confirmation that
the key was indeed deleted.

> 2) And also many search errors like:
> 2010-10-26 01:04:52 Error handling request
> (GET,/pks/lookup?op=get&exact=off&search=0x62523331,[
> 2010-10-24 14:56:10 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0xDFBFAF3B,[
> 2010-10-24 15:08:04 Error handling request
> (GET,/pks/lookup?op=vindex&hash=on&fingerprint=on&search=0x71ED3E4172121590,[
> 2010-10-24 17:08:29 Error handling request
> (GET,/pks/lookup?op=get&fingerprint=on&search=0xEA7330026C73B11B,[
> 2010-10-24 17:27:27 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x0379F145,[
> 2010-10-24 17:55:18 Error handling request
> (GET,/pks/lookup?op=get&fingerprint=on&search=0x8CD43247841C83E2,[
> 2010-10-24 21:14:35 Error handling request
> (GET,/pks/lookup?op=index&options=mr&search=sales%40top%2Dfine%2Dchem%2Ecom,[
> 2010-10-24 21:31:14 Error handling request
> (GET,/pks/lookup?op=index&options=mr&search=https%3A%2F%2Fwww%2Eaktivix%2Eorg&exact=on,[
> 2010-10-24 21:32:06 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x7EA1D419,[
> 2010-10-24 22:57:21 Error handling request
> (GET,/pks/lookup?op=index&options=mr&search=Key%20Id%20'0xD553271D',[
> 2010-10-24 23:00:08 Error handling request
> (GET,/pks/lookup?op=index&options=mr&address@hidden,[
> 2010-10-24 23:00:19 Error handling request
> (GET,/pks/lookup?op=index&options=mr&address@hidden,[
> 2010-10-24 23:08:06 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x54B3B3DB,[
> 2010-10-24 23:08:30 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x54B3B3DB,[
> 2010-10-24 23:12:17 Error handling request
> (GET,/pks/lookup?op=index&options=mr&search=alex%40henleycomputers%2Eco%2Euk,[
> 2010-10-24 23:17:04 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x8B02F9CE,[
> 2010-10-24 23:17:08 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0xEDF00B5D,[
> 2010-10-24 23:17:11 Error handling request
> (GET,/pks/lookup?op=get&options=mr&search=0x25B82406,[
> seem to be all client requests,... but why errors? I mean even if no keys
> with that IDs, etc. exist... it shouldn't give an error
> 

Because the search failed, usually because the client searched for non-existent.

Again "error" (sic) is slightly misleading: the requested operation could not be
performed.

> 
> in recon.log:
> 1) loads of the following:
> <recon as client> error in callback.: End_of_file
> <recon as client> error in callback.: Sys_error("Connection reset by
> peer")
> <recon as client> error in callback.: Unix error: Connection refused -
> connect()
> <recon as client> error in callback.: Unix error: Connection timed out -
> connect()
> <recon as client> error in callback.: Unix error: No route to host -
> connect()
> <reconciliation handler> error in callback.: End_of_file
> 

There's lots of reasons for not being able to join a reconciliation:
        1) remote daemon is busy atm, say, doing a reconciliation somewhere 
else.
        2) remote daemon isn't running
        3) remote daemon (or connection) went away
        4) remote host cannot be found

One can perhaps infer more specific details if the context is examined.
But in general, there will be some "error" messages like this in normal 
operation.

hth

73 de Jeff
> 
> Any ideas?
> 
> Cheers,
> Chris.
> 
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]