You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Info (please complete the following information):
OS: Debian 12
Browser: Firefox
RMM Version (as shown in top left of web UI): 0.19.3
Installation Method:
Standard
Standard with --insecure flag at install
Docker
Agent Info (please complete the following information):
Agent version (as shown in the 'Summary' tab of the agent from web UI): 2.8.0
Agent OS: Debian 12 / Ubuntu 20.04 / Ubuntu 22.04
Describe the bug
The boot time for a LXC is displayed incorrectly, it always says the same time as the LXC-Container-Host, also after a fresh reboot of the LXC, or shutdown and switch on again.
Expected behavior
Display of the correct boot time of the container, like other Linux devices.
Additional context
Unfortunately, I don't know how the agent determines the boot time. However, if I use the "uptime" command in one of the LXC, I get the correct time at which the system started. And also the file /proc/uptime contains the correct count of seconds.
If I can somehow help solve the problem with a debug log or something similar from the agent, please let me know.
The text was updated successfully, but these errors were encountered:
Server Info (please complete the following information):
Installation Method:
--insecure
flag at installAgent Info (please complete the following information):
Describe the bug
The boot time for a LXC is displayed incorrectly, it always says the same time as the LXC-Container-Host, also after a fresh reboot of the LXC, or shutdown and switch on again.
Expected behavior
Display of the correct boot time of the container, like other Linux devices.
Additional context
Unfortunately, I don't know how the agent determines the boot time. However, if I use the "uptime" command in one of the LXC, I get the correct time at which the system started. And also the file /proc/uptime contains the correct count of seconds.
If I can somehow help solve the problem with a debug log or something similar from the agent, please let me know.
The text was updated successfully, but these errors were encountered: