FAQ
Relatively new at hadoop, installed Cloudera on single-node debian SQUEEZE,
message "Health checks are not currently available. View the status of
Service Monitor." How to tell why Service Monitor failed to start?

Search Discussions

  • Darren Lo at Jul 10, 2013 at 7:53 pm
    Do you have Management Services installed? If not, there will be a button
    to Add Management Services in the upper right of your main page in the CM
    UI.

    If they are installed, you can click on the Service Monitor and look
    through the health checks and logs. The Processes tab is likely very useful
    for logs (available after clicking on a role, such as Service Monitor).

    Thanks,
    Darren

    On Wed, Jul 10, 2013 at 11:03 AM, Art Huston wrote:

    Relatively new at hadoop, installed Cloudera on single-node debian
    SQUEEZE, message "Health checks are not currently available. View the
    status of Service Monitor." How to tell why Service Monitor failed to start?

    --
    Thanks,
    Darren
  • Darren Lo at Jul 12, 2013 at 10:46 pm
    Hi Art,
    (Adding back scm-users)

    When you click on your management service and look at the config page, do
    you see any configuration errors?

    What do the logs for the individual management roles say? You can find them
    by clicking on the role, then click on Processes, then you can see the
    stderr, stdout, and role log file links. These are different log files from
    what you posted, which looks like the main CM server log file.

    Thanks,
    Darren

    On Fri, Jul 12, 2013 at 2:58 PM, Art Huston wrote:

    Hi Darren,

    The Management Services are installed, there is no button to Add
    Management Services.

    When I try to restart the service from the Management Control Panel, I
    get this in the log file:

    2013-07-12 17:56:10,841 ERROR
    [45060432@scm-web-12:cmf.WebController@322] Exception occurred when
    checking the service health of mgmt1
    2013-07-12 17:56:22,045 INFO
    [CommandPusher:service.AbstractBringUpBringDownCommands@607] Aborting
    BringUp command (83) on service DbService{id=24, name=mgmt1,
    serviceType=MGMT, optimisticLockVersion=1, cluster=null,
    maintenanceCount=0} role DbRole{id=52,
    name=mgmt1-ACTIVITYMONITOR-83cdf95375ed2c9c250ef8a42f5c85d5,
    hostId=debian01.arthuston.com, roleType=ACTIVITYMONITOR,
    configuredStatus=STARTING, configGeneration=6, service=mgmt1,
    maintenanceCount=0, decommissionCount=0}.
    2013-07-12 17:56:22,053 INFO
    [CommandPusher:service.AbstractBringUpBringDownCommands@607] Aborting
    BringUp command (79) on service DbService{id=24, name=mgmt1,
    serviceType=MGMT, optimisticLockVersion=1, cluster=null,
    maintenanceCount=0} role DbRole{id=50,
    name=mgmt1-HOSTMONITOR-83cdf95375ed2c9c250ef8a42f5c85d5,
    hostId=debian01.arthuston.com, roleType=HOSTMONITOR,
    configuredStatus=STARTING, configGeneration=6, service=mgmt1,
    maintenanceCount=0, decommissionCount=0}.
    2013-07-12 17:56:22,054 INFO
    [CommandPusher:service.AbstractBringUpBringDownCommands@607] Aborting
    BringUp command (81) on service DbService{id=24, name=mgmt1,
    serviceType=MGMT, optimisticLockVersion=1, cluster=null,
    maintenanceCount=0} role DbRole{id=53,
    name=mgmt1-ALERTPUBLISHER-83cdf95375ed2c9c250ef8a42f5c85d5,
    hostId=debian01.arthuston.com, roleType=ALERTPUBLISHER,
    configuredStatus=STARTING, configGeneration=0, service=mgmt1,
    maintenanceCount=0, decommissionCount=0}.
    2013-07-12 17:56:22,054 INFO
    [CommandPusher:service.AbstractBringUpBringDownCommands@607] Aborting
    BringUp command (80) on service DbService{id=24, name=mgmt1,
    serviceType=MGMT, optimisticLockVersion=1, cluster=null,
    maintenanceCount=0} role DbRole{id=51,
    name=mgmt1-EVENTSERVER-83cdf95375ed2c9c250ef8a42f5c85d5,
    hostId=debian01.arthuston.com, roleType=EVENTSERVER,
    configuredStatus=STARTING, configGeneration=1, service=mgmt1,
    maintenanceCount=0, decommissionCount=0}.
    2013-07-12 17:56:22,054 INFO
    [CommandPusher:service.AbstractBringUpBringDownCommands@607] Aborting
    BringUp command (82) on service DbService{id=24, name=mgmt1,
    serviceType=MGMT, optimisticLockVersion=1, cluster=null,
    maintenanceCount=0} role DbRole{id=54,
    name=mgmt1-SERVICEMONITOR-83cdf95375ed2c9c250ef8a42f5c85d5,
    hostId=debian01.arthuston.com, roleType=SERVICEMONITOR,
    configuredStatus=STARTING, configGeneration=6, service=mgmt1,
    maintenanceCount=0, decommissionCount=0}.




    On 7/10/13, Darren Lo wrote:
    Do you have Management Services installed? If not, there will be a button
    to Add Management Services in the upper right of your main page in the CM
    UI.

    If they are installed, you can click on the Service Monitor and look
    through the health checks and logs. The Processes tab is likely very useful
    for logs (available after clicking on a role, such as Service Monitor).

    Thanks,
    Darren

    On Wed, Jul 10, 2013 at 11:03 AM, Art Huston wrote:

    Relatively new at hadoop, installed Cloudera on single-node debian
    SQUEEZE, message "Health checks are not currently available. View the
    status of Service Monitor." How to tell why Service Monitor failed to
    start?

    --
    Thanks,
    Darren

    --
    *Art Huston * ▪ *Innovation ➢ Motivation ➢ Results*
    Software Engineering Manager & Architect • Cloud, Mobile, Big Data
    Email art@arthuston.com ▪ Mobile 978 460-5002 ▪ Home: 978 443-3278
    LinkedIn linkedin.com/in/arthuston <http://www.linkedin.com/in/arthuston>

    Twitter @arthuston <http://twitter.com/arthuston> ▪ Google+
    arthuston.com/gplus
    Blog arthuston.com <http://www.arthuston.com/> ▪
    Facebook facebook.com/art.huston <http://www.facebook.com/art.huston>
    ▪ Skype arthuston


    --
    Thanks,
    Darren

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJul 10, '13 at 6:03p
activeJul 12, '13 at 10:46p
posts3
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Darren Lo: 2 posts Art Huston: 1 post

People

Translate

site design / logo © 2022 Grokbase