sksdb issue

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

sksdb issue

gabrix-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all !
On /etc/init.d/sks start sometimes sksdb fails to start , if i
/etc/init.d/restart sks both sksdb and sksrecon go listening on the
sksconf specified ips and ports but after a little while (very little)
shsdb goes down again . What's the dial ?

Gab
- --
Key ID: BC4F9423
Fingerprint: 36C6 E257 2801 46E7 69A7  8721 F502 1342 BC4F 9423
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREKAAYFAkl7xHcACgkQ9QITQrxPlCNvHwCgtorh17I9BSDrrAi4xuYmUQQZ
ctEAnilJDt4lw4ar1qlwuxMsBZXWV8YG
=8UIe
-----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: sksdb issue

Johan van Selst
gabrix wrote:
> On /etc/init.d/sks start sometimes sksdb fails to start , if i
> /etc/init.d/restart sks both sksdb and sksrecon go listening on the
> sksconf specified ips and ports but after a little while (very little)
> shsdb goes down again . What's the dial ?

For more information about why sks stops, make sure you have set a
reasonable debuglevel in sksconf and look at your logfiles.

It could be that your database files are corrupted. You can try running
'sks cleandb' and if that doesn't work, try the Berkely DB tools:
run db_recover in both KDB and PTree subdirs.


Regards,
Johan

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

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

Re: sksdb issue

gabrix-4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Johan van Selst wrote:
>
> For more information about why sks stops, make sure you have set a
> reasonable debuglevel in sksconf and look at your logfiles.
I have set the debuglevel to 6 and the logfile /var/log/sks owned by
debian-sks and adm but they are empty still .
>
> It could be that your database files are corrupted. You can try running
> 'sks cleandb' and if that doesn't work, try the Berkely DB tools:
> run db_recover in both KDB and PTree subdirs.

The above commands didn't work so i removed DB and PTree dir and started
sks_build.sh again with this resultd (sks.pgp bunzipped):

> root@argo:/var/lib/sks# /usr/local/bin/sks_build.sh
> === Running fastbuild... ===
> Fatal error: exception Not_found
> Command failed unexpectedly. Bailing out

Regards Gab

>
>
> Regards,
> Johan
>


- --
Key ID: BC4F9423
Fingerprint: 36C6 E257 2801 46E7 69A7  8721 F502 1342 BC4F 9423
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREKAAYFAkl9KCwACgkQ9QITQrxPlCO9WQCfQWC914pJhNmhm4tu0oROdVwF
OL0AoJbPnC7nftFkR6AM9oen6AFsWjUG
=Szdh
-----END PGP SIGNATURE-----



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