On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote: > On 2021/10/01 14:43, Stuart Henderson wrote: >> On 2021/10/01 09:29, [email protected] wrote: >> > I'm getting a daily crash (call to fatalx). No clue what triggers it and >> > the logging is really sparse. I couldn't follow what the code in ca.c is >> > actually doing (what the hash belongs to that is triggering the crash). A >> > snip from /var/log/daemon is reproduced below. There are no other log >> > messages in any logs around the same time frame as the relayd shutdown. >> > Also, that fd passing failed for https is concerning. Any suggestions in >> > debugging this? OpenBSD 6.9, dmesg at bottom. >> > >> > >> > grep relayd /var/log/daemon >> > 876:Sep 30 15:07:39 mnetic relayd[222]: adding 1 hosts from table >> > axolotlfeeds:7053 (no check) >> > 877:Sep 30 15:07:39 mnetic relayd[44589]: adding 1 hosts from table >> > axolotlfeeds:7053 (no check) >> > 878:Sep 30 15:07:39 mnetic relayd[57595]: adding 1 hosts from table >> > axolotlfeeds:7053 (no check) >> > 909:Oct 1 00:42:20 mnetic relayd[95946]: ca: ca_dispatch_relay: invalid >> > relay hash >> > 'SHA256:f545fa75bd01d82c05359e21ae769d525c2971b8221a8e50e415fe3e62ea6553' >> > 910:Oct 1 00:42:20 mnetic relayd[44589]: relay: pipe closed >> > 911:Oct 1 00:42:20 mnetic relayd[8473]: hce exiting, pid 8473 >> > 912:Oct 1 00:42:20 mnetic relayd[15293]: pfe exiting, pid 15293 >> > 913:Oct 1 00:42:20 mnetic relayd[29437]: ca exiting, pid 29437 >> > 914:Oct 1 00:42:20 mnetic relayd[52845]: ca exiting, pid 52845 >> > 915:Oct 1 00:42:20 mnetic relayd[99285]: parent terminating, pid 99285 >> > 916:Oct 1 00:42:20 mnetic relayd[222]: relay exiting, pid 222 >> > 917:Oct 1 00:42:20 mnetic relayd[57595]: relay exiting, pid 57595 >> > 921:Oct 1 09:12:59 mnetic relayd[2129]: startup >> > 922:Oct 1 09:12:59 mnetic relayd[2129]: config_setrelay: fd passing >> > failed for `https': Too many open files >> >> ^^^^^^^^^^^^^^^^^^^ >> >> By default the limit for relayd is controlled by the openfiles settings >> for the "daemon" class in /etc/login.conf. You can check current use >> with fstat | grep -c relayd. If you need to raise it you can add >> something like this to the file, replacing XXX with "what you normally >> see when it's busy plus some extra leeway" and then "rcctl restart >> relayd" so it takes effect. >> >> relayd:\ >> :openfiles-max=XXX:\ >> :openfiles-cur=XXX:\ >> :tc=default: > > Hmm. Rereading your mail it might not be that..but if the limit is too > low you could have other things failing as a result..
Looks like I was using 154 (of 128) files, so I bumped openfiles-cur slightly to accommodate that. Unfortunately it's now a day or two wait to see if that was contributing to the failure.
