We updated the Icinga2 Agents to the same patch level of the Icinga2 NetEye release (2.11.9).Refer to the Icinga2 official changelog for the full list of fixes and improvements introduced by this version. The updated Icinga2 Agent packages for Windows, Debian, and Red Hat derivatives can be downloaded from our repositories.
Read MoreWith this bugfix release, we fixed an issue due to the wrong behavior of Icinga 2 when configuring a NetEye Satellite, which caused the unexpected termination of the configuration procedure. For NetEye 4.20 we updated the following packages: icinga2, icinga2-debuginfo, icinga2-ido-mysql, icinga2-bin, icinga2-ido-pgsql, icinga2-common, icinga2-resources, icinga2-doc, icinga2-selinux, icinga2-neteye-config, icinga2-autosetup to version 2.11.9_neteye1.44.5-1
Read MoreWith this bugfix release, we fixed an issue due to the wrong behavior of Icinga 2 when configuring a NetEye Satellite, which, under special conditions, can cause the Satellite to be unable to connect to the NetEye Master. For NetEye 4.20 we updated the following packages: icinga2, icinga2-debuginfo, icinga2-ido-mysql, icinga2-bin, icinga2-ido-pgsql, icinga2-common, icinga2-resources, icinga2-doc, icinga2-selinux,…
Read MoreIn the wake of offering our customers a more robust, repeatable, and automatic update experience, we extended the neteye update command to support the automatic execution of the neteye_secure_install script.This feature dramatically reduces the need for manual intervention during the update procedure. For NetEye 4.20 we updated the following packages: neteye-upgrade-manager to version 0.8.0-1
Read MoreNetEye installation topology can fluctuate over time, with hosts of various types that can be, for example, added or removed from a cluster in response to changes in business demand or customer requirements. In a cluster environment, hosts are manually mapped in a file called /etc/neteye-cluster, a sort of static inventory solution that is the…
Read MoreEver since NetEye 4.11, the NetEye upgrade procedure has been automated with the neteye upgrade command. This command performs several checks to ensure that: The currently installed version is eligible to obtain the upgrade The system is healthy The latest OS and NetEye updates and bug fixes have been installed Then, if the checks are…
Read MoreWhen you have to publicly release software like we do with NetEye every two months, it’s fundamental that users can verify that software: in our case that the RPMs that we build come from us and not from someone who pretends to be us, that they have not been tampered with, and that they do…
Read MoreWe fixed a problem in the NetEye upgrade manager for which the automatic upgrade was not able to complete because of a failure during the installed yum groups update. For NetEye 4.15 we updated: neteye-upgrade-manager to version 0.6.1-1
Read MoreWhen installing our favorite Linux distribution, the first thing we do is download the official installation image, an ISO file, from the distribution website or a third party site. Imagine for example that CentOS has just released a new version, and we are eager to give this new version a try by performing a fresh…
Read MoreWe have updated the DRBD kernel package to include the latest patches and bug fixes. You can find more details at the following link. For NetEye 4.14 we updated: DRBD to version 9.0.25-1
Read MoreWe fixed an issue related to missing dependencies in the Icingaweb2 vSphere module. We also fixed a dependency issue in the NetEye Upgrade manager. For NetEye 4.14 we updated: icingaweb2-module-vsphere package to version 1.1.0_neteye1.1.2-1 neteye-upgrade-manager package to version 0.5.1.1-1
Read MoreDistributing software content and making it available to users is not an easy task. First, you can have many different types of content like RPMs, ISO files, Python packages, and so on and so forth. And then, repositories often change. In the R&D team, we’re always implementing new features and fixing bugs, which in other…
Read MoreWith this bugfix release, we fixed a wrong setting that caused, in cluster environments, an inconsistency in the configuration of the icingaweb2 group across the cluster nodes. For NetEye 4.13 we updated: icingacli icingaweb2-selinux icingaweb2-vendor-Parsedown icingaweb2 icingaweb2-vendor-dompdf icingaweb2-vendor-zf1 icingaweb2-autosetup icingaweb2-vendor-HTMLPurifier php-Icinga icingaweb2-common icingaweb2-vendor-JShrink icingaweb2-devel icingaweb2-vendor-lessphp to version 2.7.3_neteye1.73.3-1
Read MoreUpgrading a NetEye 4 installation, either as a cluster or a single instance, is not always a painless activity. NetEye 4 is, in fact, a very sophisticated product that offers its customers a very large number of features, and operates in complex and business-critical environments. From version to version, the upgrade procedure may change: as…
Read MoreFixed a bug that affected the signature of logs written by Logstash when receiving data from Beats. For NetEye 4.10 we updated: elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack, elasticsearch-xpack-autosetup, kibana, kibana-autosetup, kibana-neteye-config, kibana-xpack, kibana-xpack-autosetup, logstash, logstash-neteye-config, logstash-neteye-config-autosetup, logstash-xpack, logstash-xpack-autosetup to version 7.4.0_neteye2.7.4-1
Read More