Date: Tue, 3 Sep 2019 14:07:50 +1000 From: MJ <mafsys1234@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Buildworld Failling Message-ID: <f06d3d4f-0815-a5af-680f-fb66febe4c1b@gmail.com> In-Reply-To: <8cc0af2a-1e27-9631-3341-df6d96c6e21f@tundraware.com> References: <8cc0af2a-1e27-9631-3341-df6d96c6e21f@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Tim, On 3/09/2019 2:02 am, Tim Daneliuk wrote: > I have a machine running 11.3-stable. It has a cron job that downloads > latest sources and the does a build of kernels and a buildworld. This > is a build only with the idea that the binaries will be available as > required for, say, a zero day problem. > > This has worked great for years, but I am now seeing this: > > --- kernel.full --- > linking kernel.full > ctfmerge -L VERSION -g -o kernel.full ... > Killed > *** [kernel.full] Error code 137 > > > I this is on a Digital Ocean droplet. Another physical server in my > domain that does the exact same thing is working fine. > > Any ideas? > That indicates a signal was sent to the script; SIGKILL in fact. Why? Maybe something in the management of the droplet killed it because it was using too much RAM, disk, your guess is better than mine. Cheers Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f06d3d4f-0815-a5af-680f-fb66febe4c1b>