Messages

Problem resolved. Just in case someone else has the problem, this is what is all was. Two machines involved, both Ubuntu boxes, no GUI, command line only. Had done the BOINCCMD --program_attach command from these boxes instead of through BOINC or BOINCTASKS. A fresh look resulted in another oh geez moment. There was a very obscure typo in the URL used. Detaching via the console using the same bad url fixed. Apparently cataract surgery only improves your vision, not the eye-brain coordination.

Normally, you can right click on an entry shown on the projects tab to take actions for a project on a specific computer. I have two entries that are "dead". Right clicking on either does nothing. No pop up listing actions you can take. I would like to remove these two entries. I expect that I will need to shut down BT and BOINC as well, make a backup copy of the relevant file, and then very carefully edit the file to do this. I suspect it's a BOINC file but have been unable to determine which one. Can someone point me to the right file?

FWIW, the two entries are for computers I was trying to attach to WCG during its move. I think neither entry ever got processed which may account for why nothing happens when right clicking on either.

Thx,
Keith

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?

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.

I've seen this quite frequently with BOINCTasks. On the Tasks page, the Status column can show either "Running" or "Running High P." When I go to BOINCManager on that machine, it shows "Running" when BOINCTasks is showing "Running High P." I think if you change your WU cache size in the BOINC profile for that machine, it can cause BOINCTasks to change the status for a task from running to running high p or vice versa. I would not expect there to be any difference.

Click on Extra, BOINCTasks Settings, View tab, set Refresh rate to Manual and some number of seconds. Update BOINCTasks (eg, V1.71 to 1.72) and this setting is set back to the default instead of being preserved. Currently running 1.73 and same problem occurred after updating from 1.72.

Okay, sorted out an issue with my wireless routers that probably affected this. I've got both computers using the main router now so I know both IPs are good. both Win boxes can connect to each other. Added the IPs to the remote_hosts.cfg, removed the allow_remote_gui_rpc completely in cc_config.xml and used both a blank and a password (in a separate attempt) in gui_rpc_auth.cfg (all in /etc/boinc-client). Turned on connecting logging in BT's logging and get

Connect, read error ---- Host: ugm-tuvok-o, IP: 192.169.171.240, Port: 31416, read error -102

each time it tries to connect. Checked /var/lib/boinc-client and all three files have lrwxrwxrwx for permissions. Going back to the old way for now.

[as long]

Ok, got access to a Ubuntu 14.04 linux server (console only) so I went with BT to manage BOINC on it. I have BT connecting to it fine as long as I stick with the blank password file and use allow_remote_gui_rpc 1 in the cc_config.xml file. I'd like to use the IP address in the remote host file, a non-blank password and allow_remote_gui_rpc 0 but it won't connect that way. I tried using the value ipconfig gave for IPV4 address on the wintel box running BT. Is there an issue with linux using a non-blank password? The file was empty in the beginning whereas it has something random looking in it on windows. I'm presuming there must be something wrong with the IP address. What's the best way for me to sort this out? thx!