http error 404 on all scheduler logs I tried, e.g. this one.
Bug or intentionally removed?
Michael
My guess is turned off temporarily during the transition period. I still have some available for contacts a day or so earlier than that.
Hopefully they will get turned back on since it sure comes in handy when troubleshooting to see what the scheduler thought was going on in addition to what the CC tells you in the local logs. ;-)
Hopefully they will get turned back on since it sure comes in handy when troubleshooting to see what the scheduler thought was going on in addition to what the CC tells you in the local logs. ;-)
Time for dumb question. I see "CC" listed in posts all over the place but I am unable to decipher the meaning. Can someone please clue me in to what "CC" is referring to in these posts?
Hopefully they will get turned back on since it sure comes in handy when troubleshooting to see what the scheduler thought was going on in addition to what the CC tells you in the local logs. ;-)
Time for dumb question. I see "CC" listed in posts all over the place but I am unable to decipher the meaning. Can someone please clue me in to what "CC" is referring to in these posts?
BOINC exists in two parts in a client/server relationship. The two parts regularly communicate with each other in order to keep all your science applications happy (download new work and upload results, etc). The part that runs on your machine is the BOINC client which used to be called the 'Core Client' - hence the acronym.
The part that runs on the server contains various daemons (background processes) like work unit generators, schedulers, transitioners, feeders, validators, database purgers, etc, all of which are capable of producing logs which can be analysed to diagnose problems, fine-tune performance, etc. The scheduler logs are of particular importance to users since they contain the 'other side' of your BOINC client's communications with the servers. You can always see your side in BOINC Manager's messages tab (also in various text files in your BOINC folder).
To prepare the scheduler logs for user consumption and analysis, a homegrown script is normally run regularly by the project. It has been found recently that this script is chewing up resources at a time when the project can't afford the extra load. The script has been suspended until it can be rewritten so as not to be a resource hog. Hopefully this is just a temporary suspension.
scheduler logs gone?
)
My guess is turned off temporarily during the transition period. I still have some available for contacts a day or so earlier than that.
Hopefully they will get turned back on since it sure comes in handy when troubleshooting to see what the scheduler thought was going on in addition to what the CC tells you in the local logs. ;-)
Alinator
Hopefully they will get
)
Hopefully they will get turned back on since it sure comes in handy when troubleshooting to see what the scheduler thought was going on in addition to what the CC tells you in the local logs. ;-)
Time for dumb question. I see "CC" listed in posts all over the place but I am unable to decipher the meaning. Can someone please clue me in to what "CC" is referring to in these posts?
Thanks for taking the time,
Dana
RE: RE: Hopefully they
)
BOINC exists in two parts in a client/server relationship. The two parts regularly communicate with each other in order to keep all your science applications happy (download new work and upload results, etc). The part that runs on your machine is the BOINC client which used to be called the 'Core Client' - hence the acronym.
The part that runs on the server contains various daemons (background processes) like work unit generators, schedulers, transitioners, feeders, validators, database purgers, etc, all of which are capable of producing logs which can be analysed to diagnose problems, fine-tune performance, etc. The scheduler logs are of particular importance to users since they contain the 'other side' of your BOINC client's communications with the servers. You can always see your side in BOINC Manager's messages tab (also in various text files in your BOINC folder).
To prepare the scheduler logs for user consumption and analysis, a homegrown script is normally run regularly by the project. It has been found recently that this script is chewing up resources at a time when the project can't afford the extra load. The script has been suspended until it can be rewritten so as not to be a resource hog. Hopefully this is just a temporary suspension.
Cheers,
Gary.