We fixed several bugs regarding the NetEye first installation on a cluster. It is now possible to successfully run the neteye_secure_install without worrying about possible problems and interruptions. In addition, we fixed the permissions of some configuration files. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug that caused a failed authentication of Alyvix sessions having some special characters in the password, due to an inconsistent encoding. Moreover, we fixed an issue related to the installation procedure of the feature modules packages on satellites, which under some circumstances was not marking the corresponding DNF group as installed. Furthermore,…
Read MoreGeneral Authentication via request-header backend We fixed a bug that did not allow the role to be associated with a user who was part of an LDAP group when the user logged in via the request-header backend. Tornado Tornado Director retry loop We fixed a bug that triggered the Tornado Director in a retry loop…
Read MoreWe fixed a bug that was preventing the upgrade from 4.29 to 4.30 and removed some concurrency issues occurring in cluster environments. Furthermore we fix a a bug where the neteye_secure_install would overwrite dashboard UIDs in some edge-cases. For NetEye 4.29 we updated the following packages:
Read MoreWe updated Icinga Web 2 to the latest bugfix version.All fixes can be found in the official documentation. We also fixed an issue where the modification of the neteye tenant configuration was possible when that would leave orphant generated configurations. For NetEye 4.29 we updated the following packages:
Read MoreWe fixed a bug on the command orchestrator module that prevented the correct command to be displayed on the “Command Execution” tab. Now is possible to see the correct command name and associate correctly the execution tab to the selected command. For NetEye 4.29 we updated the following packages:
Read MoreWe fixed a bug that was preventing the first secure install of a cluster to success. Now the ClickHouse autosetup, which contained the spotted bug, has been fixed and updated. Moreover we fixed two bugs related to Tenants having a name starting with numbers. In particular a bug that in this case caused the Satellite…
Read MoreWe fixed a bug that was preventing the first secure install of a cluster to success. Now the ClickHouse autosetup, which contained the spotted bug, has been fixed and updated. For NetEye 4.28 we updated the following packages:
Read MoreWe fixed a bug that was preventing the first secure install of a cluster to success. Now the ClickHouse autosetup, which contained the spotted bug, has been fixed and updated. For NetEye 4.27 we updated the following packages:
Read MoreWe fixed a bug that caused the command for creating or editing a tenant to fail without any error in case one of the configuration files contained an invalid JSON. For NetEye 4.29 we updated the following packages:
Read MoreFixed a bug that blocks neteye upgrade under some conditions For NetEye 4.29 we updated the following packages:
Read MoreWe applied some vulnerability fixes to GLPI. For NetEye 4.29 we updated the following packages:
Read MoreFixed a bug that caused SLM reports to fail due to a not considered condition in downtimes. For NetEye 4.29 we updated the following packages:
Read MoreFixed a bug that caused neteye_secure_install to fail due to a misconfiguration of Elastic certificates. For NetEye 4.29 we updated the following packages:
Read MoreWe fixed a bug that caused tornado smart monitoring executor to throw errors if the object name contained some special characters. Together with this bug fix we also deprecated the retry option on pending object, as we resolved this issue in NetEye 4.22. If a custom configuration was created, it will be backed up as…
Read More