Mailinglist Archive: opensuse-buildservice (193 mails)

[Troy Telford <ttelford.groups@xxxxxxxxx>]

I've been setting up the build service on my own machines.  After getting to 
the point where I could build some of the more simple packages I have, I 
decided to try the obs-worker on other systems.

So, I've done the following:
* Installed the obs-* packages on an openSUSE 10.2 machine.
* Installed the obs-worker RPM on a different openSUSE 10.2 machine
* Installed the obs-worker RPM on a SLES 10 machine

I edited /etc/sysconfig/obs-worker, and set
OBS_STORAGE_SERVER="myhost.my.com:6262"

Then I tried starting the obs-worker on the node, but nothing happened.

I noticed that /etc/init.d/obsworker starts a screen session, and 
runs 'something' inside.  So, I attached to the screen session to get a look:
starting worker d41d8cd98f00b204e9800998ecf8427e build 
d41d8cd98f00b204e9800998ecf8427e
send_state http://localhost:6262: connect to localhost:6262: Connection ;
refused

hmmm...  I know that OBS_STORAGE_SERVER was set properly; I even added a 
few 'echo' statements in the init script to verify it.

I then found that (on the obs server) /usr/lib/obs/server/BSConfig.pm had 
entries for 'localhost:6262'.

So, I changed them from localhost:6262 to 'myhost.my.com:6262', and re-started 
the service on my worker nodes, and jumped into the screen session to check 
on its status:
starting worker d41d8cd98f00b204e9800998ecf8427e build 
d41d8cd98f00b204e9800998ecf8427e

So it appears that it's not only necessary to edit /etc/sysconfig/obs-worker, 
but also /usr/lib/obs/server/BSConfig.pm (on the server).

Of course, that's not the end of the story...

Now that I am able to get it to start the worker without throwing any kind of 
error, I'm still unable to get the worker node to do any work.

So... what am I missing?
--
Troy Telford
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx