> On 23 Dec 2017, at 13:08, Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > >> On Sat, Dec 23, 2017 at 11:40:57AM +0100, Mischa wrote: >> Hi All, >> >> Since OpenBSD 6.2, just confirmed this in the latest snapshot >> (GENERIC.MP#305) as well, for some reason relayd stops processing traffic >> and starts flooding the log file with the following message: >> >> Dec 23 11:19:11 lb2 relayd[22515]: rsae_send_imsg: poll timeout >> Dec 23 11:19:12 lb2 relayd[52110]: rsae_send_imsg: poll timeout >> Dec 23 11:19:12 lb2 relayd[69641]: rsae_send_imsg: poll timeout >> Dec 23 11:19:12 lb2 relayd[22515]: rsae_send_imsg: poll timeout >> [snip] >> Dec 23 11:19:17 lb2 relayd[69641]: rsae_send_imsg: poll timeout >> Dec 23 11:19:18 lb2 relayd[22515]: rsae_send_imsg: poll timeout >> Dec 23 11:19:18 lb2 relayd[52110]: rsae_send_imsg: poll timeout >> Dec 23 11:19:18 lb2 relayd[69641]: rsae_send_imsg: poll timeout >> ...etc... >> >> Restarting the daemon "fixes" the problem. >> Not sure how to trouble shoot this but I am able to reproduce this >> consistently by pointing SSLLabs towards relayd. >> Would be great to get some pointers. >> > > I have seen this as well on our production systems. This is a problem in > the privsep part of the TLS code. I could not do more testing yet but my > assumption is that a new option / feature is freaking this code out.
Anything I can do or collect to give you more information? Mischa