Posts by Nonexistent_Admin

1) Questions and Answers : Unix/Linux : EXIT_TIME_LIMIT_EXCEEDED still present (Message 359)
Posted 17 Jun 2019 by Nonexistent_Admin
Post:
The only thing we can do (have done, will do) is increase the time limit for all WUs produced by the nanoHUB tools that have a lot of failures with the same error. For example, yesterday two tools produced most of the time limit errors (1% of all WUs), so we increased the time limit for all WUs produced by those tools.
2) Message boards : News : Request for feedback (Message 355)
Posted 13 Jun 2019 by Nonexistent_Admin
Post:
I have no idea. Let me see what I can find.
3) Message boards : News : Request for feedback (Message 351)
Posted 11 Jun 2019 by Nonexistent_Admin
Post:
Any chance to dump the vbox experience and go native

Not really. We have 209 different simulators supported by this project. We don't have the resources to maintain native versions of so many tools, especially for Windows.
4) Questions and Answers : Unix/Linux : 125 (0x0000007D) Unknown error code (Message 350)
Posted 11 Jun 2019 by Nonexistent_Admin
Post:
That is very likely the source of these problems.
5) Questions and Answers : Windows : The disk has no volume label error (Message 345)
Posted 10 Jun 2019 by Nonexistent_Admin
Post:
I don't think the BOINC client will pick up those jobs from files copied back into the project directory.
6) Message boards : News : Request for feedback (Message 344)
Posted 10 Jun 2019 by Nonexistent_Admin
Post:
Other BOINC projects have reported some successes for users who restart the client after seeing the "VM Job unmanageable" message. Restrict your client to 1 or 2 WUs at a time to conserve disk space.
7) Questions and Answers : Windows : The disk has no volume label error (Message 338)
Posted 7 Jun 2019 by Nonexistent_Admin
Post:
The error log suggests the Docker files might have been corrupted or missing. Have you seen more errors like this? Do these only occur on your new host? The error code is uncommon (10 of 27626 WUs yesterday).
8) Message boards : Number crunching : how can i fix - postponed for 86400 seconds: Detection of VM Hypervisor failed (Message 337)
Posted 7 Jun 2019 by Nonexistent_Admin
Post:
Sorry, I have no idea how to fix hypervisor issues.
9) Message boards : News : Request for feedback (Message 336)
Posted 7 Jun 2019 by Nonexistent_Admin
Post:
The Windows 7 machine with similar hardware is running 100% valid results.

For nanoHUB@home?
10) Questions and Answers : Windows : The disk has no volume label error (Message 323)
Posted 6 Jun 2019 by Nonexistent_Admin
Post:
That's a new one for me. Let me look at the WU more closely.
11) Questions and Answers : Windows : WU completes with VirtualBox errors (Message 318)
Posted 4 Jun 2019 by Nonexistent_Admin
Post:
No, you just need to run the BOINC client on your Windows computer. The installer for the BOINC client should also install VirtualBox on your system. Connect your client to https://boinc.nanohub.org, and the client will do the rest: download the necessary VM images and run VBox as needed.
12) Message boards : News : Request for feedback (Message 315)
Posted 3 Jun 2019 by Nonexistent_Admin
Post:
Looking at the results from the weekend, 3% hit the time or disk limit, and 5% were aborted via the GUI. We are working to fix the problem preventing the creation of new WUs; once again, the problem is not with BOINC but with another nanoHUB machine on which all the memory is consumed by monitoring these BOINC jobs. We fixed most of the problems with that system but obviously not all of them. Plus, the two of us running this project have been busy teaching a short class for undergrads using nanoHUB for summer research; that ends today, so we will get this fixed ASAP. Thanks for letting us know.
13) Questions and Answers : Windows : WU completes with VirtualBox errors (Message 314)
Posted 3 Jun 2019 by Nonexistent_Admin
Post:
Some users have found that VBox 5 works better than 6. Others have seen no difference. We haven't been able to identify a trend (e.g. Windows version vs. VBox version).
14) Message boards : News : Request for feedback (Message 309)
Posted 20 May 2019 by Nonexistent_Admin
Post:
Yeah, we had a big problem with workunits hitting the disk limit last week. We added a few new nanoHUB simulation tools to this project, and two of the simulators are written using Matlab. Compiling the Matlab code pulls in a huge chunk of the Matlab runtime, and most of the WUs for those tools hit the disk limit and failed. We increased the disk requirement for those two tools, and I am watching WUs produced by those tools. Thanks for letting us know.
15) Message boards : News : Running again (Message 290)
Posted 9 May 2019 by Nonexistent_Admin
Post:
The recent problem has been cleaned up. A nanoHUB machine that handled results returned from the BONIC server froze, stranding 100k successfully completed results, along with some live nanoHUB sessions. We saved all the results and set up a new dedicated machine to handle that part of the work flow. We will ramp up WU production again.
16) Message boards : News : Temporary pause (Message 288)
Posted 30 Apr 2019 by Nonexistent_Admin
Post:
We're having trouble with a nanoHUB server that sends jobs to the BOINC server for WU production. We had to temporarily halt WU production while we fix the other machine.
17) Message boards : News : Request for feedback (Message 257)
Posted 13 Apr 2019 by Nonexistent_Admin
Post:
We do track the errors, and we greatly appreciate the error reports.
18) Message boards : News : Another round of upgrades complete (Message 223)
Posted 20 Mar 2019 by Nonexistent_Admin
Post:
We are back up again. The BOINC server for this project is connected to several other key parts of the nanoHUB infrastructure. We had to upgrade the BOINC server in January to support the volume of WUs our crunchers consume. The WU's are created from nanoHUB input files by another server, and we had to do significant upgrades to that server. The database of in-progress jobs (via BOINC and other venues) was consuming all the memory on that machine, leading to swapping. That server is critical for all nanoHUB jobs, including courses at several universities, so the DB upgrade had to be thoroughly tested before rolling it out. We are tiptoeing back into the creation of WUs. TLDR: our crunchers consume jobs at a rate at least one order of magnitude higher than our other computing venues, so it stresses all the infrastructure. We're watching everything closely.
19) Message boards : Number crunching : Recently, the WU spend more and more time/memory (Message 208)
Posted 27 Feb 2019 by Nonexistent_Admin
Post:
We contacted the admin of boincstats to fix the URL. Please let us know if this problem continues.
20) Message boards : News : Request for feedback (Message 204)
Posted 21 Feb 2019 by Nonexistent_Admin
Post:
While examining the BOINC job records we noticed that some jobs are failing with the exit code EXIT_ABORTED_VIA_GUI. If you have aborted a nanoHUB@Home job in your client, what was the reason?

In the same analysis we are working to improve the time and disk estimates for nanoHUB tools that produce WUs that fail often.


Next 20


©2019 COPYRIGHT 2017-2018 NCN