[opensuse-buildservice] /etc/init.d/obsworker does not start after reboot when running behind a proxy
It seems the curl command in obsworker ignores the no-proxy settings and tries to download the worker code from our proxy.
OTOH, if I log in as root and issue a 'rcobsworker start', it does _not_ fail. Of course, when you log in, the proxy environment variables are set, but if obsworker is run as a child of the init process, none of theses env vars are set.
In the obsworker code, I see that it sources /etc/sysconfig/proxy, but this sets shell variables, not env variables.
Ciao, Martin
Am Donnerstag, 11. Juli 2013, 13:37:06 schrieb Martin Weber:
It seems the curl command in obsworker ignores the no-proxy settings and tries to download the worker code from our proxy.
OTOH, if I log in as root and issue a 'rcobsworker start', it does _not_ fail. Of course, when you log in, the proxy environment variables are set, but if obsworker is run as a child of the init process, none of theses env vars are set.
In the obsworker code, I see that it sources /etc/sysconfig/proxy, but this sets shell variables, not env variables.
Okay, I added some export lines there. Also for next 2.4 release, would be nice if you can test if that works for you.
thanks! adrian
Am 16.07.2013 08:13, schrieb Adrian Schröter:
Am Donnerstag, 11. Juli 2013, 13:37:06 schrieb Martin Weber:
It seems the curl command in obsworker ignores the no-proxy settings and tries to download the worker code from our proxy.
[...]
Okay, I added some export lines there. Also for next 2.4 release, would be nice if you can test if that works for you.
Thanks, I will do after my vacation.
BTW: All the API, webui and worker were running on a virtual machine on a winows host. After I moved the VM to a Solaris host, the problem did not appear. Weird.
Martin
buildservice@lists.opensuse.org
-
Adrian Schröter -
Martin Weber