Why is My IOP Server Adding 3600s to the Login Time Since the Time Change?

A user asked about the impact of the recent time change in France on their IOP servers, with their login time being 3600s different. Following a procedure provided, they were informed that while it is possible to set the time zone, it wouldn’t affect the logon duration. It was then suggested that this is an issue with the agent version, the 8.6.0.192, which should be updated. VSO 89643 on Userville was mentioned as addressing the daylight savings issue, though the portal is only available for on-prem customers. The user should also restart the agent for the changes to take effect.

Read the entire ‘How to Fix the Impact of Time Change on IOP Servers’ thread below:

Hello every body, lots of question currently on my side.. Sorry : since the time change in France, my IOP servers adds 3600s to the login time ! That’s huge. By checking their timezones, they are not correctly set. How can I change the timezone on IOP server and IOP data nodes please ?

Hi Philippe

Here is the procedure

https://support.controlup.com/docs/insights-settings

Setting the time zone in IOP isn’t going to change the logon duration though. The cu agent does that. What version of the agent are you running?

The daylight savings (summer/winter time) issue should have been addressed in a recent build. If it hasn’t, we need to dig deeper.

Having said that, it all depends on what agent version you’re running.

Last but not least. That data is now generated. You can’t fix it retroactively

Hello, thank you for your answers. Sorry for my late reply, out of office yesterday..

Thank you Amir for the procedure but I don’t have this menu in my IOP…

@member: the agent version installed at my customer’s is the 8.6.0.192.

Thank you also for your last information : it’s very important to know it.

Do you know if this version of the agent was fixed or this build is too old ?

Here is a screenshot of what is reported in Insights. When the daylight saving changes to summer time in France (on the 26th of March), we can see the amount of logon duration increase a lot… An hour… Since this change, the logon duration smoothly decreases but it’s still upper value than when we were in Winter time…

This should be addressed in 8.7.0.69 or above

For my own reference, in case this comes up again. VSO 89643Hello Dennis, thank you. What is VSO 89643 ?

Do you think that the data reported now are correct ? The daylight savings happened 2 weekds ago and the graph shared yesterday show the decrease of the logon duration.VSO = Visual studio online. The platform we use to track work items. VSO 89643 is the work item that addresses the issue of daylight savings.

The agent has to be restarted to correct the issue. If the agent has restarted since the switch, you should be goodOk thank you. Can I access to the VSO portal or is it an internal and private portal ?

it is internal. Hence why I mentioned that it was for my own reference. It just makes it easier if this comes up in a search in the future I don’t have to dig through thousands of work items based on keywords 🙂

Uservoice is the public version of VSO. It is available in Solve

Thank you. Don’t find it in my SOP version, but it doesn’t matter. Thank you for your explanations (and the tip to reboot the agent).

if you’re interested in ~SOP~ uservoice, we’re manually (and therefor slowly) creating accounts for on-prem customers. You can reach out to me via email if you’d like and I can see if we can get you to the top of the list

Thank you very much. 😃 It could be really interesting for me : this solution can highlight the support of the old versions and let me also argue to my customer about some opened topics with technical arguments.

Continue reading and comment on the thread ‘Why is My IOP Server Adding 3600s to the Login Time Since the Time Change?’.  Not a member? Join Here!