BOINC has troubles handling proxy on Linux (Ubuntu 12.04)

Message boards : Questions and problems : BOINC has troubles handling proxy on Linux (Ubuntu 12.04)
Message board moderation

To post messages, you must log in.

AuthorMessage
mathieuS

Send message
Joined: 7 Feb 14
Posts: 3
Switzerland
Message 52420 - Posted: 7 Feb 2014, 15:55:01 UTC

Hi !

I use BOINC 7.2.33 x64 on Ubuntu LTS 12.04.

My institution filters outgoing internet connection through a proxy. I tried to configure the proxy settings using BOINC Manager, going to Tools -> Options -> Proxy HTTP. I checked the "Connect using a HTTP proxy server" box, entered server address and port and my institutional login and password. But this doesn't work, BOINC can't reach the internet.
If I set no proxy settings in BOINC but instead open a terminal and export the http_proxy environment variable, then start BOINC from the same terminal, everything works fine.

Does anyone have an idea why BOINC behaves this way ? I am happy though I could find a workaround and use BOINC anyway.

Thanks in advance,
Mathieu
ID: 52420 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15484
Netherlands
Message 52421 - Posted: 7 Feb 2014, 17:29:07 UTC - in response to Message 52420.  

Does your institution allow something like BOINC? Best ask them for permission first.

Then you'll want to check http://boinc.berkeley.edu/wiki/Client_configuration, more specifically the <force_auth>auth_method</force_auth> option.
You can also set up your proxy through here, with the <proxy_info> option.
ID: 52421 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 52422 - Posted: 7 Feb 2014, 17:30:11 UTC - in response to Message 52420.  

Could you enable <http_debug> and <proxy_debug> log flags. See Client configuration.

Also, I hear some proxies work with HTTP 1.0. You can force BOINC to use that with <http_1_0> option.
ID: 52422 · Report as offensive
mathieuS

Send message
Joined: 7 Feb 14
Posts: 3
Switzerland
Message 52480 - Posted: 10 Feb 2014, 9:33:44 UTC

The cc_config.xml file was not present ; settings were stored in client_state.xml.
So, if I create cc_config.xml, add proxy settings and enable http and proxy debug, I get the following :


update requested by user
Sending scheduler request: Requested by user.
Requesting new tasks for CPU
[http] HTTP_OP::init_post(): http://docking.gcl.cis.udel.edu/docking_cgi/cgi
[proxy] HTTP_OP::no_proxy_for_url(): http://docking.gcl.cis.udel.edu/docking_cgi/cgi
[proxy] returning false
[proxy]: setting up proxy proxy.intranet.inst:1234
[http] [ID#1] Info: About to connect() to proxy proxy.intranet.inst port 1234 (#0)
[http] [ID#1] Info: Trying 123.456.123.456...
[http] [ID#1] Info: Connected to proxy.intranet.inst (123.456.123.456) port 1234 (#0)
[http] [ID#1] Sent header to server: POST http://docking.gcl.cis.udel.edu/docking_cgi/cgi HTTP/1.1
[http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.2.33)
[http] [ID#1] Sent header to server: Host: docking.gcl.cis.udel.edu
[http] [ID#1] Sent header to server: Accept: */*
[http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
[http] [ID#1] Sent header to server: Proxy-Connection: Keep-Alive
[http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
[http] [ID#1] Sent header to server: Content-Length: 8706
[http] [ID#1] Sent header to server: Expect: 100-continue
[http] [ID#1] Sent header to server:
[http] [ID#1] Received header from server: HTTP/1.1 100 Continue
[http] [ID#1] Received header from server: HTTP/1.1 407 Proxy Authentication Required
[http] [ID#1] Info: gss_init_sec_context() failed: : Credentials cache file '/tmp/krb5cc_1001' not found
[http] [ID#1] Received header from server: Proxy-Authenticate: NEGOTIATE
[http] [ID#1] Received header from server: Proxy-Authenticate: NTLM
[http] [ID#1] Received header from server: Proxy-Authenticate: BASIC realm="Intranet"
[http] [ID#1] Received header from server: Cache-Control: no-cache
[http] [ID#1] Received header from server: Pragma: no-cache
[http] [ID#1] Received header from server: Content-Type: text/html; charset=utf-8
[http] [ID#1] Info: HTTP/1.1 proxy connection set close!
[http] [ID#1] Received header from server: Proxy-Connection: close
[http] [ID#1] Received header from server: Set-Cookie: BCSI-CS-1DFAD46DCF1A2FDA=2; Path=/
[http] [ID#1] Received header from server: Connection: close
[http] [ID#1] Received header from server: Content-Length: 513
[http] [ID#1] Received header from server:
[http] [ID#1] Info: Closing connection #0
Scheduler request failed: HTTP proxy authentication failure
Sending scheduler request: Requested by user.
Requesting new tasks for CPU
[http] HTTP_OP::init_post(): http://docking.cis.udel.edu/docking_cgi/cgi
[proxy] HTTP_OP::no_proxy_for_url(): http://docking.cis.udel.edu/docking_cgi/cgi
[proxy] returning false
[proxy]: setting up proxy proxy.intranet.inst:1234
[http] [ID#1] Info: About to connect() to proxy proxy.intranet.inst port 1234 (#0)
[http] [ID#1] Info: Trying 123.456.123.456...
[http] [ID#1] Info: Connected to proxy.intranet.inst (123.456.123.456) port 1234 (#0)
[http] [ID#1] Sent header to server: POST http://docking.cis.udel.edu/docking_cgi/cgi HTTP/1.1
[http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.2.33)
[http] [ID#1] Sent header to server: Host: docking.cis.udel.edu
[http] [ID#1] Sent header to server: Accept: */*
[http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
[http] [ID#1] Sent header to server: Proxy-Connection: Keep-Alive
[http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
[http] [ID#1] Sent header to server: Content-Length: 8706
[http] [ID#1] Sent header to server: Expect: 100-continue
[http] [ID#1] Sent header to server:
[http] [ID#1] Received header from server: HTTP/1.1 100 Continue
[http] [ID#1] Received header from server: HTTP/1.1 407 Proxy Authentication Required
[http] [ID#1] Info: gss_init_sec_context() failed: : Credentials cache file '/tmp/krb5cc_1001' not found
[http] [ID#1] Received header from server: Proxy-Authenticate: NEGOTIATE
[http] [ID#1] Received header from server: Proxy-Authenticate: NTLM
[http] [ID#1] Received header from server: Proxy-Authenticate: BASIC realm="Intranet"
[http] [ID#1] Received header from server: Cache-Control: no-cache
[http] [ID#1] Received header from server: Pragma: no-cache
[http] [ID#1] Received header from server: Content-Type: text/html; charset=utf-8
[http] [ID#1] Info: HTTP/1.1 proxy connection set close!
[http] [ID#1] Received header from server: Proxy-Connection: close
[http] [ID#1] Received header from server: Set-Cookie: BCSI-CS-1DFAD46DCF1A2FDA=2; Path=/
[http] [ID#1] Received header from server: Connection: close
[http] [ID#1] Received header from server: Content-Length: 513
[http] [ID#1] Received header from server:
[http] [ID#1] Info: Closing connection #0
Scheduler request failed: HTTP proxy authentication failure


For me, it's got no obvious meaning ...
ID: 52480 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 52485 - Posted: 10 Feb 2014, 16:50:06 UTC - in response to Message 52480.  

Did you try the <force_auth> option? I'm guessing that it's the gss-negotiate that's failing here so something other than that.

You didn't say if you tried with <http_1_0>?
ID: 52485 · Report as offensive
mathieuS

Send message
Joined: 7 Feb 14
Posts: 3
Switzerland
Message 52490 - Posted: 11 Feb 2014, 7:37:45 UTC - in response to Message 52485.  

Did you try the <force_auth> option? I'm guessing that it's the gss-negotiate that's failing here so something other than that.

Wow ! You're good, adding this line to cc_config.xml solved the problem :
<force_auth>basic</force_auth>


You didn't say if you tried with <http_1_0>?

I didn't, because of that line :
[http] [ID#1] Received header from server: HTTP/1.1 100 Continue


Thanks very much !
ID: 52490 · Report as offensive

Message boards : Questions and problems : BOINC has troubles handling proxy on Linux (Ubuntu 12.04)

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.