Message boards :
Number crunching :
Upload and Reporting issues on Windows 8.2 and BOINC 7.4.36
Message board moderation
Author | Message |
---|---|
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
Since I upgraded to BOINC 7.4.36, when a work unit finishes, it will not upload and report as it had in the prior version. But, if I reboot the computer, BOINC will do what it has to do, almost. I say that because having just rebooted, a number of units uploaded and reported, but two which had been stuck before the reboot are still stuck. This impacts my regular and GPU work units. My older computer running Windows Vista and same BOINC version 7.4.36 is working flawlessly. So, it may be this version of BOINC with Windows 8? But it doesn't seem possible I would be the only one with Windows 8, so I am at a loss as to what is causing it. |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
I guess it must just be my issue then. I suppose I will re-install the new BOINC, and if that does not work, see if I can re do the older version. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
When you say it won't upload and report, how long have you waited and observed this behavior? I believe that uploading and reporting happens in two different stages; one immediately and one within 24 hours. I am using Windows 8.1 Update (there is no Windows 8.2 that I'm aware of), and I use the latest BOINC and have not observed the same behavior you describe. |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
My bad. I thought someone had told me in the store when I got computer a few months ago that I had 8.2. It is in fact 8.1 as you say. I understand the two stage process to upload and report. After I had upgraded the version of BOINC, the next three GPU units completed stayed in attempting upload mode for around three days. When I saw a regular completed work unit also stall in upload, I rebooted computer, and they then went on uploading successfully and reporting as well. Since then, two more GPU units have completed and neither of them wants to upload even if I do reboot. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
My bad. I thought someone had told me in the store when I got computer a few months ago that I had 8.2. It is in fact 8.1 as you say. No worries. Microsoft's brilliant marketing department decided to call it Windows 8.1 Update rather than incrementing the version to 8.2, though Windows 8.2 would be easier to say. I understand the two stage process to upload and report. After I had upgraded the version of BOINC, the next three GPU units completed stayed in attempting upload mode for around three days. When I saw a regular completed work unit also stall in upload, I rebooted computer, and they then went on uploading successfully and reporting as well. That sounds like it could have been a cached DNS entry, and rebooting is the hard way of flushing the cache. You could also try typing at the command line: IPCONFIG /FLUSHDNS (capitol letters not necessary, I use them to indicate a command to be typed). Since then, two more GPU units have completed and neither of them wants to upload even if I do reboot. Hmm. I'd suggest pinging the upload server to see if you can get a connection, but I don't happen to have the FQDN or the IP at the moment. Perhaps someone else might have it handy? |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
Thanks for suggestions. Odd that all was good before going to new BOINC version. Something must be different elsewhere that I was not aware had changed. |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
It is not BOINC. I went back to earlier version and the same upload issue persists. I have turned off getting new work units for this computer. If I cant get the finished work units to upload, is it possible to move them to my Windows Vista computer which seem to upload OK, and upload them from there? |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13731 Credit: 208,696,464 RAC: 304 |
What Antivirus/Anti spyware software are you running? Try disabling it & then see if the work uploads. They can cause issues with uploads & downloads if they consider the activity suspicious. Grant Darwin NT |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
Good idea to disable anti virus and spyware. But that did not help. I have malwarebytes and comodo internet security pro. The same two are installed on my other computer with no issues. I disabled them one at a time, and still the files will not upload. (now three) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
When you say it won't upload and report, how long have you waited and observed this behavior? I believe that uploading and reporting happens in two different stages; one immediately and one within 24 hours. Just to bring you up to speed: uploading still happens immediately, but since BOINC v7.2.36, reporting happens at most one hour after the task(s) became 'Ready to report' (i.e. uploading completed). client: report tasks within 1 hour of completion... instead of 24. Better user experience at the expense of slightly increased server load. |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
OK, I have aborted my final two work units before they got too far. I now have six completed work units that are stuck trying to upload. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
What error message are you getting? Can you post the errors here from the Event Log? |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
1/17/2015 2:40:00 PM | | cc_config.xml not found - using defaults 1/17/2015 2:40:00 PM | | Starting BOINC client version 7.4.36 for windows_x86_64 1/17/2015 2:40:00 PM | | log flags: file_xfer, sched_ops, task 1/17/2015 2:40:00 PM | | Libraries: libcurl/7.39.0 OpenSSL/1.0.1j zlib/1.2.8 1/17/2015 2:40:00 PM | | Data directory: C:\ProgramData\BOINC 1/17/2015 2:40:00 PM | | Running under account richard 1/17/2015 2:40:00 PM | | OpenCL: Intel GPU 0: Intel(R) HD Graphics (driver version 10.18.10.3412, device version OpenCL 1.2, 1784MB, 1784MB available, 32 GFLOPS peak) 1/17/2015 2:40:00 PM | | OpenCL CPU: Intel(R) Pentium(R) 3558U @ 1.70GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413)) 1/17/2015 2:40:00 PM | | Host name: rwaltonlaptop 1/17/2015 2:40:00 PM | | Processor: 2 GenuineIntel Intel(R) Pentium(R) 3558U @ 1.70GHz [Family 6 Model 69 Stepping 1] 1/17/2015 2:40:00 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 movebe popcnt rdrandsyscall nx lm vmx tm2 pbe fsgsbase 1/17/2015 2:40:00 PM | | OS: Microsoft Windows 8.1: Core x64 Edition, (06.03.9600.00) 1/17/2015 2:40:00 PM | | Memory: 3.91 GB physical, 4.91 GB virtual 1/17/2015 2:40:00 PM | | Disk: 455.06 GB total, 420.14 GB free 1/17/2015 2:40:00 PM | | Local time is UTC -8 hours 1/17/2015 2:40:00 PM | climateprediction.net | URL http://climateprediction.net/; Computer ID not assigned yet; resource share 100 1/17/2015 2:40:00 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7409774; resource share 100 1/17/2015 2:40:00 PM | SETI@home | General prefs: from SETI@home (last modified 25-Nov-2014 15:08:53) 1/17/2015 2:40:00 PM | SETI@home | Computer location: home 1/17/2015 2:40:00 PM | SETI@home | General prefs: no separate prefs for home; using your defaults 1/17/2015 2:40:00 PM | | Reading preferences override file 1/17/2015 2:40:00 PM | | Preferences: 1/17/2015 2:40:00 PM | | max memory usage when active: 2004.01MB 1/17/2015 2:40:00 PM | | max memory usage when idle: 3607.22MB 1/17/2015 2:40:00 PM | | max disk usage: 100.00GB 1/17/2015 2:40:00 PM | | (to change preferences, visit a project web site or select Preferences in the Manager) 1/17/2015 2:40:00 PM | | Not using a proxy 1/17/2015 2:40:02 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 2:40:02 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 2:40:02 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 2:40:04 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 2:40:09 PM | climateprediction.net | Sending scheduler request: To fetch work. 1/17/2015 2:40:09 PM | climateprediction.net | Requesting new tasks for CPU and Intel GPU 1/17/2015 2:40:12 PM | climateprediction.net | Scheduler request failed: Error 417 1/17/2015 2:40:23 PM | SETI@home | Started upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 2:40:27 PM | SETI@home | Backing off 05:08:30 on upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 2:48:25 PM | SETI@home | Started upload of 27ja13ag.1291.4975.438086664203.12.63_1_0 1/17/2015 2:48:25 PM | SETI@home | Started upload of 26jl12aa.1254.5384.438086664203.12.180_1_0 1/17/2015 2:48:28 PM | climateprediction.net | Sending scheduler request: To fetch work. 1/17/2015 2:48:28 PM | climateprediction.net | Requesting new tasks for CPU and Intel GPU 1/17/2015 2:48:30 PM | SETI@home | Backing off 03:44:56 on upload of 27ja13ag.1291.4975.438086664203.12.63_1_0 1/17/2015 2:48:30 PM | SETI@home | Backing off 03:18:04 on upload of 26jl12aa.1254.5384.438086664203.12.180_1_0 1/17/2015 2:48:30 PM | climateprediction.net | Scheduler request failed: Error 417 1/17/2015 2:48:35 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 2:48:35 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 2:48:35 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 2:48:38 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 2:48:40 PM | | Re-reading cc_config.xml 1/17/2015 2:48:40 PM | | cc_config.xml not found - using defaults 1/17/2015 2:48:40 PM | | log flags: file_xfer, sched_ops, task 1/17/2015 2:48:45 PM | SETI@home | General prefs: from SETI@home (last modified 25-Nov-2014 15:08:53) 1/17/2015 2:48:45 PM | SETI@home | Computer location: home 1/17/2015 2:48:45 PM | SETI@home | General prefs: no separate prefs for home; using your defaults 1/17/2015 2:48:45 PM | | Reading preferences override file 1/17/2015 2:48:45 PM | | Preferences: 1/17/2015 2:48:45 PM | | max memory usage when active: 2004.01MB 1/17/2015 2:48:45 PM | | max memory usage when idle: 3607.22MB 1/17/2015 2:48:45 PM | | max disk usage: 100.00GB 1/17/2015 2:48:45 PM | | (to change preferences, visit a project web site or select Preferences in the Manager) 1/17/2015 2:48:58 PM | SETI@home | Started upload of 26ja13ac.27945.10292.438086664204.12.8_1_0 1/17/2015 2:48:58 PM | SETI@home | Started upload of 01jl12ad.31815.400013.438086664207.12.230_1_0 1/17/2015 2:49:02 PM | SETI@home | Backing off 04:07:19 on upload of 26ja13ac.27945.10292.438086664204.12.8_1_0 1/17/2015 2:49:03 PM | SETI@home | Backing off 03:06:58 on upload of 01jl12ad.31815.400013.438086664207.12.230_1_0 1/17/2015 2:49:03 PM | SETI@home | Started upload of 08se12ae.10899.11519.438086664201.12.69_1_0 1/17/2015 2:49:03 PM | SETI@home | Started upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 2:49:06 PM | SETI@home | Backing off 04:04:58 on upload of 08se12ae.10899.11519.438086664201.12.69_1_0 1/17/2015 2:49:06 PM | SETI@home | Backing off 04:57:37 on upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 2:50:39 PM | SETI@home | Fetching scheduler list 1/17/2015 2:50:40 PM | SETI@home | Master file download succeeded 1/17/2015 2:50:45 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 2:50:45 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 2:50:45 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 2:50:47 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 2:52:48 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 2:52:48 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 2:52:48 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 2:52:51 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 2:54:00 PM | climateprediction.net | update requested by user 1/17/2015 2:54:01 PM | climateprediction.net | Sending scheduler request: Requested by user. 1/17/2015 2:54:01 PM | climateprediction.net | Requesting new tasks for CPU and Intel GPU 1/17/2015 2:54:04 PM | climateprediction.net | Scheduler request failed: Error 417 1/17/2015 2:54:35 PM | | Windows is suspending operations 1/17/2015 2:54:35 PM | | Suspending computation - requested by operating system 1/17/2015 2:54:35 PM | | Suspending network activity - requested by operating system 1/17/2015 2:54:47 PM | | Resuming after OS suspension 1/17/2015 3:07:28 PM | | Resuming computation 1/17/2015 3:07:28 PM | | Resuming network activity 1/17/2015 3:07:29 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 3:07:29 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 3:07:29 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 3:07:30 PM | | Windows is resuming operations 1/17/2015 3:07:31 PM | SETI@home | Scheduler request failed: Couldn't resolve host name 1/17/2015 3:07:58 PM | | Project communication failed: attempting access to reference site 1/17/2015 3:08:00 PM | | Internet access OK - project servers may be temporarily down. 1/17/2015 3:14:08 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 3:14:08 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 3:14:08 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 3:14:11 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 3:22:48 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 3:22:48 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 3:22:48 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 3:22:51 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 3:25:36 PM | SETI@home | Started upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 3:25:39 PM | SETI@home | Backing off 04:12:06 on upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 3:51:58 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 3:51:58 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 3:51:58 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 3:52:00 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 4:30:58 PM | SETI@home | Sending scheduler request: To report completed tasks. 1/17/2015 4:30:58 PM | SETI@home | Reporting 2 completed tasks 1/17/2015 4:30:58 PM | SETI@home | Not requesting tasks: "no new tasks" requested via Manager 1/17/2015 4:31:00 PM | SETI@home | Scheduler request failed: Error 417 1/17/2015 5:37:59 PM | SETI@home | Started upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 1/17/2015 5:38:04 PM | SETI@home | Backing off 03:11:14 on upload of 01jl12ad.31815.400013.438086664207.12.232_0_0 |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
HTTP error 417 is your problem. Snagged this from a Google search: Ageless wrote: Ah, the infamous error 417. This is a HTTP error. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13731 Credit: 208,696,464 RAC: 304 |
Upload & Scheduler failures occur within a couple of seconds. If Ozzfan's suggestion works, well & good although if things were working before it's a work around for whatever the actual issue is, particularly if things were working before. Had you recently updated your AV or Anti-spyware programmes? I've had cases where the damaged they've caused can only be fixed by uninstalling them- disabling them doesn't sort it out- Comodo's firewall being one of those offenders. Are you using the Windows firewall or a 3rd party (Comodo internet security- does that product have one?) Grant Darwin NT |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
Thanks for possible work around. Computer is off for now. I will try fix tomorrow. I am not aware that comodo Internet security had an update at this time. I do use this as a firewall though, and have all along on this computer. It is also used in the other computer that still works. But I suppose there are differences in how the Vista and windows 8 versions do things. |
Richard Walton Send message Joined: 21 May 99 Posts: 87 Credit: 192,735 RAC: 0 |
Provided I did this correctly, it did not work. But somehow before I tried, 3 of my 6 completed stalled uploads did finally go away. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13731 Credit: 208,696,464 RAC: 304 |
Provided I did this correctly, it did not work. Uninstalling both security programmes? Grant Darwin NT |
JanniCash Send message Joined: 17 Nov 03 Posts: 57 Credit: 1,276,920 RAC: 0 |
WARNING: This post may contain nuts! HTTP response code 417 means that the "server" cannot satisfy the request's Expect: header. Obviously the actual S@H scheduler/download/upload servers can satisfy that header when contacted directly by Boinc Clients, so something else must be going on if you get this error all the time. I got this error with Boinc and used the cc_config-http_1_0 fix until I found out that setting "ignore_expect_100 on" in my squid configuration will work and fix a few other clients, that are just as broken as the Boinc Client. The "Expect: 100-continue" header is an HTTP/1.1 protocol feature for doing a POST request (like for uploading a result). The specifics are explained in RFC 2616 section 8.2.3. In short: this is nuts. In not so short: when sending a POST request, an HTTP/1.1 client should send that header, then wait some time for the server to respond, but send the form data anyway if it didn't get a response from the server within the timeout (the timeout is defined in the RFC). The server may omit the 100-continue response if it gets form data before deciding how to respond, but ... you see, there is a lot of asynchronous IO and timing going on here. The client and server are both supposed to "listen" while "sending". I've been doing network programming for 30+ years now and have reassembled TCP streams using libnids for the purpose of replaying client traffic from pcap files produce by tcpdump (HTTP as well as other stuff). I do NOT expect an average application developer to get this "Expect: 100-continue" stuff right on first try! </HTTP_1_1_RANT> I believe in the S@H-Boinc case you can only get this error if you are behind some form of proxy server, like I am. My firewall is running PF (packet filter) on FreeBSD. All port 80 traffic from the internal home network is redirected to a squid server. I do this in addition to disabling the yum plugin fastestmirror so that not all of my 10+ CentOS VMs download their own copy of each and every RPM when updating. It does reduce bandwidth, but it does also create some problems, like this 417 in case the proxy server cannot transparently satisfy the Expect: request. My guess is that either your network admin (if at work) or your ISP may be running a similar, transparent proxy configuration to reduce the overall bandwidth. They may not be willing to enable the ignore_expect_100 "hack", because it is actually a HTTP/1.1 protocol violation. So you may politely ask them to enable that proxy feature, but be prepared to get nothing but an odd facial expression in return. If that much. HTTP/1.0 does not have that protocol feature, which is why downgrading the client to use HTTP/1.0 via the cc_config.xml file solves this issue. Note that whenever you change Boinc Client configuration files, you need to have the client re-read them (Boinc-Manager Menu->Advanced->Read_config_files). Just hitting "Update" for the project will not have that effect. Hope this helps (at least in understanding the problem). |
atlov Send message Joined: 11 Aug 12 Posts: 35 Credit: 32,718,664 RAC: 34 |
Speaking about http headers, maybe Verizon's supercookie is responsibe? |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.