The solution was to deploy CSD of new service. Then, it's possible to select new service type and add new service of this type. ... View more

@rok Perhaps.    I think the place to begin would be to look at this:   STACKTRACE=[java.io.IOException: Server returned HTTP response code: 403 for URL: http://cloudera_manager_ip:7180/cmf/j_spring_security_check   …and figure out why the access request to that URL is being denied with an HTTP 403 Forbidden client error. Is that URL accessing a host on your network, or the host running Cloudera Manager?     ... View more

@rok The Threshold value look less here. To avoid getting the reported health alerts we recommend to increase the corresponding configuration values: CM -> Cloudera Management Services -> Configuration -> Search for "Descriptor Fetch Max Tries" CM -> Cloudera Management Services -> Configuration -> Event Server -> Search for "Descriptor Fetch Tries Interval" and change this value for all the roles. We would recommend to increase the "Descriptor Fetch Max Tries" value from the default 5 to 10 in a first step. I after that you are facing the issue than you should look at the agent logs and start from there.  ... View more

@rok,   Also, I would like to let you know that there are few services (Most of the CSD-based) where the Role log file is not supported in UI neither we can enable it. The only way is to manually go into the host and see logs in needed.   ... View more

Start with the CM server log at   /var/log/cloudera-scm-server/cloudera-scm-server.log   and then look at agent logs at    /var/log/cloudera-scm-agent/cluster-scm-agent.log   Mike ... View more

Currently, the way i'm going to take is mimic deploy client configuration  operation on single host:   Auto recreating links using script: /etc/stack/service-env/conf -> /etc/alternatives/service-env-conf  -> /etc/stack/service-env/conf.cloudera.service-env and updating or creating client config file /etc/stack/service-env/conf/conf.properties. ... View more