VMware Cloud Community
yjd333
Contributor
Contributor
Jump to solution

VCSA host restarts 5480 page cannot login

Initial installation date: 2018
Installation location: inside esxi
Version: Has been continuously updated to the latest version 6.7.0.46000 17138064


Date of appearance: There was no problem during the initial installation. This problem exists since upgrading to a certain version in the middle.

Symptom: After VSCA restarts, the 5480 management page cannot be logged in. You must log in with SSH every time, and execute service-control --start applmgmt to return to normal.

0 Kudos
1 Solution

Accepted Solutions
Ajay1988
Expert
Expert
Jump to solution

Then you are hitting this issue where the service doesn't start  within its specified time. Increase the timeout. 

https://kb.vmware.com/s/article/68149

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ

View solution in original post

4 Replies
pdirmann01
Enthusiast
Enthusiast
Jump to solution

Going to start with the sheer basics, but did the start type of the service happened to get modified?

From the CLI you can execute:

vmon-cli --status applmgmt

...and you should get output similar to this:

Name: applmgmt
Starttype: AUTOMATIC
RunState: STARTED
RunAsUser: root
CurrentRunStateDuration(ms): 3055700860
HealthState: HEALTHY
FailStop: N/A
MainProcessId: 2261

If the StartType is not Automatic then you can execute 

vmon-cli --update applmgmt --starttype AUTOMATIC

yjd333
Contributor
Contributor
Jump to solution

Name: applmgmt
Starttype: AUTOMATIC
RunState: STARTED
RunAsUser: root
CurrentRunStateDuration(ms): 5994538
HealthState: HEALTHY
FailStop: N/A
MainProcessId: 8071

------

Status is automatic

ths.

 

0 Kudos
yjd333
Contributor
Contributor
Jump to solution

Execution: vmon-cli --status applmgmt
The display startup type is always self-starting by default.
May be caused by other reasons

0 Kudos
Ajay1988
Expert
Expert
Jump to solution

Then you are hitting this issue where the service doesn't start  within its specified time. Increase the timeout. 

https://kb.vmware.com/s/article/68149

If you think your queries have been answered
Mark this response as "Correct" or "Helpful".

Regards,
AJ