Using Setiathome 3.08 and Boinc 3.19. Having just completed the first unit of work Boinc dies with an unhandled exception error being written to stderr.txt

Reason: Access Violation (0xc0000005 at address 0x00401D68 write attempt to address 0x73614220

This is being attempted via a http proxy which requires authentication, although it downloaded the work via the proxy fine.

Any ideas?

NT4 SP6a

Just for clarification, I have the same problem on two of my machines that are using Squid as an authenticated proxy. They crash every time they attempt to upload a result.
Just to confirm the locality of the crash, if I take out:

use_http_proxy
use_http_auth

From client_state.xml, it works fine.

Cheers

> Just for clarification, I have the same problem on two of my machines that are
> using Squid as an authenticated proxy. They crash every time they attempt to
> upload a result.
> Just to confirm the locality of the crash, if I take out:
>
> use_http_proxy
> use_http_auth
>
> From client_state.xml, it works fine.
>
> Cheers
>

But won't this stop the software from working with the proxy server? If the network you're on requires the proxy server this makes it so that we can't use the computers behind the proxy.

>
> But won't this stop the software from working with the proxy server? If the
> network you're on requires the proxy server this makes it so that we can't use
> the computers behind the proxy.
>

Yep, I was only mentioning it as confirmation that I had the same problem and that it was limited to the HTTP proxy code.
I don't have to use the proxy where I am, I just turned it off to prove the error was most likely somewhere in that bit of code ;)

G.

> Just for clarification, I have the same problem on two of my machines that are
> using Squid as an authenticated proxy. They crash every time they attempt to
> upload a result.
> Just to confirm the locality of the crash, if I take out:
>
> use_http_proxy
> use_http_auth
>
> From client_state.xml, it works fine.
>
> Cheers
>

hi!

having the very same problem :(
using BOINC 3.19 and SAH 3.08

the proxy authentification itself seems to work because if
i enter false credentials i get a
[...]HTTP_OP_SET::poll(): Proxy Authentication Failed
however, if the credentials are correct i get the error mentioned
above (only the write-to address differs).

help/debug is appreciated!

Best Bytes®,
Harry

Mike's solution (here) to use Python and APS appears to work (can't quite tell as the server's not responding since I tried it out yesterday), although we're not using MS ISA. I tried FreeProxy but that also caused the same error.

Mike's instructions are easy to follow and implement taking only a matter of moments.

At a linux bases proxy/firewall (HTTP and socks 5) I cannot upload, the BOINC client just quit. Any tips?

> Mike's solution (<a> href="http://setiboinc.ssl.berkeley.edu/sah/forum_thread.php?id=25">here[/url])
> to use Python and APS appears to work (can't quite tell as the server's not
> responding since I tried it out yesterday), although we're not using MS ISA.
> I tried FreeProxy but that also caused the same error.
>
> Mike's instructions are easy to follow and implement taking only a matter of
> moments.
>
>

It looks like it'll work for an NTLM or MS based proxy. Doesn't help for an authenticating proxy that does not use the MS protocols. At least I can't get it to work for the proxy I have to work with.

But maybe I can try modifying the python scripts to work with another type of proxy, problem is I don't know python that well.

I should add that with Mike's APS/Python solution, I have only got it working with APS/Python running on the same machine as each BOINC installation, logged on under Windows NT with an account that has authorised access to the proxy and with "Use Authentication" unchecked in BOINC.

> I should add that with Mike's APS/Python solution, I have only got it working
> with APS/Python running on the same machine as each BOINC installation, logged
> on under Windows NT with an account that has authorised access to the proxy
> and with "Use Authentication" unchecked in BOINC.
>
>

if you look in the server.cfg file for:

# Set to 1 if you want to grant this authorization service to clients from other computers.
# NOTE: all the users from other hosts that will be using you copy of APS for authentication
# will be using your credentials in NTLM auth at the remote host.
ALLOW_EXTERNAL_CLIENTS:0

# If you want to allow some other but not all computers to use your proxy for authorization,
# just set ALLOW_EXTERNAL_CLIENTS:0 and put friendly IP addresses here.
# Use space as a delimiter.
# NOTE that special addesses don't work here (192.168.3.0 for example).
FRIENDLY_IPS:


It should allow you to put in the IPs for other clients. It didn't work for my setup because the network I use doesn't use an NT domain authenticated proxy. Some other sort of proxy (not socks as far as I can tell)

Having the very same problem :(
Using BOINC 3.19 and SAH 3.08 and Squid

I will add that the proxy authentication code seems to be at fault as it works for me as well if I remove the name and password from the http_user_name and http_user_passwd lines from client_state.xml and set Squid to not require a password for the Seti hosts.

Cheers
Kevin

I am having the same problem with BOINC 3.20 and SAH 3.08

My computer is behind a firewall and I have to use it to get out into the internet.

Cheers
Edmund

Hi,
I use SAH3.08 on Boinc3.20 on WinNT4sp6a on a PIII 800MHz.
I'm behind a proxy authenticated firewall.
The error is very similar but the eception is at address 0x00401D98 writing to the same protected address 0x73614220. Maybe only the different link object relocate in 3.19->3.20
Simply the BOINgui_client crash after starting to upload the first unit done, leaving seti3.08 cruncher working on another unit.
In this situation if I start again BOINCgui it start another cruncher on the same unit, sharing 50% CPU ... other bug.

If I remove:
use_http_auth
from
client_state.xml
all work fine but no connection is possible.

> Mike's solution (<a> href="http://setiboinc.ssl.berkeley.edu/sah/forum_thread.php?id=25">here[/url])
> to use Python and APS appears to work (can't quite tell as the server's not
> responding since I tried it out yesterday), although we're not using MS ISA.
> I tried FreeProxy but that also caused the same error.
>
> Mike's instructions are easy to follow and implement taking only a matter of
> moments.
I cannot open the url of Mike's solution (whats wrong in message id=25 ?).
So I installed Proxomitron proxy for Win32, listen on port 8080, configure it to modify outgoing http headers, adding a MIME coded user:password, and so to authenticate to my proxy.
Then I configure SetiBoinc to use a localhost HTTP proxy with no authentication on port 8080.
It works great.

Hi efa,

>, configure it
> to modify outgoing http headers, adding a MIME coded user:password, and so to
> authenticate to my proxy.

Could you detail the MIME code you add ?

Thanks,

Miguel

> Could you detail the MIME code you add ?
Proxomitron Main Windows, Headers button,
Select row "Proxy-Authorization: Send password to proxy server",
activate In/Out Column, Edit button, fill this field:
HTTP Header: "Proxy-Authorization: Send password to proxy server" without "",
Replacement text: "basic user:password" (use your proxy account) without "".

Then select the text part "user:password", right click on it,
in context menu select MIME encode/decode, Encode string.
The user:pass become a string like: "cbhwegacwefwef=="
Press OK, OK
Enjoy
:-))

> Press OK, OK
> Enjoy

Thanks efa. It is working here too ! :^)

Miguel

Unfortunately i am not able to change any settings as i am on a corporate network which i dont have any access to :(

I guess will have to wait for them to provide a version that works with more firewalls/proxies etc

> Unfortunately i am not able to change any settings as i am on a corporate
> network which i dont have any access to :(
The settings are client side only. You dont need to administer the proxy server.
You only need to install Proxomitron on your workstation and configure it.

> I guess will have to wait for them to provide a version that works with more
> firewalls/proxies etc
Proxomitron supply only to the bad part of SetiBoinc: proxy authentication.
In the future you can remove proxomitron.

All you need is a proxy account to come out from your corporate network.
If you dont have this, you cannot use Boinc also if it in the future have correct authentication to proxy.

bye