This is probably not a real problem, I don't know, but scheduler.log is filled with errors like:

tail -20 scheduler.log
2013-12-31 16:12:16.3463 [PID=14271] HOST::parse(): unrecognized: max_clock_frequency
2013-12-31 16:12:16.3463 [PID=14271] HOST::parse(): unrecognized: 2128
2013-12-31 16:12:16.3463 [PID=14271] HOST::parse(): unrecognized: /max_clock_frequency
2013-12-31 16:12:16.3463 [PID=14271] HOST::parse(): unrecognized: max_compute_units
2013-12-31 16:12:16.3463 [PID=14271] HOST::parse(): unrecognized: 2
2013-12-31 16:12:16.3464 [PID=14271] HOST::parse(): unrecognized: /max_compute_units
2013-12-31 16:12:16.3464 [PID=14271] HOST::parse(): unrecognized: opencl_platform_version
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: OpenCL 1.2 AMD-APP (1016.4)
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: /opencl_platform_version
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: opencl_device_version
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: OpenCL 1.2 AMD-APP (1016.4)
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: /opencl_device_version
2013-12-31 16:12:16.3465 [PID=14271] HOST::parse(): unrecognized: opencl_driver_version
2013-12-31 16:12:16.3466 [PID=14271] HOST::parse(): unrecognized: 1016.4 (sse2)
2013-12-31 16:12:16.3466 [PID=14271] HOST::parse(): unrecognized: /opencl_driver_version
2013-12-31 16:12:16.3466 [PID=14271] HOST::parse(): unrecognized: /opencl_cpu_info
2013-12-31 16:12:16.3466 [PID=14271] HOST::parse(): unrecognized: /opencl_cpu_prop
2013-12-31 16:12:16.4787 [PID=14271] Request: [USER#1] [HOST#23] [IP 217.77.80.29] client 7.2.33
2013-12-31 16:12:16.4995 [PID=14271] Sending reply to [HOST#23]: 0 results, delay req 121.20
2013-12-31 16:12:16.5007 [PID=14271] Scheduler ran 0.033 seconds

No one answered so I investigated by myself ;) and found what's wrong....

It's something related to the information about OpenCL CPU capabilities that are sent from the client tagged as 'opencl_cpu_prop' but parsed as 'cpu_opencl_prop' from the scheduler, thus all the errors...

This bug has already be fixed, recently, as in http://lists.ssl.berkeley.edu/pipermail/boinc_cvs/2013-December/030062.html

Now, to correct this I need to do a git pull and recompile the server (maybe only the scheduler).

I plan to do this on Thursday, next year...

This problem has been fixed after the server upgrade to the latest version.