I'm also seeing the same errors flooding logs on my busiest server also running 1.9.1.
In your case were the error messages immediately preceeded by "error: could not event_del on close"? -- Clay Cooper Information and Technology Services Finance & Administration Rochester Institute of Technology CONFIDENTIALITY NOTE: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. On Mon, 2019-06-17 at 14:07 +0200, A. Schulze via Unbound-users wrote: A. Schulze via Unbound-users: Am 24.05.19 um 16:09 schrieb A. Schulze via Unbound-users: unbound-1.9.1 with moderate load 1k queries/s peak after restart everything works fine but after some ours the log is flooded wthis way: 2019-05-24 15:49:53.874400500 [1558705793] unbound[33794:3] error: event_add failed. in cpsl. 2019-05-24 15:49:53.888628500 [1558705793] unbound[33794:3] error: event_add failed. in cpsl. These messages continue even if no new requests arrive. After downgrade to 1.8.1 with an unchanged configuration file the problem went away. I'll give 1.9.2 a try once it's available. I replaced 1.8.1 (known to work) with 1.9.2~rc3 on one server that "run crazy" with 1.9.1, At least over 3 days I did not noticed the log message mentioned in $subject - fine. There are numerous changes between 1.8.1/utils/netevent.c, 1.9.1/utils/netevent.c (that may introduce the failure I saw) and 1.9.2/utils/netevent.c (that may solve the issue again) Does this sound reasonable? Andreas
