We fixed some bugs related to the Elastic JVM configurations, that was duplicating log files in the default directory. The JVM configurations are now up to date and the organization of configuration files has been improved.
El Proxy
We fixed a bug in El Proxy related to the retry strategy for sending signed logs to Elasticsearch. Previously, after a document has been rejected from the Elasticsearch ingest pipeline, all non-signed logs were deleted during the retry phase including the mandatory “timestamp” field. Our solution now ensures that all mandatory fields remain intact during the retry strategy. Additionally, we enhanced the logging of El Proxy errors in the DLQ logs for easier debugging.
Logstash Elastic Agent input port
We fixed a bug for which the port, used by Logstash to listen from events coming from Elastic Agent, was not opened on the firewall of some of the Operative Nodes.
NetEye Setup
During new cluster installations, the /etc/neteye-cluster configuration file was missing a field indicating the creation timestamp of the cluster. We fixed this bug by reintroducing the missing field in new cluster installations.
Upgrade Manager
We fixed a bug in the upgrade procedure related to fencing. The procedure now, whenever an update of pacemaker or corosync is present, ensures fencing is disabled to prevent possible issues when nodes are put in standby.
Furthermore, we fixed an issue related with the check of missing updates, which may have given an error in case a change of RedHat Release.
Updated packages
We updated the following packages:
elastic-agent, elastic-agent-neteye-config, elastic-stack-configurator, elasticsearch, elasticsearch-neteye-config, elasticsearch-xpack-license, filebeat, filebeat-neteye-config, kibana, kibana-neteye-config, logstash, logstash-neteye-config to version 8.11.3_neteye3.63.5-1
neteye-setup, neteye-setup-configurator to version 1.127.1-1
elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup, elastic-blockchain-proxy-configurator to version 1.2.5-1
We fixed a procmail misconfiguration that was occurring after the upgrade. We updated the following packages: tornado, tornado-autosetup to version 1.32.2-1
We resolved an issue in the neteye update and neteye upgrade commands where the process would halt if the Elasticsearch cluster took longer than 30 seconds to respond to API requests. We updated the following packages: elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, elastic-stack-configurator, Read More
We resolved a bug in the nginx configuration for our clickhouse integration. This fix guarantees that queries will no longer be directed to the voting-only node in cluster environments, preventing potential errors. We updated the following packages: clickhouse-neteye-config, clickhouse-neteye-config-autosetup, clickhouse-neteye-config-configurator Read More
We fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade. This enhancement guarantees proper pcs resource management throughout this phase. We updated Read More
We fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade, to ensure a correct handling of the resources during this phase. We Read More