Posts by jjch

1) Questions and Answers : Windows : Python compute error - Exit status 1 (0x00000001) Unknown error code (Message 106748) Posted 10 Aug 2022 by jjch Post: Update - I found the problem causing this with BOINC being installed as a Service Install. That makes it run under the boinc_master account which does not have the correct privileges. The BOINC application needed to be installed without the service install box checked which allows it to run under the Administrator account. I was able to deinstall the BOINC program and re-install it with the correct setting. So far it seems to be running the python tasks so I'm pretty sure it will work now. I also found out that if you run too many python tasks it can fill up your disk. If you don't have a lot of disk space, you might need to limit how many tasks run with an app_config file. Jeff
2) Questions and Answers : Windows : Python compute error - Exit status 1 (0x00000001) Unknown error code (Message 106731) Posted 7 Aug 2022 by jjch Post: I have been experiencing many failures with the current Python application on several servers. I have 2 out of 5 systems running the Python tasks successfully. The other 3 systems tasks fail with compute error in about 15 seconds. The Python VM's don't even show up in VBox so they are not getting that far. What I can see from the system events log is 10016 errors from DCOM server. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {74AB5FFE-8726-4435-AA7E-876D705BCBA5} and APPID {EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA} to the user DL360G8-02boinc_master SID (S-1-5-21-138663538-4015345470-751189161-1006) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool. The two that are working run Windows server 2019 and 2022. Two of the ones that are failing run 2012 R2 and the other is running 2019. All of them have been updated with Boinc version 7.20.2 with the default VBox version 6.1.34. I did have a different issue with Hyper-V running on one server so I removed that but still cant figure it out. I have already tried a number of things to fix this but cannot find a working combination or what is different between the ones that are working and not. Deinstalled/reinstalled BOINC including VBox Updated VBox to the more recent version 6.1.36 Deinstalled BOINC and VBox and installed as Administrator Tried editing the CLSID and APPID permissions in the registry and the DCOM config I gave up after that. It shouldn't be that complicated. Here are links to a few of the failing stderr output files for reference. They are all the same. https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247574 https://boinc.bakerlab.org/rosetta/result.php?resultid=1492248465 https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247745 https://boinc.bakerlab.org/rosetta/result.php?resultid=1492247240 Any further thoughts would be appreciated.
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 90066) Posted 23 Dec 2018 by jjch Post: The tasks that I had piling up with the In progress status are now cleared. They have gone to the error status list with the Timed out - no response status. See here: https://boinc.bakerlab.org/rosetta/results.php?userid=486414 A sample work unit show Too many total results WU cancelled https://boinc.bakerlab.org/workunit.php?wuid=942284714 Looks like something was crossed up with these tasks on the processing side but I didn't see any loss of compute cycles. I think the rewards are better with Rosetta so I may go back to that project after I let the WCG clear out.
4) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 90025) Posted 18 Dec 2018 by jjch Post: From what I can tell these work units were cancelled but the status remained In progress. If you check the Workunit under errors you will see WU cancelled. For example: https://boinc.bakerlab.org/workunit.php?wuid=942284714 I don't think there is anything major to worry about just an annoyance. It's not likely you lost any compute cycles either. The Rosetta programming team should clean this up if possible however I think they will disappear after the deadline expires. For now I have stopped all Rosetta computing until after Dec 23rd to see if this is true. FYI, I am giving WCG cycles in the meantime.
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 90006) Posted 16 Dec 2018 by jjch Post: I think I may be experiencing a similar issue. Recently I noted the work in progress value appeared to be approximately double the normal amount of work units I have running at a time. In order to trouble shoot this I set Rosetta to no new tasks and let them run out. Checking Boincstats I no longer have any work left on any host. According to Rosetta I currently have a total of 1709 tasks in progress. For example host 1770544 it is not running any Rosetta tasks but yet the In progress count is 216. https://boinc.bakerlab.org/rosetta/results.php?hostid=1770544&offset=0&show_names=0&state=1&appid= I did try resetting the project on that host but it didn't make any difference. My impression there is a problem on the Rosetta server side and it isn't updating the task status properly. I think we need the Rosetta programming team look into this further.
6) Message boards : Number crunching : Rosetta Mini v3.78 - Declining credit since October 24th (Message 87742) Posted 24 Nov 2017 by jjch Post: I am seeing a few 4.0 tasks now but only a very small amount. The RAC is continuing to drop. If this is the new credit model than that's fine. I will just have wait to see when it levels off. If there is something broken I would like to fix it.
7) Message boards : Number crunching : Rosetta 4.0+ (Message 87741) Posted 24 Nov 2017 by jjch Post: Right after I said I wasn't getting any 4.06 tasks I have started seeing a few. It is only a very small amount. Maybe less than 5% of the total. They do seem to be working fine though. What I'm trying to figure out is why the Rosetta RAC has been dropping so much since about a month ago. These are mostly 3.78 tasks but it is way down from what it used to be. See this post https://boinc.bakerlab.org/rosetta/forum_thread.php?id=12320
8) Message boards : Number crunching : Rosetta Mini v3.78 - Declining credit since October 24th (Message 87734) Posted 23 Nov 2017 by jjch Post: I have noticed a significant RAC decline since October 24th running the Rosetta Mini v3.78 application. Refer to my Rosetta Stats here: https://boincstats.com/en/stats/14/user/detail/486414/charts As far as I know everything is working properly and it seems unusual that this would have such a steady drop unless there is a problem somewhere or Rosetta changed something with the 3.78 app. I did see there is a 4.0 app however I have not been receiving tasks for that version yet.
9) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 80942) Posted 27 Dec 2016 by jjch Post: Since December 24th I have noted that my Rosetta@home average work has been steadily dropping. Looking at it a bit further today I found the message "Rosetta Mini for Android is not available for your type of computer" I have seen this message before sometime earlier this year and it seems to have come back again. The Rosetta server appears to have plenty of work available and my systems are all windows based. If I shutdown and restart Boinc it will start retrieving work units again but that is a painful process to go through all the systems. These are all running Boinc version 7.6.33 and Rosetta version 3.73. If there is a better method to keep up production please let me know. I would be willing to try testing some things if needed. Let me know if you need more information. jjch
10) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79608) Posted 24 Feb 2016 by jjch Post: The servers are all in a lab room that has an AC cooling unit but I'm actually close to the limit it will handle. Works pretty well during the winter and cooler months but when the weather gets hot outside I have to throttle them back during that day and only run at night. If it gets past 90 F I have had to just let them run out of work units and idle. If we get to 100+ F I have had to shut them off and let the weather cool down a bit before starting back up again. Gives me a chance to update things and reset them anyway.
11) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79600) Posted 23 Feb 2016 by jjch Post: Update - Several of the servers that had 0 work left yesterday started up again today and began processing Rosetta tasks. Probably after the communication deferred timer ran out. Seems that if you manually update the project it triggers the loop but if you leave it alone it might sort it out by itself. There are a few that still are stuck so I can check on those tomorrow. Several servers already have 32GB memory so those are reporting a similar message with slightly different memory size available. Also, there are three servers one each with 64, 128 and 256GB of memory. They need patching and BOINC updates to 7.6.22 anyway. When I restart them I will watch how they behave.
12) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79597) Posted 22 Feb 2016 by jjch Post: I'm not seeing an option to change that setting in rosetta. It is available on a few other BOINC projects though.
13) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79593) Posted 22 Feb 2016 by jjch Post: All of the systems are running Windows, either 2012/R2, 7 or 8.1. There isn't any that have an android emulator either. Had to give up my Linux servers. There were a couple of these that were left with more than 8GB memory. I am going to check if those also have the same problem. I will also check if one might already have 64 GB memory or upgrade it and see if it makes any difference.
14) Message boards : Number crunching : Minirosetta 3.73-3.78 (Message 79582) Posted 22 Feb 2016 by jjch Post: It looks like there are two different things going on here but they may be related. I have a number of servers and workstations that are being used for CPU and GPU computing. These were recently set to primarily to run rosetta for CPU work to help out that project. The rosetta Task status shows Ready to report but the Project Status goes to Communication Deferred for multiple hours (ex. 18 hrs) and the server runs dry. What I am seeing is that the project happily goes along for a while Requesting new tasks for CPU and gets the Scheduler request completed: got 1 task message. Then after a few hours it gets the Scheduler request completed: got 0 tasks. No work sent. Rosetta Mini for Android is not available for your type of computer. Finally, the message Rosetta Mini needs 57220.46 MB RAM but only 7363.62 MB is available for use. After that it stops updating. Remaining tasks will continue to upload until it runs out. Rosetta does not automatically download any more tasks or report any that were finished. You can manually update and get it to reset and start again however it will just run through to the same result in a few hours. I'm not going to baby sit all of these servers everyday to keep running rosetta. Also, these were purposefully only populated with 8GB memory to save on power and cooling requirements. CPU and GPU computing remember. Please look into this and provide a resolution soon or I will have to move on to other projects. Let me know if I can be of assistance or provide any more detailed information. Thanks.