vmware-dataservice-sca status changed from yellow to green

[vmhelp201110141]

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

[Legacy User]

I'm getting this as well.  Just finished the upgrade from 6.0 to 6.0U1.  Not sure how to fix or if it's really something I should be worrying about.

[johndiaz]

Just upgraded to 6.0U1 and turned on alarms and now I am getting

[VMware vCenter - Alarm alarm.HealthStatusChangedAlarm] vmware-dataservice-sca status changed from green to yellow

and

[VMware vCenter - Alarm alarm.HealthStatusChangedAlarm] vsphere-client status changed from green to yellow

these are coming in approximately every 8 minutes

[vmhelp201110141]

for me every one min.

[greco827]

Check out this link, it may be of some help or guidance.

VMware KB: VMware vCenter Server status alarms continually changing from green to yellow

Also, if you have external PSC's, make sure the NTP is synching properly on both the VCSA and the PSC it connects to.

[vmhelp201110141]

mine was windows vCenter .

[greco827]

The link I posted is geared more towards Windows based vCenter.  Worth a look.

[Gyress]

I looked at the Link posted above and it seems to be for a different version of vCenter than what I have. I have vCenter 6.0 and the "Path" (in the article for the link) they give to set-up the debugging is invalid (doesn't exist on my server in any case).

While doing some searching I found another post here in the communities vCenter 6 3018524 "vmware-dataservice-sca status changed from green to yellow" .

My issue seems to be almost exactly the same I did some digging (based on this posting) and I found this:

C:\ProgramData\VMWare\vCenterServer\logs\sca\sca.log

2015-10-05T10:03:54.549-07:00 [pool-5-thread-16 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for vsphere-client

2015-10-05T10:03:54.550-07:00 [pool-5-thread-11 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]

2015-10-05T10:03:54.550-07:00 [pool-5-thread-11 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 68d88041-e5f5-4ff0-b51f-5c0c9e3a316a_com.vmware.vsan.mgmt

2015-10-05T10:03:54.552-07:00 [pool-5-thread-26 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]

2015-10-05T10:03:54.552-07:00 [pool-5-thread-26 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 68d88041-e5f5-4ff0-b51f-5c0c9e3a316a_com.vmware.vsan.health

2015-10-05T10:03:54.552-07:00 [pool-5-thread-26 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 68d88041-e5f5-4ff0-b51f-5c0c9e3a316a_com.vmware.vsan.health healthStatusString: null endpointUrl :(null)

We had tried to set-up VSAN and found that we didn't have the licensing for it. We removed the VSAN configuration and now we getting this error.

[SavkoorSuhas]

Hello,

This is a known issue with Appliance 6.01 U1 for the vmware-dataservice-sca health alarm and dummy script not found.

We have an ongoing case with Engineering and hopefully it will fixed in coming releases.

Suhas

[MatteoMarchetti]

Same problem here, any fix? Windows-based vCenter.

[SavkoorSuhas]

Windows, not sure. But appliance, it is a known issue. Hopefully a patch/update will fix this.

[Nizzmo]

We get exactly the same messages. Did you find any solution?

[Irina Nikolova]

Hi Surya,

are you seeing this alarm in the vSphere web client? If so, you can see further information about the health degradation by going to Administration > System Configuration > Services (you'll have to be logged in as Administrator). If you go to the "VMware vSphere Web Client" and "Data Service", you should be able to see the reason for this alarm in the "Health Message" portlet on the Summary page.

Regards,

Irina

[gsinjari]

After having issue with VDP, I start seeing this message every 5 minutes, the alarm is configured in "Data Service Health Alarm", I have changed the triggering action to trap instead of sending email for now, till I resolve the VDP issue with VMWare.

[jfbordenjr]

Having same exact issue.  6.0 U1 Appliance.  Anyone have a solution for this yet?

[davidlivecchi]

Just wanted to post stating we are seeing the exact same thing. we get the two alarms.

vmware-dadaservice-sca status changed from green to yellow which is concidered a critical alarm

we also get the warning vsphere-client status changed from green to yellow

if we reset to green within 1-2 min it will come back. I have noticed though that if i open only the web client and clear both of them and then open vsphere they pop up as soon as vsphere is done loading. has been since I updated to 6.0U1

when we were just on 6.0 we were getting the postrgress warning that they finally came out with a workaround which changed the time that it would check the database.

Something i was thinking about to maybe pinpoint the problem we did upgrade our 5.5 from a vmware image to an image from HP i wonder if any of the problems we are seeing are in relation to the drivers HP has in the image. anyone else with the warnings use an image from HP?

[Pcunha]

I am getting the same error at 5-8 minutes inteval.

Running vcenter version 6 - Appliance.

Got the following from /var/log/vmware/sca/sca.log:

2015-11-16T13:02:16.846Z [pool-3-thread-2 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: No SSO token found in request

2015-11-16T13:02:16.916Z [pool-3-thread-4 INFO  com.vmware.identity.token.impl.SamlTokenImpl] SAML token for SubjectNameId [value=[e-mail], format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

2015-11-16T13:02:16.921Z [pool-3-thread-4 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: Successfully authenticated '[e-mail]' on session f07fd653-9650-4be4-943a-1a220ba6dab7

2015-11-16T13:02:17.834Z [pool-3-thread-1 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: No SSO token found in request

2015-11-16T13:02:17.863Z [pool-3-thread-3 INFO  com.vmware.identity.token.impl.SamlTokenImpl] SAML token for SubjectNameId [value=[e-mail], format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

2015-11-16T13:02:17.868Z [pool-3-thread-3 INFO  com.vmware.sca.vlsi.util.AuthParser] parseSamlData: Successfully authenticated '[e-mail]' on session 7b88e0b6-856a-4b1c-8060-3fda2dff7adc

2015-11-16T13:02:17.869Z [pool-5-thread-18 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for vsphere-client

2015-11-16T13:02:17.871Z [pool-5-thread-16 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [/usr/lib/vmware-sca/scripts, /etc/vmware-sca/scripts], [java.lang.Exception: Script doesn't exist; path: /etc/vmware-sca/scripts/dummy_path]

2015-11-16T13:02:17.871Z [pool-5-thread-16 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 9e0c1f61-019e-45d6-8b9d-e66bc458a152_com.vmware.vsan.health

2015-11-16T13:02:17.871Z [pool-5-thread-9 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [/usr/lib/vmware-sca/scripts, /etc/vmware-sca/scripts], [java.lang.Exception: Script doesn't exist; path: /etc/vmware-sca/scripts/dummy_path]

2015-11-16T13:02:17.872Z [pool-5-thread-9 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 9e0c1f61-019e-45d6-8b9d-e66bc458a152_com.vmware.vsan.mgmt

2015-11-16T13:02:17.873Z [pool-5-thread-21 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [/usr/lib/vmware-sca/scripts, /etc/vmware-sca/scripts], [java.lang.Exception: Script doesn't exist; path: /etc/vmware-sca/scripts/dummy_path]

2015-11-16T13:02:17.873Z [pool-5-thread-21 WARN  com.vmware.sca.servicecontrol.ServiceControlImplTemplate] executeControlRequest: Script missing for 9e0c1f61-019e-45d6-8b9d-e66bc458a152_com.vmware.vcIntegrity

2015-11-16T13:02:17.871Z [pool-5-thread-16 WARN  com.vmware.sca.health.HealthStatusRequest] getHealth: Could not find health status endpoint or file for serviceId: 9e0c1f61-019e-45d6-8b9d-e66bc458a152_com.vmware.vsan.health healthStatusString: null endpointUrl :(null)

It was a clean install.

Any news from Vmware? I'm opening a ticket now.

[jgudnason]

+1 here,

same issue, after upgrading to 6 U1, on a windows vCenter.

[flyingpig]

Same thing here very frustrating. Even more so since this appears to be affecting quite a few customers and VMware seems to be remaining silent regarding the issue.

[CoreyNice]

Same thing here.  It stopped under vCenter 6, but after updating to Update 1, it comes and goes (along with the Postgres Green to Gray) but is coming more than not.  Just keeps flooding email.  Normally I can reboot VCSA and get it to quiet down for a while.  Also using HP Gen8 server.

Event details:

vmware-dataservice-sca status changed from green to yellow

[CoreyNice]

Just got the issue fixed by support. EDIT:: This is a "good" fix.  Issue has never come back.  The instructions pertains to VCSA (Not windows server.)

As folks have noted, it is a known issue in vCenter 6 Update 1 (VCSA,) but I recall having the issue some when I was running vCenter 6.  The fix appears to legitimately take care of the problem, not just turn off stateless alarms in whole.  I mentioned to my support rep that a bunch of folks would appreciate a KB article on this, but until one comes out, here are the steps.  Sorry they are a bit generic, but hoping you can follow.

1) Log into vCenter. Go to Alarm Settings --> Health status changed alarm --> Edit Settings -->

2) Under Triggers --> Change Status from Unset to Warning.  In advanced options on the same page --> Add argument data center name --> Operator as equal to --> Value is Data Center name.

3) Restart the vCenter Server Services by logging in via Putty, running "service-control --stop vmware-vpxd" then "service-control --start vmware-vpxd"

Hope this helps some folks!

[flyingpig]

This fix took care of the issue for a while in our environment, but it has since returned. I hoped that maybe the alarm setting somehow got set back to it's default, but when I checked, it was still in effect. I restarted the service again and even rebooted the vCenter appliance and it's still happening at both our disaster recovery and production sites.

Has anybody else implemented this fix and had the problem return later?\

[eode]

Gave this a look tonight. Seems like the vmware-dataservice-sca/vmware-sca is looking for a script called "dummy_path" (I know).

Found this little gem in the sca.log:

grep -Hin "dummy" /var/log/vmware/sca/sca.log|head -1
/var/log/vmware/sca/sca.log:8:2015-12-30T23:17:36.083Z [pool-5-thread-14 ERROR com.vmware.sca.servicecontrol.handlers.ScriptControlHandler] Failed to locate script; name: dummy_path, dirs: [/usr/lib/vmware-sca/scripts, /etc/vmware-sca/scripts], [java.lang.Exception: Script doesn't exist; path: /etc/vmware-sca/scripts/dummy_path]

So created a little "dummy_path"-script, which will only exit when run.

cat /etc/vmware-sca/scripts/dummy_path
#!/bin/sh
#I'm dumb, and will now exit. With a zero. Because. Awesome.
exit 0

I didn't have the time to check which process which was trying to run the script, so I gave everyone rights (I know. Not cool).

chmod 777 /etc/vmware-sca/scripts/dummy_path

Profit (I've not seen the issue since, nor any complaints about the dummy_path-script). Oh, and I'm running the VCSA 6.0.0.10000 Build Number 3018521.

Guessing this isn't a "supported workaround", or anything like that (and may cause other problems). Just playing around with my home lab.

Regards,

Espen Ødegaard

[DaneTruscott]

Same issue running V6 U1 on windows 2012 R2, reboot seems to clear the problem for a while.

This is a vanilla install, i'm planing on moving my current ESXi host onto this new VC.

Does anyone know if this been confirmed as a known issue or is there something I need to do, like call tech support.

[eode]

If running VC in Windows, you could check the sca.log from:

%allusersprofile%\vmware\vcenterserver\logs\sca\sca.log, which is usually C:\programdata\vmware\vcenterserver\logs\sca\sca.log

Like others, if it's regarding the "dummy_path"-script, this (hopefully) is a known issue by now. As commented above. I've created a "dummy_path"-script (which will only exit, with the status 0 see my comment above). I've not tested this in VC in Windows, but guessing it's the same issue (script not found = script not found, right?).

Before, I was getting alarms from "Data Service" every 1-2 minutes. If really quick, I saw something like "The Data Service container process is running low on heap memory (> 90% utilized.)". I've also traced the sca-process (java), just to monitor the memory usage.

The alarms haven't triggered since I created the "dummy_path"-script.

[probinp]

It seems that newest patch (VC-6.0.0U1b-Appliance Build 3343022) resolved this bug

[DaneTruscott]

Windows update 1b seems to have fixed the issue, however it still complains it can't find the file dummy_path in the sca.log

I tried to create a script as suggested above but it couldn't recognize it as a win 32 application.

[probinp]

Ok my hura optimism was premature. The problems still occurs.

[eode]

I know. Bummer. Actually seemed fine after the U1b-upgrade (I upgraded about 5 days ago), until last night, then the alarms hit me (lots of email notifications). Seems like my little "dummy_path"-script doesn't apply as a workaround this time :smileysad: (even though the errors disappears from the sca.log). Removed the SendEmail-action for now. Maybe I'll dig into the VCSA logs later.

[llois]

in case anyone is experiencing, I'm running windows vcenter 6U1b and am still getting the issue

[ChrisHage]

same problem here, windows 2008 r2 running latest vcenter 6U1b.

any solution or workaround for vcenter on windows ?

[sbaltic]

Not really. Same problem after upgrade.

[RSMSysadmin]

Same problem here....

vpxd status changed from green to yellow and keeps coming back.

[Chad Taylor]

I ran into a similar issue after upgrading from vCenter 5.5 to 6.0 U1b (Windows Server) this morning: I'd receive alarms for vsphere-client and vmware-dataservice-sca status changes green -> yellow every 10 - 15 minutes and came across this thread while troubleshooting.

I added the server's IP address under runtime settings "Managed IP Address" and it's been over 1 hour since I received any more alarms... so I'm hoping that did it, at least for my scenario.  This setting is blank by default, which might also explain why it's happening to fresh installs?  I also have a ticket open with VMware to see what they have to say about it...

[JMangino]

Interesting, we received these alarms when doing a fresh install of 6.0 U1a. We just recently updated to 6.0 U1b in hopes this issue would go away however that is not the case. We are actually receiving even more variations of the green --> yellow alarms including but not limited to dataservice, syslog, vsphere web client etc. Originall we only received dataservice alarms.

[probinp]

I added too and frorn yesterday (>24h) i dindn't receive any alarms.

[mcvosi]

Seeing them too on my Update 1b appliance.

[VirtualKenneth]

I've also created a VMware SR for this and their response (which worked for me) is:

1) Log into vCenter server using thick Client/ vsphere client. Navigate to Alarm Settings *--> Health status changed alarm --> Edit Settings --> Triggers --> Change 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.

[bugblatterbeast]

Where you say "Value is Data Center name", does this actually mean the Datacenter you have created inside the vCenter instance?  If so then what happens if (like me) you have mulitple Datacenters in your vCenter instance?

Danny

[KennieGC]

Dunno, guess you fill in one of the DC's (which you apparently did?)

I was just repeating VMware's response.

[eode]

Adding the "vCenter Server managed address" in the "Runtime settings" seems to have solved the issue for me as well.

That's Web Client > vCenter > Manage > Settings > General > Edit > Update "Runtime settings". Reboot VC-server.

PS: Still running the latest VCSA (U1b / 3339084).

Br.

Espen

[mcvosi]

This so far has kept these alarms at bay.

[bugblatterbeast]

This looks like a fix to me ...... so far!

[DavideDeon]

Same problem for me on vCenter appliance 6.0U2. Nothing of the previous solutions works..

[KennieGC]

I've applied my solution above to multiple environments in the mean time and all were a success. Also this was an official VMware answer. Strange that this doesn't work for you.

I would suggest on creating a SR for it then.

[DavideDeon]

Which solutions works for you?

[KennieGC]

Ah I now see that I'm logged in with a different account :smileyhappy:. See "VirtualKenneth's" post above.

[DavideDeon]

Ah ok! :smileylaugh:

The solutions that you have indicated keep at bay the alarms, but in the event console I still see information like below. I'm not sure if are ok.....

[DavideDeon]

At the end I've resolved the problem (I hope).

I think the problem comes out to the people (like me) who have configured 8GB of memory for the Vcenter appliance.

If I log into vcenter shell and digit "free -m" I see that used memory is near the total, and this cause the alarm.

I've increased the appliance VM memory to 16gb (maybe 10-12gb are enough)  and the error has not come out yet.

[ChrisHaag]

Just discovered this thread - best source of information so far...

I started with the latest idea and according to DavideeDeon increased the RAM. My first attempt was to increase from 8 to 10 GB.

Before upgrading to U1b the error would re-occur after several minutes to few hours after rebooting the vCSA.

With U1b the error would start 8 hours to 3 days after reboot, most times after 2 days.

With increased memory the error did not show up since 2 day. Too early for a statement...

I'll keep you posted.

[RSMSysadmin]

Seems to work for me!

[ChrisHaag]

It did not for me.

After 3,5 days the error messages started bothering me again...

It seems that increasing the RAM just makes the time at bit longer until the error messages start again. Might be a formular like 1 GB = day.

Looks very much like a vCSA process having a memory leak. I could actually see the memory decreasing and count the days backwards.

[DavideDeon]

Chris, can you post "free -m" result of your VCSA? (Maybe 10GB is not enough)

[ChrisHaag]

I have just set the memory back to 8 GB to try the "runtime settings" approach as described above.

After 15 minutes the errors came back.

The current situation is:

1) Running since 30 minutes

2) Errors present

"free -m" shows:

[DavideDeon]

It would be interesting to view free -m on 10gb for Memory.

Probably your enviroment needs more than 10GB?

90% of 10GB are 9GB, if your memory usage increase up to 9GB the error still come out.

But it is only assumption.

[ChrisHaag]

It looked similar after 3 days. I guess memory gets eaten by a service and if would increase RAM to 12 GB, it would just give me some extra days - but not solve the issue.

We have 7 hosts managed by that vCSA and I  assume the factory memory setting would normally do in that tiny enivronment...

[DavideDeon]

Yes, you are right..

It is looking similar also for me. After 14-15 days with 16gb memory the error come out.

We must continue to find a solution...

[OSUBrian]

I'm running a fresh install (not upgraded) vCenter Server 6.0 U2 Appliance, managing only 3 hosts, all running fresh installs of ESXi 6.0 U2 using the latest HPE Custom Image.  There are currently only 8 VMs spread across the 3 hosts and I'm getting this alarm about every 1 minute.  The vCenter server appliance is configured with 8GB of RAM which should be more than adequate to manage our tiny environment.  If I reboot the vCenter Appliance the error begins to show up again after about 5 minutes.

[UofMVSI]

Going to throw my hat in the ring on this one.  Getting the error about every 6-8 minutes.  Due to failed testing of an upgrade with other components, we are unable to upgrade to the latest vSphere (something we're working with VMware on).  Currently on v6.0.

These two triggers almost always occur at the same time:

"vsphere-client status changed from green to yellow"

"vmware-dataservice-sca status changed from green to yellow"

We're using the non-Windows appliance.

[rothb]

Hello,

seems to be a known issue and sadly there is no workaround yet.

VMware KB: In vCenter Server 6.0 the vmware-dataservice-sca and vsphere-client status change from green to yellow co…

Best regards,

Bjoern

[BrianNielsen666]

Hi,

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

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 :smileyhappy:

[clafty]

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=[e-mail], 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 '[e-mail]' 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)

[danyxy]

Look no further ...

In vCenter Server 6.0, the vmware-dataservice-sca and vsphere-client status change from green to yellow continually (214…

A greeting

[clafty]

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

[myoth]

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=2144950

anyone manage to fix it?

[randd0]

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.

[TomKalabis]

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

[Zahni]

I seeing this issue after installing Netapp VSC...

[Zahni]

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"

[cometti21]

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.

[Ulianovic]

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

[lukehsieh]

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

[benorado]

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

[kashifkarar01]

Have you checked this KB:

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

[lukehsieh]

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