That looks like an ldaps cert change on whatever DC is handling the login for your scrubbed out AD user. Skyline is a bit basic in that never expects the cert it recorded when you installed AD auth...
See more...
That looks like an ldaps cert change on whatever DC is handling the login for your scrubbed out AD user. Skyline is a bit basic in that never expects the cert it recorded when you installed AD auth to change, and spits out this error when it does. Going in as the local admin user and updating the AD config should fix it until it breaks again. Tough if you're using LE based certs that update regularly. It's a shame this problem has never been seen before /s
So I have problems to deploy microservices, Wright Know I have a supervisor cluster with 6 nodes of 2vCPU and 4GB RAM each one. I have deployed 4 microservices. But when i deploy another one. The pod...
See more...
So I have problems to deploy microservices, Wright Know I have a supervisor cluster with 6 nodes of 2vCPU and 4GB RAM each one. I have deployed 4 microservices. But when i deploy another one. The pod is not created and the pods that i created before start to fail. I assume that because I am using Best-Effort VMs. I need to change them, create a new node pool with another machine kind that is not best effort. or another choice is to create another cluster with VMs with more capacity and delete the actual one. I would like to know witch one is the best way to approuch this issue. The testing environment with the microservices has 40 of RAM and 4vCPUs.
Hello, How can I remove a collector that's been decommissioned from Skyline? The deactivate/deregister button is greyed out, the VM has been deleted - need to force it somehow.
Hi i just struggled with this error for a few hours but wondering why isn't the documentation easier to address this issue? the allowUnexpectedHost parametter did not work for me as everyone lik...
See more...
Hi i just struggled with this error for a few hours but wondering why isn't the documentation easier to address this issue? the allowUnexpectedHost parametter did not work for me as everyone like to say. my horizon architecture consist of 3 connection servers and a loadbalancer (fortinet) What worked for me is editing the file C:\Program Files\VMware\VMware View\Server\sslgateway\conf\locked.properties On every connection server : just add or create a new file (in our config there wasn't this file) portalHost.1 = YOUR_CONNECTIONSERVER HOSTNAME portalHost.2 = YOUR_CONNECTIONSERVER FQDN portalHost.3 = YOUR_CONNECTIONSERVER IPADDRESS portalHost.4 = YOUR_LOADBALANCER HOSTNAME portalHost.5 = YOUR_LOADBALANCER FQDN portalHost.6 = YOUR_LOADBALANCER IPADDRESS Save & Restart Connexionserver service , wait until the other services are started and wait for tomcat process to stop freezing the cpu. Retry the connection Enjoy!
I checked this issue internally and got to know that the finding "OPERATIONS-Skippinglocal6rotate-KB#92387" was a false positive. They have disabled this finding.
I checked this issue internally and got to know that the finding "vSphere-VMunresponsive-KB#88138" was a false positive. They have disabled this finding.
As stated, we received an email alert stating our collector is unhealthy. The email shows a status of : "NO_DATA". The web portal dashboard shows the collector is healthy although it also shows a "...
See more...
As stated, we received an email alert stating our collector is unhealthy. The email shows a status of : "NO_DATA". The web portal dashboard shows the collector is healthy although it also shows a "Notification" on the right is a link that states "Collector Skyline - Collector is Unhealthy. Please resotry your Collectors to Healthy status to resume receiving proactive Findings in Advisor Pro". If I click on the link, it takes me to the collectors page and shows me my one healthy collector that shows my last successful upload 21 minutes ago. I'm not sure if this is a false positive? Does the "Notification" remain for a set amount of time before it resets even if the condition changed from unhealthy to healthy? How can I clear the "Notification"? Any other input? Thanks, Aaron
Take a look at the Connection Server logs: 2021-09-24T22:05:34.737-07:00 ERROR (1B08-1A58) <SimpleDeamonThread> [h] (ajp:admin:Request190) Unexpected Origin: https://newname.net The Unexpected Orig...
See more...
Take a look at the Connection Server logs: 2021-09-24T22:05:34.737-07:00 ERROR (1B08-1A58) <SimpleDeamonThread> [h] (ajp:admin:Request190) Unexpected Origin: https://newname.net The Unexpected Origin line will show you which portaHost entry is missing. Also take a look at: Cross-Origin Resource Sharing (CORS) with Horizon 8 and loadbalanced HTML5 access. (85801) https://kb.vmware.com/s/article/85801 Unified Access Gateway(UAG):HTML Access fails with "Failed to connect to the Connection Server" (2151877) https://kb.vmware.com/s/article/2151877
This worked for me as well. Unfortunately, this (https://kb.vmware.com/s/article/85801) did not resolve my issues after upgrading. I added every portalHost possible to the locked.properties as we run...
See more...
This worked for me as well. Unfortunately, this (https://kb.vmware.com/s/article/85801) did not resolve my issues after upgrading. I added every portalHost possible to the locked.properties as we run 2 UAG's set in HA mode.
Skyline showing ALL my VMs as affected by this finding ID, no VMs are set to 0 memory limit, all are set to UNLIMITED memory as the KB article suggests for resolution.
Hi, We have a single skyline collector pointed at two vcenters, two vrOps, two NSX managers, and a single Log Insight and vRA instance. Basically it has been causing stability and latency issues...
See more...
Hi, We have a single skyline collector pointed at two vcenters, two vrOps, two NSX managers, and a single Log Insight and vRA instance. Basically it has been causing stability and latency issues on our network by triggering the DoS/Flooding/Packet Buffer Protection on our Palo Alto firewall from creating too many sessions to the 208.91.0.89 IP address when periodically uploading to the cloud. Not sure if this is a known issue and what we can do from the application/Skyline side to help mitigate this. We have had tickets open with the firewall vendor for some time but no other application we have is causing this behaviour. Thanks
I'm getting an alert for finding OPERATIONS-Skippinglocal6rotate-KB#92387 which indicates a missing HF for Aria Operations 8.12.0 indicating that should apply HF1 to build 21786724, but my environmen...
See more...
I'm getting an alert for finding OPERATIONS-Skippinglocal6rotate-KB#92387 which indicates a missing HF for Aria Operations 8.12.0 indicating that should apply HF1 to build 21786724, but my environment is running 8.12.1 build 21952151.
@wilgee, This old post might help, please check. https://communities.vmware.com/t5/Skyline-Community-Discussions/Deregister-Skyline-Collector/td-p/2298482
