Time Sync is enabled, but system shows a different time / date from 2021 (ARM Server)

Answered

Comments

6 comments

  • Avatar
    Norman - Nx Support

    Hi Jens Schneider,

    I'm not sure why this happens.

    I have checked my ARM systems, but they all display the date and time correctly.

    Since you are using Ubuntu for ARM, I assume you use a supported Nvidia Jetson device?
    Is that correct? I'm kind of surprised that it doesn't display the CPU model.

    I also notice that the timeline show 2022 data. Could it be that the recording started before the timesync was set to the Internet time? In that case it should be resolved as soon as the 2021 data has been deleted (when the storage is full for example), but that leaves us wondering why the VMS time in the Nx WebAdmin is way off.

    0
    Comment actions Permalink
  • Avatar
    Jens Schneider

    Hi Norman - Nx Support

    Thank you for your response. 
    I use the Rockchip RK3399 - from ALLNET (one of your distributors in Germany) 
    200656 - ALLNET Videoserver NVR Box mit Networkoptix Server, RK3399, 4GB, ALL2288

    According to ALLNET, the image is the same as the Image for the NVIDIA Jetson. 

    You're right—the database shows entries from 2022 ; however, I cannot replay them. The Database is actually messed up due to the date confusion. 

    The weird thing is, that the time is even send and synced to the two hikvision cameras. 
    I, indeed, started the recorder and then changed the timezone via SSH when the system was recording already for 10 / maybe 15 minutes. 

    What can I do? 
    I'm unable to change the time, as booth VMS Time & OS time has been configured correctly. 
    Are you available for a Zoom/Teams Call or TeamViewer Session? Let's say tomorrow? 

    Thank you,
    Jens 

     

    0
    Comment actions Permalink
  • Avatar
    Norman - Nx Support

    Hi Jens Schneider,

    The device you link to isn't on our list of supported ARM boards and neither do we support Ubuntu for other devices than the Nvidia Jetson boards and x64 platforms (either AMD or Intel), so I would recommend you to address this issue to your supplier first. 

    From what I can see, it looks like the board doesn't have an RTC module, but I could be wrong, and that might be a reason the specific date and time was displayed.

    In the meantime, what you could try is to remove the old data manually, and perform a reindex.
    This way the time in the web admin still might be incorrect, but the new data will have the current time as it is synchronized with the internet, and I assume you could use the device this way.

    0
    Comment actions Permalink
  • Avatar
    Jens Schneider

    Hi Norman - Nx Support

    Thank you. Interesting, I bought that device from the Germany NX Witness Distributor – Even ask before I ordered the device as I noticed that it's not on the supported ARM boards list. The Distributor told me that NX shifted the hardware business to them. So, I assumed it must be supported. 

    I doubt that just wiping the database will help because the VMS sync the time to the cameras + every new recording will be stored with the wrong date/time code from 2021. But anyway, I'll test it. 

    Can you please reach out to your team and ask why one of your distributions sells not supported hardware? I'll return the hardware anyway, as I cannot rely on not supported devices for my clients. 

    Thank you, 
    Jens 

     

     

    0
    Comment actions Permalink
  • Avatar
    Jens Schneider

    Hi Norman - Nx Support,

    Issue is solved – time sync port (outbound) for NX was closed. 
    (TCP 37)

    Strangely, the deskop app still shows the correct time in the dialog. Maybe worth a feature request? For an error message in the dialog when the service cannot be reached?

    https://www.dropbox.com/s/i6czorkm95owqfy/right%20time.png?dl=0

    Firewall Log: https://www.dropbox.com/s/c6fj2zwxysyssq3/firewall.png?dl=0

    Thank you,
    Jens

    0
    Comment actions Permalink
  • Avatar
    Norman - Nx Support

    Hi Jens Schneider,

    A few years ago we bought hardware from them and supported that specific piece of hardware till version 4.0.
    Since then, we stopped selling hardware, since hardware isn't our core business, and it conflicted with partners that also offered hardware.

    If any of our authorized resellers decide to sell non-supported ARM hardware, it is their responsibility to support it. We also have an article for people that want to develop their own Linux-based NVRs.

    But as described in the ARM support article, if the issue can be reproduced on supported hardware, like I tried on my own ARM boards, we will try to resolve it, but due to the huge variety in ARM SBC we cannot support them all, missing dependencies and insufficient security options (many boards don't support TLS 1.2+) occur frequently. And it never hurts to ask something specific, since if we have a solution, we definitely will try to help people out since we also encourage people to create solutions that incorporate our software and that was one of the reasons to support ARM in the first place.

    That all being said; it still seems hard to buy ARM SBC on a frequent basis, especially the Raspberry Pi (already waiting for months for my Pi Zero's), that we noticed that more and more people shifted to barebone mini PC's with lightweight CPU like the Celerons and Pentiums. As a complete box (computer+RAM+Drive) slightly more expensive, but for many applications a great alternative opposed to boxed ARM boards.

    ----

    Thank you very much for sharing the root cause of the issue, I will discuss this internally if we can add such event to our rules engine. For me, it makes sense to get such notification, but I don't know the impact and therefore it isi not up to me to decide whether we can add it or not and if we can do it asap, in a next release, or in the future.

    ---

    Ich hoffe, Sie werden einen wunderbaren Tag haben!

     

    0
    Comment actions Permalink

Please sign in to leave a comment.