Check your firewall and/or proxy. The http errors are mostly caused by BOINC being blocked by the firewall. Check that nothing changed in that direction.
I am getting this error . (temporarily failed upload http error). .any help ? For 3 weeks I have had this problem.
I could solve that problem by switching from htt protocol version 1.1 to version 1.0.
To do so, you must create a text file named cc_config.xml in your BOINC data directory (if it doesn't exist already). The data directory is mentioned in the message tab of BOINC manager (the default is C:\\program files\\BOINC).
With notepad or a similar editor, enter (copy&paste) the following into that file:
1
There are no lower case 'L' characters in that code, only digits '1'. More information to cc_config you can find here.
In BOINC Manager (Advanced view) select menu 'Advanced->Read config file' to activate the new configuration.
Hope that helps.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I did both of those suggestions already and still the same error. I can download work just fine, sending the completed work back is the problem.
Then you should probably turn on some debugging output. The problem is that I can tell you how to do so, but am unable to analyze the result. :-(
But perhaps some other people can help you, if you paste some of the messages here.
You'd have to change your cc_config.xml to look similar to this (since it didn't work, I think you can discard the part):
1
Perhaps some of the following options could be helpful too:
Show completion status of file transfers.
Debugging information about HTTP operations.
Debugging information about network communication.
Debugging information about HTTP proxy operations.
The output with those log flags can get quite lengthy, so you should turn them off again after you got some error messages. You can also find them in the file stdoutdae.txt.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Seti works fine both download and upload. I can download work from Einstein but not upload work to Einstein. It uploads a large portion ie. 69.43% then stops, one even gets to 100% ??????
Is this at work that has URL filter in the proxy server? I have the same problem at work is due to the fact that the upload URL has recently been added to the list of banned URLs. It could just be by chance, but it was at about the same time you started experiencing problems. For some reason the download site is not block and still accessable.
...And if it's not the URL itself that is blocked, there might be a size limit. The Einstein@Home results files that are upload via BOINC as HTTP "post" requests are approx 75-80kB in size, far more than what you would usually see in "normal" web-browsing (when filling out HTML forms etc). So in a way this is "unusual" http traffic.
In an attempt to limit "subliminal" channels around corporate firewalls, some web proxies might be configured to limit the size of HTTP request bodies.
Mine seems to have started when MS released that patch on Update Tuesday and things got pooched with ZoneAlarm. It's now showing in Boinc Manager that my local host is (5.10.45) when it used to be 127.0.0.1.
What's weird is that I have 3 systems here and 2 don't seem to have the problem but one does. Then suddenly it works for a while and then goes on the fritz again.
Checking my local host file in Windows XP Pro it shows my localhost address as 127.0.0.1. You can't change it to the (5.10.45) because it is not a valid address needs to have xxx.xxx.xxx.xxx I think and I don't know how to get around this. I can connect to the internet fine in all other programs. Only Boinc seems to have this problem.
It's now showing in Boinc Manager that my local host is (5.10.45) when it used to be 127.0.0.1.
What it shows in BOINC Manager is "Connected to localhost (5.10.45)". This does NOT mean that the loopback address isn't 127.0.0.1 (which it most assuredly is). It simply means that BOINC Manager is connected to the local host (and not some remote host) and that the version of BOINC running there is 5.10.45. This is nothing to do with any IP address.
Quote:
What's weird is that I have 3 systems here and 2 don't seem to have the problem but one does. Then suddenly it works for a while and then goes on the fritz again.
You probably haven't observed things for long enough to form a fully accurate picture. All machines do have occasional hiccups in negotiating connections from time to time, probably due to congested networks and congested servers. BOINC is designed to cope with any flakiness by retrying until successful. Do you have any examples of retries not succeeding in the longer term?
Quote:
Checking my local host file in Windows XP Pro it shows my localhost address as 127.0.0.1. You can't change it to the (5.10.45) because it is not a valid address needs to have xxx.xxx.xxx.xxx I think and I don't know how to get around this.
Please leave well enough alone :-) You shouldn't be trying to "fix" something that's probably not broken. Why are you trying to change the standard loopback address 127.0.0.1 into the BOINC version number?? :-).
What it shows in BOINC Manager is "Connected to localhost (5.10.45)". This does NOT mean that the loopback address isn't 127.0.0.1 (which it most assuredly is). It simply means that BOINC Manager is connected to the local host (and not some remote host) and that the version of BOINC running there is 5.10.45. This is nothing to do with any IP address.
Now that you mention it it makes sense on the version #. I was just so used to seening the loopback address and then suddenly its changed. (senior moment on my part)
Quote:
You probably haven't observed things for long enough to form a fully accurate picture. All machines do have occasional hiccups in negotiating connections from time to time, probably due to congested networks and congested servers. BOINC is designed to cope with any flakiness by retrying until successful. Do you have any examples of retries not succeeding in the longer term?
Actually I've been watching this system like a hawk. I've been trouble shooting various components in this system for weeks now and have had to RMA both a processor and motherboard. If you look Here you'll see some of the reasons for my watching over this system. I've seen these same error messages for a few days and I was just concerned that I had something else going on here. I was looking on the board here to see if anyone else was having the same problem. You're right though after the 4th try (automatic) it succeeded.
Quote:
Please leave well enough alone :-) You shouldn't be trying to "fix" something that's probably not broken. Why are you trying to change the standard loopback address 127.0.0.1 into the BOINC version number?? :-).
temporarily failed upload . . http error
)
Check your firewall and/or proxy. The http errors are mostly caused by BOINC being blocked by the firewall. Check that nothing changed in that direction.
RE: I am getting this error
)
I could solve that problem by switching from htt protocol version 1.1 to version 1.0.
To do so, you must create a text file named cc_config.xml in your BOINC data directory (if it doesn't exist already). The data directory is mentioned in the message tab of BOINC manager (the default is C:\\program files\\BOINC).
With notepad or a similar editor, enter (copy&paste) the following into that file:
1
There are no lower case 'L' characters in that code, only digits '1'. More information to cc_config you can find here.
In BOINC Manager (Advanced view) select menu 'Advanced->Read config file' to activate the new configuration.
Hope that helps.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
I did both of those
)
I did both of those suggestions already and still the same error. I can download work just fine, sending the completed work back is the problem.
RE: I did both of those
)
Then you should probably turn on some debugging output. The problem is that I can tell you how to do so, but am unable to analyze the result. :-(
But perhaps some other people can help you, if you paste some of the messages here.
You'd have to change your cc_config.xml to look similar to this (since it didn't work, I think you can discard the part):
1Perhaps some of the following options could be helpful too:
Show completion status of file transfers.
Debugging information about HTTP operations.
Debugging information about network communication.
Debugging information about HTTP proxy operations.
The output with those log flags can get quite lengthy, so you should turn them off again after you got some error messages. You can also find them in the file stdoutdae.txt.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Seti works fine both download
)
Seti works fine both download and upload. I can download work from Einstein but not upload work to Einstein. It uploads a large portion ie. 69.43% then stops, one even gets to 100% ??????
Is this at work that has URL
)
Is this at work that has URL filter in the proxy server? I have the same problem at work is due to the fact that the upload URL has recently been added to the list of banned URLs. It could just be by chance, but it was at about the same time you started experiencing problems. For some reason the download site is not block and still accessable.
One quick way to test this is to try access http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/file_upload_handler though a browser, if you receive some sort of 'access denied' error then it is likely the site is blocked:-(
Hope this helps.
Peter
Hi! ...And if it's not the
)
Hi!
...And if it's not the URL itself that is blocked, there might be a size limit. The Einstein@Home results files that are upload via BOINC as HTTP "post" requests are approx 75-80kB in size, far more than what you would usually see in "normal" web-browsing (when filling out HTML forms etc). So in a way this is "unusual" http traffic.
In an attempt to limit "subliminal" channels around corporate firewalls, some web proxies might be configured to limit the size of HTTP request bodies.
CU
Bikeman
I've been getting this error
)
I've been getting this error as well...
Mine seems to have started when MS released that patch on Update Tuesday and things got pooched with ZoneAlarm. It's now showing in Boinc Manager that my local host is (5.10.45) when it used to be 127.0.0.1.
What's weird is that I have 3 systems here and 2 don't seem to have the problem but one does. Then suddenly it works for a while and then goes on the fritz again.
Checking my local host file in Windows XP Pro it shows my localhost address as 127.0.0.1. You can't change it to the (5.10.45) because it is not a valid address needs to have xxx.xxx.xxx.xxx I think and I don't know how to get around this. I can connect to the internet fine in all other programs. Only Boinc seems to have this problem.
RE: It's now showing in
)
What it shows in BOINC Manager is "Connected to localhost (5.10.45)". This does NOT mean that the loopback address isn't 127.0.0.1 (which it most assuredly is). It simply means that BOINC Manager is connected to the local host (and not some remote host) and that the version of BOINC running there is 5.10.45. This is nothing to do with any IP address.
You probably haven't observed things for long enough to form a fully accurate picture. All machines do have occasional hiccups in negotiating connections from time to time, probably due to congested networks and congested servers. BOINC is designed to cope with any flakiness by retrying until successful. Do you have any examples of retries not succeeding in the longer term?
Please leave well enough alone :-) You shouldn't be trying to "fix" something that's probably not broken. Why are you trying to change the standard loopback address 127.0.0.1 into the BOINC version number?? :-).
Cheers,
Gary.
RE: What it shows in BOINC
)
Now that you mention it it makes sense on the version #. I was just so used to seening the loopback address and then suddenly its changed. (senior moment on my part)
Actually I've been watching this system like a hawk. I've been trouble shooting various components in this system for weeks now and have had to RMA both a processor and motherboard. If you look Here you'll see some of the reasons for my watching over this system. I've seen these same error messages for a few days and I was just concerned that I had something else going on here. I was looking on the board here to see if anyone else was having the same problem. You're right though after the 4th try (automatic) it succeeded.
Senior moment I suppose.... :-)