Search the VMware Knowledge Base (KB)
View by Article ID

Starting vCenter Server or PSC services fails with error message: INFO:root:'<Service Name>' startMode is Manual, skipping to start (2151528)

  • 0 Ratings

Symptoms

  • Starting vCenter Server or PSC services on vCenter server appliance fails.
  • You see the error message: INFO:root:'<Service Name>' startMode is Manual, skipping to start"

Example:

#service-control --start --all

INFO:root:Service: vmafdd, Action: start
Service: vmafdd, Action: start
2017-08-14T17:03:50.261Z Running command: ['/sbin/chkconfig', u'vmafdd']
2017-08-14T17:03:50.323Z Done running command
'vmafdd' startMode is Manual, skipping to start:
INFO:root:'vmafdd' startMode is Manual, skipping to start:
INFO:root:Service: vmware-rhttpproxy, Action: start
Service: vmware-rhttpproxy, Action: start
2017-08-14T17:03:50.325Z Running command: ['/sbin/chkconfig', u'vmware-rhttpproxy']
2017-08-14T17:03:50.385Z Done running command
'vmware-rhttpproxy' startMode is Manual, skipping to start:
INFO:root:'vmware-rhttpproxy' startMode is Manual, skipping to start:
INFO:root:Service: vmdird, Action: start
Service: vmdird, Action: start
2017-08-14T17:03:50.385Z Running command: ['/sbin/chkconfig', u'vmdird']
2017-08-14T17:03:50.445Z Done running command
'vmdird' startMode is Manual, skipping to start:
INFO:root:'vmdird' startMode is Manual, skipping to start:
INFO:root:Service: vmcad, Action: start
Service: vmcad, Action: start
2017-08-14T17:03:50.446Z Running command: ['/sbin/chkconfig', u'vmcad']
2017-08-14T17:03:50.505Z Done running command
'vmcad' startMode is Manual, skipping to start:
INFO:root:'vmcad' startMode is Manual, skipping to start:
INFO:root:Service: vmware-sts-idmd, Action: start
Service: vmware-sts-idmd, Action: start

Cause

This error occurs when the services start mode is set to Manual.

Resolution

 1. Run this command to check the start status : chkconfig -A

Example:

#chkconfig -A

applmgmt off

vmafdd off
vmcad off
vmci on
vmdird off
vmware-cis-license off
vmware-cm off
vmware-psc-client off
vmware-rhttpproxy off
vmware-sca off
vmware-sts-idmd off
vmware-stsd off
vmware-syslog off
vmware-syslog-health off
vmware-tools-services on
vmware-tools-vgauth on
vsock on

In the above example, most of the VMware service status is OFF.


2. If the service status is set to off, then perform these steps to turn it ON.

  1. Run this command to stop all the running services:

    service-control --stop --all

  2. Run this command to change the service state from Off to On state:
    chkconfig <servicename> on

    Example:
    chkconfig vmware-cm on

  3. Once all the service status is set to ON, run this command to start all the services:
    service-control --start --all


Note: Change the status of the dependent service to ON before changing the status of any service that you are trying to start. Attempting to change the status without changing the status of the dependent service will fail.

Example:

#chkconfig vmware-cis-license on
insserv: FATAL: service vmware-cm has to be enabled to use service vmware-cis-license
insserv: Service syslog is missed in the runlevels 2 to use service cgrulesengd
insserv: exiting now!
/sbin/insserv failed, exit code 1

In the above example, change the status of  vmware-cm service to ON before changing the status of vmware-cis-license

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: