VMware Cloud Community
Gratts90
Contributor
Contributor
Jump to solution

Error 404 after installing update 6.7U3 on both VCA and external PSC

AS the titlte states after installing update 6.7U3 on both VCA and external PSC I get error 404 when accessing https://FQDN on both the VCA and external PSC.   The appliance Management page works though, https://FQDN:5480 is fine on both and the summary from the management page shows everyting green.  I have tried the sam by IP with the same results.

Note, we updated 4 vcenters with external PSC and 2 are fine, 2 are as above.

I can ping all devices via FQDN and IP.

Both devices have been rebooted, PSC first off and first on.

All services seem be be stopped

root@ [ ~ ]# service-control --status

Stopped:

applmgmt lwsmd vmafdd vmcam vmonapi vmware-analytics vmware-certificatemanagement vmware-cm vmware-content-library vmware-eam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-topologysvc vmware-updatemgr vmware-vapi-endpoint vmware-vcha vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsan-dps vsphere-client vsphere-ui

root@ [ ~ ]# service-control --start all

Operation not cancellable. Please wait for it to finish...

Service-control failed. Error: {

    "resolution": {

        "id": "install.ciscommon.cmlookup.resolution",

        "translatable": "Please refer to component manager documentation to troubleshoot.",

        "localized": "Please refer to component manager documentation to troubleshoot."

    },

    "problemId": null,

    "detail": [

        {

            "id": "install.ciscommon.service.notfound",

            "translatable": "Unable to locate service '%(0)s'",

            "localized": "Unable to locate service 'all'",

            "args": [

                "all"

            ]

        }

    ],

    "componentKey": null

}

root@ [ ~ ]#

root@ [ ~ ]# service-control --start vmware-vpxd

Operation not cancellable. Please wait for it to finish...

Performing start operation on service vpxd...

Service vmware-vmon startup type is not automatic. Skip

2020-04-16T11:03:41.443Z  Service vMon is not running. Failed to get startType of service vpxd

Error executing start on service vpxd. Details Error: startType of svc: vpxd rc : 11 stdout:  stderr: Connect error. ErrCode: 111

Service-control failed. Error: Error: startType of svc: vpxd rc : 11 stdout:  stderr: Connect error. Er111

root@ [ ~ ]# df -h

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  7.9G     0  7.9G   0% /dev

tmpfs                                     7.9G     0  7.9G   0% /dev/shm

tmpfs                                     7.9G  660K  7.9G   1% /run

tmpfs                                     7.9G     0  7.9G   0% /sys/fs/cgroup

/dev/sda3                                  11G  5.8G  4.3G  58% /

tmpfs                                     7.9G     0  7.9G   0% /tmp

/dev/sda1                                 120M   34M   78M  31% /boot

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/autodeploy_vg-autodeploy      9.8G   23M  9.2G   1% /storage/autodeploy

/dev/mapper/netdump_vg-netdump            985M  1.3M  916M   1% /storage/netdump

/dev/mapper/updatemgr_vg-updatemgr         99G  2.0G   92G   3% /storage/updatemgr

/dev/mapper/archive_vg-archive             50G   23G   25G  49% /storage/archive

/dev/mapper/dblog_vg-dblog                 15G  2.4G   12G  17% /storage/dblog

/dev/mapper/core_vg-core                   50G   52M   47G   1% /storage/core

/dev/mapper/seat_vg-seat                  542G  1.7G  513G   1% /storage/seat

/dev/mapper/log_vg-log                    9.8G  2.3G  7.0G  25% /storage/log

/dev/mapper/db_vg-db                      9.8G  1.5G  7.8G  17% /storage/db

0 Kudos
1 Solution

Accepted Solutions
Gratts90
Contributor
Contributor
Jump to solution

The problem that was found by vmware tech support:

root@vca [ /var/log/vmware/vmon ]# tail vmon-syslog.log

2020-04-15T23:12:59.854937+00:00 warning vmon  vecs-cli failed. Error 1021: Cannot connect to vmafd service.

2020-04-15T23:12:59.856579+00:00 warning vmon

And the solution that resolved it:

find /etc/systemd/system/ -lname '/dev/null' -exec ls {} \;

find /etc/systemd/system/ -lname '/dev/null' -exec rm {} \;

systemctl daemon-reload

service-control --start --all

View solution in original post

2 Replies
scott28tt
VMware Employee
VMware Employee
Jump to solution

Moderator: Moved to vCenter Server


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
0 Kudos
Gratts90
Contributor
Contributor
Jump to solution

The problem that was found by vmware tech support:

root@vca [ /var/log/vmware/vmon ]# tail vmon-syslog.log

2020-04-15T23:12:59.854937+00:00 warning vmon  vecs-cli failed. Error 1021: Cannot connect to vmafd service.

2020-04-15T23:12:59.856579+00:00 warning vmon

And the solution that resolved it:

find /etc/systemd/system/ -lname '/dev/null' -exec ls {} \;

find /etc/systemd/system/ -lname '/dev/null' -exec rm {} \;

systemctl daemon-reload

service-control --start --all