climateprediction.net home page
Posts by Glenn Carver

Posts by Glenn Carver

1) Questions and Answers : Unix/Linux : New Work Coming? (Message 70558)
Posted 3 hours ago by Glenn Carver
Post:
Testing showed up some problems, that's why the Linux work has been delayed. There is alot in the pipeline, but I can't give you a date just yet.
2) Message boards : Number crunching : WaH v8.29 bug leaves files behind in BOINC/data/projects/climateprediction -- please delete by hand (Message 70548)
Posted 1 day ago by Glenn Carver
Post:
Thanks for filling in the bits of info I missed in the original post.

A design flaw in the original WaH code is responsible for leftover files/dirs in the project dir. The task directories should really be in the boinc/slots directory, not the projects directory. Only the output files waiting to transfer should go into the projects directory. That way, the boinc client cleans out the slot dir even if the task has a catastrophic failure. The OpenIFS tasks were designed this way and I'm planning on making this change for WaH too.
3) Questions and Answers : Windows : "Calculation failure" after whenever i reboot the PC (Message 70537)
Posted 1 day ago by Glenn Carver
Post:
It's because the current batches are using a new version of the wah2 app, version 8.29. This fixes the problems with tasks crashing on restart.
4) Message boards : Number crunching : WaH v8.29 bug leaves files behind in BOINC/data/projects/climateprediction -- please delete by hand (Message 70535)
Posted 1 day ago by Glenn Carver
Post:
A bug has been found in the latest v8.29 Weather@Home app currently running EAS25 batches as app-name wah2_ri.

When the task finishes it mistakenly leaves some text files behind in the task directory inside the BOINC/data/projects/climateprediction.net directory. Task directories have long names such as 'wah2_eas25_a3pf_200912_24_1007_012269659'. This is the same as the task 'Name' column in boincmgr.

When a task finishes, it should delete the task directory (e.g. wah2_eas25_a3pf_200912_24_1007_012269659) in the projects/climateprediction.net folder, but unfortunately it leaves behind the 3 text files:
stdout_mon.txt
stdout_rm.txt
stdout_um.txt
Task directories with only these 3 files can be safely deleted.
DO NOT delete task directories which also contain 'datain', 'dataout', 'jobs' and any other files. These indicate running tasks. Also do not delete the entire 'climateprediction.net' directory as this will kill all running tasks.

Apologies for the inconvenience. The bug has been identified and corrected. A new version will be issued before any more batches are released.

Thanks to George (@geophi) for the initial report.
5) Questions and Answers : Windows : Norton Internet Security (Message 70534)
Posted 2 days ago by Glenn Carver
Post:
I've now reported this to Norton as a false positive detection. I'll let you know what response I get.
6) Questions and Answers : Windows : Norton Internet Security (Message 70533)
Posted 2 days ago by Glenn Carver
Post:
Hi Ian,

Thanks for reporting.

I created the new 8.29 app and it also tripped my McAfee. I have reported it as a false positive to McAfee which they have accepted. I will look at Norton as well.

The name of the virus 'Heur.AdvMLC' suggests they have matched it heuristically, in other words, it 'looked like', or, 'behaves like a virus'. Unfortunately, boinc apps can look like malware; they download executables & other files, use alot of system resource and run for a long time, even though they are not.

I run multiple AV systems (Defender & McAfee) on my development PC. They do not report any malware. The code did not change much between v8.29 and v8.24. I'm not going to tell you to ignore your AV system but from my point of view the application is safe.

CPDN are looking at how best to prevent this in the future.

Hope that helps.
7) Message boards : Number crunching : Time taken anomaly. (Message 70528)
Posted 2 days ago by Glenn Carver
Post:
It's not that easy unfortunately. The fortran models call C++ and shared memory is used for the 3 processes to talk to each. Would need work to check sizes. Ok, looks like best to move to 64bit first. The other option would be to distribute on macOS as a VM. More urgent things to do first. Interesting discussion though.
8) Message boards : Number crunching : Time taken anomaly. (Message 70525)
Posted 2 days ago by Glenn Carver
Post:
I'll chat to the Oxford folk and see what they say. Mind you, WaH is still 32bit and I don't know if that would complicate it on macOS.
9) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70524)
Posted 2 days ago by Glenn Carver
Post:
Ok. I don't think there's anything more I can do to help. Try contacting McAfee support?
10) Message boards : Number crunching : Time taken anomaly. (Message 70521)
Posted 2 days ago by Glenn Carver
Post:
Poking about in the WAH2 code, I've noticed sections related to earlier macOS builds, plus some notes on steps to build. Might be worth a go. I presume it's no problem to install macOS on a VM these days? Testing on real hardware would be the problem though.
11) Message boards : Number crunching : New Work 2024 (Message 70520)
Posted 2 days ago by Glenn Carver
Post:
Confirmation from the S.Korean scientists that the remaining wah2 batches will be released sometime early March.
12) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70519)
Posted 2 days ago by Glenn Carver
Post:
I've only just had the email from them, so it'll take a while yet.
13) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70517)
Posted 2 days ago by Glenn Carver
Post:
Yes, as I said in my earlier message. For some reason I sometimes have to try 'Add File' twice on the same file before it appears on the page. Probably a bug or McAfee being slow. Try it again, it does work.
That is probably the case.

Should I put the old 'wah2_8.29_windows_intelx86.exe' file back and try again? I am keeping it in the trash bin.
Sure. Now McAfee have emailed to confirm it's a false positive it's a safe thing to do.
14) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70515)
Posted 2 days ago by Glenn Carver
Post:
I had a response from McAfee and they have accepted the binary file wah2_8.29_windows_intelx86.exe for whitelisting as a false positive. Hopefully this will soon propagate down to users and stop being a problem.
15) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70514)
Posted 2 days ago by Glenn Carver
Post:
At the bottom of the real-time scanning window, click on 'Add file'. Navigate to the ../boinc/projects/climateprediction.net folder, select 'wah2_8.29_windows_intelx86.exe' and add it. It should then appear in the list of 'Excluded files'.
I have never been able to find a list of Excluded files. Where is it?
On my version of McAfee, the list of 'Excluded Files' is on the same settings page as 'Real time scanning'. The file list appears above the 'Add file' button. You probably can't see it because there's none added?

When I click Add file, a pop-up menu of files in the right directory appears. If I click on the file to be excluded, nothing happens. I can select either open or cancel. If I try open, it does not really respond. And I do not really want to open it anyway. There feels to be something wrong there.
Yes, as I said in my earlier message. For some reason I sometimes have to try 'Add File' twice on the same file before it appears on the page. Probably a bug or McAfee being slow. Try it again, it does work.
16) Message boards : Number crunching : New Work 2024 (Message 70513)
Posted 3 days ago by Glenn Carver
Post:
And because the boinc client suspends the task, for whatever reason.
17) Message boards : Number crunching : New Work 2024 (Message 70508)
Posted 3 days ago by Glenn Carver
Post:
So is there any word on when further new work will drop?
Server status currently showing 704 tasks ready to send, though doubtless that has dropped a bit since the last server update. I am guessing it may not be till next week that we get another of the batches that was mis configured sent out. The person who normally sends batches out is away and I don't know how much time Glenn has free to do this. If he doesn't have time it will have to wait till the person who normally does it is back.
I've been sending out the WaH2 EAS25 batches as soon as they are ready. The previous mis-configured batches are still being checked and aren't ready. Linux batches are not far away, again, still under test on the dev site.
18) Message boards : Number crunching : New Work 2024 (Message 70500)
Posted 4 days ago by Glenn Carver
Post:
Not quite, there are two apps for Weather@Home. wah2 & wah2_ri, all the latest batches are using wah2_ri. You need two different <app> sections if you are going to use <app>.

Also, you need to tell the client to 'Reread the config files' otherwise this won't take effect until the next time the client is started.

CPDN models are very floating point intensive. Since a cpu core only has one set of floating point units, two threads have to compete for resource. That's why your throughput drops. Checkout this post https://www.cpdn.org/forum_thread.php?id=9184&postid=68081 on these forums for an illustration and more explanation.

<app_config>
<app>
<name>wah2</name>
<max_concurrent>4</max_concurrent>
</app>
<app>
<name>wah2_ri</name>
<max_concurrent>4</max_concurrent>
</app>
</app_config>
19) Message boards : Number crunching : New Work 2024 (Message 70497)
Posted 4 days ago by Glenn Carver
Post:
Additional workunits for batch 1007 are going out today. They were omitted from the original send due to a misconfiguration.
20) Message boards : Number crunching : couldn't start app: CreateProcess() failed. Check your antivirus. (Message 70491)
Posted 4 days ago by Glenn Carver
Post:
Failed again same way.

Hi Jean-David, I've got this working with McAfee. For reference I have: McAfee LiveSafe 1.14.212.

Starting from scratch, that is, no wah-ri 8.29 tasks and no wah 8.29 executables in the ...../boinc/projects/climateprediction.net folder.

Set 'Allow new tasks' for climateprediction.net in boincmgr.
Starts download for a new wah-ri 8.29 task. 'Suspend' the climateprediction.net project in boincmgr -- this will allow the download to complete but not start.

Open McAfee and from Home page go to 'My Protection => Real-time scanning' in the left hand bar. Make sure 'Real time scanning' is ON. It's not possible to exclude files without it on.

At the bottom of the real-time scanning window, click on 'Add file'. Navigate to the ../boinc/projects/climateprediction.net folder, select 'wah2_8.29_windows_intelx86.exe' and add it. It should then appear in the list of 'Excluded files'. If it doesn't, do it again (for some odd reason, I find I sometimes have to do this twice). Then in boincmgr, Resume the climateprediction.net project and the task should then run fine.

If boinc has already downloaded the exe file, you might find it under 'My Protection => Quarantined Files'. In which case, select it, click 'Restore'. Then as above, go to 'Real-time scanning' and 'Add' the file to the excluded list.

If the boinc data directory is hidden from you to get to the exe in File explorer, turn on 'View - Show - Hidden folders'.

Hope that gets things going for you.

p.s. we are looking into why this is tripping a few AV systems. I can assure you there are no viruses on my development PC.


Next 20

©2024 climateprediction.net