Created 03-04-2025 07:36 PM
/etc/cloudera-scm-agent/config.ini
[General]
server_host=192.168.88.54
server_port=7182
max_collection_wait_seconds=10.0
metrics_url_timeout_seconds=30.0
task_metrics_timeout_seconds=5.0
monitored_nodev_filesystem_types=nfs,nfs4,tmpfs
local_filesystem_whitelist=ext2,ext3,ext4,xfs
impala_profile_bundle_max_bytes=1073741824
stacks_log_bundle_max_bytes=1073741824
stacks_log_max_uncompressed_file_size_bytes=5242880
orphan_process_dir_staleness_threshold=5184000
orphan_process_dir_refresh_interval=3600
scm_debug=INFO
dns_resolution_collection_interval_seconds=60
dns_resolution_collection_timeout_seconds=30
[Security]
use_tls=0
max_cert_depth=9
[Hadoop]
[Cloudera]
[JDBC]
[Cgroup_Paths]
The Internet said that the problem of auto-tls, but I did not open, try a lot of online methods can not solve, can anyone help me solve this problem
Created 03-10-2025 12:01 AM
Hello @SIGOYI if you do not have Cloudera Management service installed till this point that it is expected
You can install the same using the below steps
>> So we setup those using the API
CM UI >> Support >> API explorer >>Go to MgmtServiceResource
Here expand the PUT (/cm/service (setup the cloudera management service)
Now CMS should be setup
If this solves your problem, please accept the solution else please let me know if you have any further queries
Created 03-10-2025 12:01 AM
Hello @SIGOYI if you do not have Cloudera Management service installed till this point that it is expected
You can install the same using the below steps
>> So we setup those using the API
CM UI >> Support >> API explorer >>Go to MgmtServiceResource
Here expand the PUT (/cm/service (setup the cloudera management service)
Now CMS should be setup
If this solves your problem, please accept the solution else please let me know if you have any further queries
Created 03-10-2025 12:40 AM
Hello @upadhyayk04
oh.thank you so much,i can open it
Created 03-10-2025 12:42 AM
Thanks, @SIGOYI, for the update. Glad to know that the issue is fixed now