As a NetEye User I want to handle node failures when they happen in my cluster. When a node becomes unresponsive, it might still be accessing your data: the only way to ensure that a node is truly offline is to shut it down. This procedure is called fencing. NetEye 4 relies on Corosync/Pacemaker, also…
Read MoreWe fixed a bug which prevents DRBD and Tornado health checks to run successfully on elasticsearch-only nodes. For NetEye 4.11 we updated: neteye-setup to version 1.45.3-1 tornado and tornado-autosetup to version 0.30.2-1
Read MoreWe fixed errors which prevents correct execution of neteye_secure_install during first installation of a NetEye cluster. For NetEye 4.11 we updated: httpd-neteye-config httpd-neteye-config-autosetup to version 1.6.2-1
Read MoreWe fixed errors which prevents moving httpd certificates to cluster resource caused by unexpected options in httpd ssl configuration. For NetEye 4.11 we updated: httpd-neteye-config httpd-neteye-config-autosetup httpd-neteye-config-devel to version 1.6.1-1 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.65.1-1 icingaweb2-module-assetmanagement icingaweb2-module-assetmanagement-autosetup to version 1.15.1-1
Read MoreA common issue in cluster environment is the split brain condition. A split brain occurs when some nodes of the cluster are not able to communicate properly, but instead continue to work like two separate, distinct clusters leading to data or service inconsistency. To prevent this situation a common solution is to introduce the concept…
Read MoreFixed a bug which overrides logstash certificates when neteye_secure_install is executed preventing external beats to connect to logstash. 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.2-1
Read MoreFixes NetEye deep check error on passive nodes when module logmanagement is installed. For NetEye 4.9 we updated: searchguard-plugin-common, searchguard-plugin-common-autosetup, elasticsearch-plugin-searchguard, elasticsearch-plugin-searchguard-autosetup, kibana-plugin-searchguard,kibana-plugin-searchguard-autosetup to versions 8.4.2-1 icingaweb2-module-logmanager, icingaweb2-module-logmanager-autosetup to version 0.29.1-1
Read MoreThis bugfix improves DRBD resiliency respect to all outages which might cause split brain or diverging data of replicas. On a cluster with three or more Red Hat HA Clustering nodes, quorum is enable and, in case of loss of quorum, the nodes will report io-error: this prevents diverging of data and split brain conditions….
Read MoreFixed a bug which requires to manually restart Kibana when upgrading from NetEye 4.8 to NetEye 4.9. Nagvis fixes a bug in cluster installations on NetEye 4.9. For NetEye 4.8 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.3.1_neteye2.3.5-1 For NetEye 4.9 we updated:…
Read MoreFixed a bug that prevented NetEye from being installed successfully when the locale is a value different than English. For NetEye 4.8 we updated: neteye-setup to version 1.24.4-1
Read MoreFixed a bug that prevented Elasticsearch from starting on a fresh NetEye 4.8 cluster installation. This bug was caused by two deprecated options,discovery.zen.ping.unicast.hosts and discovery.zen.minimum_master_nodes,which are no longer used now that Zen Discovery has been removed in Elastic 7.To start Elasticsearch 7.3.1 correctly on a first install requires two options to be set: discovery.seed_hosts to…
Read More