Starting just after the shutdown for maintenance ended and SETI came up, I began getting these error messages:

8/27/2014 3:48:42 AM | SETI@home | Project is temporarily shut down for maintenance
8/27/2014 5:19:58 AM | SETI@home | Sending scheduler request: To report completed tasks.
8/27/2014 5:19:58 AM | SETI@home | Reporting 61 completed tasks
8/27/2014 5:19:58 AM | SETI@home | Requesting new tasks for NVIDIA
8/27/2014 5:20:08 AM | SETI@home | [unparsed_xml] SCHEDULER_REPLY::parse(): unrecognized external_cpid
8/27/2014 5:20:08 AM | SETI@home | [unparsed_xml] SCHEDULER_REPLY::parse(): unrecognized 691ad2c6efaecd5462fb95dc278885bb
8/27/2014 5:20:08 AM | SETI@home | [unparsed_xml] SCHEDULER_REPLY::parse(): unrecognized /external_cpid
8/27/2014 5:20:08 AM | SETI@home | Scheduler request completed: got 1 new tasks

Before this time, no error messages. Is this causing a problem somewhere that I don't see it?

Whatever it is, it happens on the server. I forwarded this to the admins.

---

It is not just Seti@home. I have recently seen the same "unparsed" message returned in a NFS@home sched_reply...xml string. I don't have "sched_reply" warnings back very far (via stdoutdae.txt) but I think this has been appearing in my event log for quite some time -- maybe a couple(?) of months. I have boinc manager 7.2.42 . It seems harmless as far as I can tell, i.e. an informative message rather than a fault. And I just assumed it was some new feature introduced in the servers that would go away some day when I upgrade boincmgr.

---