Hi, I came back to my OpenDNSSEC installation after a while, trying to add a zone. I find the kasp.db locked. Further inspection reveals that ods-signerd is looping, doing no syscalls, hogging one of my CPUs, and it looks like it's been doing this for the last 1-2 weeks...:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 14552 ods 26 0 178M 5696K CPU/3 298.9H 99.02% 99.02% ods-signerd This is with OpenDNSSEC 1.4.2 and SoftHSM 1.3.4, running on NetBSD/amd64 6.0. I've tried to attach a debugger to this process, but I get some nonsense about it looping around somewhere in ld.elf_so, which I'm not entirely certain I beleive to be true. In my syslog I still see messages from ods-signerd; a few per day, but they do not appear to be tagged with the PID of the ods-signerd process (why not?), so it's not a given that it's the one which appears to be looping which has sent these messages... Has anyone else seen something like this? For now I've left it, in "stopped" state. Regards, - Håvard _______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
