Bryan, I terminated builder2 it was running in incorrect security group. You can delete it. The one we need to use is called "launch-wizard-1" - this is where both koji and builder3 which I spawned today are. I set the rules to accept all TCP/UDP connections in this group (ssh/https from outside only).
We are now running "standard" setup of koji master with kojibuilder1 (slow, only 3.5 GB RAM, no createrepo tasks there) and one builder (kojibuilder3, 8GB RAM, 2 cores, can do all tasks). http://koji.katello.org/koji/hosts I have updated our wiki with some changed commands. I had some troubles with NFS when we moved external-repos to different volume. Also added some permission changes. http://projects.theforeman.org/projects/foreman/wiki/KojiBuilderSetup Please give it a try now, it should be hopefully fine. On Thu, Jun 8, 2017 at 11:17 AM, Lukas Zapletal <l...@redhat.com> wrote: > Yeah we are in process of adding new builder, did not go well > yesterday, Bryan what is the status? Can you bring one up? Make sure > it's the same specs, then I will enable it and remove repocreate tasks > from builder1. > > Unfortunately, I can't make swap, there's not make enough room for it. > Bryan, did you not create volume for swap on purpose? It used to be > the /dev/xvdj2 on the old system, now I can see that /dev/xvdj1 spans > across whole volume and there is no room for it. In the meantime, I > created /swapfile of size 1GB, that's all I can do for now. > Resubmitted your task, but I don't believe one extra gig will do it. > We need to wait for Bryan. > > Wait I have access to AWS now, checking. The builder is not corrrectly > configured, it's in wrong security group. Let me spawn new one and > configure it. > > > On Wed, Jun 7, 2017 at 10:10 PM, Dominic Cleal <domi...@cleal.org> wrote: >> On 04/06/17 12:34, Lukas Zapletal wrote: >>> I had to brought Koji services offline, I expect them to come back in >>> an hour, we are trying to move the data to different EC2 instance. >>> This is just a test and if the new instance will work fine, we will do >>> the switchover during the week. >> >> This appears to be active now, but some newRepo tasks are failing with >> segfaults. I am able to log into the new host and it appears to be out >> of memory - dmesg contains OOM messages, killing mergerepo_c. Could you >> add more memory or swap please? >> >> Example task: http://koji.katello.org/koji/taskinfo?taskID=644261 >> >> dmesg snippet: >> Out of memory: Kill process 25711 (mergerepo_c) score 406 or sacrifice child >> Killed process 25711, UID 0, (mergerepo_c) total-vm:1738484kB, >> anon-rss:1619816kB, file-rss:72kB >> >> -- >> Dominic Cleal >> domi...@cleal.org >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
