VMware vSphere

 View Only

  • 1.  Masked Services

    Posted Dec 30, 2022 04:11 PM

    I am sure this is a newbie question, but I am quite confused. I noted that the vpxd service needs to be started manually via SSH when Vcenter is rebooted. From that I started to research and it could be that the vpostgres service is not starting/failing, under running services on SSH I see both listed as running, in VAMI I see them as running, even restarted the vpostgres in VAMI and it completed.

    When in SSH I ask for status on vpostgres I see Loaded: masked (dev/null; bad) Active: inactive (dead)

    So in VAMI it shows fine and running, in SSH when I list running services I see it running, when I inquire to status of the service individually I get masked.

    Is this normal?

    VCenter - 6.7.0.54000



  • 2.  RE: Masked Services

    Posted Dec 30, 2022 05:44 PM

    Hi,


    That you have to manually start the VPXD service via SSH on every start / restart of the VCSA object is not normal at all.
    Try taking a look at this KB article: https://kb.vmware.com/s/article/83113 and check what the LOGs report.


    Regards,
    Ferdinando



  • 3.  RE: Masked Services

    Posted Dec 30, 2022 06:41 PM

    Yeah I found that article which is why I started down the path of services and noted that they were masked, but yet still running when I ask in SSH to list all services. VAMI shows they are running and normal as well. Someone stated somewhere else that if the root password expires that this can happen (the services getting masked). 



  • 4.  RE: Masked Services

    Posted Dec 30, 2022 07:47 PM

    Hi,


    I understand, but if the VPXD service doesn't start correctly when starting the VCSA object you need to consult the relevant LOGs to look for the presence of errors.
    If things never worked properly from the beginning it was a problem that needed to be solved in that momenty but if they started not working from a certain moment on, something must have happened that could have been recorded in the LOGs.


    As it is always better to be careful you could take a snapshot of VCSA powered off and then you could try using the contents of this FLING: https://flings.vmware.com/vsphere-diagnostic-tool


    It does not remedy the possible problem but it could highlight it saving you from carrying out all the usual checks by hand one by one.


    Regards,
    Ferdinando