IPM 8.x / 9.x does not pick up changes with daylight savings.

The daylight savings start date changed this year for Australian states. We have many servers based in Australia, and we have found that maintenance is 1 hour late to start. This is causing all our servers to alert.

Our IPM8.5 server is based on the US east coast, and it did not recognize changes to DST even though we patched the server.

I have been working with the Solarwinds support team on this issue and it has been found to be a bug. It will be addressed in the next service pack for 9.x. Unfortunately, it appears that no more patches/service packs will be released for 8.x, which means, 8.x is not actually supported. This is very disapointing for us.

Find more posts tagged with

support

team

support_end_of_life

service

dst_bug_case

9.01

8.5

dst

poor

customer_satisfaction_zero

Accepted answers

bshopp

brock, I just looked up your case and the associated case in our tracking system and this appears to be resolved in the next release, I will reach out to you offline to discuss further.

All comments

brock.c

I was working with the support team, but now they will not answer my emails.

simonpt

You're not alone. I have a case logged for New Zealand daylight saving time changes that were brought in over 12 months ago. I logged the call in March and I was advised that a 'bug' has been opened with the development team but have heard nothing since. They also won't reply to my emails. Talk about unprofessional.

Here's an excerpt from the unanswered email I sent last month which shares some light on how trivial this would be to fix:

Many daylight saving changes occurred around the world last year. Our other software vendors put a lot of effort in to make sure their solutions would work correctly with the new daylight saving rules. For example, here is Microsoft's knowledge base article which lists 35 daylight saving changes included in their August 2007 cumulative update: http://support.microsoft.com/kb/933360/en-us.

I'm disappointed that six months after I logged this bug and one year after our new daylight saving rules came into effect there is still no fix from SolarWinds for ipMonitor. I'm even more disappointed to discover today that ipMonitor has an internal database for daylight saving rules (see http://support.ipmonitor.com/faqs/6220a21099e14beba582569d3d913bc3.aspx) so there are no software changes required -- just an update to a record.

Rgds, Simon

mark_wiggans

Simon-

Thanks for bringing this up. It looks like an error on our end here. I'll see if the DEV team might have a workaround for you.

simonpt

Thanks Mark. I appreciate your assistance.

brock.c

The support team gave me the following work around.

"The workaround is to just schedule the maintenance to run one hour early"