I have a virtual server in ESXI version 6.7 that has been running for so long that I can not access it automatically after an hour or two in a few days.
Ping from the IP of this server gives time out
Also, when I open the console in the browser, no page appears to me and it is black.
I looked at the VMware.log file and saw the text below
Please help fix this problem
2021-04-06T18:09:54.194Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:10:54.619Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:11:54.621Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:12:54.695Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:13:54.694Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:14:54.694Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:15:54.688Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:16:54.676Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:17:54.687Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:18:54.688Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:19:54.687Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:20:54.689Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:21:54.688Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:22:54.682Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:23:54.685Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:24:54.685Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:25:54.738Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:26:56.734Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:27:56.724Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:28:57.292Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:29:57.418Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:30:57.538Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:31:57.658Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T18:32:57.808Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T19:09:04.650Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.
2021-04-06T19:09:19.158Z| vcpu-0| I125: Tools: Tools heartbeat timeout.
2021-04-06T19:09:19.158Z| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.
2021-04-06T19:09:19.158Z| vcpu-0| I125: Tools: Changing running status: 1 => 0.
2021-04-06T19:09:24.654Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.
2021-04-06T19:09:24.654Z| vmx| I125: GuestRpc: app toolbox's second ping timeout; assuming app is down
2021-04-06T19:09:24.656Z| vmx| I125: GuestRpc: Reinitializing Channel 0(toolbox)
2021-04-06T19:09:24.656Z| vmx| I125: GuestMsg: Channel 0, Cannot unpost because the previous post is already completed
2021-04-06T19:26:43.213Z| svga| I125: MKSScreenShotMgr: Taking a screenshot
2021-04-06T19:26:45.817Z| vmx| I125: VigorTransportProcessClientPayload: opID=esxui-b809-85e2 seq=1920878: Receiving MKS.IssueTicket request.
2021-04-06T19:26:45.817Z| vmx| I125: SOCKET creating new socket listening on /var/run/vmware/ticket/5c88c1cc3a32bd3c
2021-04-06T19:26:45.818Z| vmx| I125: SOCKET 7121 (80) creating new listening socket on port -1
2021-04-06T19:26:45.818Z| vmx| I125: Issuing new webmks ticket 5c88c1... (120 seconds)
2021-04-06T19:26:45.818Z| vmx| I125: VigorTransport_ServerSendResponse opID=esxui-b809-85e2 seq=1920878: Completed MKS request with messages.
2021-04-06T19:26:45.913Z| mks| I125: Accepting connection for webmks ticket 5c88c1...
2021-04-06T19:26:45.913Z| mks| I125: Expiring webmks ticket 5c88c1...
2021-04-06T19:26:45.913Z| mks| I125: SOCKET 7122 (117) AsyncTCPSocketSetOption: Option layer/level [6], option/name [1]: successfully set OS option for TCP socket.
2021-04-06T19:26:45.913Z| mks| W115: SOCKET 7123 (117) unable to determine remote IP address
2021-04-06T19:26:45.914Z| mks| I125: SOCKET 7122 (117) AsyncTCPSocketSetOption: sendLowLatencyMode set to [1].
2021-04-06T19:26:45.914Z| mks| I125: SOCKET 7123 (117) Creating VNC remote connection.
2021-04-06T19:26:45.914Z| mks| I125: MKSControlMgr: New VNC connection 87
2021-04-06T19:26:45.914Z| svga| I125: VNCENCODE 7123 VNCEncode: VNCEncode_ServerSetTopology - original root: (0, 0) size: (603, 499)
2021-04-06T19:26:45.914Z| svga| I125: VNCENCODE 7123 VNCEncode: Number of screens changed from 0 to 1
2021-04-06T19:26:45.914Z| svga| I125: VNCENCODE 7123 VNCEncode: screen: 0 BoundingBox: (603x499) Screen (603x499) @ (0,0) bytesPerLine: 2412
2021-04-06T19:26:46.050Z| mks| W115: VNCENCODE 7123 JPEG quality levels (min, mid, max). Input: (25, 35, 90) Clamped: (25, 35, 90)
2021-04-06T19:26:46.050Z| mks| I125: VNCENCODE 7123 VNCEncodeChooseRegionEncoder: region encoder adaptive. Screen 1/1 @ Resolution: 603 x 499
2021-04-06T19:26:46.343Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 603 499
2021-04-06T19:26:51.498Z| mks| I125: SOCKET 7123 (117) Received websocket close frame with empty status code
2021-04-06T19:26:51.498Z| mks| I125: SOCKET 7123 (117) Sending websocket close frame, status code = 1000
2021-04-06T19:26:51.498Z| mks| I125: SOCKET 7123 (117) VNC Remote Disconnect: socket closed.
2021-04-06T19:26:51.499Z| mks| I125: MKSControlMgr: Remove VNC connection 87
Moderator edit by wila: Moved post to VMware ESXi discussions