Hey all, I think about to get the Beta Version. Question: Since the automatic download of this .pdb file is not working in the current version, should I take it manually to my Laptop? Of course I hope there will be no problems, but just in case, you know?
Happy crunching, Christoph
Hey all, I think about to get the Beta Version. Question: Since the automatic download of this .pdb file is not working in the current version, should I take it manually to my Laptop? Of course I hope there will be no problems, but just in case, you know?
Happy crunching, Christoph
Hey all, I think about to get the Beta Version. Question: Since the automatic download of this .pdb file is not working in the current version
It works fine on my machines (I just checked). It might indeed be a firewall setting or sth. that blocks it on Garys machines. But it's definitely working in principle.
A few days ago (in this message), I reported a problem with a v4.33 result that may have been related to an update of "McAfee Security Center".
Today, I discovered that another host also had a problem with the most recent McAfee updates and it also required a "System Restore" to resolve. This time, after the restore, the Einstein result that was "In Progress" on that host was able to resume processing but apparently it could not find a usable checkpoint. That is, although "CPU time" shows that it has processed 38+ hours, "Progress" reset to 0.00% and "To completion" went to 100+ hours (the original estimate plus 38 hours).
I would note that I had exited BOINC before I started troubleshooting the McAfee problem and doing the System Restore. I would also note that Einstein was again the only BOINC project to have a problem afterward. (In this case, both SETI and SETI Beta had "In Progress" WU's that restarted without any problem.)
Given that this is a "Monster" WU that is now restarting about a week closer to its deadline , I am inclined to abort rather than risk not finishing. However, I will wait a few days, in case Bernd would like to me to send in any of its related files.
A few days ago (in this message), I reported a problem with a v4.33 result that may have been related to an update of "McAfee Security Center".
Today, I discovered that another host also had a problem with the most recent McAfee updates and it also required a "System Restore" to resolve. This time, after the restore, the Einstein result that was "In Progress" on that host was able to resume processing but apparently it could not find a usable checkpoint. That is, although "CPU time" shows that it has processed 38+ hours, "Progress" reset to 0.00% and "To completion" went to 100+ hours (the original estimate plus 38 hours).
I would note that I had exited BOINC before I started troubleshooting the McAfee problem and doing the System Restore. I would also note that Einstein was again the only BOINC project to have a problem afterward. (In this case, both SETI and SETI Beta had "In Progress" WU's that restarted without any problem.)
Given that this is a "Monster" WU that is now restarting about a week closer to its deadline , I am inclined to abort rather than risk not finishing. However, I will wait a few days, in case Bernd would like to me to send in any of its related files.
I have a minor update to report: As it turned out, the "System Restore" reported above did not resolve the McAfee problem on my second host. So I checked the McAfee web-site and found instructions and tools for removing and reinstalling their program. That process appears to have worked.
Then, after fixing McAfee, I decided to try reversing the System Restore that I did yesterday. I thought the reversal just might "find" the Einstein checkpoint that was lost when System Restore was originally done. Unfortunately, that trick did not help. Instead, it appears that Einstein, once again, could not find a usable checkpoint and, again, started the WU from the beginning. However, once again, my "In Progress" SETI WU resumed from its checkpoint without problem.
Thanks. You'll probably understand that I'm hoping that the error occurs again :-)
Hi Bernd,
Well. you had to wait a bit for it but the machine that I originally reported back on July 30 has now finally produced this error result - once again an Unhandled Exception. According to the information in the stderr.txt, the PDB symbols were loaded so hopefully this will give you what you are looking for.
This is another "Unhandled Exception" error from a totally different machine but running the beta app with the .pdb file in place so hopefully of use to you. The stderr.txt does say "PDB Symbols Loaded" so it looks useful.
It's a different line number in houghmap.c - 404 instead of 385.
I don't think that small a difference is meaningful. I'm getting about the same number of seconds variation within the same app on much faster machines that a dedicated crunchers.
Hey all, I think about to get
)
Hey all, I think about to get the Beta Version. Question: Since the automatic download of this .pdb file is not working in the current version, should I take it manually to my Laptop? Of course I hope there will be no problems, but just in case, you know?
Happy crunching, Christoph
Greetings, Christoph
RE: Hey all, I think about
)
Yes, follow the inst. on the download page.
RE: Hey all, I think about
)
It works fine on my machines (I just checked). It might indeed be a firewall setting or sth. that blocks it on Garys machines. But it's definitely working in principle.
BM
BM
A few days ago (in this
)
A few days ago (in this message), I reported a problem with a v4.33 result that may have been related to an update of "McAfee Security Center".
Today, I discovered that another host also had a problem with the most recent McAfee updates and it also required a "System Restore" to resolve. This time, after the restore, the Einstein result that was "In Progress" on that host was able to resume processing but apparently it could not find a usable checkpoint. That is, although "CPU time" shows that it has processed 38+ hours, "Progress" reset to 0.00% and "To completion" went to 100+ hours (the original estimate plus 38 hours).
I would note that I had exited BOINC before I started troubleshooting the McAfee problem and doing the System Restore. I would also note that Einstein was again the only BOINC project to have a problem afterward. (In this case, both SETI and SETI Beta had "In Progress" WU's that restarted without any problem.)
Given that this is a "Monster" WU that is now restarting about a week closer to its deadline , I am inclined to abort rather than risk not finishing. However, I will wait a few days, in case Bernd would like to me to send in any of its related files.
RE: A few days ago (in this
)
I have a minor update to report: As it turned out, the "System Restore" reported above did not resolve the McAfee problem on my second host. So I checked the McAfee web-site and found instructions and tools for removing and reinstalling their program. That process appears to have worked.
Then, after fixing McAfee, I decided to try reversing the System Restore that I did yesterday. I thought the reversal just might "find" the Einstein checkpoint that was lost when System Restore was originally done. Unfortunately, that trick did not help. Instead, it appears that Einstein, once again, could not find a usable checkpoint and, again, started the WU from the beginning. However, once again, my "In Progress" SETI WU resumed from its checkpoint without problem.
RE: Thanks. You'll probably
)
Hi Bernd,
Well. you had to wait a bit for it but the machine that I originally reported back on July 30 has now finally produced this error result - once again an Unhandled Exception. According to the information in the stderr.txt, the PDB symbols were loaded so hopefully this will give you what you are looking for.
Cheers,
Gary.
This is another "Unhandled
)
This is another "Unhandled Exception" error from a totally different machine but running the beta app with the .pdb file in place so hopefully of use to you. The stderr.txt does say "PDB Symbols Loaded" so it looks useful.
It's a different line number in houghmap.c - 404 instead of 385.
Cheers,
Gary.
Finished my first wu with
)
Finished my first wu with 4.33. It was successful: http://einsteinathome.org/workunit/34430221
It was on a PIII and was very slightly slower than the previous wu run with 4.30.
Joe B
I don't think that small a
)
I don't think that small a difference is meaningful. I'm getting about the same number of seconds variation within the same app on much faster machines that a dedicated crunchers.
Hi, Reporting a successful
)
Hi,
Reporting a successful run using 4.33:
http://einsteinathome.org/task/86241547
Cheers,
Igor