@SandeepSingh This looks like the issue with TLS.
Eventhough the flag 'Use TLS Authentication of Agents to Server' in CM WebUI is not set, the following flag must be set for status_server to use TLS protocol using port 9000. Go to the /opt/cloudera/security/x509/ directory and use 'pem' and 'key' file under that directory. You may also have to use the password file for the private key if there is one.
Then edit the /etc/cloudera-scm-agent/config.ini file with below parameters.
# PEM file containing client private key.
# If client_keypw_cmd isn't specified, instead a text file containing the client private key password can be used.
# PEM file containing client certificate.
Restart of the status_server is required
/opt/cloudera/cm-agent/bin/supervisorctl -c /var/run/cloudera-scm-agent/supervisor/supervisord.conf restart status_server
In addition, restart of the cloudera-scm-agent is also needed
service cloudera-scm-agent restart
@GangWar Thanks for your suggestion.
All the parameters except the following one were already set in /etc/cloudera-scm-agent/config.ini
Apparently, the only reason why agent wasn't serving requests for logs was because the above flat wasn't set.
The moment we configured the flag verify_cert_file and restarted agent, it started serving logs correctly.