In the past this sort of problem was caused when compression was turned on by the ISP, but not correctly recognised by the connected PC. Very frustrating to diagnose exactly where this is happening without full access to the intermediate server and router logs.

That sort of (lossy) compression is only used for image files - jpegs for the simple view slideshow, for example.

The log Siran showed us a week ago was for an ordinary MB WU data file: even if that was compressed (which this project doesn't do), it would be done with lossless compression (zip or gz), and should arrive intact.

If the errors are still the same as last week (I think we could do with a fresh example from the log), I still think opening the received file with a text editor might reveal some clues.

Very much doubt that will have any effect as the MD5 error you are seeing is suggestive of the file being corrupted somewhere between the SETI servers and you PC. As this problem does not appear to be affecting many people (you are the only one reporting it) I would be looking at the link between your ISP and your PCs.

In the past this sort of problem was caused when compression was turned on by the ISP, but not correctly recognised by the connected PC. Very frustrating to diagnose exactly where this is happening without full access to the intermediate server and router logs.

Greetings Rob,

Yeah, ain't that the truth. ;)

Our ISP is Mediacom and they are the only cable game in town. Their motto is: 'If there's something wrong, it's ALL on your end.' They never take credit for anything proved wrong on their end. Our only other options would be satellite or whatever the acronym is for the phone line, I forget anymore.

A few years ago, Mediacom swore up and down that a problem we were having was 'our equipment'. There was NO problem on their end. After 3 weeks or so a tech came out and lo and behold, the problem was the cable from the street to our house. The tech guy replaced the cable and our problem went away. So I guess you could say they were right and wrong. Right that it wasn't their equipment and wrong that it was ours.

Anyway, thanks for this. I doubt we could get through to Mediacom to found out anything about changes. :|

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

In the past this sort of problem was caused when compression was turned on by the ISP, but not correctly recognised by the connected PC. Very frustrating to diagnose exactly where this is happening without full access to the intermediate server and router logs.

That sort of (lossy) compression is only used for image files - jpegs for the simple view slideshow, for example.

The log Siran showed us a week ago was for an ordinary MB WU data file: even if that was compressed (which this project doesn't do), it would be done with lossless compression (zip or gz), and should arrive intact.

If the errors are still the same as last week (I think we could do with a fresh example from the log), I still think opening the received file with a text editor might reveal some clues.

Greetings Richard,

I looked for the newest file that had an error when you mentioned this and the file was gone. I don't think they stick around for any length of time. I will see if any from today are on my PC.

Keep on BOINCing...! :)
[edit] I just got another error and looked. The file is not on my PC. I've no clue what else to do. [/edit]
[edit2] By the way, my PC is not the only one getting the MD5 errors. The other half's PC does too. [/edit2]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

[edit2] By the way, my PC is not the only one getting the MD5 errors. The other half's PC does too. [/edit2]

Is this when it is connected using the same physical connection as you are?

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Greetings Richard,

I looked for the newest file that had an error when you mentioned this and the file was gone. I don't think they stick around for any length of time. I will see if any from today are on my PC.

I was discussing your problem during last week with a colleague, and we referred back to a post I wrote some years ago at another project:

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/forum_thread.php?id=7110&nowrap=true#41681

Since I wrote "... both copies had an MD5 of ...", I'm pretty sure that the file will be stored on your hard disk - but it will be deleted when BOINC reports the error back to the server, so you may only have five minutes to intercept it and make a safe copy somewhere.

I saw your most recent error at result 4425352904, again with an MD5 error for the WU data file 23ap11ab.16071.7189.438086664195.12.20

I downloaded a copy of that file, and got an MD5 of 95d682d493a37bcd44d2da298687fd69 - is that what's shown in your log?

To give you an idea what to expect, the file itself starts

<workunit>
<workunit_header>
  <name>23ap11ab.16071.7189.438086664195.12.20</name>
  <group_info>
    <tape_info>
      <name>23ap11ab</name>
      <start_time>2455674.7489223</start_time>
      <last_block_time>2455674.7489223</last_block_time>
      <last_block_done>7189</last_block_done>
      <missed>0</missed>
      <tape_quality>0</tape_quality>
      <beam>0</beam>
    </tape_info>
    <name>23ap11ab.16071.7189.3.12</name>
    <data_desc>
      <start_ra>15.585970798341</start_ra>
      <start_dec>0.073901325222965</start_dec>
      <end_ra>15.615669439571</end_ra>
      <end_dec>2.7650063333102</end_dec>
      <true_angle_range>2.7277199009677</true_angle_range>

- it's easier to read if you open it with WordPad.

hmm i'm not getting any gpu tasks on ati nor nvidia o.0

anyone a clue?

10/4/2015 2:40:25 PM | SETI@home | Sending scheduler request: To fetch work.
10/4/2015 2:40:25 PM | SETI@home | Requesting new tasks for NVIDIA GPU
10/4/2015 2:40:26 PM | SETI@home | Scheduler request completed: got 0 new tasks
10/4/2015 2:40:26 PM | SETI@home | Project has no tasks available

---

I came down with a bad case of i don't give a crap

hmm i'm not getting any gpu tasks on ati nor nvidia o.0

anyone a clue?

10/4/2015 2:40:25 PM | SETI@home | Sending scheduler request: To fetch work.
10/4/2015 2:40:25 PM | SETI@home | Requesting new tasks for NVIDIA GPU
10/4/2015 2:40:26 PM | SETI@home | Scheduler request completed: got 0 new tasks
10/4/2015 2:40:26 PM | SETI@home | Project has no tasks available

Could it be related to the RTS buffer being empty, or maybe it's just VLARS coming down the pipe at the moment, that might explain the lack og gpu tasks.

P.

---

hmm i'm not getting any gpu tasks on ati nor nvidia o.0

anyone a clue?

10/4/2015 2:40:25 PM | SETI@home | Sending scheduler request: To fetch work.
10/4/2015 2:40:25 PM | SETI@home | Requesting new tasks for NVIDIA GPU
10/4/2015 2:40:26 PM | SETI@home | Scheduler request completed: got 0 new tasks
10/4/2015 2:40:26 PM | SETI@home | Project has no tasks available

Could it be related to the RTS buffer being empty, or maybe it's just VLARS coming down the pipe at the moment, that might explain the lack og gpu tasks.

P.

ah only vlar's huh that would explain why i only have vlar haha

---

I came down with a bad case of i don't give a crap

[edit2] By the way, my PC is not the only one getting the MD5 errors. The other half's PC does too. [/edit2]

Is this when it is connected using the same physical connection as you are?

Greetings Rob,

Yes, we are on the same connection.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings Richard,

I looked for the newest file that had an error when you mentioned this and the file was gone. I don't think they stick around for any length of time. I will see if any from today are on my PC.

I was discussing your problem during last week with a colleague, and we referred back to a post I wrote some years ago at another project:

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/forum_thread.php?id=7110&nowrap=true#41681

Since I wrote "... both copies had an MD5 of ...", I'm pretty sure that the file will be stored on your hard disk - but it will be deleted when BOINC reports the error back to the server, so you may only have five minutes to intercept it and make a safe copy somewhere.

I saw your most recent error at result 4425352904, again with an MD5 error for the WU data file 23ap11ab.16071.7189.438086664195.12.20

I downloaded a copy of that file, and got an MD5 of 95d682d493a37bcd44d2da298687fd69 - is that what's shown in your log?

To give you an idea what to expect, the file itself starts

<workunit>
<workunit_header>
  <name>23ap11ab.16071.7189.438086664195.12.20</name>
  <group_info>
    <tape_info>
      <name>23ap11ab</name>
      <start_time>2455674.7489223</start_time>
      <last_block_time>2455674.7489223</last_block_time>
      <last_block_done>7189</last_block_done>
      <missed>0</missed>
      <tape_quality>0</tape_quality>
      <beam>0</beam>
    </tape_info>
    <name>23ap11ab.16071.7189.3.12</name>
    <data_desc>
      <start_ra>15.585970798341</start_ra>
      <start_dec>0.073901325222965</start_dec>
      <end_ra>15.615669439571</end_ra>
      <end_dec>2.7650063333102</end_dec>
      <true_angle_range>2.7277199009677</true_angle_range>

- it's easier to read if you open it with WordPad.

Greetings Richard,

I do believe you are correct. This was what I found in the log:

10/4/2015 11:54:49 AM | SETI@home | [error] MD5 check failed for 23ap11ab.16071.7189.438086664195.12.20
10/4/2015 11:54:49 AM | SETI@home | [error] expected 95d682d493a37bcd44d2da298687fd69, got bebd84ab6830924294f0d44161e4d178
10/4/2015 11:54:49 AM | SETI@home | [error] Checksum or signature error for 23ap11ab.16071.7189.438086664195.12.20

Hope this helps. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If your cable modem is owned by your ISP, just tell them you want a replacement.

---

If your cable modem is owned by your ISP, just tell them you want a replacement.

Cable modem is owned by us. It's not much more than a year old.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I downloaded a copy of that file, and got an MD5 of 95d682d493a37bcd44d2da298687fd69 - is that what's shown in your log?

Greetings Richard,

I do believe you are correct. This was what I found in the log:

10/4/2015 11:54:49 AM | SETI@home | [error] MD5 check failed for 23ap11ab.16071.7189.438086664195.12.20
10/4/2015 11:54:49 AM | SETI@home | [error] expected 95d682d493a37bcd44d2da298687fd69, got bebd84ab6830924294f0d44161e4d178
10/4/2015 11:54:49 AM | SETI@home | [error] Checksum or signature error for 23ap11ab.16071.7189.438086664195.12.20

Hope this helps. :)

Keep on BOINCing...! :)

Yup, we seem to be on course. The file exists on the server, and arrives in one piece, with the expected MD5, when it downloads to my machine.

The file on your machine has a different MD5, so it must be a different file in some way. The next step is to catch one in the act, and see in what way it's different. You probably have to catch it during the five minutes before it could possibly be deleted: but don't delay too long in telling us about it, because they can be deleted from the server in not much more than 24 hours. Once we have a matched pair - your download and somebody else's download - we can compare them and see that's going wrong.

Maybe the Anti-Virus/Anti-Malware programs are interfering with the proper download of the file(s).... on those PC's???

You should have DISABLED Scanning (including Real-Time) of ALL BOINC Directories/Folders by your Anti-Virus programs.

---

I downloaded a copy of that file, and got an MD5 of 95d682d493a37bcd44d2da298687fd69 - is that what's shown in your log?

Greetings Richard,

I do believe you are correct. This was what I found in the log:

10/4/2015 11:54:49 AM | SETI@home | [error] MD5 check failed for 23ap11ab.16071.7189.438086664195.12.20
10/4/2015 11:54:49 AM | SETI@home | [error] expected 95d682d493a37bcd44d2da298687fd69, got bebd84ab6830924294f0d44161e4d178
10/4/2015 11:54:49 AM | SETI@home | [error] Checksum or signature error for 23ap11ab.16071.7189.438086664195.12.20

Hope this helps. :)

Keep on BOINCing...! :)

Yup, we seem to be on course. The file exists on the server, and arrives in one piece, with the expected MD5, when it downloads to my machine.

The file on your machine has a different MD5, so it must be a different file in some way. The next step is to catch one in the act, and see in what way it's different. You probably have to catch it during the five minutes before it could possibly be deleted: but don't delay too long in telling us about it, because they can be deleted from the server in not much more than 24 hours. Once we have a matched pair - your download and somebody else's download - we can compare them and see that's going wrong.

Greetings Richard,

THAT is going to be easier said than done. That would pretty much require me to sit and stare at my event log waiting for it to happen. But! I will endeavor to try to catch 'one in the act' just to get this issue resolved. :)

Someone mentioned that a running AV or other security program may be the culprit. I doubt that since this did not start until after I upgraded to Window$ 10 and then did the roll back to Win7 Pro 64bit. Before Window$ 10 I never once saw this error and I have been checking my account for errors several times a day for a very long time, like years.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Are you computers plugged into the cable modem or your wireless router?

If you can get direct off your modem you can eliminate one piece of the puzzle/

---

If two machines are affected and they don't have an identical setup, then it rather points to a transmission problem than a problem with the computer.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

If two machines are affected and they don't have an identical setup, then it rather points to a transmission problem than a problem with the computer.

Since it doesn't seem to be a widespread problem, perhaps a 'reception' problem - what's received by your particular modem/router, rather than what's transmitted by the project.

I have seen cases where routers produce a very pretty graphical error page when something goes wrong - which is helpful if you're sitting at a browser and can read it, unhelpful if it's handed to a program like BOINC. BOINC ignores very small files if received in error, which weeds out most text-based error messages, but the graphical ones can be big enough to be mis-intepreted as data.

That might explain why both machines get occasional errors, but it's hard to see that a problem like that would start because of the upgrade to Windows 10 and subsequent reversions. Was that done on your other half's machine too?

Thinking ... Some modems will let you into their interface but going to
http://home

If it lets you in, you can see the error count.

---

if it's comcast it's 192.168.100.1

---

I came down with a bad case of i don't give a crap