Re: [Sks-devel] Re: Hi everybody!
Feel free to add my server, as well. WAN connection is currently down, so it'll say broken link, but I should be getting that restored within a week or so. keyserver.nyfnet.net 11370 On Sun, Nov 29, 2009 at 4:13 PM, MailFighter.net Admin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Daniel Kahn Gillmor wrote: >> Are you filing bugs about this with ubuntu? it would be really good for >> them to know that their packages are busted (with as much detail as >> possible). > > It's this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535469 > > It's exactly the same problem: > r...@mx4:~# sks recon > unknown timeout type argument to DB_ENV->rep_get_timeout > Segmentation fault > r...@mx4:~# sks db > unknown timeout type argument to DB_ENV->rep_get_timeout > Segmentation fault > > I felt no need to notify Ubuntu, but I can start working on that if you want. > > Yours, > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEAREKAAYFAksTDi0ACgkQAlpOsGhXcE21vQCfTu+PaCGaDreNBH9Wkn3JAvlx > ekEAn22CVGRklmsGjsqzIquMuZzv+h9b > =RrY2 > -END PGP SIGNATURE- > > > ___ > Sks-devel mailing list > Sks-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/sks-devel > ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Hi everybody!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Daniel Kahn Gillmor wrote: > Are you filing bugs about this with ubuntu? it would be really good for > them to know that their packages are busted (with as much detail as > possible). It's this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535469 It's exactly the same problem: r...@mx4:~# sks recon unknown timeout type argument to DB_ENV->rep_get_timeout Segmentation fault r...@mx4:~# sks db unknown timeout type argument to DB_ENV->rep_get_timeout Segmentation fault I felt no need to notify Ubuntu, but I can start working on that if you want. Yours, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAksTDi0ACgkQAlpOsGhXcE21vQCfTu+PaCGaDreNBH9Wkn3JAvlx ekEAn22CVGRklmsGjsqzIquMuZzv+h9b =RrY2 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Hi everybody!
On 11/29/2009 07:03 PM, MailFighter.net Admin wrote: > r...@mx4:/var/lib/sks# sks build -n 13 -cache 100 /var/sks/dump/*.pgp > unknown timeout type argument to DB_ENV->rep_get_timeout > Segmentation fault > > It SIGSEGV's immediately. It's not a RAM problem. > > I'll compile sks manually and ignore Ubuntu's packages for it. Are you filing bugs about this with ubuntu? it would be really good for them to know that their packages are busted (with as much detail as possible). --dkg signature.asc Description: OpenPGP digital signature ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Hi everybody!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 John Clizbe wrote: > I ran > sks build -n 13 -cache 100 /var/sks/dump/*.pgp r...@mx4:/var/lib/sks# sks build -n 13 -cache 100 /var/sks/dump/*.pgp unknown timeout type argument to DB_ENV->rep_get_timeout Segmentation fault It SIGSEGV's immediately. It's not a RAM problem. I'll compile sks manually and ignore Ubuntu's packages for it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAksTC78ACgkQAlpOsGhXcE0sOgCdHhByj632w/8fS0NX2rjBa5LZ 1D0An1uAnc/wz52XAwlGof5GHNWPAG4+ =FGWS -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Hi everybody!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jens Leinenbach wrote: > Where/when exactly do you get the segfault? After starting sks_build.sh? > Does your system run out of memory? See below for a trace. > E.g. if you don't have much RAM: r...@mx4:/var/lib/sks# free -m total used free sharedbuffers cached Mem: 2012467 1544 0 19240 - -/+ buffers/cache:208 1803 Swap: 3812 0 3812 r...@mx4:/var/lib/sks# uname -a Linux mx4 2.6.31-15-generic-pae #50-Ubuntu SMP Tue Nov 10 16:12:10 UTC 2009 i686 GNU/Linux CPU: Dual Intel(R) Xeon(R) CPU3065 @ 2.33GHz Would that be ok? > /usr/sbin/sks build /var/lib/sks/dump/keydump* -n 1 -cache 20 I tried different values for the parameters, to no avail. From what I read, the problem is related to two different versions of libdb... ===trace start r...@mx4:/var/lib/sks# /usr/lib/sks/sks_build.sh + ask_mode + echo 'Please select the mode in which you want to import the keydump:' Please select the mode in which you want to import the keydump: + echo '' + echo '1 - fastbuild' 1 - fastbuild + echo 'only an index of the keydump is created and the keydump cannot be' only an index of the keydump is created and the keydump cannot be + echo 'removed.' removed. + echo '' + echo '2 - normalbuild' 2 - normalbuild + echo '' + echo 'all the keydump will be imported in a new database. It takes longer' all the keydump will be imported in a new database. It takes longer + echo 'time and more disk space, but the server will run faster (depending' time and more disk space, but the server will run faster (depending + echo 'from the source/age of the keydump).' from the source/age of the keydump). + echo 'The keydump can be removed after the import.' The keydump can be removed after the import. + echo '' + echo -n 'Enter enter the mode (1/2): ' Enter enter the mode (1/2): + read 2 + case "$REPLY" in + mode='build /var/lib/sks/dump/*.pgp' + echo '=== Running (fast)build... ===' === Running (fast)build... === + /usr/sbin/sks build /var/lib/sks/dump/sks-dump-.pgp /var/lib/sks/dump/sks-dump-0001.pgp /var/lib/sks/dump/sks-dump-0002.pgp /var/lib/sks/dump/sks-dump-0003.pgp /var/lib/sks/dump/sks-dump-0004.pgp /var/lib/sks/dump/sks-dump-0005.pgp /var/lib/sks/dump/sks-dump-0006.pgp /var/lib/sks/dump/sks-dump-0007.pgp /var/lib/sks/dump/sks-dump-0008.pgp /var/lib/sks/dump/sks-dump-0009.pgp /var/lib/sks/dump/sks-dump-0010.pgp /var/lib/sks/dump/sks-dump-0011.pgp /var/lib/sks/dump/sks-dump-0012.pgp /var/lib/sks/dump/sks-dump-0013.pgp /var/lib/sks/dump/sks-dump-0014.pgp /var/lib/sks/dump/sks-dump-0015.pgp /var/lib/sks/dump/sks-dump-0016.pgp /var/lib/sks/dump/sks-dump-0017.pgp /var/lib/sks/dump/sks-dump-0018.pgp /var/lib/sks/dump/sks-dump-0019.pgp /var/lib/sks/dump/sks-dump-0020.pgp /var/lib/sks/dump/sks-dump-0021.pgp /var/lib/sks/dump/sks-dump-0022.pgp /var/lib/sks/dump/sks-dump-0023.pgp /var/lib/sks/dump/sks-dump-0024.pgp /var/lib/sks/dump/sks-dump-0025.pgp /var/lib/sks/dump/sks-dump-0026.pgp /var/lib/sks/dump/sks-dump-0027.pgp /var/lib/sks/dump/sks-dump-0028.pgp /var/lib/sks/dump/sks-dump-0029.pgp /var/lib/sks/dump/sks-dump-0030.pgp /var/lib/sks/dump/sks-dump-0031.pgp /var/lib/sks/dump/sks-dump-0032.pgp /var/lib/sks/dump/sks-dump-0033.pgp /var/lib/sks/dump/sks-dump-0034.pgp /var/lib/sks/dump/sks-dump-0035.pgp /var/lib/sks/dump/sks-dump-0036.pgp /var/lib/sks/dump/sks-dump-0037.pgp /var/lib/sks/dump/sks-dump-0038.pgp /var/lib/sks/dump/sks-dump-0039.pgp /var/lib/sks/dump/sks-dump-0040.pgp /var/lib/sks/dump/sks-dump-0041.pgp /var/lib/sks/dump/sks-dump-0042.pgp /var/lib/sks/dump/sks-dump-0043.pgp /var/lib/sks/dump/sks-dump-0044.pgp /var/lib/sks/dump/sks-dump-0045.pgp /var/lib/sks/dump/sks-dump-0046.pgp /var/lib/sks/dump/sks-dump-0047.pgp /var/lib/sks/dump/sks-dump-0048.pgp /var/lib/sks/dump/sks-dump-0049.pgp /var/lib/sks/dump/sks-dump-0050.pgp /var/lib/sks/dump/sks-dump-0051.pgp /var/lib/sks/dump/sks-dump-0052.pgp /var/lib/sks/dump/sks-dump-0053.pgp /var/lib/sks/dump/sks-dump-0054.pgp /var/lib/sks/dump/sks-dump-0055.pgp /var/lib/sks/dump/sks-dump-0056.pgp /var/lib/sks/dump/sks-dump-0057.pgp /var/lib/sks/dump/sks-dump-0058.pgp /var/lib/sks/dump/sks-dump-0059.pgp /var/lib/sks/dump/sks-dump-0060.pgp /var/lib/sks/dump/sks-dump-0061.pgp /var/lib/sks/dump/sks-dump-0062.pgp /var/lib/sks/dump/sks-dump-0063.pgp /var/lib/sks/dump/sks-dump-0064.pgp /var/lib/sks/dump/sks-dump-0065.pgp /var/lib/sks/dump/sks-dump-0066.pgp /var/lib/sks/dump/sks-dump-0067.pgp /var/lib/sks/dump/sks-dump-0068.pgp /var/lib/sks/dump/sks-dump-0069.pgp /var/lib/sks/dump/sks-dump-0070.pgp /var/lib/sks/dump/sks-dump-0071.pgp /var/lib/sks/dump/sks-dump-0072.pgp /var/lib/sks/dump/sks-dump-0073.pgp /var/lib/sks/dump/sks-dump-0074.pgp /var/lib/sks/dump/sks-dump-0075.pgp /var/lib/sks/dump/sks-dump-0076.pgp /var/lib/sks/dump/sks-dump-0077.pgp /var/lib/sks/dump/
Re: [Sks-devel] Re: Hi everybody!
Hi Buanzo, > Now, I finished downloading the dump, but I'musing Ubuntu, and it > fails with a segfault. Where/when exactly do you get the segfault? After starting sks_build.sh? Does your system run out of memory? Then try to reduce memory usage by reducing the cache values of sks_build.sh E.g. if you don't have much RAM: /usr/sbin/sks build /var/lib/sks/dump/keydump* -n 1 -cache 20 (Change the paths for your needs.) Cheers, Jens ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Re: Hi everybody!
MailFighter.net Admin wrote: > First of all, > > Thanks to everyone that emailed me off-list offering to peer up. :) > > Now, I finished downloading the dump, but I'm using Ubuntu, and it fails with > a segfault. I know it's got to do with different versions of libdb (compiled > vs runtime), so I upgraded to karmic. Still the same problem. Ergo, I'm stuck. > > SO, should I just d/l && configure && make && make install? SKS builds pretty easily. You just need a libdb >= 4.6 and a recent ocaml compiler. That's what I would do. -- John P. Clizbe Inet:John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net or mailto:pgp-public-k...@gingerbear.net?subject=help Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" ___ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
