The system was only running poudriere when the reboot occurred.
It's a hp-proliant-g8 2u rackmount server. Xenon E5-2690v2 (x2)
On Sat, Oct 18, 2025 at 06:15:59PM -0700, Mark Millard wrote:
Do you use anything like:
# Delay when persistent low free RAM leads to
# Out Of Memory killing of processes:
vm.pageout_oom_seq=120
Yes
# For plunty of swap/paging space (will not
# run out), avoid pageout delays leading to
# Out Of Memory killing of processes:
#vm.pfault_oom_attempts=-1
That is also set.
#vm.pfault_oom_wait= 10
This isn't set in loader or sysctl.conf, but it is that value,
so I guess it's the default. For swap, my sysctl.conf has these:
# swap
vm.pageout_oom_seq=120
vm.pfault_oom_attempts=-1
vm.pageout_update_period=0
(Mine are in /boot/loader.conf .)
Why is that (asking because I thought using loader.conf was being
discouraged)
I'm attempting to build this port again after clearing obj ccache dirs
then rebuilding the system then deleting the builder, its pkgs & logs
then recreating the builder from the obj of the rebuilt system.
it's got as far as building electron37 right now. top looks like this
last pid: 7554; load averages: 9.96, 10.01, 10.00 up 0+17:11:14 11:53:51
106 processes: 11 running, 95 sleeping
CPU: 48.2% user, 0.0% nice, 1.9% system, 0.0% interrupt, 49.9% idle
Mem: 38G Active, 5202M Inact, 12G Wired, 1267M Buf, 70G Free
ARC: 5946M Total, 2664M MFU, 2426M MRU, 645K Anon, 40M Header, 781M Other
4379M Compressed, 6795M Uncompressed, 1.55:1 Ratio
Swap: 4034M Total, 4034M Free
--
