On Wed 2013-06-26 11:32:08 -0400, Daniel Kahn Gillmor wrote:
> I'm running sks 1.1.3 on a debian system, and it uses the logrotate
> package to ensure that the logs don't get out of control.
>
> this means that they rotate daily, and when they rotate, the system
> invokes:
>
> /etc/init.d/sks reload > /dev/null
>
> This just sends a SIGHUP to both the db and the recon processes.
>
> However, back on June 6th, i find this during the sighup:
>
> 2013-06-06 06:26:54 Added 1 hash-updates. Caught up to 1370514358.812619
> 2013-06-06 06:26:54 Raising Sys.Break -- PTree may be corrupted:
> Sys_error("Bad file descriptor")
> 2013-06-06 06:26:54 <get_missing_keys.catchup> callback interrupted by break.
> 2013-06-06 06:27:20 DB closed
This continues to happen with sks 1.1.4.
it seems that sometimes, sending a SIGHUP to my sks recon process causes
it to terminate, and other times it does not.
Is anyone else seeing this misbehavior? I'm concerned because i'd like
to ship sks in debian with a configuration that isn't vulnerable to this
sort of intermittent shutdowns.
I also should note that the PTree does not appear to me to be corrupt.
sks recon starts back up just fine, without error.
--dkg
pgpRhxwpYCNQl.pgp
Description: PGP signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
