Re: ERROR: Ports Collection support for your FreeBSD version has ended o_O
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 09 Sep 2022 03:08:27 UTC
Tomek CEDRO <tomek_at_cedro.info> wrote on Date: Thu, 08 Sep 2022 03:02:30 UTC : > By the way, make buildworld -j8 failed, but make buildworld (no -j > switch) works although takes much more time. Is there any way to speed > up the build process? I have MAKE_JOBS_NUMBER=8 already set in > /etc/make.conf. There are many ways for a buildworld to fail and you have given no clue what way yours did via, say, showing any of the messages about the failure(s) involved. Did any of the following types of messages show up on the console (or in related logs): > pid . . .(?), jid . . ., uid . . ., was killed: failed to reclaim memory > pid . . .(?), jid . . ., uid . . ., was killed: a thread waited too long to allocate a page > pid . . .(?), jid . . ., uid . . ., was killed: out of swap space If yes, which? How about the following messages (which, of themselves to not indicate any process has been kiled): > swap_pager: out of swap space > swp_pager_getswapspace(. . .): failed Are you using something like ( in, say, /boot/loader/conf ): # # Delay when persistent low free RAM leads to # Out Of Memory killing of processes: vm.pageout_oom_seq=120 This delays potential "killed: failed to reclaim memory" kills, possibly long enough to reach a state where sufficient memory is reclaimed. I'll note that the status "killed: failed to reclaim memory" does not require that swap be used much at all. Sustained low free RAM from just one process that always stays runnable can be sufficient to end up with such kills. Thus, SWAP need not be relevant. If you did not get messages such as the above, what was reported about the failure? I'll note that ZFS use and ZFS configuration can be important to the memory usage. So can tmpfs use (which is covered by RAM+SWAP). You may have other unreported competition for memory. But it is not clear if there is evidence of a RAM or memory usage related problem. I'm going to stop trying to guess more alternative failures that you might have run into. Note: In another message that did not quote from the message I'm replying to here, you wrote: QUOTE I have 32GB RAM and 100GB swap, If -j should work problem is somewhere else, will investigate, thanks :-) END QUOTE Having such information together in one message makes things easier to find, even if one ends up quoting material from past messages in order to make the related information easier to find. === Mark Millard marklmi at yahoo.com