Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Rest API runTimeInfo Timezone

Comments

4 comments

  • Elan Paul

    hello support,

    were you able to answer my question above?

    Thank you

    0
  • Elan Paul

    Hello support,

    Were you able to answer my question above?

    Thank you,

    Elan

    0
  • Elan Paul

    Hello support,

    Were you able to answer my previous question?

    Thank you, Elan

    0
  • Ichiro
    • Network Optix team

    Hi Paul,

    Could you give us more detail on this specific case: "one server has 'UTC' as the 'timeZoneId', but the 'timeZoneOffsetMs' value is -14400000, which maps to the EST timezone"?

    How do you reproduce it? I've tried a number of servers, both standalone sites and multiple servers merged into a single site, and I haven't been able to see this behaviour.

    In general, a report like this is much easier for us to act on if it includes your Media Server version and either a screen recording or step-by-step reproduction steps. That gives us a clear picture of what you're seeing.

    At the moment there isn't much I can explain, because your understanding of 'timeZoneId' and 'timeZoneOffsetMs' is correct, and the API documentation describes the same behaviour: https://meta.nxvms.com/doc/developers/api-tool/rest-v4-servers-id-runtimeinfo-get

    To move this forward, could you confirm the following?

    • Which Media Server version are you running?
    • Is the timezone set correctly at the OS level on the affected server?
    • When you mention "one account", which account do you mean, and what type of account is it?
    • What does the Time Synchronization page show in the UI?

    There are a number of unknowns here. Once we have those details, we should be able to identify what to check next and suggest steps you can apply.

     

    Thanks.

    0

Please sign in to leave a comment.