| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Devices STILL Not Acknowledged |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
jmcgaw
Advanced Cruncher US Joined: Feb 2, 2007 Post Count: 54 Status: Offline Project Badges: 
|
If only it were so simple. There IS a reason I asked about clearing the log file: I had previously followed the path of copying the file and dropping it into a text file. What I find is that the log file has content running back into yesterday and is 2001l lines long. Stopping the BOINC client software did nothing to clear the log and the host name string doesn't appear (I did a search for "host" in the log file and it was not found.
So, how do I get rid of all of the detritus in the old log file so that I can make a fresh start? Y'know, it really shouldn't be this difficult to do what should be a relatively simple task.This machine is pumping 24 MCM tasks roughly every two hours and I'd like to know that they are not simply vanishing into the ether since electrical power is not free and I'd like to think it is not a total waste. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges: 
|
So, how do I get rid of all of the detritus in the old log file so that I can make a fresh start? The simplest way I know is to do an orderly shutdown of the machine. Then restart it. When I shut down my Windows machine each night and then restart it in the morning, the log starts anew. On my Linux machines which run 24/7 the logs just continue to grow. It does not hurt to periodically shut down your machines and give them a fresh start from time to time. Clears out some detritus so to speak. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 638 Status: Offline Project Badges: 
|
All this stuff in in client_state.xml.
Under <host_info> is <domain_name>XXXXXXXX</domain_name>. This is name by which the machine was named at install time and what, for me, shows on this site as Device name. /var/lib/boinc-client on Linux; C:\ProgramData\boinc on Windows. Search for <project> in this same file for <project_name>World Community Grid</project_name>. <hostid> is what you want for device id. All kinds of info in there also. OR In Boincmgr click WCG in the Projects tab then click properties in the commands on the left. Computer ID = <hostid> in client_state.xml = device id in WCG site. Yes, the names are not consistent. No need to boot the machines. |
||
|
|
jmcgaw
Advanced Cruncher US Joined: Feb 2, 2007 Post Count: 54 Status: Offline Project Badges:
|
I believe that this is futile in my case. The entire beginning of the file is missing. I believe that the client keeps a rolling log, dropping early entries at the head as later entries are added at the tail. Since this machine processes so many tasks at a time the file gets rolled over very quickly. I have no idea how soon I'd have to get to the log if the log file was purged so that the needed information would still be visible -- certainly within a few hours.
|
||
|
|
jmcgaw
Advanced Cruncher US Joined: Feb 2, 2007 Post Count: 54 Status: Offline Project Badges:
|
Good idea. I'll give that a try when I can and hope for the best. Perhaps if I get to the log file before it gets rolled over the needed information will still be there.
----------------------------------------+++++++++++++++++++++++++++++++++ That worked! It seems so simple now that you've revealed the secret handshake. I managed to grab a snapshot of the log within perhaps 15 seconds of the client starting. +++++++++++++++++++++++++++++++++ [Edit 1 times, last edit by jmcgaw at Nov 8, 2023 2:28:10 PM] |
||
|
|
|