Hi, I think I know the reason for this. If you are using the latest openSUSE:Tools/obs-server, adrian accidentially commited the two new scripts: - obsdispatcher - obspublisher to be == obsscheduler. With the new backend, the dispatcher and publisher were separated from the scheduler. So what you need to do is: rcobsrepserver start rcobssrcserver start rclighttpd start rcobsscheduler start rcobsdispatcher start rcobspublisher start I have attached to this e-mail the correct scripts obsdispatcher & obspublisher Hope it helps. Martin Oliver Bengs wrote:

Am Sun, 4 Nov 2007 19:05:38 +0100 schrieb Adrian Schröter :

...

On Saturday 03 November 2007 12:48:36 wrote aledr:

...

Hi!

I followed the wiki informations and the README.setup steps to install a local build service, and seems that almost everything is working. But the "Build Status" of the packages are just "scheduled".

Same here, since the last update.

<snip>

...

do you have a worker process running ?

The worker idles.

# cat /srv/obs/workers/idle/i686\:apollo_2 <worker hostarch="i686" ip="192.168.0.5" port="16732" workerid="apollo/2" />

There isn't a Firewall running and the IP is correct.

...

Without it, it will remain to be scheduled (this means the scheduler did it's job), but nothing starts to build it ...

So it looks like ;)

Olli

#! /bin/sh # Copyright (c) 2007, Novell Inc. # # Author: adrian@suse.de # # /etc/init.d/obsdispatcher # and its symbolic link # /usr/sbin/rcobsdispatcher # ### BEGIN INIT INFO # Provides: obsdispatcher # Required-Start: $time $syslog obssrcserver obsrepserver # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 4 6 # Description: openSUSE build service ### END INIT INFO . /etc/rc.status . /etc/sysconfig/obs-server # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} obsdir=/usr/lib/obs/server/ rc_reset case "$1" in start) echo -n "Initializing obsdispatcher" cd "$obsdir" # FIXME: not nice, this should receive a proper daemon handling, # including real logging, pid file and startproc ./bs_dispatch >& /srv/obs/log/dispatcher_$i.log & rc_status -v ;; stop) echo -n "Shutting down obsdispatcher" killall bs_dispatch rc_status -v ;; restart) ## If first returns OK call the second, if first or ## second command fails, set echo return value. $0 stop && $0 start rc_status ;; try-restart) $0 status if test $? = 0; then $0 restart else rc_reset # Not running is not a failure. fi # Remember status and be quiet rc_status ;; reload) ;; status) echo -n "Checking for obsdispatcher:" checkproc bs_dispatch rc_status -v ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|reload}" exit 1 ;; esac rc_exit #! /bin/sh # Copyright (c) 2007, Novell Inc. # # Author: adrian@suse.de # # /etc/init.d/obspublisher # and its symbolic link # /usr/sbin/rcobspublisher # ### BEGIN INIT INFO # Provides: obspublisher # Required-Start: $time $syslog obssrcserver obsrepserver # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 4 6 # Description: openSUSE build service ### END INIT INFO . /etc/rc.status . /etc/sysconfig/obs-server # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} obsdir=/usr/lib/obs/server/ rc_reset case "$1" in start) echo -n "Initializing obspublisher" cd "$obsdir" # FIXME: not nice, this should receive a proper daemon handling, # including real logging, pid file and startproc ./bs_publish >& /srv/obs/log/publisher_$i.log & rc_status -v ;; stop) echo -n "Shutting down obspublisher" killall bs_publish rc_status -v ;; restart) ## If first returns OK call the second, if first or ## second command fails, set echo return value. $0 stop && $0 start rc_status ;; try-restart) $0 status if test $? = 0; then $0 restart else rc_reset # Not running is not a failure. fi # Remember status and be quiet rc_status ;; reload) ;; status) echo -n "Checking for obspublisher: " checkproc bs_publish rc_status -v ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|reload}" exit 1 ;; esac rc_exit

Works perfectly Martin! =D Many thanks! 2007/11/4, Martin Mohring :

Hi,

I think I know the reason for this. If you are using the latest openSUSE:Tools/obs-server, adrian accidentially commited the two new scripts: - obsdispatcher - obspublisher to be == obsscheduler. With the new backend, the dispatcher and publisher were separated from the scheduler.

So what you need to do is:

rcobsrepserver start rcobssrcserver start rclighttpd start rcobsscheduler start rcobsdispatcher start rcobspublisher start

I have attached to this e-mail the correct scripts obsdispatcher & obspublisher

Hope it helps. Works perfectly Martin! :D

Martin

Oliver Bengs wrote:

...

Am Sun, 4 Nov 2007 19:05:38 +0100 schrieb Adrian Schröter :

...

On Saturday 03 November 2007 12:48:36 wrote aledr:

...

Hi!

I followed the wiki informations and the README.setup steps to install a local build service, and seems that almost everything is working. But the "Build Status" of the packages are just "scheduled".

Same here, since the last update.

<snip>

...

do you have a worker process running ?

The worker idles.

# cat /srv/obs/workers/idle/i686\:apollo_2 <worker hostarch="i686" ip="192.168.0.5" port="16732" workerid="apollo/2" />

There isn't a Firewall running and the IP is correct.

...

Without it, it will remain to be scheduled (this means the scheduler did it's job), but nothing starts to build it ...

So it looks like ;)

Olli

#! /bin/sh # Copyright (c) 2007, Novell Inc. # # Author: adrian@suse.de # # /etc/init.d/obsdispatcher # and its symbolic link # /usr/sbin/rcobsdispatcher # ### BEGIN INIT INFO # Provides: obsdispatcher # Required-Start: $time $syslog obssrcserver obsrepserver # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 4 6 # Description: openSUSE build service ### END INIT INFO

. /etc/rc.status . /etc/sysconfig/obs-server

# Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]}

obsdir=/usr/lib/obs/server/

rc_reset case "$1" in start) echo -n "Initializing obsdispatcher" cd "$obsdir" # FIXME: not nice, this should receive a proper daemon handling, # including real logging, pid file and startproc ./bs_dispatch >& /srv/obs/log/dispatcher_$i.log & rc_status -v ;; stop) echo -n "Shutting down obsdispatcher" killall bs_dispatch rc_status -v ;; restart) ## If first returns OK call the second, if first or ## second command fails, set echo return value. $0 stop && $0 start rc_status ;; try-restart) $0 status if test $? = 0; then $0 restart else rc_reset # Not running is not a failure. fi # Remember status and be quiet rc_status ;; reload) ;; status) echo -n "Checking for obsdispatcher:" checkproc bs_dispatch rc_status -v ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|reload}" exit 1 ;; esac rc_exit

#! /bin/sh # Copyright (c) 2007, Novell Inc. # # Author: adrian@suse.de # # /etc/init.d/obspublisher # and its symbolic link # /usr/sbin/rcobspublisher # ### BEGIN INIT INFO # Provides: obspublisher # Required-Start: $time $syslog obssrcserver obsrepserver # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 4 6 # Description: openSUSE build service ### END INIT INFO

. /etc/rc.status . /etc/sysconfig/obs-server

# Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]}

obsdir=/usr/lib/obs/server/

rc_reset case "$1" in start) echo -n "Initializing obspublisher" cd "$obsdir" # FIXME: not nice, this should receive a proper daemon handling, # including real logging, pid file and startproc ./bs_publish >& /srv/obs/log/publisher_$i.log & rc_status -v ;; stop) echo -n "Shutting down obspublisher" killall bs_publish rc_status -v ;; restart) ## If first returns OK call the second, if first or ## second command fails, set echo return value. $0 stop && $0 start rc_status ;; try-restart) $0 status if test $? = 0; then $0 restart else rc_reset # Not running is not a failure. fi # Remember status and be quiet rc_status ;; reload) ;; status) echo -n "Checking for obspublisher: " checkproc bs_publish rc_status -v ;; *) echo "Usage: $0 {start|stop|status|try-restart|restart|reload}" exit 1 ;; esac rc_exit

-- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Monday 12 November 2007 10:45:21 wrote Jordi Massaguer i Pla:

Hi,

I am evaluating the implementation of a local build service for a derived and customized distribution (building and mantaining it up to date). This means, rebuilding only some packages and building a few more. Let's say around 100 packages and 5 to 10 builds each day. Right now it is build only for i386, but will be nice to build it also for other architectures.

However, I have no idea about the hardware requirements for that. Can you give me some advice? Which are the variables that should be considered?

Depends how long you are willing to wait ;) We usually esitmate to build 6000 source packages within 24 hours using 40 build instances ( 1 CPU core, 0.5 GB memory, 20 GB hdd ) so, you can may calculate what you will need. 5 to 10 builds each can get done by a single system (except all jobs are OpenOffice.org), I think. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

5 to 10 builds each can get done by a single system (except all jobs are OpenOffice.org), I think.

When you say a single system, you mean something like this: 1CPU 4GB 500GB ?

bye adrian

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

I'm with the same problem again... ¬¬ Installed a new x86_64 server and created the project, then the packages and finally uploaded all the sources. Changed /etc/sysconfig/obs-server architectures from "i586" to "i586 x86_64". Created the /etc/init.d/obspublisher and /etc/init.d/obsdispatcher scripts and Its symbolic links. Started all process. And got this: ---------------------------------------------------------------------------------------------------------------------------------- server:~ # chkconfig obsdispatcher --add insserv: script obsdispatcher: service obsscheduler already provided! insserv: exiting now! /sbin/insserv failed, exit code 1 obsdispatcher 0:off 1:off 2:off 3:off 4:off 5:off 6:off server:~ # chkconfig obspublisher --add insserv: script obsdispatcher: service obsscheduler already provided! insserv: script obspublisher: service obsscheduler already provided! insserv: exiting now! /sbin/insserv failed, exit code 1 obspublisher 0:off 1:off 2:off 3:off 4:off 5:off 6:off ---------------------------------------------------------------------------------------------------------------------------------- Sometimes obsworker is not running, and the packages stays all the time as "scheduled" again. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org