02:34:04 eeby 03:05:20 Fixed my issue used Intel instead of Nvidia and modesetting 03:05:34 Using Intel 06:25:26 what's the link to the poudriere server that builds packages every Wednesday? I can't find it 07:26:00 Greetings 07:26:52 Greetings 07:26:56 a fellow scientist 07:27:04 Did you eat all the donuts? 09:58:19 antranigv: there isn't one specific server, it's a whole bunch of servers - there's a status page that links to them individually, on https://pkg-status.freebsd.org 11:33:04 hi, if i am mostly using bin packages but want a few ports installed is it recommended to stick those into a jail? 14:41:02 OwlWizard: i don't see the correlation 17:41:09 Hi folks. Trying to get DKIM going, and I understand it starts a daemon to keep the milter open (I'm using sendmail), but I don't see an rc.d file to handle starts. Am I supposed to run it manually? Is there some other tool that is recommended? 18:19:42 gh00p, Which DKIM daemon are you setting up? 18:22:22 OpenDKIM which I am familiar with has a port/pkg and it comes with /usr/local/etc/rc.d/milter-opendkim therefore I deduce you are using a different DKIM milter? 18:33:01 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280303 , have you heard/read of any update of this one ? 18:36:33 neither of the two reports from this feel particularly credible 18:36:36 are you hitting this? 18:36:46 yes 18:37:14 what do you get from `readelf -n /lib/libcxxrt.so.1` and `readelf -n /lib/libc++.so.1`? 18:37:20 just the "ABI tag:" line, preferably 18:38:08 ABI tag: 1400097 18:38:31 ABI tag: 1401000 18:38:56 that would be a problem 18:39:25 your libcxxrt.so.1 is from a 14.0 build for some reason, while libc++.so.1 is from a 14.1 build 18:39:37 was this installed 14.0 then upgraded to 14.1? 18:40:19 yes pfctl -sr gives : Assertion failed: (elems <= maxelems), function pf_nvuint_32_array, file /usr/src/lib/libpfctl/libpfctl.c, line 147. Abort (core dumped) 18:40:25 but pf seems to be running 18:41:01 yes 18:41:02 ok, so for some reason the upgrade from 14.0 -> 14.1 was wrong 18:42:42 on this system , I was running 12.3-RR and import a raw image of 14.1p4 boot environment, but I checked on the source host that has been upgraded from 12.3, 13.3, 14.0, and 14.1, and I confirm the problem too 18:43:01 s/12.3-RR/12.3-R 18:43:55 from what I read 14.1p0 didn't have this problem 18:48:00 kevans: from a fresh install from 14.1 iso, we have the correct libs 18:48:03 i don't think it would be too surprising if the recent libc++ changes only just made the mismatch relevant 18:48:25 i.e. this was almost certainly just a ticking timebomb and people have gotten lucky 18:49:14 I'd be curious to see if there's anything else in /{,usr/}lib{,exec} /{,usr/}{s,}bin with a 14.0 ABI tag 18:49:47 this feels like a pretty clear freebsd-update problem, though 18:51:04 tbh, here the problem is considered seriously, as it rises pfctl result with nagios checks 19:05:13 kevans: in /lib only 4 lib*.so.* are in ABI tag 1401000 19:06:25 and 70 in 1400097 19:09:48 in /usr/lib 17 are in ABI tag 1401000 19:10:16 337 are in in 1400097 19:16:04 so the vast majority of your system libraries are still 14.0 19:17:27 do any of the binaries fare any better? 19:18:16 fare ? 19:18:30 are the majority of them 14.1, or 14.0? 19:18:49 majority is 14.0 19:18:58 by far 19:20:27 ok, thanks 19:20:32 i'm throwing this transcript into the PR 19:21:10 thank you very much 21:26:53 sidh: is it possible that this machine didn't complete the full freebsd-update procedure going to 14.1? 21:27:59 there's something like three install invocations needed for that kind of upgrade 22:41:35 rwp, sorry, my irc client disconnected. Thanks for taking an interest. I've installed opendkim, but I didn't see that startup script. I do now, thanks. :)  I also haven't configured sendmail to use it yet...