nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Polling timestamps are 1.5 hours behind

rawk

At some point over the past day or two, all of our traffic graphs have only been current up until 1.5 hours ago (from the present). I checked on the NPM database and it appears that the timestamps are being written with the wrong datetime. For example, if I run the following query against the NPM database right now:

select max(datetime) from interfacetraffic_detail

It returns 2012-03-12 14:54:56.293. The current time here is 2012-03-12 16:25.

I have double checked the time settings on both the NPM machine and the MS SQL Server machine and they are both set correctly.

Could this issue have been cased by daylight savings? If so, how do we get it back on the right track?

Thanks

Find more posts tagged with

Accepted answers

All comments

bobross

Does the displayed server time match up with the local time or is it coinciding with what you are seeing in the database?

I'm inclined to believe that it has something to do with DST. You might want to verify that all of your timezone settings are correct. Is it possible that they are set to one of those funny mini-timezones that don't change (or maybe you are in one of the funny zones)?

You should also try running a select datetime query against your database to help you determine if its an issue with SQL directly.

rawk

bob ross lol... my wife loves that guy....

anyhow...

Yes, the time on the database and the time on NPM machine are set to the correct local time. Also, both machines are in the proper time zone (eastern US).

running the following query on the database returns the correct current time:

select getdate()

the query from my original post is still returning a timestamp about 1.5 hours behind getdate()

I have also restarted all of the services on the NPM machine to no avail.

rawk

When all else fails, reboot. That did the trick.

rawk

I spoke to soon. I rebooted last night and the timestamps were perfect. Sometime between then and about 12 hours later, the timestamps are lagged by 1 hour and 24 minutes.

Anyone have any ideas?