Using BOINCTasks to edit config file adds invalid tags to cc_config.xml

[keithhenry]

Currently V1.73 running. Use BOINCTasks function to edit the config file (can start with a cc_config.xml that contains only tags being used (set to 1)), click on check syntax gives no errors, click apply. Go to Messages and select that same machine and you will see these errors reported by BOINC:

soval

2873859         9/4/2017 7:57:41 PM   Re-reading cc_config.xml   
2873860         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <lower_client_priority>   
2873861         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <dont_suspend_nci>   
2873862         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <dont_use_vbox>   
2873863         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <no_opencl>   
2873864         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <process_priority>   
2873865         9/4/2017 7:57:41 PM   Unrecognized tag in cc_config.xml: <process_priority_special>   
2873866         9/4/2017 7:57:41 PM   Not using a proxy   
2873867         9/4/2017 7:57:41 PM   Config: report completed tasks immediately   
2873868         9/4/2017 7:57:41 PM   Config: GUI RPC allowed from any host   
2873869         9/4/2017 7:57:41 PM   Config: GUI RPCs allowed from:   
2873870         9/4/2017 7:57:41 PM   log flags: file_xfer, sched_ops, task   

To correct, you have to shut down BOINC on each machine, manually edit cc_config.xml to remove these tags. Could these tags be for the version of BOINC with VirtualBox? I am running BOINC without that.

[fred]

To correct, you have to shut down BOINC on each machine, manually edit cc_config.xml to remove these tags. Could these tags be for the version of BOINC with VirtualBox? I am running BOINC without that.

Whey you have an older BOINC client running I expect this might happen.
The config file keeps on changing all the time.
Just tested it on my machine, no problems.

[keithhenry]

Fred, the machines that were giving these errors are all Linux machines where I only have console access. They are all running the latest BOINC version for Linux (7.2.42) but that is rather old. I shut down BOINC on one, edited the cc_config.xml file to remove these tags and any others with a 0 value. After restarting BOINC, I went in to edit the cc_config.xml file thru BOINCTasks and the screen was populated with all of the options including these that get flagged as errors. Quit out of that and checked this on one of my Windows machines (Win 10 running BOINC 7.8.2). Here's the contents of the cc_config.xml file (in /ProgramData/BOINC):

<cc_config>
    <log_flags>
    </log_flags>
    <options>
        <allow_remote_gui_rpc>1</allow_remote_gui_rpc>
        <report_results_immediately>1</report_results_immediately>
    </options>
</cc_config>

If I go edit the file via BOINCTasks, a whole bunch of tags are listed including these that BOINC is flagging as errors. As you say, the config file keeps on changing all the time. So, I looked for a way to edit the file via BOINCManager but under Options, it has an interface for just the <log_flags>. The tags flagged as invalid are all under <options>. Looking at the BOINC Wiki, some of the invalid tags are for levels after 7.2.42 but not all of them. I presume that you are getting the list of tags for the config file from BOINC somehow, otherwise, you'd be having to update BOINCTasks every time they changed/added a tag. Given that that is the case, why would a machine running 7.2.42 give you tags that were added after that version?

[fred]

Fred, the machines that were giving these errors are all Linux machines where I only have console access.

Yes, the Linux versions are much older than the Windows releases.
BoincTasks reads back all the possible tags and writes them bag.
Let's see if I can catch the invalid tags and don't write them back. I have a Linux machine here, so will try that.

[fred]

Fred, the machines that were giving these errors are all Linux machines where I only have console access. They are all running the latest BOINC version for Linux (7.2.42) but that is rather old.

OK just checked, my Ubuntu machine is using 7.6.33 that is newer than https://boinc.berkeley.edu/download_all.php That shows a very very old version.
On my Linux machine everything works as intended.

So in order for this to work you might want to switch to BoincTasks 1.69 https://efmer.com/download-boinctasks/ that should match the older BOINC version.

Please read this: https://boinc.berkeley.edu/dev/forum_thread.php?id=10803  to get a more up to date Linux version.