sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] Server won't start after copy of DB


From: C.J. Adams-Collier
Subject: Re: [Sks-devel] Server won't start after copy of DB
Date: Wed, 23 Jun 2010 08:11:06 -0700

Yowza.  There could be many things causing this.  I can't tell you how
to fix this, but I can recommend using kvm or qemu or xen or something
to split off part of your server so that you can do tasks related only
to your sks server on a separate system.

Sorry I can't help more.

On Wed, 2010-06-23 at 00:49 +0200, Arnold wrote:
> Hello,
> 
> My Debian SKS-server was running very well, until this weekend.
> 
> I moved the database to an SSD hard disk and since that moment it
> immediately exits after it starts.
> 
> These are the last lines of my db.log and recon.log, with debug level 100
> (same result at 10 or 9):
> $ tail -n 3 /var/log/sks/db.log
> 2010-06-22 22:06:00 Membership: <ADDR_INET
> 76.185.38.113:11370>(keyserver.gingerbear.net 11370 ), <ADDR_INET
> 76.191.185.172:11370>(www.mainframe.cx 11370 ), <ADDR_INET
> 83.169.43.165:11370>(keyserver.ccc-hanau.de 11370 ), <ADDR_INET
> 195.111.98.30:11370>(keys.niif.hu 11370 ), <ADDR_INET
> 69.134.24.120:11370>(keys.rpm5.org 11370 ), <ADDR_INET
> 198.49.244.154:11370>(keys.n3npq.net  11370   ), <ADDR_INET
> 85.113.243.78:11370>(keyserver.nijkamp.net 11370 ), <ADDR_INET
> 140.186.70.102:11370>(keys.sugarlabs.org 11370  ), <ADDR_INET
> 84.16.235.61:11370>(keyserver.pki.scientia.net 11370 ), <ADDR_INET
> 66.109.111.12:11370>(keyserver.kjsl.org 11370  ), <ADDR_INET
> 203.33.246.146:11370>(keyserver.oeg.com.au 11370 ), <ADDR_INET
> 208.84.222.190:11370>(ice.mudshark.org 11370 )
> 2010-06-22 22:06:00 Opening KeyDB database
> 2010-06-22 22:06:00 Shutting down database
> 
> $ tail  /var/log/sks/recon.log
> 2010-06-22 22:06:00 sks_recon, SKS version 1.1.0
> 2010-06-22 22:06:00 Copyright Yaron Minsky 2002-2003
> 2010-06-22 22:06:00 Licensed under GPL.  See COPYING file for details
> 2010-06-22 22:06:00 recon port: 11370
> 2010-06-22 22:06:00 Opening PTree database
> 2010-06-22 22:06:00 Setting up PTree data structure
> 2010-06-22 22:06:00 PTree setup complete
> 2010-06-22 22:06:00 Initiating catchup
> 2010-06-22 22:06:00 Marshalling: LogQuery: (5000,1276993585.849555)
> 2010-06-22 22:06:00 DB closed
> 
> 
> The system is running
> - Debian Stable 'Lenny' with
> - Linux 2.6.32-bpo.4-686 (from the back ported archive)
> - SKS-server v 1.1.0
> 
> The database is now on this partition:
> - /dev/sdb13 on /srv type ext4 (rw,nosuid,nodev,user_xattr)
> 
> With the change of HD, I also moved from ext3 to ext4, which is better for
> an SSD. Ext4 is also the reason to use the newer, back ported Linux kernel
> (running this Linux kernel for several weeks already). The mount option
> 'user_xattr' was already in use for one or two weeks to accommodate
> 'calendar server' (Apple's open source CalDav server).
> 
> Also this weekend several packages were updated. I think I did not reboot
> after installing these updates. So the move of the database to the SSD was
> the first restart of the SKS-server.
> 
>   The following packages will be upgraded:
>     bind9 bind9-doc bind9-host bind9utils dnsutils libbind9-50 libdns55
>     libisc52 libisccc50 libisccfg50 liblwres50 libsmbclient libwbclient0
>     samba samba-common samba-doc smbclient smbfs sudo swat
> 
> 
> Here the log lines (default debug level 4) of the last working situation and
> the first problem, after the copy to the new SSD.
> 
> 2010-06-20 02:26:15 Hashes recovered from <ADDR_INET 83.169.43.165:11371>
> 2010-06-20 02:26:15     419EEB36F639BD5CB7FB89D684566FBF
> 2010-06-20 02:26:15     91FB304214BE8D083426E37480435103
> 2010-06-20 02:26:15     C165660D7A7D0AA0EFA1198BAC1811DD
> 2010-06-20 02:26:15     D2F3FCAE96B06E766E891F24997F76C4
> 2010-06-20 02:26:25 Requesting 4 missing keys from <ADDR_INET
> 83.169.43.165:11371>, starting with 419EEB36F639BD5CB7FB89D684566FBF
> 2010-06-20 02:26:25 4 keys received
> 2010-06-20 02:26:26 Added 7 hash-updates. Caught up to 1276993585.849555
> 2010-06-20 02:26:28 DB closed
> 2010-06-20 05:10:58 Opening log
> 2010-06-20 05:10:58 sks_recon, SKS version 1.1.0
> 2010-06-20 05:10:58 Copyright Yaron Minsky 2002-2003
> 2010-06-20 05:10:58 Licensed under GPL.  See COPYING file for details
> 2010-06-20 05:10:58 Opening PTree database
> 2010-06-20 05:10:58 Setting up PTree data structure
> 2010-06-20 05:10:58 PTree setup complete
> 2010-06-20 05:10:58 Initiating catchup
> 2010-06-20 05:11:00 DB closed
> 
> From 2:26 to 5:10, I copied several partitions.
> 
> 
> So, has anybody a clue why the SKS-server refuses operation? The log lines
> (at debug level 10 or 100) don't help me further. Are there any known issues
> with SKS and ext4 or with the last Debian update to bind, samba, etc? Any
> other things I can try? (Oh, I copied the /srv/pub/sks directories again,
> now with "rsync -xaX" instead of "cp -a", but with the same result...)
> 
> Please, help. TIA!
> 
>    Arnold
> 
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

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