Psc service health alarm что это
Как я оживлял VCSA 6.0
Все начиналось не так все печально, как случилось уже потом. Мне необходимо было создать одну VM. Зайдя в vCenter создал VM, но при попытке запуска – произошла ошибка. Две других VM (сам vCenter и еще одна) работали без проблем. Поэтому я решил перегрузить vCenter, что собственно и сделал. Через 10 мин при попытке доступа из VmWare client в vCenter – получил ошибку, что соединение не может быть установлено. О как. Решили зайти через Web – то же самое – ошибка 503.
Печаль. При том, что решил сделать это в конце рабочего дня, к счастью vCenter не особо активно используется. И так решил разбираться, что происходит.
Консоль доступа – просит логин и пароль. Ввожу логин и пароль – получаю – Login incorrect.
Приехали…( Перепробовал все пароли (и даже тот, который 100% рабочий) – результат нулевой – не могу войти и все тут. Поэтому решаю сбросить пароль от root. Для этого, нам нужно дописать init=/bin/bash в строку загрузки ядра – ничего сложного подумал я и еще раз перегрузил vCenter. Выбираю строку – жму E – ничего не происходит. Читаем внизу текст и видим, что нужно нажать на P… Жму, упс – просит пароль – стандартный vmware из доков не походит. Гуглим еще немного и находит, что пароль может быть последним паролем от root – вбиваю и ура – можно редактировать добавляю init=/bin/bash, далее уже идет классика и описывать не буду.
Тут же проверяю место – и увы… в / и /storage/log – свободно места нет – очищаю место и перегружаюсь в надежде, что все будет ОК.
Проверяю вход в vCenter через 15 мин – результат 0. Захожу через ssh на сервер и смотрю, что из сервисов запущено, а что нет. Для этого использую команду:
vmware-invsvc (VMware Inventory Service) vmware-rbd-watchdog (VMware vSphere Auto Deploy Waiter) vmware-sps (VMware vSphere Profile-Driven Storage Service) vmware-vdcs (VMware Content Library Service) vmware-vpx-workflow (VMware vCenter Workflow Manager) vmware-vpxd (VMware vCenter Server) vmware-vsan-health (VMware VSAN Health Service) vmware-vsm (VMware vService Manager) vmware-vws (VMware System and Hardware Health Manager) vsphere-client ()
Это сервисы, которые не поднялись. Можно сказать, что почти ничего не поднялось. Пытаюсь поднять vmware-invsvc:
В ответ получаю, что сервис не может быть стартован. Изучаю логи:
В момент запуска service-control –start vmware-invsvc в логах вижу следующее:
2017-07-07T09:50:01.022955+06:00 err vmdird t@140238302082816: Bind Request Failed ([3] ip_server:636 пишем:
cd HKEY_THIS_MACHINE\services\vmdir\ — жмем Enter
set_value dcAccountPassword «сгенерированный пароль»
quit
После чего перегружаем vCenter.
После 10 мин ожидания – vCenter запустился и работает стабильно.
Psc service health alarm что это
I’m currently setting up a new environment using ESXi 6.7 with an vCenter appliance deployed on the host. Setting up the hsot and the vCenter worked pretty well, and so far everything seems to be working alright, but I noticed some strange behaviour regarding the services of the vCenter:
VMware Postgres Archiver:
This service seems to change to status «stopped» every once in a while. I searched the KB and found a tip to change the wal_sender_timeout parameter to 600s, so the service doesn’t run into any timeouts, but sadly this didn’t help. I tried setting wal_sender_timeout to 0 (disabling the timeout), bu the issue still persists.
My logfiles present the same Messages as described in this KB-article:
ERROR pg_archiver could not receive data from WAL stream: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
[unknown] archiver LOG: terminating walsender process due to replication timeout
VMware PSC Health & VMware vCenter Server:
Both of these services currently show up as «degraded»:
Meanwhile the summary page reports everything as «good»:
The appliance has been assigned 16GB of RAM and 2vCPUs. Current Version:
Any ideas how to fix these services, or where to check for further information about the status of the PCS Service and the vCenter Server?
What is VMware Platform Service Controller (PSC)?
By Vladan SEGET | Last Updated: February 24, 2017
Several folks asked me recently What is VMware Platform Service Controller. I’ve published few guides on VMware vCenter Server Appliance (VCSA), the migration of vCenter to VCSA or in-place migration of Windows based vCenter but I think that I have not published enough information about VMware Platform Service Controller (PSC). Hence this post.
VMware PSC is not new. It was a part of vSphere 6.0 where it assured a number of services already. Services such as VMware Appliance Management Service, VMware License Service, VMware Component Manager, VMware Identity Management Service, VMware HTTP Reverse Proxy, VMware Service Control Agent, VMware Security Token Service, VMware Common Logging Service, VMware Syslog Health Service, VMware Authentication Framework, VMware Certificate Service, VMware Directory Service.
VMware PSC when deployed separately, in a separate VM, it deploys only the services bundled with the PSC, not the vCenter specific services. There are different topologies which exists and which has advantages or inconveniences.
PSC user interface allows many tasks already.
PSC allows:
Using single PSC in Single domain
The most simple are to deploy VMware PSC and vCenter server on a single VM, together. As such, the PSC component does not need a network connection to the vCenter server (as it communicates already, it is within the same VM).
Further, it has some following advantages:
Using multiple PSCs in single domain
Single PSC has several vCenter servers “hooked” into it.
The notion of a site, vSphere domain, Domain names….
PSC Domain – when installing PSC, there is a prompt to create vCenter SingleSign-On Domain (SSO) or join an existing domain. The domain name is used by VMware directory service for their internal LDAP structuring. You should always use another name then you’re using for your Microsoft AD, Open LDAP or other directory services within your organization.
PSC Site – You can organize PSC domains into logical sites. A site in the VMware Directory Service is a logical container for grouping PSC instances within a vCenter Single Sign-On domain.
PSC can also be deployed without a load balancer, but in this case, in a case of failure the PSC, you must manually fail over the vCenter Server instances that are registered to it by repointing them to other functional PSC instances within the same site.
Know that other types of deployments exist which we will sum here:
Platform Service Controller (PSC) services:
There is quite a few of them in vSphere 6.5.
Wrap up:
Most of the time you can stick with single VM where vCenter server and PSC collaborate together. If you want enhanced linked mode for your vCenter, and being able to manage several sites within a single console, than you’ll probbably deploy an external PSC, or 2 external PSCs behind a load balancer. You should know that not all load balancers are supported. Only F5, Netscaler, and NSX are supported. Nginix, haproxy, A10, etc are not supported.
Check more articles from ESX Virtualization:
Stay tuned through RSS, and social media channels (Twitter, FB, YouTube)
VMware Platform Services Controller (PSC)
VMware Platform Services Controller (PSC) is a new service in vSphere 6 that handles the infrastructure security functions such as vCenter Single Sign-On, licensing, certificate management and server reservation.
PSC provides one appliance- or Windows-based virtual machine platform to systems administrators for centralized management of these common infrastructure services.
PSC is a distributed service that automatically replicates information such as licenses, permissions and roles to other PSC instances. The maximum number of PSCs per vSphere domain is set at eight. High-availability for PSCs is achieved through local load-balancing technologies, though only four PSCs can reside behind a load balancer. PSCs are also latency sensitive and can only tolerate up to five minutes of time skew between PSC nodes.
In vSphere 6, the following components are installed in PSC:
Related Terms
IR35 private sector reforms: HMRC under fire over ‘omission’ of employers’ NI from webinar guidance
IR35 private sector reforms: IBM joins list of enterprises applying blanket ban to PSCs
VMware HCX improves VM mobility between vSphere clusters
Tanzu integration and vSphere VM Service lets developers and admins spin up VMs and guest OSes as desired-state images in vSphere.
The cloud can help improve an app’s performance and cost, but businesses need to plan for success. Follow these best practices to.
Psc service health alarm что это
I have installed two vCenter servers (with extended PSC) in enhanced linked mode.
I can’t connect to second vCenter2, but I can connect to vCenter1. In vCenter1 web client I see alarm «vAPI endpoint vCenter2. vmware vapi service health alarm».
There are some errors In C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint\endpoint.txt
| 2015-05-03T00:26:18.284+03:00 | WARN | state-manager1 | | InvProviderClientFactory | | Unable to login/logout to/from inventory service |
com.vmware.vim.query.client.exception.ClientException: java.util.concurrent.ExecutionException: (vmodl.fault.SecurityError) <
Caused by: java.util.concurrent.ExecutionException: (vmodl.fault.SecurityError) <
Caused by: (vmodl.fault.SecurityError) <
at sun.reflect.GeneratedConstructorAccessor54595.newInstance(Unknown Source)
at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext. (ComplexStackContext.java:31)
at com.sun.proxy.$Proxy79.loginBySamlToken(Unknown Source)
| 2015-05-03T00:17:44.369+03:00 | ERROR | state-manager1 | | RestBuilder | | Failed to create the REST. |
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘com.vmware.vapi.rest.configuration.LinkLocatorRegistrator#0’ defined in class path resource [rest-navigation.xml]: Invocation of init method failed; nested exception is java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.springframework.context.support.ClassPathXmlApplicationContext. (ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext. (ClassPathXmlApplicationContext.java:105)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at org.springframework.context.support.ClassPathXmlApplicationContext. (ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext. (ClassPathXmlApplicationContext.java:105)
| [2015-05-01T16:54:04.746+03:00] [ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth | Search failed for Health Status Endpointcom.vmware.vim.vmomi.client.exception.ConnectionException: java.net.SocketException: Connection reset |
| [2015-05-01T16:54:04.746+03:00] [ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth | Could not find Health Status EndPoint for Inventory Service |
In vCenter1 I saw this error, but after some days it disappeared.