Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Supervisord failed. Restarting Agent

Supervisord failed. Restarting Agent

New Contributor

Hi,

 

I am just wondering if any of the CDH role processes exited unexpectedly can cause the supervisord to fail? In my case, I am seeing a kudu TServer exited unexpectedly. Then the supervisord failed.

 cloudera-scm-agent.log

[17/Nov/2017 01:37:53 +0000] 184210 MonitorDaemon-Reporter proc_metrics_utils ERROR    Failed to read file descriptor max for process 12714: [Errno 2] No such file or directory: '/proc/12714/limits'
[17/Nov/2017 01:37:53 +0000] 184210 MonitorDaemon-Reporter proc_metrics_utils ERROR    Failed to get file descriptor count for process 12714: [Errno 2] No such file or directory: '/proc/12714/fd/'
[17/Nov/2017 01:37:53 +0000] 184210 MonitorDaemon-Reporter proc_metrics_utils ERROR    Failed to get process metrics 12714: no process found with pid 12714
[17/Nov/2017 01:37:54 +0000] 184210 MainThread agent        INFO     PID '12714' associated with process '3411-kudu-KUDU_TSERVER' with payload 'processname:3411-kudu-KUDU_TSERVER groupname:3411-kudu-KUDU_TSERVER from_state:RUNNING expected:0 pid:12714' exited unexpectedly
[17/Nov/2017 01:37:54 +0000] 184210 MainThread agent        WARNING  Supervisor failed (pid 33293).  Restarting agent.