vmhelp201110141
Enthusiast
Enthusiast

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
74 Replies
howardtopher
Contributor
Contributor

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.

0 Kudos
nikol
VMware Employee
VMware Employee

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

0 Kudos
johndiaz
Contributor
Contributor

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


0 Kudos
vmhelp201110141
Enthusiast
Enthusiast

for me every one min.

Surya
0 Kudos
greco827
Expert
Expert

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.

If you find this or any other answer useful please mark the answer as correct or helpful https://communities.vmware.com/people/greco827/blog
0 Kudos
vmhelp201110141
Enthusiast
Enthusiast

mine was windows vCenter .

Surya
0 Kudos
greco827
Expert
Expert

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

If you find this or any other answer useful please mark the answer as correct or helpful https://communities.vmware.com/people/greco827/blog
0 Kudos
Gyress
Contributor
Contributor

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.

0 Kudos
Nizzmo
Contributor
Contributor

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

0 Kudos
gsinjari
Contributor
Contributor

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.

0 Kudos
jfbordenjr
Contributor
Contributor

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

0 Kudos
davidlivecchi
Contributor
Contributor

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

pastedImage_1.png

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

pastedImage_0.png

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?

0 Kudos
Pcunha
Contributor
Contributor

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=vpxd-extension-a4476ec9-7311-460a-81cb-92196518e87b@vsphere.local, 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 'vpxd-extension-a4476ec9-7311-460a-81cb-92196518e87b@vsphere.local' 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=vpxd-a4476ec9-7311-460a-81cb-92196518e87b@vsphere.local, 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 'vpxd-a4476ec9-7311-460a-81cb-92196518e87b@vsphere.local' 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.

0 Kudos
jgudnason
Contributor
Contributor

+1 here,

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

0 Kudos
flyingpig
Contributor
Contributor

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.

0 Kudos
CoreyNice
Contributor
Contributor

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

0 Kudos
CoreyNice
Contributor
Contributor

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

pastedImage_3.png

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.

pastedImage_5.png

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

pastedImage_8.png

Hope this helps some folks!

0 Kudos
SavkoorSuhas
Expert
Expert

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

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points. Don't Backup. Go Forward! Rubrik Peek into my Website: http://www.virtuallypeculiar.com
0 Kudos
MatteoMarchetti
Contributor
Contributor

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

0 Kudos