Sometimes, This occurs if the agent cannot write data under /opt/cloudera/parcels/.flood, if your parcel is using by the other hosts, don't deactivate parcel as first step. Check directory space and delete /opt/cloudera/parcels/.flood folder and restart the agent. ... View more

What action triggered the stacktrace? The stacktrace is from deep within Spring and suggests system level issue, e.g. out of memory. A few things to check: - server log (/var/log/cloudera-scm-server/cloudera-scm-server.log) - management daemon logs (/var/log/cloudera-scm-firehose/*.log - check "Hosts"->"All Hosts" for memory pressure. The "Resources" tab of individual Host page may help as well  ... View more

You can fix it this way: 1. Determine name of the ALERTPUBLISHER role. Go to ${your-scm-host}:7180/api/v1/cm/service/roles/ Find json with name like '"name" : "mgmt1-ALERTPUBLISHER-107a27c5a1fc39a5cb9ce9ea1947e296",' 2. Using name from step 1, do the following: curl -X PUT -H "Content-Type:application/json" -u admin:admin -d '{"items": [{"name" : "alert_mailserver_password", "value": "SUPER_MEGA_PASSWORD"}]}' '${your-scm-host}:7180/api/v1/cm/service/roles/mgmt1-ALERTPUBLISHER-107a27c5a1fc39a5cb9ce9ea1947e296/config' ... View more