Dear Maintainer,

on a buster system, keyd uses 100% CPU:

onak     30318 98.6  0.0   8864  4884 ?        Rs   08:04   5:39 /usr/sbin/keyd -f

vz15:~# strace -p 30318 2>&1 | head -20
strace: Process 30318 attached
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])
accept(3, 0xffee6d8c, [110])            = -1 EINVAL (Invalid argument)
_newselect(4, [3], NULL, NULL, NULL)    = 1 (in [3])

This is in a LXC container running also on a buster host kernel 4.19.0-17-amd64.

Any idea what I should try?

Thank you.

...

Is this a fresh install? I've not seen that behaviour before. I suspect
FD 3 is the keyd socket (in ${sock_dir}/keyd.sock), but if it couldn't
be opened then keyd should have failed to start rather than busy waiting
on the FD.

Anything in the onak.log file?

J.

That's good to know; I'd been trying to find the time to setup an i386
chroot so I could try the database files you'd sent but done so yet.

Ah, I think I've seen something similar myself. Will try to get that
sorted.

J.