Posts by robertmiles

41) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80349)
Posted 13 Jul 2016 by Profile robertmiles
Post:
I have ten completed tasks, with six of them due tomorrow, and some have been sitting in my queue for over 24 hours trying to upload.


Five of the six tasks I earlier had waiting for uploads have now uploaded and automatically reported, so it looks like the problem is now PARTLY fixed.


It looks like the project is trying to persuade users to support other projects instead by not fixing the long delays before clients can contact the server again.
42) Message boards : Cafe Rosetta : An Alzheimer\'s reversal? (Message 80295)
Posted 26 Jun 2016 by Profile robertmiles
Post:
This looks worth investigating to determine how accurate it is.

The first study to ever show Alzheimers can be reversed has just been published
Alzhreverse

http://www.dailykos.com/stories/2016/6/21/1540972/-The-first-study-to-ever-show-Alzheimers-can-be-reversed-has-just-been-published?detail=email&link_id=5&can_id=04cf7618a5486f0ccaca597540d8df5e&source=email-church-whose-pastor-praised-orlando-shootings-is-being-asked-to-leave-by-landlord&email_referrer=church-whose-pastor-praised-orlando-shootings-is-being-asked-to-leave-by-landlord&email_subject=church-whose-pastor-praised-orlando-shootings-is-being-asked-to-leave-by-landlord
43) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80286)
Posted 24 Jun 2016 by Profile robertmiles
Post:
I have ten completed tasks, with six of them due tomorrow, and some have been sitting in my queue for over 24 hours trying to upload.


Five of the six tasks I earlier had waiting for uploads have now uploaded and automatically reported, so it looks like the problem is now PARTLY fixed.
44) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80260)
Posted 24 Jun 2016 by Profile robertmiles
Post:
Could something be added to the Server Status to show the amount of free disk space available available for uploading? I\'ve seen some BOINC projects that had to delay uploads when such space ran short.
45) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80245)
Posted 23 Jun 2016 by Profile robertmiles
Post:
I see a growing number of pending upload jobs in my queues, is there an issue with the disks or access at R@H ?

\"Temporarily failed upload\" ... \"project communication failed\", \"Internet access OK\". My internet access is ok, I can download new packages, but not upload them. Those failing are usually around 400 Kb in size.

Regards,
BP


If it were an issue with the disks, I\'d expect it to block downloads as well.

It looks more likely to be an issue with a server program handling uploads but not downloads.

BP, you may want to change the sort option at the top right of the thread - it show the messages oldest first by default.
46) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80226)
Posted 23 Jun 2016 by Profile robertmiles
Post:
Rosetta@Home appears to have had some problem that block uploads for the last several hours.

This workunit is affected:

http://boinc.bakerlab.org/rosetta/workunit.php?wuid=759093541

It appears that downloads and getting new workunits to clients are probably not affected.
47) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 80164)
Posted 7 Jun 2016 by Profile robertmiles
Post:
Hi Sid,

Thanks for the alert! looks like these jobs require lots of memory. We have a way to specify how much memory to use. It will corrected in the next round of submission!

That would kind of explain why the task runs for a reasonable while before crashing out, and I\'ve seen occasional tasks using 1.2Gb, but I\'m running with just short of 10Gb free of 16Gb total.

I set Boinc to run 60% of memory when the computer is in use (90% when not in use). Do people routinely allocate more than that? What can I safely adjust that setting to, or is it just trial and error?


I\'ve found that 64-bit Windows Vista is rather inefficient at handling memory for running 32-bit applications, so I set that computer to use 30% to 40% of the memory for BOINC out of 8 GB. 64-bit Windows 7 and Windows 10 are more efficient, so I set that computer to use 70% out of 16 GB. 64-bit BOINC is not very good at giving up memory when the computer is in use, so these settings are the same for when the computer is in use as when not in use.
48) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 80021)
Posted 4 May 2016 by Profile robertmiles
Post:
I\'m seeing the same issue that\'s been reported above: an intermittent failure to get new workunits accompanied by this message in the event log.

Rosetta Mini for Android is not available for your type of computer.

Do Network Communication successfully reports the task.

I\'m running 2 R@h workunits/Ubuntu 14.04 LTS/Boinc 7.2.42/No workbuffer


I just discovered: ANDROID is a 32 bit operating system. Is it possible that Rosetta@Home cannot provide for a 32bit operating system? My computer is 32bit Linux -- I could easily load in the 64bit and try again. What does one think? :^)


I\'ve been seeing this problem under 64 bit Windows, so don\'t expect 64 bits alone to be a cure.
49) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 80011)
Posted 3 May 2016 by Profile robertmiles
Post:

Is there an ETA for the resolution of this issue?


As I understand it, the issue is that the project briefly exhausted it\'s supply of work available for non-Android devices. When only Android tasks are found in the scheduler, and you are coming in with a non-Android host, it reports the message \"Rosetta Mini for Android is not available for your type of computer.\"

This problem is resolved in ebbs and flows as large number of new hosts are coming in to the system. The tasks that make new work available are running continuously, but seem to hit periods of time where they still are barely keeping up with the incoming requests for work.


Could the number of tasks ready to send be divided by what host types they are suitable for, so that users can easily tell when only Android tasks are found in the scheduler?

Also, could thing be adjusted so that when no tasks are available for the type of computer requesting them, but many are available for other types of computers, the delay is set much below 24 hours?
50) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79982)
Posted 30 Apr 2016 by Profile robertmiles
Post:
I have the same problem here on my Win7 Ultimate, no updates / changes from my side. Everything works fine up to now.

30.04.2016 11:19:55 | rosetta@home | Sending scheduler request: To fetch work.
30.04.2016 11:19:55 | rosetta@home | Requesting new tasks for CPU and NVIDIA GPU and Intel GPU
30.04.2016 11:19:58 | rosetta@home | Scheduler request completed: got 0 new tasks
30.04.2016 11:19:58 | rosetta@home | No work sent
30.04.2016 11:19:58 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

Wtf, since when have i a Android? What comes next? A Alien? A Zombie?


Looks like someone with access to the source code for the Windows application should add a check at the end for whether the operating system setting still indicates Windows.
51) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79976)
Posted 30 Apr 2016 by Profile robertmiles
Post:
I\'m seeing the same issue that\'s been reported above: an intermittent failure to get new workunits accompanied by this message in the event log.

Rosetta Mini for Android is not available for your type of computer.

Do Network Communication successfully reports the task.

I\'m running 2 R@h workunits/Ubuntu 14.04 LTS/Boinc 7.2.42/No workbuffer

I just discovered the same thing in a machine I just assembled. I have a hunch while I am waiting for the Volunteer at BOINC to get back to me: My box has only one \'new\' component: the SSD. I purchased an economy SSD at Amazon which works perfectly otherwise. This is just a hunch. Could the memory chips in the SSD somehow be marked as for use in a cellphone? Forgive me if that is stupid. All my other components have crunched Rosetta before (all the other parts I used in this build.) I also have NO gripes pending on this SSD.


What operating system did you see this under? Windows, Linux, Android, or something else?

I\'ve had many Rosetta Mini workunits complete on one of my computers, which came with an SSD as its main drive. It uses Windows 10.

It\'s happening everywhere, Win7 and no SSD here. Manually updating often fixes it, but in the meantime Boinc puts in a 24hr delay before retrying, which is very annoying if you don\'t notice.


Something you might want to try: Check if restarting Win7, with no updates, fixes the problem, with a possible exception for the 24hr delay.

Also, you might want to check for a problem I\'ve seen in my last three completed workunits: For two of them, the application apparently completed with no problem seen. But then, the upload process for the output files gave a compute error of the upload error type. For the third one, a wingmate had this upload error, but then my computer got the workunit, completed it properly, then uploaded the output properly, then had one more validated workunit. The computer appears to about 5 hours into a 24hr delay; the other 19 hours should be more than enough to finish the other three Rosetta@home task it currently has.
52) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79958)
Posted 28 Apr 2016 by Profile robertmiles
Post:
I\'m seeing the same issue that\'s been reported above: an intermittent failure to get new workunits accompanied by this message in the event log.

Rosetta Mini for Android is not available for your type of computer.

Do Network Communication successfully reports the task.

I\'m running 2 R@h workunits/Ubuntu 14.04 LTS/Boinc 7.2.42/No workbuffer

I just discovered the same thing in a machine I just assembled. I have a hunch while I am waiting for the Volunteer at BOINC to get back to me: My box has only one \'new\' component: the SSD. I purchased an economy SSD at Amazon which works perfectly otherwise. This is just a hunch. Could the memory chips in the SSD somehow be marked as for use in a cellphone? Forgive me if that is stupid. All my other components have crunched Rosetta before (all the other parts I used in this build.) I also have NO gripes pending on this SSD.


What operating system did you see this under? Windows, Linux, Android, or something else?

I\'ve had many Rosetta Mini workunits complete on one of my computers, which came with an SSD as its main drive. It uses Windows 10.
53) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79919)
Posted 24 Apr 2016 by Profile robertmiles
Post:
Mine seems to be locking up since Friday 4/22/16. I run both SETI and Rosetta but each time it\'s locked up, it\'s been stuck on Rosetta. It\'s running on an XP machine so I don\'t know if that\'s the issue. System logs don\'t show anything other than events stop happening. I\'ve already uninstalled as well as completely wipe the BOINC folder then reinstalled. I have noticed in Task Manager that Minirosetta has recently been starting itself when I\'ve been using the computer despite my preferences.

Since I haven\'t seen any other entries on the BOINC/SETI/Rosetta board, I presume that it is this computer or XP. As it stands, I\'m going to remove BOINC for awhile since the issues with it just turning itself on while the computer is in use as well as it locking up have become too much to ignore. However, if this is happening to anyone else and they worked around it, feel free to post. I also wasn\'t sure which thread to post this in so I posted it in the top 2 threads concerning technical problems.


Does the SETI@HOME work use a graphics card with an Nvidia GPU? If so, the 364.* series of drivers for Nvidia GPUs has problems, so you might want to check whether going back to the 362.00 driver fixes any problems for you.
54) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79733)
Posted 8 Mar 2016 by Profile robertmiles
Post:
Any news on getting the communication problem fixed? Been sitting here for 2 days without any new work being available.....



For some reason, I decided to clear my IE cache and then tried to dl a new work unit and to my surprise IT WORKED! Happily crunching......


I decided to try that on my Windows 10 computer. Surprise - if Windows 10 even includes IE, it is very well hidden.

I told BOINC Manager to update for Rosetta@home anyway - it downloaded a workunit.

It looks likely that the problem is fixed on the server and IE is not involved.
55) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79711)
Posted 7 Mar 2016 by Profile robertmiles
Post:
Both of my computers received 24 hour backs after a single request for work resulted in this reply:
[quote]Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

When I noticed the problem several hours after the back-off began I simply hit the update button and successfully retrieved new tasks.

*****Wild Speculation Alert*****
If the amount of Android tasks exceeds the number of available devices by too great a number and/or fail at too high a rate then the new tasks/resends could be clogging the queue. As long as there are in fact plenty of cpu tasks to crunch, a 24 hour back-off would seem excessive.


I should add that I only became concerned because I recently reduced my preferred cpu runtime and my cache and set other projects to no new tasks (preparing for a possible imminent shut down of computers for an indeterminate period of time) so this 24 hour back-off actually lead to no tasks crunching at all. Otherwise I might have noticed but not been concerned enough to explore the possible causes or to comment.

I only comment now in the possibility that this back-off interval could be changed to something shorter. I know the project doesn\'t want a bunch of computer asking every 5 minutes while there\'s a clog but if it is a predictable clog and you can see how long it typically lasts perhaps you could adjust the back-off accordingly. Would anything longer than the 6 hour default target runtime really be necessary? Although not a big deal in the overall scheme of things, would things run somewhat smoother, on both sides of the connection, if crunchers weren\'t left to go idle unnecessarily for such a long
56) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79710)
Posted 7 Mar 2016 by Profile robertmiles
Post:
Both of my computers received 24 hour backs after a single request for work resulted in this reply:
Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

When I noticed the problem several hours after the back-off began I simply hit the update button and successfully retrieved new tasks.
[snip]


I\'ve seen a similar problem twice. I have an Android device in addition to my Windows devices, but so far I have BOINC installed only on the Windows devices.
57) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79709)
Posted 7 Mar 2016 by Profile robertmiles
Post:
Both of my computers received 24 hour backs after a single request for work resulted in this reply:
[quote]Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

When I noticed the problem several hours after the back-off began I simply hit the update button and successfully retrieved new tasks.

*****Wild Speculation Alert*****
If the amount of Android tasks exceeds the number of available devices by too great a number and/or fail at too high a rate then the new tasks/resends could be clogging the queue. As long as there are in fact plenty of cpu tasks to crunch, a 24 hour back-off would seem excessive.


I should add that I only became concerned because I recently reduced my preferred cpu runtime and my cache and set other projects to no new tasks (preparing for a possible imminent shut down of computers for an indeterminate period of time) so this 24 hour back-off actually lead to no tasks crunching at all. Otherwise I might have noticed but not been concerned enough to explore the possible causes or to comment.

I only comment now in the possibility that this back-off interval could be changed to something shorter. I know the project doesn\'t want a bunch of computer asking every 5 minutes while there\'s a clog but if it is a predictable clog and you can see how long it typically lasts perhaps you could adjust the back-off accordingly. Would anything longer than the 6 hour default target runtime really be necessary? Although not a big deal in the overall scheme of things, would things run somewhat smoother, on both sides of the connection, if crunchers weren\'t left to go idle unnecessarily for such a long
58) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79708)
Posted 7 Mar 2016 by Profile robertmiles
Post:
Both of my computers received 24 hour backs after a single request for work resulted in this reply:
[quote]Sun Mar 6 03:51:29 2016 | rosetta@home | Rosetta Mini for Android is not available for your type of computer.

When I noticed the problem several hours after the back-off began I simply hit the update button and successfully retrieved new tasks.

*****Wild Speculation Alert*****
If the amount of Android tasks exceeds the number of available devices by too great a number and/or fail at too high a rate then the new tasks/resends could be clogging the queue. As long as there are in fact plenty of cpu tasks to crunch, a 24 hour back-off would seem excessive.


I should add that I only became concerned because I recently reduced my preferred cpu runtime and my cache and set other projects to no new tasks (preparing for a possible imminent shut down of computers for an indeterminate period of time) so this 24 hour back-off actually lead to no tasks crunching at all. Otherwise I might have noticed but not been concerned enough to explore the possible causes or to comment.

I only comment now in the possibility that this back-off interval could be changed to something shorter. I know the project doesn\'t want a bunch of computer asking every 5 minutes while there\'s a clog but if it is a predictable clog and you can see how long it typically lasts perhaps you could adjust the back-off accordingly. Would anything longer than the 6 hour default target runtime really be necessary? Although not a big deal in the overall scheme of things, would things run somewhat smoother, on both sides of the connection, if crunchers weren\'t left to go idle unnecessarily for such a long
59) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79624)
Posted 25 Feb 2016 by Profile robertmiles
Post:
[snip]
coming to think about ram, i think linux and windows o/s are able to utilize swap for virtual memory hence disk space as swap memory if you have allocated sufficient space for that. but for atlas@home, i think the use of virtualbox probably limits what could be swappable.

you may like to see if disk swap spaces may be somewhat tunable in that respects.


BOINC tasks usually have swapping turned off, in an effort to make them run faster. This means that there is often no effort to make the applications able to stand the address changes caused by swapping something out of memory, and then swapping it back in at a different address because the original address is still in use by some other program.


The OS (Windows, all variants of Linux, MACOS, ... ) provides the program with VIRTUAL memory. The virtual memory is translated into PHYSICAL memory using the TLB translations. A virtual page of memory can get swapped to disk and then be relocated into a different PHYSICAL memory location by setting the TLB entry properly. The executing program does not even know if the page has been swapped out to disk.

The last time I looked, Windows allocated a disk swap file the same size as memory ( C:\\pagefile.sys ). You can explicitly set the size of this file, even to 0 bytes .... but when you run low on memory, the OS will kill stuff \"Out of Memory\".

Virtualbox is just a program in memory that runs on top of your OS and you set the memory size that virtualbox is allowed to use. I usually set virtualbox to be able to use about 50% of my physical memory BUT I have 16gb or more on my systems.



It\'s hard to get Virtualbox working correctly - once the versions of BOINC available so far have detected that virtualization is not enabled in the BIOS or the UEFI, they will remember this forever and prevent the test of whether it is enabled from being run again.

Also, all of the Virtualbox workunits I\'ve seen much about so far seize 4 GB of physical memory, and won\'t allow any of it to be paged. I\'m hoping that a new version of Virtualbox will remove this restriction.

As far as I know, Virtualbox can handle 32-bit workunits, but not 64-bit workunits.
60) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79615)
Posted 24 Feb 2016 by Profile robertmiles
Post:
[snip]
coming to think about ram, i think linux and windows o/s are able to utilize swap for virtual memory hence disk space as swap memory if you have allocated sufficient space for that. but for atlas@home, i think the use of virtualbox probably limits what could be swappable.

you may like to see if disk swap spaces may be somewhat tunable in that respects.


BOINC tasks usually have swapping turned off, in an effort to make them run faster. This means that there is often no effort to make the applications able to stand the address changes caused by swapping something out of memory, and then swapping it back in at a different address because the original address is still in use by some other program.


Previous 20 · Next 20



©2019 University of Washington
http://www.bakerlab.org