| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: BOINC Client 7.24.1 and non-default profiles |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 885 Status: Offline Project Badges: 
|
Some further diagnostic information, edited to point out that I might have identified the problem:
----------------------------------------I had a [brief] look at the sources for client 7.20.5 and 7.24.1 as held in Ubuntu's repositories, and there's a lot of re-organization of the code for when global prefs or venue changes occur. It would appear that without a viable modified time the newer client thinks there's a change even when there isn't -- having the client think the global prefs were modified at time zero is not a good thing!... I have a 7.24.1 client in a VM that I use for testing without risk to production systems; I forced it to get global preferences from a site other than WCG (TN-Grid) so I could monitor sched_reply files from a "standard" BOINC. As expected, when changes are made to the "global preferences" aspect of a venue and an update is done there is a global_preferences block in the sched_reply file and the first item is the mod_time. However, if I force a change to the same venue profile on WCG and update the client there is a global_preferences section but the mod_time appears at the end of that section! I have finally located the client source file that parses global preferences, and it appears that if it finds a <venue> tag that matches the current venue it parses that block and stops when it sees the </venue> tag. Anything after that will, therefore, be ignored. However, if the default profile is current any venue sections will be skipped so it would see the mod_time wherever it appeared within the global_preferences block. As far as I'm concerned this is not a bug in the client :-) so the fix is to make sure that the <mod_time> tag in global preferences appears at the top! For now, my work-around is to force the client to get the global preferences from a non-WCG site, but it's going to be a nuisance when I eventually update systems to the latest Ubuntu releases and have no option but to use client 7.24.x... Cheers - Al P.S. If someone expert on BOINC client happens to see this and can confirm what I seem to have found, input would be welcome :-) [Edit 2 times, last edit by alanb1951 at Apr 21, 2024 12:56:33 AM] |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 603 Status: Offline Project Badges: 
|
Ever since I updated to 7.24.1 this machine suspends itself for about 20 seconds. And it seems to do it every time it uploads a file. This never happened before 7.24.1.
----------------------------------------It's the only one with only 16GB memory. The other two have 32GB. Most of the memory is free as seen below in top. The suspend when non-Boinc CPU usage is above is set at 50%. I tried 90% and no difference. 2024-05-04 21:21:25 | | Processor: 12 AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor [Family 23 Model 113 Stepping 0] 2024-05-04 21:21:25 | | OS: Linux Ubuntu: Ubuntu 22.04.4 LTS [5.15.0-105-generic|libc 2.35] 2024-05-04 21:21:25 | | Memory: 15.52 GB physical, 2.00 GB virtual 2024-05-04 21:21:25 | | Disk: 227.68 GB total, 194.68 GB free ... ... ... 2024-05-05 9:38:23 | World Community Grid | Computation for task MCM1_0216456_6639_1 finished 2024-05-05 9:38:23 | World Community Grid | Starting task MCM1_0216452_4166_0 2024-05-05 9:38:26 | World Community Grid | Started upload of MCM1_0216456_6639_1_r954305562_0 2024-05-05 9:38:28 | World Community Grid | Finished upload of MCM1_0216456_6639_1_r954305562_0 (625 bytes) 2024-05-05 9:38:33 | | Suspending computation - CPU is busy 2024-05-05 9:38:53 | | Resuming computation 2024-05-05 9:50:27 | World Community Grid | Computation for task MCM1_0216451_4306_1 finished 2024-05-05 9:50:27 | World Community Grid | Starting task MCM1_0216450_3973_1 2024-05-05 9:50:29 | World Community Grid | Started upload of MCM1_0216451_4306_1_r2115721206_0 2024-05-05 9:50:31 | World Community Grid | Finished upload of MCM1_0216451_4306_1_r2115721206_0 (575 bytes) 2024-05-05 9:50:36 | | Suspending computation - CPU is busy 2024-05-05 9:50:56 | | Resuming computation 2024-05-05 9:52:50 | World Community Grid | Computation for task MCM1_0216456_6641_1 finished 2024-05-05 9:52:50 | World Community Grid | Starting task MCM1_0216455_6525_0 2024-05-05 9:52:52 | World Community Grid | Started upload of MCM1_0216456_6641_1_r340529015_0 2024-05-05 9:52:54 | World Community Grid | Finished upload of MCM1_0216456_6641_1_r340529015_0 (1337 bytes) 2024-05-05 9:52:57 | | Suspending computation - CPU is busy 2024-05-05 9:53:17 | | Resuming computation top - 10:26:21 up 13:06, 2 users, load average: 14.39, 14.17, 14.05 Tasks: 269 total, 13 running, 256 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy,100.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15894.7 total, 13765.6 free, 721.8 used, 1407.3 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 14849.6 avail Mem [Edit 1 times, last edit by BobbyB at May 5, 2024 2:41:50 PM] |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2106 Status: Recently Active Project Badges: 
|
Ever since I updated to 7.24.1 this machine suspends itself for about 20 seconds. And it seems to do it every time it uploads a file. (…) The suspend when non-Boinc CPU usage is above is set at 50%. I tried 90% and no difference. BobbyB, Have you tried unticking "Suspend when non-BOINC usage is above ___ %"? Adri |
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 885 Status: Offline Project Badges:
|
A [late] footnote [2024-10-21]...
I have recently arrived at a situation where I must be able to use named profiles for WCG on some of my systems and will sometimes be changing details therein. It appears that WCG and Einstein both have the "venue data in the middle of the global preferences instead of at the end" problem, whilst MilkyWay and CPDN are two examples of sites with fairly recent servers that don't have the issue. And some of my clients only access WCG and Einstein... Out of self-defence, I eventually spent a couple of days ploughing through the source of client 7.24.1 to see if I could stop it losing the mod_time (and hence sending a zero mod_time in every scheduler request, resulting in every reply containing global preferences -- rinse and repeat...); just suppressing the writes to the BOINC log wouldn't stop the sending back of zero mod_time, so that wasn't a fix candidate. I eventually decided on some patches that work in my situation[*1], applied them and the mod_time is now collected correctly (and reported back in scheduler requests), even if the profile is for a named venue... I don't know whether the placement of part of the global preferences after the venue data in a scheduler reply is a server "feature" or the result of some server site-specific configuration stuff (see above about CPDN and MilkyWay not being affected!), so I can't decide whether the BOINC folks should be fixing up the clients to match! And I don't intend to spend a lot of my [non-existent] spare time and effort trying to persuade the BOINC folks that there's a problem as no-one else appeared to have reported it as a client issue... Cheers - Al. *1 -- I usually use local preferences so if my fix has messed anything up regarding web preferences it might not show up. However, I think that shouldn't be the case, and I might test it some time :-) |
||
|
|
|