After a recent system update, BOINC client has been making reported some odd non-critical errors which I reported in a different thread. I rebuilt the client and manager, which didn't resolve that problem, but now I see this in the manger's version of the log:

Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max memory usage when active: 12836.66MB]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max memory usage when idle: 19254.98MB]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max disk usage: 5.00GB]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[Number of usable CPUs has changed from 6 to 5.]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max CPUs used: 5]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ suspend work if non-BOINC CPU load exceeds 90%]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max download rate: 90000 bytes/sec]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ max upload rate: 50000 bytes/sec]]>
Sat 15 Oct 2016 12:13:48 PM | | <![CDATA[ (to change preferences, visit a project web site or select Preferences in the Manager)]]>

stdoutdae.txt looks normal.

This means that your Client is newer than your Manager. A newer Manager will strip the CDATA tags from the output. Please check that you updated the Manager after rebuilding it.

Hmm, well, I just ran 'make' and both 'client/boinc' and 'clientgui/boincmgr' have the same time stamp. So, I don't *think* that is the cause of this problem in my case.

But, I did find that this happens when I start boinc client first, then start boincmgr afterward. If I start boincmgr first, this isn't a problem.

After realizing this, I checked the options for boinc. Now I'm using '--redirectio --dir .' for boinc and this effect is gone. Not 100% sure these are related, but this option fixed yet another problem I had where boinc completely stopped logging to stdoutdae.txt, which started back in June 2016.

Using this option, I get stdout logged to a file, I dont' have to start boinc/boincmgr in any order, and this data format error is gone. I haven't rebuilt either client or manager since I posted this question.