Updating VISULOX
Each VISULOX installation can be updated with a newer version provided by amitego engineering as long as the underlaying database structure has not been changed.
Please have a look at the release notes of the new version before update.
After update of VISULOX the VISULOX PORTAL Service and the VISULOX Service must be restarted once!
See also: Network communication within VISULOX
Updating VISULOX
dnf install visulox-rte-1.2.0-1.el8.x86_64.rpm
dnf install visulox-4.3.2-1.el8.x86_64.rpm visulox-portal-4.3.2-1.el8.x86_64.rpm
On pure VISULOX Service Nodes only the RTE and the VISULOX package is needed.
The RTE package is only needed, if there is a newer version available.
On environments with a local Gateway, the Gateway package is needed.
On each VISULOX PORTAL, the VISULOX Service has to be re-registered.
visulox portal attach
After the update it has to be checked, if there are policies without a timeprofile or missing links to scripts. The following commands can be used:
Example checks
visulox policy login list -fields basicname,pin_script,login_script
visulox policy access list -fields basicname,timeprofile,region,acc_script
visulox policy application list -fields basicname,kbi_general_script,app_script
visulox policy transit list -fields basicname,ft_script,scan_script
If errors are displayed. the according settings have to be adjusted manually (via VISULOX Cockpit or command line).
See also: How to control regions from the command line, How to control timeprofiles from the command line, How to control access from the command line, etc
If it is necessary to adjust changed fields in policies, this must be done, when all nodes are active.
After installation of VISULOX, the VISULOX PORTAL Service and the VISULOX Service must be restarted once!
In case of log entries affecting the etcd instances, the node has to be reconfigured:
visulox etcd node reconfigure -verbose
During an update in larger environments it is possible, that some of the VISULOX etcd nodes are offline.
If there are not enough nodes for the quorum, needed configuration parameters can not be set.
There is a possibility to force the start of etcd on offline nodes to reach the number of nodes needed for the quorum.
Please contact the system integrator in this case.