1. Home
  2. Docs
  3. ClusterControl
  4. Changelogs
  5. Changes in v1.9.2

Changes in v1.9.2

Maintenance Release: May 13th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5450
    • clustercontrol-1.9.2-8318
  • Controller:
    • Address an issue where pg_backrest created the directory /home/pgbackrest. It now uses /var/lib/pgbackrest instead (CLUS-1173)
    • Address an issue with warnings of a non-existing maxscale1.log file (CLUS-1246)
    • Address an issue with Microsoft SQL Server deployment due to the failure of creating a SA user (CCv2-281)
  • Frontend (UI):
    • Address an issue with Cluster to Cluster replication where it showed duplicated clusters (CLUS-1229)

Maintenance Release: April 24th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5384
  • Controller:
    • Address an issue to allow adding a new slave even if log_slave_updates was not set on a master (CLUS-1254)
    • Address an issue to only install required snmp packages if snmp has been enabled (CLUS-1138)
    • Address an issue promoting a Microsoft SQL Server replica to become a new primary (CCV2-323)

Maintenance Release: April 14th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5345
  • Controller:
    • Address an issue with the installation of the snmptrap package (CLUS-1138)
    • Address an issue deploying MariaDB Galera with SSL enabled (CLUS-1208)

Maintenance Release: March 28th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5308
  • Controller:
    • Address an issue with MySQL 8.x when accessing DB Users and Schemas. New privileges for MySQL 8.x added to our parser. (CLUS-1154)

Maintenance Release: March 21st, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5292
    • clustercontrol-1.9.2-8273
  • Controller:
    • Address an issue when PgBackRest was setup to use the same host as the backup verification host (CLUS-1173)
    • Address an issue with deprecated SSL parameters that are no longer in use with MySQL 5.7.34 and 8.0.24 and newer versions (CLUS-1093)
    • Address an issue to execute snmptrap with sudo to run as root (CLUS-1138)
    • Address an issue with MS SQL Server to handle overriding existing /etc/odbcinst.ini to use the correct odbc ini file (CCV2-305)
    • Address an issue where setting disk space thresholds for Critical and Warning to 100% still sent alarms (CLUS-1144)
  • Frontend (UI):
    • Address an issue with blank ProxySQL pages for Monitoring, Users, Rules, and Variables (CLUS-1162)

Maintenance Release: March 7th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5242
    • clustercontrol-1.9.2-8244
  • Controller:
    • Address an issue with snmptrap installation on RHEL 8 and improve tracing for troubleshooting (CLUS-1138)
    • Address an issue with MS SQL server cluster where a node was verified twice (CCV-279)
    • Address an issue with MS SQL Server which requires that the hostname used for the nodes are identical to what the hostname command returns on the hosts. The hostname requirement will stop a deployment job much earlier (CCV-281)
    • Address an issue importing MariaDB Galera cluster where wsrep_incoming_addresses values were all AUTO (CLUS-1137)
    • Address an issue where the disk filled up without any alarms. The home, staging and backup directories are now all monitored (CLUS-1082)
  • Frontend (UI):
    • Address an issue when upgrading ClusterControl with ProxySQL v1.x which has been deprecated. An upgrade message is now shown instead of a broken page (CLUS-1130)
Attention

We no longer support ProxySQL v1.x since ClusterControl v1.9.0. Please upgrade to ProxySQL 2.x.

Maintenance Release: February 28th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5214
    • clustercontrol-1.9.2-8236
  • Controller:
    • Address an issue with PgBackRest installations where the rpm EPEL repo was not installed (CLUS-745)
    • Address an issue where the /etc/passwd file was used to check for existing users. This file is no longer used. (CLUS-1134)
    • Address an issue with single node MS SQL server clusters which failed to show up in the cluster and node lists (CCV2-279)
    • Address issues with the CMON agents where the status returned was “none” and storage usage of /var/lib/cmnd/.storageConnection, Default storage retention is changed from 7 days to 24h (CLUS-1112)
    • Address an issue with CC user management where the system users and groups failed to be automatically created
    • Address an issue with log “pollution” where pulling non-existing log files was repeatedly mentioned (CLUS-953)
    • Address an issue with patch management where Installed packages were empty with PostgreSQL 14 (CLUS-1039)
    • Address an issue with MySQL recovery when the error code is either 2002 or 2003 (CLUS-1117)
    • Address an issue with license checks for MySQL and MongoDB (CLUS-791)
    • Upgrade of MySQL Oracle repository signing key
  • Frontend (UI):
    • Address an issue with spotlight where the CMON agents’ state was shown as unknown (CLUS-782)

Maintenance Release: February 18th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5177
    • clustercontrol-1.9.2-8229
  • Controller:
    • Address an issue where MaxScale failed to be deployed due to trying to install the deprecated mmmon monitor (CLUS-1068)
  • Frontend (UI):
    • Address an issue where MongoDB replicaset cluster failed to be converted to a sharded cluster (CLUS-903)
    • Address an issue where PostgreSQL v9.6 still could be selected for deployment (CLUS-1104)

Maintenance Release: February 16th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5168
  • Controller:
    •  Address further issues with Percona xtrabackup v8.0.27 and later versions (CLUS-1072)

Maintenance Release: February 14th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5155
    • clustercontrol-1.9.2-8223
  • Controller:
    • Address an issue where a failed authentication response is missing an error message (CLUS-1067)
    • Address an issue where ProxySQL credentials were exposed in the job log (CLUS-1079)
    • Address an issue to support Percona xtrabackup v8.0.27 and newer (CLUS-1072)
    • Address an issue where stopping and (re)starting a MySQL Replication node failed due to the node not being part of the topology (CLUS-1091)
  • Frontend (UI):
    • Address a potential php API vulnerability where code could be executed through the endpoint (CLUS-1033)
    • Address an issue with the PostgresQL import wizard where the basedir is not needed (CLUS-1035)
    • Address an issue where adding a MongoDB shard fails due to a wrong configuration template in the job spec (CLUS-826)

Maintenance Release: February 4th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5116
    • clustercontrol-1.9.2-8218
  • Controller:
    • Address an issue where failed MongoDB import job log entries were missing in the CMON logs (CLUS-1066)
    • Address an issue were the CMON logs were spammed with CMON Cloud refresh log entries (CLUS-1065)
    • Address an issue with CMON crashing when importing a MongoDB cluster (CLUS-1061)
    • Address an issue where restarting CMON would change a secondary Microsoft SQL Server replication state (CLUS-1049)
    • Address an issue where the Microsoft SQL Server password was not ODBC string safe
  • Frontend (UI):
    • Address an issue where a ProxySQL node could not be installed on an arbitrary host (CLUS-945 take 2)
    • Address an issue where the created timestamp for failed backups were missing in the alarms log/view (CLUS-733)
    • Address an issue where the Keepalived deployment deployment button was broken (CLUS-1040)

Maintenance Release: January 27th, 2022

  • Build:
    • clustercontrol-controller-1.9.2-5090
  • Controller:
    • Address an issue where read-only was set for the MySQL server (primary) due to differences in the hostname saved in ClusterControl at deploy/import time vs the report_host in the my.cnf file (CLUS-919 reopened)
    • Address issues with Microsoft SQL Server:
      • Improve Start node by waiting for 30s (default) to check if the SQL Server has been started and is accepting queries after a start service has been requested (CLUS-1042)
      • CREATE MASTER KEY was created twice (CLUS-1038)
    • Address an issue where the CMON log file contains cmon-cloud entries when there are no cloud integrations configured (CLUS-992)

Maintenance Release: January 25th, 2022

  • Build:
    • clustercontrol-1.9.2-8197
    • clustercontrol-controller-1.9.2-5066
  • Frontend (UI):
    • Address an issue with shell_exec (PHP) where a user could inject and run potential malicious code (CLUS-1033)
    • Address an issue with broken documentation links on the deployment/import wizard (CLUS-995)
    • Address an issue with inconsistent timestamp on failed backup alarms for the web frontend (CLUS-733)
  • Controller:
    • Address issues with Microsoft SQL Server
      • Create a default DB admindb’ for AlwaysOn Availability Group (CLUS-1005)
      • Promote Secondary with force=false did not work properly (CLUS-1017)
      • The monitor user and certs for backups were only created on the primary and not for all nodes (CLUS-1042)
    • Address issues with imperative scripts (CLUS-1011)
      • validate_sst_auth.js – not applicable on PXC 8.0
      • grant_no_password.jsmysql.pxc.sst.role does not have a password so that is ok
      • unused_indexes.js – do not inspect p_s schema
    • Address an issue with HAProxy and PostgreSQL where RW and RO ports (rw_splitting) were not handled properly (CLUS-1031)

Initial Release: January 13th, 2022

  • Build:
    • clustercontrol-1.9.2-8197
    • clustercontrol2-0.50-281
    • clustercontrol-controller-1.9.2-5066
    • clustercontrol-cloud-1.9.2-332
    • clustercontrol-ssh-1.9.2-118
    • clustercontrol-notifications-1.9.2-306

With our first release of ClusterControl in 2022, we are excited to introduce support for Always On Availability Groups with MS SQL Server 2019. This is a high availability deployment that does not require a shared storage solution and instead uses a replication setup for the Microsoft SQL Server nodes. It can be used for read-scaling, to offload backups to a secondary node, or to provide fault tolerance.

You can also now enable SNMP traps to send alarms/alerts to SNMP monitoring systems. This will enable our customers to centralize notifications for their managed services and devices with EMS management platforms. It can help reduce the email load and make the alerts more visible in a centralized location and can be corrected in a more timely manner.

And finally, support has been added for the latest versions of AlmaLinux 8.x, RockyLinux 8.x Debian 11.x, MariaDB 10.6, PostgreSQL v14 and TimescaleDB.

Let us know what you think about these features and changes anytime at submitting feedback!

Features

Microsoft SQL Server 2019

  • Always On availability groups with Microsoft SQL Server 2019
    • Deploy 1 primary and up to 7 replica nodes.
    • Automatic failover of failed primary / Promote replica to primary.
    • Performance monitoring.
    • Upload backups to the cloud.
  • Current limitations:
    • Only asynchronous replication mode is supported for AlwaysOn.
    • Only Ubuntu 20.04 and RedHat/Centos 8 are supported.
    • Rebuild replication node is currently not supported.
    • Only Microsoft SQL Server 2019 is supported.
    • Configuration files management, Scaling, and Upgrades are not supported.
    • Backups cannot be stored on the Controller (CMON) host.
    • SSL/TLS is not supported.

Simple Network Management Protocol – SNMP (v2c)

  • Send ClusterControl alarms/alerts to SNMP monitoring systems with SNMP traps.
    • Easy to enable by adding an SNMP monitoring/target host, port and a trap community string.
      • Edit the CMON configuration file directly or make the changes using the ‘Runtime configuration’
    • Automatically generates a ClusterControl MIB file.
    • Severalnines Private Enterprise Number (PEN) is 57397.
  • Current limitations:
    • Only support for SNMP v2c protocol.
    • No client-side filtering of the alarms – all alarms are sent to the SNMP monitoring host.
    • Only one SNMP monitoring target/host can be specified.

ClusterControl v2

  • Deploy Always On availability group for Microsoft SQL Server 2019
  • Cloud backups – upload backups to any S3-compliant cloud storage provider
  • Performance monitoring:
    • MS SQL Server 2019

New versions support

  • AlmaLinux 8.x, RockyLinux 8.x, Debian 11.x.
  • MariaDB 10.6.
  • PostgreSQL v14.
  • TimescaleDB with PostgreSQL v13 and v14.

FAQs

Q: How can I start using ‘Always on Availability Groups’ with MS SQL Server?

A: Please follow the instructions outlined in the Getting Started with ClusterControl v2 to install ClusterControl v2 and then use the Service Deployment wizard to deploy the AlwaysOn Availbility Group Microsoft SQL Server 2019 database.

 

Q: What is Always On Availability Groups – Always AG for MS SQL Server?

A: It is a replicated environment where you have one primary replica node and up to 7 secondary replicas using asynchronous replication. It doesn’t require a shared storage solution like AlwaysOn Failover Cluster Instances.

 

Q: How many secondary MS SQL Server replicas can I deploy?

A: You can deploy up to 7 replica nodes.

 

Q: How can I get started using SNMP with ClusterControl?

A: You need to edit your cluster’s CMON configuration file and add a few parameters. The file is usually located at /etc/cmon.d/cmon_N.cnf where N is your ‘clusterID’. The parameters to add are:

snmp_trap_target_host={SNMP monitoring host} # The SNMP monitoring host/target (required).
snmp_trap_target_port=162                    # The default SNMP port to use (optional).
snmp_community_str='private'                 # Default SNMP trap community string (optional).

You can also edit/add these parameters by using the ‘Runtime configuration’ for the cluster. After you have set these configuration parameters the last step is to restart the CMON process.

$ systemctl restart cmon

You can verify that SNMP has been enabled by:

1) Check the /var/log/cmon.log file for the following package installation output:

2021-12-23T04:55:56.617Z : (INFO) Installing SNMP requirement: snmp
2021-12-23T04:56:29.649Z : (INFO) Installing SNMP requirement: snmp-mibs-downloader

2) Verify that the ClusterControl (CMON) mib file has been generated/created:

$ ls -l /usr/share/snmp/mibs/SEVERALNINES-CLUSTERCONTROL-MIB.txt
-rw-r--r-- 1 root root 47012 Dec 23 04:57 /usr/share/snmp/mibs/SEVERALNINES-CLUSTERCONTROL-MIB.txt

This file can also be copied to the SNMP manager to be used there if needed.

 

Q: Which version of the SNMP protocol do you support?

A: There are three different versions of SNMP:

  • SNMP version 1 (SNMPv1) – This was the first implementation, operating within the structure management information specification, and described in RFC 1157.
  • SNMP version 2 (SNMPv2) – This version was improved to support more efficient error handling and is described in RFC 1901. It was first introduced as RFC 1441. It is often referred to as SNMPv2c.
  • SNMP version 3 (SNMPv3) – This version improves security and privacy. It was introduced in RFC 3410.
  • SNMP version 2 is the most commonly deployed SNMP protocol version today.
  • The most recent version, SNMP version 3, includes new security features that add support for authentication and encryption of SNMP messages as well as protecting packets during transit.

We support only SNMPv2 at the moment.

 

Q: How does ClusterControl provide SNMP integration/support?

A: ClusterControl uses the command-line tool snmptrap to send traps to an SNMP monitoring host.

 

Q: What is Severalnines MIB’s Private Enterprise Number – PEN?

A: It is 57397.

 

Q: What is a Management Information Base – MIB?

A: SNMP Management Information Bases (called MIBs for short) are data structures that define what can be collected from the local device or software and what can be changed and configured.
There are many MIBs defined by standards bodies such as the IETF and ISO, as well as proprietary MIBs defined by specific IT equipment vendors.

 

Q: What does our ClusterControl MIB look like?

A: The example of ClusterControl MIB is available here.

Was this article helpful to you? Yes No