root@XXXXX[ ~ ]# service-control --start vmware-sts-idmd
Perform start operation. vmon_profile=None, svc_names=['vmware-sts-idmd'], include_coreossvcs=False, include_leafossvcs=False
2018-08-08T22:46:01.701Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-sts-idmd']
2018-08-08T22:46:01.718Z Done running command
2018-08-08T22:46:01.726Z Service vmware-sts-idmd does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.
2018-08-08T22:46:01.726Z Running command: ['/sbin/service', u'vmware-sts-idmd', 'status']
2018-08-08T22:46:01.785Z Done running command
2018-08-08T22:46:01.794Z Running command: ['/usr/bin/systemctl', 'daemon-reload']
2018-08-08T22:46:01.956Z Done running command
2018-08-08T22:46:01.956Z Running command: ['/usr/bin/systemctl', 'set-property', u'vmware-sts-idmd.service', 'MemoryAccounting=true', 'CPUAccounting=true', 'BlockIOAccounting=true']
2018-08-08T22:46:01.984Z Done running command
2018-08-08T22:46:03.226Z RC = 1
Stdout =
Stderr = Job for vmware-sts-idmd.service failed because the control process exited with error code. See "systemctl status vmware-sts-idmd.service" and "journalctl -xe" for details.
2018-08-08T22:46:03.226Z {
"resolution": null,
"detail": [
{
"args": [
"Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n"
],
"id": "install.ciscommon.command.errinvoke",
"localized": "An error occurred while invoking external command : 'Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n'",
"translatable": "An error occurred while invoking external command : '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Error executing start on service vmware-sts-idmd. Details {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
please if you can help me I need to solve this issue since not all the services of the external psc upload
Message was edited by: Jose Franco
1) Take a snapshot of the VM.
2) Run the command <kill 1904>.
3) Run the command <ps aux | grep -i idmd> to validate if both processes 1904 and 1905 have been killed. If 1905 still shows up, run <kill 1905> to kill it.
4) Run the command <service-control --stop vmware-sts-idmd>.
5) Now, run the command <service-control --start vmware-sts-idmd>.
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Cheers,
Supreet
Can you check if there is a process already running?
ps aux | grep -i idmd
If yes, kill the process and try to start the service.
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Cheers,
Supreet
after executing the command I get the following information. it seems that he was not running
root@SAPL1454 [ ~ ]# ps aux | grep -i idmd
root 1904 0.0 0.0 10592 24 ? Ss Aug08 0:00 vmware-sts-idmd -procname vmware-sts-idmd -wait 120 -server -Xmx179m -XX:CompressedClassSpaceSize=160m -Xss256k -XX:ParallelGCThreads=1 -XX:ErrorFile=/var/log/vmware/sso/hs_err_idm_pid%p.log -XX:HeapDumpPath=/var/log/vmware/sso -home /usr/java/jre-vmware -pidfile /var/run/vmware-sts-idmd.pid -errfile /var/log/vmware/sso/vmware-sts-idmd.err -cp /opt/vmware/lib64/commons-lang-2.5.jar:/opt/vmware/lib64/commons-logging-1.1.1.jar:/opt/vmware/lib64/log4j-api-2.2.jar:/opt/vmware/lib64/log4j-1.2-api-2.0.2.jar:/opt/vmware/lib64/log4j-core-2.2.jar:/opt/vmware/lib64/log4j-1.2.12rsa-1.jar:/opt/vmware/lib64/jna.jar:/opt/vmware/lib64/commons-daemon-1.0.8.jar:/opt/vmware/lib64/bcpkix-jdk15on-147.jar:/opt/vmware/lib64/bcprov-jdk15on-147.jar:/opt/vmware/lib64/vmware-identity-platform.jar:/opt/vmware/lib64/vmware-identity-idm-interface.jar:/opt/vmware/lib64/vmware-identity-idm-server.jar:/opt/vmware/lib64/vmware-identity-diagnostics.jar:/opt/vmware/lib64/bcprov-jdk16-145.jar:/opt/vmware/lib64/authentication-framework.jar:/opt/vmware/lib64/afd-heartbeat-service.jar:/opt/vmware/lib64/httpclient-4.5.1.jar:/opt/vmware/lib64/authapi-8.5.jar:/opt/vmware/lib64/cryptoj-6.1.jar:/opt/vmware/lib64/xmlsec-1.5.5.jar:/opt/vmware/lib64 -Djava.rmi.server.codebase=file:////opt/vmware/lib64/vmware-identity-idm-interface.jar file:////opt/vmware/lib64/vmware-identity-idm-server.jar -Djava.security.policy=/opt/vmware/share/config/server.policy -Dvmware.log.dir=/var/log/vmware/sso -Dlog4j.configurationFile=file:///opt/vmware/share/config/log4j2.xml com.vmware.identity.idm.server.IdmServer
root 1905 1.2 5.2 1922520 210956 ? Sl Aug08 16:26 vmware-sts-idmd -procname vmware-sts-idmd -wait 120 -server -Xmx179m -XX:CompressedClassSpaceSize=160m -Xss256k -XX:ParallelGCThreads=1 -XX:ErrorFile=/var/log/vmware/sso/hs_err_idm_pid%p.log -XX:HeapDumpPath=/var/log/vmware/sso -home /usr/java/jre-vmware -pidfile /var/run/vmware-sts-idmd.pid -errfile /var/log/vmware/sso/vmware-sts-idmd.err -cp /opt/vmware/lib64/commons-lang-2.5.jar:/opt/vmware/lib64/commons-logging-1.1.1.jar:/opt/vmware/lib64/log4j-api-2.2.jar:/opt/vmware/lib64/log4j-1.2-api-2.0.2.jar:/opt/vmware/lib64/log4j-core-2.2.jar:/opt/vmware/lib64/log4j-1.2.12rsa-1.jar:/opt/vmware/lib64/jna.jar:/opt/vmware/lib64/commons-daemon-1.0.8.jar:/opt/vmware/lib64/bcpkix-jdk15on-147.jar:/opt/vmware/lib64/bcprov-jdk15on-147.jar:/opt/vmware/lib64/vmware-identity-platform.jar:/opt/vmware/lib64/vmware-identity-idm-interface.jar:/opt/vmware/lib64/vmware-identity-idm-server.jar:/opt/vmware/lib64/vmware-identity-diagnostics.jar:/opt/vmware/lib64/bcprov-jdk16-145.jar:/opt/vmware/lib64/authentication-framework.jar:/opt/vmware/lib64/afd-heartbeat-service.jar:/opt/vmware/lib64/httpclient-4.5.1.jar:/opt/vmware/lib64/authapi-8.5.jar:/opt/vmware/lib64/cryptoj-6.1.jar:/opt/vmware/lib64/xmlsec-1.5.5.jar:/opt/vmware/lib64 -Djava.rmi.server.codebase=file:////opt/vmware/lib64/vmware-identity-idm-interface.jar file:////opt/vmware/lib64/vmware-identity-idm-server.jar -Djava.security.policy=/opt/vmware/share/config/server.policy -Dvmware.log.dir=/var/log/vmware/sso -Dlog4j.configurationFile=file:///opt/vmware/share/config/log4j2.xml com.vmware.identity.idm.server.IdmServer
root 77922 0.0 0.0 13876 2272 pts/0 S+ 09:38 0:00 grep --color=auto -i idmd
1) Take a snapshot of the VM.
2) Run the command <kill 1904>.
3) Run the command <ps aux | grep -i idmd> to validate if both processes 1904 and 1905 have been killed. If 1905 still shows up, run <kill 1905> to kill it.
4) Run the command <service-control --stop vmware-sts-idmd>.
5) Now, run the command <service-control --start vmware-sts-idmd>.
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Cheers,
Supreet
It seems that it did not work. My son's mistake is to throw when I try to lift the service. I followed the steps you indicated but still nothing
root@SAPL1454 [ ~ ]# kill 1904
root@SAPL1454 [ ~ ]# ps aux | grep -i idmd
root 108905 0.0 0.0 13872 2344 pts/0 S+ 11:14 0:00 grep --color=auto -i idmd
root@SAPL1454 [ ~ ]# service-control --stop vmware-sts-idmd
Perform stop operation. vmon_profile=None, svc_names=['vmware-sts-idmd'], include_coreossvcs=False, include_leafossvcs=False
2018-08-09T15:15:36.450Z Service vmware-sts-idmd does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.
2018-08-09T15:15:36.450Z Running command: ['/sbin/service', u'vmware-sts-idmd', 'status']
2018-08-09T15:16:10.406Z Done running command
Successfully stopped service vmware-sts-idmd
root@SAPL1454 [ ~ ]# service-control --start vmware-sts-idmd
Perform start operation. vmon_profile=None, svc_names=['vmware-sts-idmd'], include_coreossvcs=False, include_leafossvcs=False
2018-08-09T15:16:15.105Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-sts-idmd']
2018-08-09T15:16:17.386Z Done running command
2018-08-09T15:16:17.395Z Service vmware-sts-idmd does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.
2018-08-09T15:16:17.395Z Running command: ['/sbin/service', u'vmware-sts-idmd', 'status']
2018-08-09T15:16:17.455Z Done running command
2018-08-09T15:16:17.465Z Running command: ['/usr/bin/systemctl', 'daemon-reload']
2018-08-09T15:16:42.486Z Done running command
2018-08-09T15:16:42.487Z Invoked command: ['/usr/bin/systemctl', 'daemon-reload']
2018-08-09T15:16:42.487Z RC = 1
Stdout =
Stderr = Failed to execute operation: Connection timed out
2018-08-09T15:16:42.487Z {
"resolution": null,
"detail": [
{
"args": [
"Command: ['/usr/bin/systemctl', 'daemon-reload']\nStderr: Failed to execute operation: Connection timed out\n"
],
"id": "install.ciscommon.command.errinvoke",
"localized": "An error occurred while invoking external command : 'Command: ['/usr/bin/systemctl', 'daemon-reload']\nStderr: Failed to execute operation: Connection timed out\n'",
"translatable": "An error occurred while invoking external command : '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Error executing start on service vmware-sts-idmd. Details {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
thanks, it was very helpful
I am facing the same problem, what is the solution?
Stderr = Job for vmware-sts-idmd.service failed because the control process exited with error code. See "systemctl status vmware-sts-idmd.service" and "journalctl -xe" for details.
2019-05-07T05:15:57.411Z {
"resolution": null,
"detail": [
{
"args": [
"Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n"
],
"id": "install.ciscommon.command.errinvoke",
"localized": "An error occurred while invoking external command : 'Stderr: Job for vmware-sts-idmd.service failed because the control process exited with error code. See \"systemctl status vmware-sts-idmd.service\" and \"journalctl -xe\" for details.\n'",
"translatable": "An error occurred while invoking external command : '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Error executing start on service vmware-sts-idmd. Details {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"vmware-sts-idmd"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'vmware-sts-idmd'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}