VMware Cloud Community
vmhelp201110141
Enthusiast
Enthusiast
‎09-21-2015 05:15 AM

vmware-dataservice-sca status changed from yellow to green

Hello ,

Below  vCenter 6.0 U1 alarm frequently changing, any idea ?

alarm.VsphereClientHealthAlarm - Event: Status change (7582963) Summary: vsphere-client status changed from green to yellow Date: 9/21/2015 12:05:53 PM Arguments: componentId = vsphere-client componentName = vsphere-client newStatus = yellow oldStatus = green serviceId = vsphere-client

regards

Surya

Surya
Reply
74 Replies
BrianNielsen666
Contributor
Contributor
‎05-11-2016 01:35 AM

Hi,

Just upgraded to vCenter and ESXi 6.0 U2 and everything went with out any problems (almost) Smiley Happy

But we are also having this issue and we are running on vCenter version 6.0 U2 Build: 3634793 (Windows)

VMWARE properly do not think that this is an important or critical error since there still hasen't been made a fix or workaround for this issue. WHY ????

Are VMWARE going to be "MS" on this issue? Hope not MS never fixes anything Smiley Happy

Reply
0 Kudos
defcon321
Contributor
Contributor
‎05-17-2016 09:44 AM

Having same issue here with my fresh install (failed upgrade 5.1 to 6U2).  Mine appears to be related to the nimble and netapp plugins I have installed. 

016-05-17T12:21:04.854-04:00 [pool-3-thread-4 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: No SSO token found in request


2016-05-17T12:21:04.871-04:00 [pool-3-thread-3 INFO  com.vmware.identity.token.impl.SamlTokenImpl] SAML token for SubjectNameId [value=vpxd-3f1bc050-1b91-11e6-b3e2-000c2962ddaa@vsphere.local, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element


2016-05-17T12:21:04.874-04:00 [pool-3-thread-3 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: Successfully authenticated 'vpxd-3f1bc050-1b91-11e6-b3e2-000c2962ddaa@vsphere.local' on session 4d8ee872-ffc0-47d3-a446-a2aab7c6a35a


2016-05-17T12:21:04.874-04:00 [pool-5-thread-25 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for vsphere-client


2016-05-17T12:21:04.874-04:00 [pool-5-thread-6 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [C:\Program Files\VMware\vCenter Server\sca\scripts, C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts], [java.lang.Exception: Script doesn't exist; path: C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts\dummy_path]


2016-05-17T12:21:04.874-04:00 [pool-5-thread-6 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.nimblestorage.hi.7587853624680939864


2016-05-17T12:21:04.875-04:00 [pool-5-thread-6 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.nimblestorage.hi.7587853624680939864 healthStatusString: null endpointUrl :(null)


2016-05-17T12:21:04.875-04:00 [pool-5-thread-10 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [C:\Program Files\VMware\vCenter Server\sca\scripts, C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts], [java.lang.Exception: Script doesn't exist; path: C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts\dummy_path]


2016-05-17T12:21:04.875-04:00 [pool-5-thread-10 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.nimblestorage.hi


2016-05-17T12:21:04.875-04:00 [pool-5-thread-10 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.nimblestorage.hi healthStatusString: null endpointUrl :(null)


2016-05-17T12:21:04.875-04:00 [pool-5-thread-29 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [C:\Program Files\VMware\vCenter Server\sca\scripts, C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts], [java.lang.Exception: Script doesn't exist; path: C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts\dummy_path]


2016-05-17T12:21:04.875-04:00 [pool-5-thread-9 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [C:\Program Files\VMware\vCenter Server\sca\scripts, C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts], [java.lang.Exception: Script doesn't exist; path: C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts\dummy_path]


2016-05-17T12:21:04.875-04:00 [pool-5-thread-29 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.netapp.nvpf


2016-05-17T12:21:04.875-04:00 [pool-5-thread-29 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.netapp.nvpf healthStatusString: null endpointUrl :(null)


2016-05-17T12:21:04.875-04:00 [pool-5-thread-9 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.vmware.vsan.health


2016-05-17T12:21:04.876-04:00 [pool-5-thread-4 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [C:\Program Files\VMware\vCenter Server\sca\scripts, C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts], [java.lang.Exception: Script doesn't exist; path: C:\ProgramData\VMware\vCenterServer\cfg\sca\scripts\dummy_path]


2016-05-17T12:21:04.876-04:00 [pool-5-thread-4 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.netapp.nvpf.webclient


2016-05-17T12:21:04.876-04:00 [pool-5-thread-4 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 0a977fc5-813f-4602-9171-2ac72dcc8a16_com.netapp.nvpf.webclient healthStatusString: null endpointUrl :(null)
Reply
0 Kudos
defcon321
Contributor
Contributor
‎06-08-2016 04:55 AM

Thanks danyxy.  My errors stopped over that weekend I upgraded and haven't been back since.  Gotta love it.

Reply
0 Kudos
myoth
Contributor
Contributor
‎06-19-2016 06:20 PM

I am on 6.0U2 build 3634794 and still having issue. there is an article saying no workaround yet https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21449...

anyone manage to fix it?

Reply
0 Kudos
randd0
Contributor
Contributor
‎07-25-2016 07:08 AM

I am on 6.0 U2 build 3634794 of the VCenter appliance.  I'm experiencing these same symptoms on a fresh install.   Ive tried both suggestions of setting a VCenter server managed address and adjusting the alarm settings, neither have worked.  While the alarms are harmless, it's pretty frustrating that VMware has yet to produce a solution after this issue has seemed to go on for quite a while.  I have an SR open, and a call with VMware today.  If they produce any recommendations that seem to help I'll make sure and post them here.

Reply
0 Kudos
TomKalabis
Enthusiast
Enthusiast
‎07-30-2016 12:57 AM

hi,

i had same issue with my vcenter...

follow this post and add more RAM for VCSA :

VMware vCenter - Data Service Container Process Heap Memory Alarms

Reply
0 Kudos
Zahni
Contributor
Contributor
‎08-01-2016 03:21 AM

I seeing this issue after installing Netapp VSC...

Reply
0 Kudos
Zahni
Contributor
Contributor
‎08-01-2016 07:54 AM

I may found  a possible  solution for the Windows-Installation (not fully tested)

go to "C:\ProgramData\VMware\vCenterServer\cfg\sca\services\" Alter all .properties wich contains "controlScriptPath=dummy_path"

Comment out these line to "#controlScriptPath=dummy_path"  Make sure, you only change files  wich contains "controlScriptPath=dummy_path"

Restart the service "VMware Service Control Agent"

Reply
0 Kudos
cometti21
Contributor
Contributor
‎10-04-2016 11:31 AM

I've tested this solution, work in parts, but not sorted. there is a workaround that is:

1) Logged in to VC using thick Client. Go to Alarm Settings --> Health status changed alarm --> Edit Settings --> Triggers --> Changed Status from unset to Warning.

2) In advanced options on the same page --> Select argument as data center name --> Operator as equal to --> Value is Data Center name.

3) Click on Actions Tab --> Select warning to alert and Warning to OK as once.

4) Restart the vCenter Server Services.

Reply
0 Kudos
Ulianovic
Contributor
Contributor
‎11-02-2016 03:18 AM

I have solved this issue in a vCenter appliance apllying a VMware Knowledge Base article, KB 2144950.

vmware-dataservice-sca and vsphere-client status change from green to yellow (2144950) | VMware KB

Reply
0 Kudos
lukehsieh
Contributor
Contributor
‎11-17-2016 07:14 PM

The article suggests to update the 'cloudvm-ram-size' to desired heap size in MB.  What's everyone setting theirs to?

Reply
0 Kudos
lukehsieh
Contributor
Contributor
‎12-26-2016 10:26 PM

What was the value you set for cloudvm-ram-size?  The default for vsphere-client seems to be 1472 MB.

Reply
0 Kudos
benorado
Contributor
Contributor
‎04-14-2017 12:43 PM

Hey Lukehsieh, did you ever figure out the value in MB to change vsphere-client to?

Reply
0 Kudos