FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 03-02-2010, 04:21 AM
 
Default One builder is distconnetcted when building

One builder is distconnetcted when building,then our packages in this builder are
missing.What methods can koji do to deal with it?Can I do someting to move these
packages to another builder?Thanks.


--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 03-02-2010, 07:35 PM
Mike McLean
 
Default One builder is distconnetcted when building

On 03/02/2010 12:21 AM, lixiao@nudt.edu.cn wrote:
> One builder is distconnetcted when building,then our packages in this builder are
> missing.What methods can koji do to deal with it?Can I do someting to move these
> packages to another builder?Thanks.

Your question is a bit unclear. In the future please help us help you by
providing more detail and background.

I'm guessing that during a build in your koji system, one of your
builders was reset or went offline for some reason. I assume that by
"packages in this builder are missing" you mean that one of the
buildArch subtasks is stalled out in an incomplete state.

All the advice that follows is based on this reading of your question.
If I have misinterpreted, then please explain your question in more detail.

So....

First of all you'll want to deal with that stalled builder. If the task
has been stalled for long time, then you may need to restart kojid on
that host. When the kojid task restarts, it should free all the open
tasks for that host which should allow other builders (or itself) to
pick them up again.

Should there be any issues restarting the builder, you can just free the
stalled subtask manually. You can use the 'koji free-task' command. Note
the terminology: there is no "package" moving to another builder, it is
a task that is moving.

In my experience stalled tasks happen for one of two reasons:
1. a stall within the build itself (typically infinite loop or deadlock)
2. a dropped packet on the network

Problem 1 is outside the scope of Koji. Though Koji does configure mock
to time out after 24hrs.
Problem 2 is ultimately a network problem. While Koji tries to be
tolerant of network errors, there are certain scenarios that it can't do
much about.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 04:43 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org