Deployment Health Time Settings Potential Issues

Since Upgrading our Platform from 2020.2.6 to 2023.4.2, we have had a couple of errors in Deployment Health regarding Time Settings not syncing.

Although we have checked our connection with our APE and the agents the error is warning about, the "Potential Issues" still appear in Deployment Health.

Raised this with SolarWinds who advised it is a bug as part of 2023.4.2 and is being looked into by their development team.

Just uploading this as a post in-case anyone else gets the same errors.

Find more posts tagged with

sam

deployment health

Agent

server & application monitor

ape

Time Settings

2020.2.6

2023.4.2

Comments

kande29

Any update on this issue. How it is resolved ?

SOHanlon2

SolarWinds Ticket Reference was 01556253 and this was their response "Unfortunately, it's a bug in 2023.4.2 and above version not fixed yet. The development team is working on this currently there is not any eta when this will be fixed. This is still under investigation by engineering, with the only workaround to silence the check."

I have checked the release notes of 2024.1 and it does not seem to have been resolved here either.

kande29

Thanks for the update.

bmrad

We plan to resolve this in a future release, check the release notes for your issue.

SOHanlon2

Thank you, will keep an eye out

rdavidsoncca

We are running 2024.1 and still see this. No mention of this being fixed in the release notes for 2024.1.1 either.

dc4networks

We are seeing this Deployment Health issue within an upgrade from 2020.2.6 to 2024.2.0

dc4networks

We are seeing this Deployment Health issue within an upgrade from 2020.2.6 to 2024.2.0

fhernandezm

Any update on this issue. How it is resolved ?

SOHanlon2

Unfortunately no, we have recently upgraded to 2024.2.1 and are still experiencing the issue

chad.every

@SOHanlon2 , everything that I checked internally points to the issue being fixed in the version you upgrade to. I'd open a support case (or reopen the original one) and have support investigate.

FYI: There is a high change that support would suggest upgrading to the latest version, which is currently 2024.4.1. Version 2025.1 is slated to be released in a few weeks.

alanmpadgett

We're on 2024.4.0 and also show this as an issue still.

jameslindsay

Slightly different but, I can't seem to get this resolved either

What went wrong

Failed to get time settings.

Failed to get time settings on...insert polling engine

I have three pollers at a remote datacenter. They are actively syncing time (NTP) with domain controllers and having no issues. They all have the same time and timezone as the Core/Main. Still, everyday, there is that deployment health warning (Medium) for these three remote pollers.