|
41)
Message boards :
BOINC client :
allow multiple clients
(Message 69399)
Posted 3 May 2016 by Erich56 Post:
Well, maybe my problem concerning the password could be solved very easily, if someone could just give me the proper hint. I am still hoping :-) |
|
42)
Message boards :
BOINC client :
allow multiple clients
(Message 69396)
Posted 3 May 2016 by Erich56 Post:
after following all the steps as described, I could get the second BOINC manager to open, but right thereafter the message "the password you have provided is incorrect - please try again" shows up :-( I had replaced the many xxx with exactly what was contained in the original gui_rpc_auth.cfg. So - no idea why this password is not being accepted. So, unfortunately, the second BOINC manager does not work here :-( |
|
43)
Message boards :
BOINC client :
allow multiple clients
(Message 69383)
Posted 2 May 2016 by Erich56 Post: NM ??? |
|
44)
Message boards :
BOINC client :
allow multiple clients
(Message 69381)
Posted 2 May 2016 by Erich56 Post: But this may not work well. Remembering what I have read some time ago in other postings, it seems indeed to be difficult to run 2 BOINC clients on one machine. What is it you're trying to accomplish, and isn't it easier to do that with something else? My problem is as follows: I run BOINC on a RAMdisk, after I had found out that crunching several instances of ATLAS@home concurrently will write up to 200GB per day on my SSD, thus causing early wear. Besides ATLAS, I run WCG and GPUGRID. And the problem comes with the latter - GPUGRID tasks are only downloaded if there is 7.629MB free space on the disc (i.e. on the RAMDisk in my case). No one knows the reason for this huge space requirement, as in reality a GPUGRID task does not need more than some 140MB disk space. So, with my 17GB RAMDisk, I permanently need to leave some 8GB free space just for GPUGRID downloading new tasks. Valueable space which I could use for at least 2, if not 3 more ATLAS tasks. Hence, my plan would have been to install a second BOINC not on the RAMDisk, but on the SSD, just for GPUGRID, and leave ATLAS plus WCG on the RAMDisk. Okay, this obviously is not that easy. Alternately I could buy a new SSD with an enormous high TBW, which either replaces the current one (with "only" 150TB) or being installed as second SSD. Or I could buy an external USB3 HD and install BOINC on this one. Although I am aware that the drawback in speed would probably be enormous, particularly vis-a-vis the RAMDisc solution that I have currently. Or would it perhaps not be that bad? Installing an internal HDD, in addition, would not work, as I had to remove the HDD cage for being able to put in the two huge GTX980Ti GPUs. Any other suggestions I might not have thought of? |
|
45)
Message boards :
BOINC client :
allow multiple clients
(Message 69380)
Posted 2 May 2016 by Erich56 Post: Looks like a continuation from here http://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=519719 no, the background is a different one. |
|
46)
Message boards :
BOINC client :
allow multiple clients
(Message 69374)
Posted 2 May 2016 by Erich56 Post: I ran across this interesting website: https://boinc.berkeley.edu/wiki/Client_configuration in the sub-chapter "options" of the main chapter "Configuration file" (cc_config.xml), among other things, it says: <allow_multiple_clients>0|1</allow_multiple_clients> Allow multiple BOINC clients to run on a single host. Each must run in a different data directory. What exactly does this mean? I could simply put this cc_config.xml to the data directory of my current BOINC installation, and then I could add a second instance of BOINC? After I had read before in several places how complicated it is to install BOINC twice, it's hard for me to believe that it could be that simple. So, if this is not the case, what else could this then mean? |
|
47)
Message boards :
Questions and problems :
how to set/change interval for requesting new tasks
(Message 69290)
Posted 29 Apr 2016 by Erich56 Post: okay, I'll try to explain: beside other projects, I am running GPUGRID, where, as you may know, since beginning 2016 thay have only one scientist left who feeds the WU queue. This results in a chronic shortage of new tasks. I have made the experience that when trying to get a task "manually", i.e. by frequently (i.e. every two minutes or so) pushing the "update" button for GPUGRID in the projects tab of the BOINC manager, the chances are somewhat higher. However, it's clear that I cannot sit there all the time and push the "update" button in 2-minutes' intervals for hours :-) So what I am trying to find out is whether there is a possibility to set a shorter interval for "requesting new tasks" as it is when BOINC does it by itself (I guess, on the average every 10 or 15 minutes or so, from what I think I saw). I have realized that by NOT trying to get a task manually, it could take up to 10 or 12 hours to finally receive a new WU :-( |
|
48)
Message boards :
Questions and problems :
how to set/change interval for requesting new tasks
(Message 69288)
Posted 29 Apr 2016 by Erich56 Post: Is there any possibility to set/change in the BOINC manager (or somewhere else) the interval in which BOINC is automatically requesting new tasks from either a specific project or all projects? |
|
49)
Message boards :
Questions and problems :
event log: "CPU cache full" - which cannot be the case
(Message 69025)
Posted 17 Apr 2016 by Erich56 Post: good question: there were several ATLAS tasks in "Ready to start" queue. Once I removed them, WCG tasks were downloaded and started. So, I had 2 GPUGRID tasks running, 4 ATLAS, 4 WCG. That's what I intended to happen. I then left for a while, and when I came back, beside the 2 GPUGRID tasks, 8 WCG tasks were running, and the ATLAS tasks were in "Waiting to run" queue. Very nice :-( Although I had set the ressource share to equal values for these both projects. My target is to run concurrently: 2 GPUGRID tasks (which so far has always worked well, since this is the only project with GPU use, plus ressource share set to 1000). 4 ATLAS tasks 4 WCG tasks So, I decided to write the following app_config.xml, like I have it for ATLAS (which works well): <app_config> <app> <name>wcgrid</name> <max_concurrent>4</max_concurrent> </app> </app_config> However, it does not work. after loading the app into the WCG project folder, the BOINC event log says: 17/04/2016 17:51:09 | World Community Grid | Your app_config.xml file refers to an unknown application 'wcgrid'. Known applications: 'mcm1', 'ugm1', 'fahb' That's what I was afraid of :-( Any idea what an app_config.xml has to look like in order the limit of WCG tasks to 4 running concurrently? One thing that seems clear is: the ressource share thing will not help much in this case, as it weighs other parameters also, like task finishing deadline, and what not. |
|
50)
Message boards :
Questions and problems :
event log: "CPU cache full" - which cannot be the case
(Message 69010)
Posted 17 Apr 2016 by Erich56 Post: Recently, I got a new PC with a 6-core HT CPU, i.e. 12 cores altogether. I am running 2 GPUGRID tasks (using my 2 high-end GPUs), 4 ATLAS@home tasks, and now I had planned to add 4 tasks for WCG - in order to have 10 tasks running altogether. The ressource share for GPUGRID is at 1000 (so that two such tasks are running in any case), the ressource share for ATLAS presently is at 200, the ressource share for WCG presently is at even 300. In the BOINC computing preferences, CPU usage is at 80%, which means 10 tasks (for 12 cores). When I added the WCG project, 2 GPUGRID tasks and 4 ATLAS tasks were running (for other reasons, by a config_app.xml I had limited ATLAS to maximum 4 tasks), so I expected WCG to download and run 4 tasks. However, only 1 task is running. When I go to "projects" and "update", the BOINC event log says: 17/04/2016 09:27:36 | World Community Grid | update requested by user 17/04/2016 09:27:39 | World Community Grid | Sending scheduler request: Requested by user. 17/04/2016 09:27:39 | World Community Grid | Not requesting tasks: don't need (CPU: job cache full; NVIDIA GPU: ) 17/04/2016 09:27:41 | World Community Grid | Scheduler request completed why so ??? CPU job cache is definitely NOT full with 7 tasks running - as said, before I had 10 task running with CPU usage set to 80% of my 12-core CPU. Any comments / help ? I would definitely like to have 4 WCG task running, not only 1. |
|
51)
Message boards :
Questions and problems :
How to reduce a project to a given number of CPU tasks? - BOINC on external USB3 drive possible?
(Message 68993)
Posted 15 Apr 2016 by Erich56 Post: many thanks for your app_config.xml proposal. It will for sure help to get GPUGRID tasks running besides ATLAS tasks. However, it still is only some kind or work-around, as - at least in my specific case - there is a huge waste of RAMDisk space and system RAM space. Normally, with my RAMDisk (14GB) and system RAM (18GB) setting, plus my 6+6 core CPU, plus my 2 high-end GPUs, I could without problems crunch 6 ATLAS + 2 GPUGRID tasks at the same time. But in fact, I will have to limit the ATLAS tasks to 2 (or maximum 3, what I doubt, but I have to try it out). It's really too bad that GPUGRID has this 7.629MB free disk space requirement, which might only be "historical" and not valid in reality. Meanwhile, I have contacted the GPUGRID people; so we'll see what they say. |
|
52)
Message boards :
Questions and problems :
config.xml possible for reducing false GPUGRID 7629MB free disk requirement ?
(Message 68988)
Posted 15 Apr 2016 by Erich56 Post: in this thread https://boinc.berkeley.edu/dev/forum_thread.php?id=10957 I have reported about my problem to get GPUGRID tasks downloaded while running serveral ATLAS tasks, with the BOINC event log notice: Long runs [8-12 hours on fastest card] needs 2146.64MB more disk space. You currently have 5482.75 MB available and it needs 7629.39 MB In the GPUGRID forum, a forum member was mentioning "But I wonder if GPUGrid really needs all that much space? I doubt it for the GPU client; it may be an artifact of the CPU work they were doing at one time. Maybe you could post separately about it, and it could be reduced." I looked it up closer, and in the BOINC directory, the projects folder for GPUGRID is about 90MB big, the slots folder is about 48MB. So, no idea why when downloading a new task, GPUGRID requests 7.629MB of free space. The assumption about outdated "historical" reasons may be correct. I wonder whether this stumbling block could be circumvented by some hand-written config.xml or whatever ??? Maybe an interesting challenge for the specialists here? |
|
53)
Message boards :
Questions and problems :
How to reduce a project to a given number of CPU tasks? - BOINC on external USB3 drive possible?
(Message 68987)
Posted 15 Apr 2016 by Erich56 Post: I just read a posting in the ATLAS forum where someone else was having a similar issue - and he said that it got solved by installing a separate BOINC client. I am wonderung whether it is really possible to just setup BOINC twice - this works? No interferences or other complications? Is there anything I would have to particularly observe during installation or thereafter? If this could be done, it most probably would solve my problem (unless any other unforeseen issues come up). I would have one BOINC for ATLAS, and another one for GPUGRID, and just set the CPU usage %values as needed. Any comments? |
|
54)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68986)
Posted 15 Apr 2016 by Erich56 Post: Of course you've been reading the message/event log where most all is being told of what the client is or is not doing, with a why. after a short while, it's all turned out running okay - what concerns the ATLAS project. However, after adding the GPUGRID project, another problem came up. I have described it here: https://boinc.berkeley.edu/dev/forum_thread.php?id=10957 |
|
55)
Message boards :
Questions and problems :
How to reduce a project to a given number of CPU tasks? - BOINC on external USB3 drive possible?
(Message 68985)
Posted 15 Apr 2016 by Erich56 Post: I am running BOINC on a RAMDisk with 14GB size (the reason is that ATLAS@home writes tremendous amounts of data on the SSD, and I'd like to prevent it from early wear). My projects are GPUGRID (with 2 GPUs, so 2 tasks should run simultaneously) and ATLAS. My CPU is a 6-core plus 6 Hyperthreading. Total RAM is 32GB, with 14GB RAMDisk deducted, there are 18GB system RAM remaining. This, and a 50% CPU use setting in the BOINC manager, allows for 6 ATLAS tasks running simultaneously, so that there is sufficient space on the RAMDisk for the Atlas .vdi-image files in the BOINC SLOTS folder, and enough system RAM (ATLAS needs up to almost 3GB per task). However, the problem is that GPUGRID would not download any tasks, even not if only 4 or 5 ATLAS task are running (instead of 6), since, according to the BOINC event log entry, more free disk space is needed ("Long runs [8-12 hours on fastest card] needs 2146.64MB more disk space. You currently have 5482.75 MB available and it needs 7629.39 MB."). From my observations, it seems that if only 3 ATLAS tasks are running, there should be enough free disk space for GPUGRID. So - my question now is: how can I limit the number of simultaneously running ATLAS tasks to 3, and yet leave the CPU usage at 50% ? I have tried it with the "Ressource share" - this, however, did not yield the desired result. Value for GPUGRID was set to 1000, value for ATLAS to 200. Still, as soon as a GPUGRID task is not downloaded due to not enough disk space, ATLAS tasks are being downloaded instead - with the result of 6 ATLAS tasks running simultaneously, and no GPUGRID task. So I need some other instrument for limiting the number of ATLAS tasks. Any idea what I can do? If nothing can be done on the software-side, the only solution of course would be a HDD in addition. However, with this I would have a space problem in my PC, since because of the two huge GPUs (GTX980Ti) and the huge CPU cooler (Noctua), the HDD cage had to be removed. If really no other solution should work out, would running BOINC on an external USB-3 HDD be possible? I have not observed this during BOINC installation, as to whether one could point the data folder to an external USB drive. I am aware that this would mean setbacks speedwise, but it might be worth trying (particularly, if it would be the only way to get GPUGRID running beside ATLAS). Any thoughts and comments? |
|
56)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68975)
Posted 14 Apr 2016 by Erich56 Post: I have a new, clean install of BOINC. The complete data directory is on the 14GB RAMDisk now. And the ATLAS work units, after uploading, are no longer showing the "computation error" with -161 error. However, what is different to how it was before, is the following: Presently, just to start with "half speed" and increasing everything later, under BOINC computing preferences, I have set CPU use to 50%. Before, with this setting, 6 ATLAS tasks were running (6-core CPU with HT). Now, only 4 ATLAS tasks are running, altough there is 5,4GB free space on the RAMDisk (1 ATLAS task uses about 1,6GB for the vm_image.vdi in the SLOTS folder). BOINC settings are such that 97% of disk space can be used, and 95% of RAM (system RAM is 18GB, currently some 5GB are free). Also, setting for storing work and for storing additional work is at 0,2 days of work ea, (before, it was only at 0,1 days of work), but no ATLAS tasks are downloaded in advance. Only after one of the four gets finished and uploaded, the next one is being downloaded. Before, I always had between 2 and 4 task in "waiting to run" status. Why are all these things so different to what they were before when I was not working with the RAMDisk? What am I doing wrong? Which of the settings are incorrect? |
|
57)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68966)
Posted 13 Apr 2016 by Erich56 Post: Make a backup, restore it later and you have an out-of-sync situation that's exactly what I guess - so backups probably wouldn't make any sense. Anyway, today I re-installed BOINC from scratch, with the complete data-directory on the RAMDisk (in contrast to how it was before: only the SLOTS folder on the RAMDisk) - and now the ATLAS tasks work well. So, it definitely had NOT been a good idea to split the BOINC data folder to SSD and to RAMDisk. |
|
58)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68963)
Posted 13 Apr 2016 by Erich56 Post:
This would definitely make sense; however, automated backups by a backup software, in certain time intervals, will unfortunately not work, as BOINC must be closed before it's files can be backed up. So, the only thing that I can do is to make manual backups by shutting down BOINC first and than start the backup. It's too bad that it doesn't work any other way, but I could not think of anything else. However, I even doubt the usefulness of such backups unless they are made every hour so. Because what would it help if in case of a power failure or a system crash (or whatever else) I restore a BOINC data folder which is even not older than a day? It would bring me back work units that most probably were finished and uploaded in the meantime. Or is my thinking wrong and I am missing something? Please give me your comments. |
|
59)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68947)
Posted 12 Apr 2016 by Erich56 Post: Why haven't you just moved the whole data directory to the RAMdisk? there was a strong reason for not moving the whole BOINC data to the RAMdisk: the original intention was to have only that part of BOINC there, where there is a frequent exchange (writing, reading, deleting) of huge amounts of data (in order to avoid early wear of the SSD); and this is the SLOTS folder where ATLAS puts in the .vdi image files (between 1.3GB and 1.8GB each) for the VirtualBox. Each new task writes a new image file. Besides this, each ATLAS task requires up to 2.5 GB system RAM. The data in the PROJECTS folder, however, is very static, not much exchange at all (at least no big amounts of data are moved in there). So, in order to make best use of my 32GB RAM with a maximum of ATLAS tasks running simultaneously, it turned out that a RAMdisk size of 13.5GB is about ideal, in view of how much RAM this leaves for the system (18.5GB). In fact, it would balance out even better with 14.5GB / 17.5GB. Said the above, if I install the complete BOINC data directory to the RAMDisk, I am "wasting" some 3,5GB of RAM, so to say (I hope I was able to explain this correctly so that you understand what I mean). Do I gather from your posting that you think that the source of my problem might be that part of the BOINC data is on the SSD, and part of it is on the RAMDisk? Most probably we would only find out for sure by changing my setting to have it the way you were describing it (= all BOINC data on the RAMDisk) - I don't know. It's just too bad that it was not clear to me beforehand how much writing ATLAS is doing. With up to 200GB per day, my SSD will probably not last longer than 2 years maximum. On the other hand, most of my 32GB RAM would stay unused (which, for me personally, is even a stronger reason than the SSD wear) That's why I decided for the RAMDisk solution. |
|
60)
Message boards :
Questions and problems :
ERR_NOT_FOUND -161
(Message 68943)
Posted 12 Apr 2016 by Erich56 Post: unfortunately, I could not edit my above posting any more. Additional thought: could the problem be caused by the fact that within the BOINC folder, the "projects" folder in on the SSD, and the "slots" folder is on the ramdisk? Any argueable indication that this is not going well? |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.