Current versions?

Evgeny Balashov

October 16, 2020 17:58

Hi Pieter, the answer to your question mostly depends on what specific build you are interested in?

Usually, we have an official release available on Nx Cloud:

Nx Witness - https://nxvms.com/download/- 4.1.0.31398

Nx Meta - https://meta.nxvms.com/download/ - 4.1.0.31466 R9

A simple way to request the latest official release is through this call: https://meta.nxvms.com/api/utils/downloads

And we also roll out patches, and we make them available at

Nx Witness - https://my.networkoptix.com/#/download

Nx Meta - https://meta.nxvms.com/downloads/patches (Requires Meta Early Access Program participation)

(more info about Meta release process: https://support.networkoptix.com/hc/en-us/articles/360033351933-Meta-Release-Process)

But we do not recommend installing a patch unless it addresses a specific issue that you face in your system.

Other Powered-by-Nx partners choose different policies regarding making their releases and patches available, so we can't provide an answer for them.

0

Pieter Viljoen

October 16, 2020 18:01

Thx, I'll explore the API option.

For docker hub, all builds should be available, and the "customer" can choose which build to run.

I just want to make sure that all builds are available on docker hub as the installers are made available.

0

Pieter Viljoen

October 16, 2020 19:40

Is there a downloads API for NxWitness?

0

Andrey Terentyev

Network Optix team

October 27, 2020 18:53

Hello Pieter,

Download API for what purpose?

0

Pieter Viljoen

October 27, 2020 19:13

To get the current version, e.g. similar to https://meta.nxvms.com/api/utils/downloads

0

Evgeny Balashov

October 27, 2020 19:29

Sure: https://nxvms.com/api/utils/downloads

0

Pieter Viljoen

October 27, 2020 19:39

Cool, thx.

I know you said you don't support partner versions, but do you know if there is such an API for DW?

0

Evgeny Balashov

October 28, 2020 16:57

Pieter, for other customizations the same data is available if you add /api/utils/downloads to the cloud portal URL:

https://{CLOUD PORTAL URL}/api/utils/downloads

0

Pieter Viljoen

October 28, 2020 17:31

Got it, https://dwspectrum.digital-watchdog.com/api/utils/downloads

Is there a way to get the latest / beta patch version reported, maybe a parameters in the query, or a different API?

E.g. Nx API shows 31398 as latest, beta patches shows 31946 as latest?

0

Evgeny Balashov

November 09, 2020 18:09

Unfortunately, for now, we do not have a universal way to retrieve a patch, because different partners choose different ways to distribute patches.

0

R DS

April 20, 2021 19:50

Pieter Viljoen I’m using one of your excellent lsio builds, and note that you’d warned about licensing issues with updating.

Are you doing anything special to avoid having the license revoked when updating, or is it mostly safe just to follow the UI prompts I get from the client to update ?

0

R DS

April 20, 2021 20:04

I can see Alan Hares updated from the client https://support.networkoptix.com/hc/en-us/community/posts/360043799714-NX-Server-updating- but not sure if he’s using the official docker build

I remember reading somewhere here that it was suggested to keep the db on the host to avoid licensing issues, and I wonder if the official build does this by default...

0

Pieter Viljoen

April 20, 2021 23:30

As long as you use host networking, the MAC address and BIOS information will be that of the host machine, and the license id will not change, you can see it in the hardware log file.

0

R DS

April 23, 2021 00:22 Edited

Pieter Viljoen not sure where I'm going wrong here. Using ptr727-nxwitness-lsio

I think it's a permissions issue, but I've set PUID:PGID exactly the same as my current working container, host is networking, and I've checked the config, media and archive volumes and they all have the same PUID:PGID

1. If I try to update my working server version (4.1.0.31398) from within the client, the update fails, and appears to be getting a new hwid

The errors in the log I see are

2021-04-23 09:46:01.218    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/product_uuid
2021-04-23 09:46:01.219    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/board_serial
2021-04-23 09:46:01.219    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/board_vendor
2021-04-23 09:46:01.219    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/board_name
2021-04-23 09:46:01.219    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/product_serial
2021-04-23 09:46:01.219    341 WARNING HardwareId: [RootTool] Failed to open /sys/class/dmi/id/bios_vendor
2021-04-23 09:46:01.224    341 WARNING QMessageLogContext(0x7ff6c00ba3b8): Got hwID "{xxxxxxxxxxxxxxxxx}"

2021-04-23 09:46:30.800    347 WARNING QnStorageManager(0x7ff6c005e420, Normal): No storage available for recording

2021-04-23 09:49:18.985    291 WARNING QMessageLogContext(0x7ff6c01757e8): Stopping server
2021-04-23 09:49:18.985    341    INFO MediaServerProcess(0x55fb69c82e10): Event loop has returned. Destroying objects...
2021-04-23 09:49:19.226    341    INFO QnStorageManager(0x7ff6c005e420, Normal): Catalog rebuild operation is canceled
2021-04-23 09:49:19.226    341    INFO QnStorageManager(0x7ff6c005fbb0, Backup): Catalog rebuild operation is canceled
2021-04-23 09:49:21.531    341    INFO QnStorageManager(0x7ff6c005e420, Normal): Catalog rebuild operation is canceled
2021-04-23 09:49:21.531    341    INFO QnStorageManager(0x7ff6c005fbb0, Backup): Catalog rebuild operation is canceled

2. If I pull the latest version from the registry and load it manually, it gets the same new hwid, and the logs are full of

./run: line 14: /opt/networkoptix/mediaserver/bin/root-tool: No such file or directory

and

2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/sit0/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/ovs-system/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/ovs_eth1/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/ovs_eth0/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/lo/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/hassio/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/eth1/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/eth0/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/dockerf526fce/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/dockerf2d3549/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/dockerd77a10d/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/dockerc63d648/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker9dc0e63/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker9a737f0/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker86fa3f5/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker54e7346/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker360e576/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker2d2c076/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker0/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker05ee153/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/docker02cee22/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/default/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 40: /proc/sys/net/ipv4/conf/all/rp_filter: Read-only file system
2021-04-22 23:29:00	stdout	/opt/networkoptix/mediaserver/bin/mediaserver: line 34: /opt/networkoptix/installation_info.json: Permission denied

And when I look with the client, it says that the storage is inaccessible, and licenses are not valid for this hardware...

0

R DS

April 23, 2021 01:05

Actually looking through the update log, the error is

/tmp/networkoptix_installer-{8c90a4ba-4d89-4491-b52b-1823f24862a6}/install.sh: line 40: /opt/networkoptix/mediaserver/bin/root-tool-bin: Permission denied

How do I change permissions here to get root tool working ?

0

Pieter Viljoen

April 23, 2021 01:23

I've never tried updating the server inside docker, it kinda goes against how docker is supposed to be updated, I just update docker when a new server is released.

But, the `./run: line 14: /opt/networkoptix/mediaserver/bin/root-tool: No such file or directory` probably means the container is incorrectly loading the new 4.3 named file instead of the 4.2 named file.

I have not tested the NxWitness container myself recently, just NxMeta, let me have a look and verify I did not break something.

0

Pieter Viljoen

April 23, 2021 18:23

My bad, I screwed up the conditional file testing on builds prior to 4.3 with the stable tag, I just fixed it, the stable tags should now be able to launch the root-tool again. Please feel free to report bugs on my github repo, it is easier to track. https://github.com/ptr727/NxWitness/

I looked at the root-tool permissions, and it does look like the permissions are changed, I assume by mediaserver? Don't know why, and even if I chown them, the next launch it is change again. I would still suggest just pulling a new docker release when available vs. updating in-place, it is the docker way.

0

R DS

April 24, 2021 00:59

Thanks Pieter Viljoen, much appreciated

Loads fine now; however it does come up as a new system, and asks me to set it up as such

Is this normal and ok to do (I've not tried to upgrade before) ?

The HWID is thankfully the same as the old working version...

0

R DS

April 24, 2021 08:42

All good - I set it up as new and then restored from a backup

Thanks for all your help

0

Current versions?

Comments

Didn't find what you were looking for?