weizhouapache commented on PR #13030:
URL: https://github.com/apache/cloudstack/pull/13030#issuecomment-5190548556

   > tested ok,
   > 
   > one issue (unrelated to this PR I think)
   > 
   > ```
   > (localcloud) 🐱 > list hosts filter=name,lastpinged
   > {
   >   "count": 4,
   >   "host": [
   >     {
   >       "lastpinged": "2026-08-05T09:15:18+0000",
   >       "name": "pr13030-t16705-kvm-ol8-kvm1"
   >     },
   >     {
   >       "lastpinged": "2026-08-05T05:01:44+0000",
   >       "name": "pr13030-t16705-kvm-ol8-kvm2"
   >     },
   >     {
   >       "lastpinged": "2026-08-05T08:55:57+0000",
   >       "name": "s-333-VM"
   >     },
   >     {
   >       "lastpinged": "2026-08-05T08:55:50+0000",
   >       "name": "v-334-VM"
   >     }
   >   ]
   > }
   > ```
   > 
   > while `pr13030-t16705-kvm-ol8-kvm2` was pinged much more recently:
   > 
   > ```
   > 2026-08-05 10:05:05,213 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(AgentManager-Handler-13:[]) (logid:) Ping from Routing host AgentAttache 
{"_id":2,"_name":"pr13030-t16705-kvm-ol8-kvm2","_uuid":"26b683ce-34d7-
   > 4448-8634-91282c273081”}
   > ```
   > 
   > and ..kvm1 as well btw;
   > 
   > ```
   > 2026-08-05 10:04:59,091 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
(AgentManager-Handler-10:[]) (logid:) Ping from Routing host AgentAttache 
{"_id":1,"_name":"pr13030-t16705-kvm-ol8-kvm1","_uuid":"f989b3eb-44dd-
   > 4674-ab83-8814ac2b1ffe”}
   > ```
   > 
   > I redid the `list hosts` again after retrieving the logs but the output is 
still identical. The unix time stamps in the DB seem more accurate:
   > 
   > ```
   > The Unix timestamp 1744063788 corresponds to May 5, 2025, at 12:29:48 PM 
UTC.
   > The Unix timestamp 1744048930 corresponds to May 5, 2025, at 12:15:30 PM 
UTC.
   > ```
   
   @DaanHoogland 
   I think it reflects the time of the last (re)connection of agent, rather 
than the last ping.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to