This is the log, Name "BSConfig::bsgroup" used only once: possible typo at ./bs_sched line 51. starting build service scheduler cold start, scanning all projects getting data for all projects from http://build.de.scorpio-it.net:6362 calculating project dependencies... sorting projects and repositories... looking at low prio SUSE:SLE-10 (0/0/11/7) looking at low prio SUSE:SLE-10:SDK (0/0/10/7) looking at low prio home:Admin (0/0/9/7) looking at low prio openSUSE:10.2 (0/0/8/7) looking at low prio openSUSE:10.3 (0/0/7/7) looking at low prio SUSE:SLE-10/standard (0/0/6/7) - SUSE:SLE-10/standard (spec) packages found: 2000 (hits: 2000, misses: 0) expanding dependencies sorting 0 packages building: 0, notready: 0 looking at low prio openSUSE:10.2/standard (0/0/5/7) - openSUSE:10.2/standard (spec) packages found: 5102 (hits: 5102, misses: 0) expanding dependencies sorting 0 packages building: 0, notready: 0 looking at low prio openSUSE:10.3/standard (0/0/4/7) - openSUSE:10.3/standard (spec) packages found: 6359 (hits: 6359, misses: 0) expanding dependencies sorting 0 packages building: 0, notready: 0 looking at low prio SUSE:SLE-10:SDK/standard (0/0/3/7) - SUSE:SLE-10:SDK/standard (spec) packages found: 1940 (hits: 1940, misses: 0) expanding dependencies sorting 0 packages building: 0, notready: 0 looking at low prio home:Admin/openSUSE_10.2 (0/0/2/7) - home:Admin/openSUSE_10.2 (spec) expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 looking at low prio home:Admin/openSUSE_10.3 (0/0/1/7) - home:Admin/openSUSE_10.3 (spec) expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 looking at low prio home:Admin/SLE_10 (0/0/0/7) - home:Admin/SLE_10 (spec) expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 waiting for an event... and how to understand ? here it says "notready: 1" but webclient said finished ?? But will also have a look without NFS-shares. Chris Dominique Leuenberger schrieb:
On 26.05.2008 at 17:52, Christian
wrote: Hi Dominique,
Dominique Leuenberger schrieb:
Is the worker running on the same station as the scheduler? (I'd start with
this setup...)
you can also try to switch to the 'screen' session of a worker...sometimes
this can reveal some information (screen -R as root)
worker is running on same station. And there are two remote workers. screenseesion only shows "starting worker d41d8cd98f00b204e9800998ecf8427e build d41d8cd98f00b204e9800998ecf8427e"
I need to mention that /srv/obs/{build,repos} are shared via NFS. Could this be the problem ?
I doubt this should be a problem. Anyhow, the workers do never access those directories on their own. They get all they need from the Source server and send also the packages back there. (at least that's what I understood so far.. I'm not an expert in this domain).
check the log files in /srv/obs/log, especially the scheduler logs. They appear sometimes a bit cryptic (to me) but still are valuable once understood.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org