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. Want to know more about what has changed? Check out the Community News blog.

Failed to start LSB: Cloudera SCM Agent.

Failed to start LSB: Cloudera SCM Agent.

Contributor
 

Hi,

 

I am getting this error during installation:

 

 

 

  ------------------------------------------------------------------------------------------------------ Starting Cloudera Manager Agent...

BEGIN /sbin/service cloudera-scm-agent status
● cloudera-scm-agent.service - LSB: Cloudera SCM Agent
Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-agent)
Active: failed (Result: exit-code) since Wed 2016-09-14 07:25:09 EDT; 2min 53s ago
Docs: man:systemd-sysv-generator(8)

Sep 14 07:25:09 VM03_cent7 systemd[1]: Starting LSB: Cloudera SCM Agent...
Sep 14 07:25:09 VM03_cent7 su[20999]: (to root) root on none
Sep 14 07:25:09 VM03_cent7 cloudera-scm-agent[20986]: Starting cloudera-scm-agent: [FAILED]
Sep 14 07:25:09 VM03_cent7 systemd[1]: cloudera-scm-agent.service: control process exited, code=exited status=1
Sep 14 07:25:09 VM03_cent7 systemd[1]: Failed to start LSB: Cloudera SCM Agent.
Sep 14 07:25:09 VM03_cent7 systemd[1]: Unit cloudera-scm-agent.service entered failed state.
Sep 14 07:25:09 VM03_cent7 systemd[1]: cloudera-scm-agent.service failed.
Sep 14 07:27:01 VM03_cent7 systemd[1]: Stopped LSB: Cloudera SCM Agent.
Sep 14 07:27:02 VM03_cent7 systemd[1]: Stopped LSB: Cloudera SCM Agent.
Sep 14 07:27:45 VM03_cent7 systemd[1]: Stopped LSB: Cloudera SCM Agent.
END (3)
BEGIN /sbin/service cloudera-scm-agent start
Starting cloudera-scm-agent (via systemctl): Job for cloudera-scm-agent.service failed because the control process exited with error code. See "systemctl status cloudera-scm-agent.service" and "journalctl -xe" for details.

nt.

8 REPLIES 8

Re: Failed to start LSB: Cloudera SCM Agent.

Contributor

not much detail

 

 

 

[root@VM03_cent7 /]# systemctl status cloudera-scm-agent.service


â cloudera-scm-agent.service - LSB: Cloudera SCM Agent
Loaded: loaded (/etc/rc.d/init.d/cloudera-scm-agent)
Active: failed (Result: exit-code) since Wed 2016-09-14 07:28:04 EDT; 9min ago
Docs: man:systemd-sysv-generator(8)
Process: 22595 ExecStart=/etc/rc.d/init.d/cloudera-scm-agent start (code=exited, status=1/FAILURE)

Sep 14 07:28:03 VM03_cent7 systemd[1]: Starting LSB: Cloudera SCM Agent...
Sep 14 07:28:03 VM03_cent7 su[22608]: (to root) root on none
Sep 14 07:28:04 VM03_cent7 cloudera-scm-agent[22595]: Starting cloudera-scm-agent: [FAILED]
Sep 14 07:28:04 VM03_cent7 systemd[1]: cloudera-scm-agent.service: control process exited, code=exited status=1
Sep 14 07:28:04 VM03_cent7 systemd[1]: Failed to start LSB: Cloudera SCM Agent.
Sep 14 07:28:04 VM03_cent7 systemd[1]: Unit cloudera-scm-agent.service entered failed state.
Sep 14 07:28:04 VM03_cent7 systemd[1]: cloudera-scm-agent.service failed.

Re: Failed to start LSB: Cloudera SCM Agent.

Contributor

Not sure what does this mean.

 

 

 

 

 

 

Sep 14 07:28:04 VM03_cent7 systemd[1]: Failed to start LSB: Cloudera SCM Agent.
-- Subject: Unit cloudera-scm-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cloudera-scm-agent.service has failed.
--
-- The result is failed.
Sep 14 07:28:04 VM03_cent7 systemd[1]: Unit cloudera-scm-agent.service entered failed state.
Sep 14 07:28:04 VM03_cent7 systemd[1]: cloudera-scm-agent.service failed.
Sep 14 07:28:04 VM03_cent7 polkitd[684]: Unregistered Authentication Agent for unix-process:22590:1137494 (system bus name :1.71, object path /org/freedesktop/PolicyKit1/Authent
lines 1434-1486/1486 (END)
Sep 14 07:27:53 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +cloudera-scm-server-db.service, ignoring: Invalid argument
Sep 14 07:27:53 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +mysql.service, ignoring: Invalid argument
Sep 14 07:27:53 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +postgresql.service, ignoring: Invalid argument
Sep 14 07:27:53 VM03_cent7 systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Pr
Sep 14 07:27:53 VM03_cent7 systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 14 07:27:53 VM03_cent7 polkitd[684]: Unregistered Authentication Agent for unix-process:21924:1136456 (system bus name :1.69, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C) (disconnected
Sep 14 07:27:56 VM03_cent7 polkitd[684]: Registered Authentication Agent for unix-process:22090:1136720 (system bus name :1.70 [/usr/bin/pkttyagent --notify-fd 6 --fallback], object path /org/freedesktop/PolicyKit1/
Sep 14 07:27:56 VM03_cent7 systemd[1]: Reloading.
Sep 14 07:27:56 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +cloudera-scm-server-db.service, ignoring: Invalid argument
Sep 14 07:27:56 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +mysql.service, ignoring: Invalid argument
Sep 14 07:27:56 VM03_cent7 systemd[1]: [/run/systemd/generator.late/cloudera-scm-server.service:8] Failed to add dependency on +postgresql.service, ignoring: Invalid argument
Sep 14 07:27:56 VM03_cent7 systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Pr
Sep 14 07:27:56 VM03_cent7 systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 14 07:27:56 VM03_cent7 polkitd[684]: Unregistered Authentication Agent for unix-process:22090:1136720 (system bus name :1.70, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale C) (disconnected
Sep 14 07:28:03 VM03_cent7 polkitd[684]: Registered Authentication Agent for unix-process:22590:1137494 (system bus name :1.71 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/
Sep 14 07:28:03 VM03_cent7 systemd[1]: Starting LSB: Cloudera SCM Agent...
-- Subject: Unit cloudera-scm-agent.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cloudera-scm-agent.service has begun starting up.
Sep 14 07:28:03 VM03_cent7 su[22608]: (to root) root on none
Sep 14 07:28:03 VM03_cent7 systemd[1]: Started Session c10 of user root.
-- Subject: Unit session-c10.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c10.scope has finished starting up.
--
-- The start-up result is done.
Sep 14 07:28:03 VM03_cent7 su[22608]: pam_unix(su:session): session opened for user root by (uid=0)
Sep 14 07:28:03 VM03_cent7 systemd[1]: Starting Session c10 of user root.
-- Subject: Unit session-c10.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c10.scope has begun starting up.
Sep 14 07:28:04 VM03_cent7 cmf-agent[22622]: Starting daemon.
Sep 14 07:28:04 VM03_cent7 cmf-agent[22622]: Stopping daemon.
Sep 14 07:28:04 VM03_cent7 su[22608]: pam_unix(su:session): session closed for user root
Sep 14 07:28:04 VM03_cent7 cloudera-scm-agent[22595]: Starting cloudera-scm-agent: [FAILED]
Sep 14 07:28:04 VM03_cent7 systemd[1]: cloudera-scm-agent.service: control process exited, code=exited status=1
Sep 14 07:28:04 VM03_cent7 systemd[1]: Failed to start LSB: Cloudera SCM Agent.
-- Subject: Unit cloudera-scm-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit cloudera-scm-agent.service has failed.
--
-- The result is failed.
Sep 14 07:28:04 VM03_cent7 systemd[1]: Unit cloudera-scm-agent.service entered failed state.
Sep 14 07:28:04 VM03_cent7 systemd[1]: cloudera-scm-agent.service failed.
Sep 14 07:28:04 VM03_cent7 polkitd[684]: Unregistered Authentication Agent for unix-process:22590:1137494 (system bus name :1.71, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en

Re: Failed to start LSB: Cloudera SCM Agent.

Super Guru

check selinux:

 

sestatus

 

It can cause problems like this

Re: Failed to start LSB: Cloudera SCM Agent.

Explorer

Hello,

           could you post the log in directory : /var/log/cloudera-scm-agent ?

 

Regards

Re: Failed to start LSB: Cloudera SCM Agent.

Contributor

Thanks, i found in another post about having underscore in the hostname, after changed that i passed this and can move forward.

 

Shannon

Highlighted

Re: Failed to start LSB: Cloudera SCM Agent.

New Contributor

Can you post the link

Re: Failed to start LSB: Cloudera SCM Agent.

LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: could not resolve "localhost": Temporary failure in name resolution
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2018-04-14 23:21:00 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down
LOG: could not resolve "localhost": Temporary failure in name resolution
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2018-04-14 23:41:37 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down

Re: Failed to start LSB: Cloudera SCM Agent.

LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
LOG: could not resolve "localhost": Temporary failure in name resolution
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2018-04-14 23:21:00 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down
LOG: could not resolve "localhost": Temporary failure in name resolution
LOG: disabling statistics collector for lack of working socket
WARNING: autovacuum not started because of misconfiguration
HINT: Enable the "track_counts" option.
LOG: database system was shut down at 2018-04-14 23:41:37 IST
LOG: MultiXact member wraparound protections are now enabled
LOG: database system is ready to accept connections
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down