Support Questions
Find answers, ask questions, and share your expertise

Job for cloudera-scm-server.service failed because the control process exited with error code. See "systemctl status cloudera-scm-server.service" and "journalctl -xe" for details.

New Contributor

ubuntu@ip-172-31-33-93:~$ systemctl status cloudera-scm-server.service
● cloudera-scm-server.service - LSB: Cloudera SCM Server
Loaded: loaded (/etc/init.d/cloudera-scm-server; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-03-15 11:06:20 UTC; 2min 23s ago
Docs: man:systemd-sysv-generator(8)
Process: 10035 ExecStart=/etc/init.d/cloudera-scm-server start (code=exited, status=1/FAILURE)

Mar 15 11:06:15 ip-172-31-33-93 systemd[1]: Starting LSB: Cloudera SCM Server...
Mar 15 11:06:15 ip-172-31-33-93 su[10062]: Successful su for cloudera-scm by root
Mar 15 11:06:15 ip-172-31-33-93 su[10062]: + ??? root:cloudera-scm
Mar 15 11:06:15 ip-172-31-33-93 su[10062]: pam_unix(su:session): session opened for user cloudera-scm by (uid=0)
Mar 15 11:06:20 ip-172-31-33-93 cloudera-scm-server[10035]: Starting cloudera-scm-server: * Couldn't start cloudera-scm-server
Mar 15 11:06:20 ip-172-31-33-93 systemd[1]: cloudera-scm-server.service: Control process exited, code=exited status=1
Mar 15 11:06:20 ip-172-31-33-93 systemd[1]: Failed to start LSB: Cloudera SCM Server.
Mar 15 11:06:20 ip-172-31-33-93 systemd[1]: cloudera-scm-server.service: Unit entered failed state.
Mar 15 11:06:20 ip-172-31-33-93 systemd[1]: cloudera-scm-server.service: Failed with result 'exit-code'.

0 REPLIES 0