right.  restarting cloudera-scm-server fixed the problem, but it came back a few days later.   then we remembered to end the edh trial period (via cm..administration..license..)   [http://www.cloudera.com/documentation/enterprise/5-7-x/topics/cm_ag_licenses.html#cmug_topic_13_7__section_gd2_ql1_fn]   it looks this resolved the issue.  at least we haven't seen it since.     we are running cm 5.7.1 the cluster is running cdh 5.7.1 on a cluster that was upgraded from cdh 5.4.3   apparently the upgrade process restarted the trial period, but not completely or correctly.   ... View more

we saw this on 5.7.0 as well.  same problem after upgrading to 5.7.1:   Error 500: Error creating bean with name 'newServiceHandlerRegistry' ...   workaround seems to be restarting the cloudera-scm-server service.   root cause still unknown though.   ... View more