[Buildbot-devel] Buildbot through stacktrace during SVNPoller
Fulvio Cervone
fcervone at me.com
Wed Jun 15 00:05:14 UTC 2011
Yeah, in your case 4 Gb were not that much.
I have SVN on a different machine, so I don't get impacted by it.
-f
On Jun 14, 2011, at 4:54 PM, William Deegan wrote:
> Fulvio,
>
> The machine is running buildbot + svn + a few nx hosts.
> The startup in question doesn't have a lot of hardware and will likely be migrating everything but svn off of that machine in the near term.
> It's centos 5.5 64 bit linux.
>
> Buildbot's eating ~1GB
> SVN+ Subversion edge (activestate) eating another 1GB
> So that doesn't leave a whole lot for the rest.
> 16GB should be sufficient.
>
> -Bill
> On Jun 14, 2011, at 4:28 PM, Fulvio Cervone wrote:
>
>> Glad that it helped.
>>
>> Just as suggestion, a machine running buildbot should run just the OS and buildbot; nothing else (if you have a windows machine probably the firewall and the antivirus are also suggested).
>>
>> I run a master with 2 Gb and a slave with 4 Gb and rarely have memory problems; try to keep the system resource monitor up to see what is sucking memory and just close it (i bet is the web browser; it can eat easily a GB or 2).
>>
>> If you are on mac or linux/unix you can check with ps aux to see what is going on with your system; 4 GB should be pretty much a good amount just for buildbot :)
>>
>> -f
>>
>>
>> On Jun 14, 2011, at 3:48 PM, William Deegan wrote:
>>
>>> Thanks all.
>>> We're increasing memory from an anemic 4GB to 16GB tonight.
>>> Hopefully that will resolve the issue.
>>> If not.. I'll be back.. :)
>>>
>>> -Bill
>>> On Jun 13, 2011, at 11:50 PM, P. Christeas wrote:
>>>
>>>> On Tuesday 14 June 2011, William Deegan wrote:
>>>>> Greetings,
>>>>>
>>>>> Found this while investigating why buildbot skipped a specific checkin.
>>>>> Any idea what might've caused this?
>>>>
>>>>> 390, in _fork self.pid = os.fork()
>>>>> exceptions.OSError: [Errno 12] Cannot allocate memory
>>>>>
>>>>
>>>> Your machine is out of resources.. I guess one way would be to keep a console
>>>> open and run sth. like 'top' to see what's going on at the time of OOM.
>>>> Until then, anything else would be just a wild guess. Your OOM may be
>>>> triggered by any other process, rather than buildbot itself.
>>>>
>>>>
>>>> --
>>>> Say NO to spam and viruses. Stop using Microsoft Windows!
>>>>
>>>> ------------------------------------------------------------------------------
>>>> EditLive Enterprise is the world's most technically advanced content
>>>> authoring tool. Experience the power of Track Changes, Inline Image
>>>> Editing and ensure content is compliant with Accessibility Checking.
>>>> http://p.sf.net/sfu/ephox-dev2dev
>>>> _______________________________________________
>>>> Buildbot-devel mailing list
>>>> Buildbot-devel at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> EditLive Enterprise is the world's most technically advanced content
>>> authoring tool. Experience the power of Track Changes, Inline Image
>>> Editing and ensure content is compliant with Accessibility Checking.
>>> http://p.sf.net/sfu/ephox-dev2dev
>>> _______________________________________________
>>> Buildbot-devel mailing list
>>> Buildbot-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>
More information about the devel
mailing list