From 28142b49a8458fa5fa4b4aa15b2ae3d18059d64c Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Wed, 12 Feb 2025 15:10:32 -0500 Subject: [PATCH 01/11] Update kvm.rst - iptables before rule On Ubuntu 24.04 LTS I found the described issue with the forwarding traffic back and fourth from guests system VMs and the physical interfaces attached to the bridges. This solved my problems. --- source/installguide/hypervisor/kvm.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/installguide/hypervisor/kvm.rst b/source/installguide/hypervisor/kvm.rst index 969730cc26..beadf39cc1 100644 --- a/source/installguide/hypervisor/kvm.rst +++ b/source/installguide/hypervisor/kvm.rst @@ -1551,8 +1551,8 @@ To open the required ports, execute the following commands: sudo vi /etc/ufw/before.rules .. parsed-literal:: - -A FORWARD -d 192.168.42.11 -j ACCEPT - -A FORWARD -s 192.168.42.11 -j ACCEPT + -A FORWARD -d 192.168.42.0/24 -j ACCEPT + -A FORWARD -s 192.168.42.0/24 -j ACCEPT Additional Packages Required for Features From 5345f3957547bdf1ea4ec10f120c0480393c79e9 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 18 Feb 2025 21:55:21 -0500 Subject: [PATCH 02/11] Update qig.rst --- source/quickinstallationguide/qig.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/quickinstallationguide/qig.rst b/source/quickinstallationguide/qig.rst index da74fe90cf..346e1f2951 100644 --- a/source/quickinstallationguide/qig.rst +++ b/source/quickinstallationguide/qig.rst @@ -353,8 +353,8 @@ section: innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log-bin=mysql-bin - binlog-format = 'ROW' + log_bin=mysql-bin + binlog_format = 'ROW' Now that MySQL is properly configured we can start it and configure it to From 05641a2046d106e886df1d5299e7261a4c23e0ed Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 18 Feb 2025 21:58:24 -0500 Subject: [PATCH 03/11] Update optional_installation.rst From aca1381e9050494b7f7b6f20f08fb7bb18e15c79 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 18 Feb 2025 22:01:56 -0500 Subject: [PATCH 04/11] Update _database.rst --- .../installguide/management-server/_database.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/installguide/management-server/_database.rst b/source/installguide/management-server/_database.rst index ca70a13e8c..61301d0f02 100644 --- a/source/installguide/management-server/_database.rst +++ b/source/installguide/management-server/_database.rst @@ -64,20 +64,20 @@ MySQL. See :ref:`install-database-on-separate-node`. innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log-bin=mysql-bin - binlog-format = 'ROW' + log_bin=mysql-bin + binlog_format=ROW .. note:: - For Ubuntu 16.04 and later, make sure you specify a ``server-id`` in your ``.cnf`` file for binary logging. Set the ``server-id`` according to your database setup. + For Ubuntu 16.04 and later, make sure you specify a ``server_id`` in your ``/etc/mysql/mysql.conf.d/mysqld.cnf`` file for binary logging. Set the ``server_id`` according to your database setup. .. parsed-literal:: - server-id=source-01 + server_id=source-01 innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log-bin=mysql-bin - binlog-format = 'ROW' + log_bin=mysql-bin + binlog_format=ROW .. note:: You can also create a file ``/etc/mysql/conf.d/cloudstack.cnf`` @@ -328,8 +328,8 @@ same node for MySQL. See `“Install the Database on the Management Server Node innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=700 - log-bin=mysql-bin - binlog-format = 'ROW' + log_bin=mysql-bin + binlog_format = 'ROW' bind-address = 0.0.0.0 #. Start or restart MySQL to put the new configuration into effect. From 1a9c7a461c46c7ecfa2c727df815dffd7409da19 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 18 Feb 2025 22:03:33 -0500 Subject: [PATCH 05/11] Update _database.rst --- source/installguide/management-server/_database.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/installguide/management-server/_database.rst b/source/installguide/management-server/_database.rst index 61301d0f02..8db4fbd355 100644 --- a/source/installguide/management-server/_database.rst +++ b/source/installguide/management-server/_database.rst @@ -329,8 +329,8 @@ same node for MySQL. See `“Install the Database on the Management Server Node innodb_lock_wait_timeout=600 max_connections=700 log_bin=mysql-bin - binlog_format = 'ROW' - bind-address = 0.0.0.0 + binlog_format=ROW + bind-address=0.0.0.0 #. Start or restart MySQL to put the new configuration into effect. From e302881fc76285366094628e10526755e6953721 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 18 Feb 2025 22:05:27 -0500 Subject: [PATCH 06/11] Update qig.rst --- source/quickinstallationguide/qig.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/quickinstallationguide/qig.rst b/source/quickinstallationguide/qig.rst index 346e1f2951..7f08777b19 100644 --- a/source/quickinstallationguide/qig.rst +++ b/source/quickinstallationguide/qig.rst @@ -354,7 +354,7 @@ section: innodb_lock_wait_timeout=600 max_connections=350 log_bin=mysql-bin - binlog_format = 'ROW' + binlog_format=ROW Now that MySQL is properly configured we can start it and configure it to From 44233b1e6e99ac992777e7835cbf532d464436b3 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Tue, 25 Feb 2025 15:53:44 -0500 Subject: [PATCH 07/11] Update kvm.rst --- source/installguide/hypervisor/kvm.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/installguide/hypervisor/kvm.rst b/source/installguide/hypervisor/kvm.rst index beadf39cc1..8acaece3b0 100644 --- a/source/installguide/hypervisor/kvm.rst +++ b/source/installguide/hypervisor/kvm.rst @@ -1551,8 +1551,7 @@ To open the required ports, execute the following commands: sudo vi /etc/ufw/before.rules .. parsed-literal:: - -A FORWARD -d 192.168.42.0/24 -j ACCEPT - -A FORWARD -s 192.168.42.0/24 -j ACCEPT + -A FORWARD -j ACCEPT Additional Packages Required for Features From 6c3f7401a2b048eb9530d0b86ec33153fbede3f5 Mon Sep 17 00:00:00 2001 From: Davi Torres <90287660+daviftorres@users.noreply.github.com> Date: Thu, 27 Feb 2025 08:29:21 -0500 Subject: [PATCH 08/11] Update kvm.rst --- source/installguide/hypervisor/kvm.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/source/installguide/hypervisor/kvm.rst b/source/installguide/hypervisor/kvm.rst index 8acaece3b0..5c969f9707 100644 --- a/source/installguide/hypervisor/kvm.rst +++ b/source/installguide/hypervisor/kvm.rst @@ -1541,17 +1541,17 @@ To open the required ports, execute the following commands: $ ufw allow proto tcp from any to any port 49152:49216 .. note:: - By default UFW is not enabled on Ubuntu. Executing these commands with the - firewall disabled does not enable the firewall. + Since Ubuntu 22.04 LTS, the UFW's default policy for forwarding is set to "DROP". + Change it to "ACCEPT". - If you have an issue with ufw while using a bridged connection, - add those two lines at the end of the /etc/ufw/before.rules just before COMMIT +.. parsed-literal:: + sudo vi /etc/default/ufw .. parsed-literal:: - sudo vi /etc/ufw/before.rules + DEFAULT_FORWARD_POLICY="ACCEPT" .. parsed-literal:: - -A FORWARD -j ACCEPT + sudo ufw enable Additional Packages Required for Features From 30594b5baf145030503fab1ef7449788f883e116 Mon Sep 17 00:00:00 2001 From: Davi Torres Date: Wed, 16 Apr 2025 12:28:11 -0400 Subject: [PATCH 09/11] smtp and threshold settings --- source/adminguide/management.rst | 242 +++++++++++++++++-------------- 1 file changed, 132 insertions(+), 110 deletions(-) diff --git a/source/adminguide/management.rst b/source/adminguide/management.rst index 271faedd47..4621b1f28c 100644 --- a/source/adminguide/management.rst +++ b/source/adminguide/management.rst @@ -231,6 +231,48 @@ Emails will be sent to administrators under the following circumstances: - The Host cluster runs low on CPU, memory, or storage resources +The following global settings are available to configure Alerts via SMTP. + +.. list-table:: Management Alerts Global Settings + :header-rows: 1 + + * - Global setting + - Default + - Description + * - ``alert.smtp.host`` + - `null` + - SMTP hostname used for sending out email alerts. + * - ``alert.smtp.port`` + - `465` + - Port the SMTP server is listening on. + * - ``alert.smtp.useAuth`` + - `false` + - If true, use SMTP authentication when sending emails. + * - ``alert.smtp.username`` + - `null` + - Username for SMTP authentication (applies only if alert.smtp.useAuth is true). + * - ``alert.smtp.password`` + - `null` + - Password for SMTP authentication (applies only if alert.smtp.useAuth is true). + * - ``alert.smtp.useStartTLS`` + - `false` + - If set to true and if we enable security via alert.smtp.useAuth, this will enable StartTLS to secure the connection. + * - ``(alert.smtp.enabledSecurityProtocols`` + - `null` + - White-space separated security protocols; ex: "TLSv1 TLSv1.1". Supported protocols: SSLv2Hello, SSLv3, TLSv1, TLSv1.1 and TLSv1.2 + * - ``alert.smtp.connectiontimeout`` + - `30000` + - Socket connection timeout value in milliseconds. -1 for infinite timeout. + * - ``alert.smtp.timeout`` + - `30000` + - Socket I/O timeout value in milliseconds. -1 for infinite timeout. + * - ``alert.email.addresses`` + - `null` + - Comma separated list of email addresses which are going to receive alert emails. + * - ``alert.email.sender`` + - `null` + - Sender of alert email (will be in the From header of the email). + Sending Alerts to External SNMP and Syslog Managers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -246,116 +288,96 @@ The alerts which can be sent are: The following is the list of alert type numbers. The current alerts can be found by calling listAlerts. -:: - - MEMORY = 0 // Available Memory below configured threshold - -:: - - CPU = 1 // Unallocated CPU below configured threshold - -:: - - STORAGE =2 // Available Storage below configured threshold - -:: - - STORAGE_ALLOCATED = 3 // Remaining unallocated Storage is below configured threshold - -:: - - PUBLIC_IP = 4 // Number of unallocated virtual Network public IPs is below configured threshold - -:: - - PRIVATE_IP = 5 // Number of unallocated private IPs is below configured threshold - -:: - - SECONDARY_STORAGE = 6 // Available Secondary Storage in availability zone is below configured threshold - -:: - - HOST = 7 // Host related alerts like host disconnected - -:: - - USERVM = 8 // User Instance stopped unexpectedly - -:: - - DOMAIN_ROUTER = 9 // Domain Router VM stopped unexpectedly - -:: - - CONSOLE_PROXY = 10 // Console Proxy VM stopped unexpectedly - -:: - - ROUTING = 11 // Lost connection to default route (to the gateway) - -:: - - STORAGE_MISC = 12 // Storage issue in system VMs - -:: - - USAGE_SERVER = 13 // No usage server process running - -:: - - MANAGMENT_NODE = 14 // Management Network CIDR is not configured originally - -:: - - DOMAIN_ROUTER_MIGRATE = 15 // Domain Router VM Migration was unsuccessful - -:: - - CONSOLE_PROXY_MIGRATE = 16 // Console Proxy VM Migration was unsuccessful - -:: - - USERVM_MIGRATE = 17 // User Instance Migration was unsuccessful - -:: - - VLAN = 18 // Number of unallocated VLANs is below configured threshold in availability zone - -:: - - SSVM = 19 // SSVM stopped unexpectedly - -:: - - USAGE_SERVER_RESULT = 20 // Usage job failed - -:: - - STORAGE_DELETE = 21 // Failed to delete storage pool - -:: - - UPDATE_RESOURCE_COUNT = 22 // Failed to update the resource count - -:: - - USAGE_SANITY_RESULT = 23 // Usage Sanity Check failed - -:: - - DIRECT_ATTACHED_PUBLIC_IP = 24 // Number of unallocated shared Network IPs is low in availability zone - -:: - - LOCAL_STORAGE = 25 // Remaining unallocated Local Storage is below configured threshold - -:: - - RESOURCE_LIMIT_EXCEEDED = 26 //Generated when the resource limit exceeds the limit. Currently used for recurring Snapshots only - - -You can also display the most up to date list by calling the API command ``listAlerts``. +.. list-table:: List of Alerts + :header-rows: 1 + + * - Name + - Default + - Description + * - ``MEMORY`` + - `0` + - Available Memory below configured threshold + * - ``CPU`` + - `1` + - Unallocated CPU below configured threshold + * - ``STORAGE`` + - `2` + - Available Storage below configured threshold + * - ``STORAGE_ALLOCATED`` + - `3` + - Remaining unallocated Storage is below configured threshold + * - ``PUBLIC_IP`` + - `4` + - Number of unallocated virtual Network public IPs is below configured threshold + * - ``PRIVATE_IP`` + - `5` + - Number of unallocated private IPs is below configured threshold + * - ``SECONDARY_STORAGE`` + - `6` + - Available Secondary Storage in availability zone is below configured threshold + * - ``HOST`` + - `7` + - Host related alerts like host disconnected + * - ``USERVM`` + - `8` + - User Instance stopped unexpectedly + * - ``DOMAIN_ROUTER`` + - `9` + - Domain Router VM stopped unexpectedly + * - ``CONSOLE_PROXY`` + - `10` + - Console Proxy VM stopped unexpectedly + * - ``ROUTING`` + - `11` + - Lost connection to default route (to the gateway) + * - ``STORAGE_MISC`` + - `12` + - Storage issue in system VMs + * - ``USAGE_SERVER`` + - `13` + - No usage server process running + * - ``MANAGEMENT_NODE`` + - `14` + - Management Network CIDR is not configured originally + * - ``DOMAIN_ROUTER_MIGRATE`` + - `15` + - Domain Router VM Migration was unsuccessful + * - ``CONSOLE_PROXY_MIGRATE`` + - `16` + - Console Proxy VM Migration was unsuccessful + * - ``USERVM_MIGRATE`` + - `17` + - User Instance Migration was unsuccessful + * - ``VLAN`` + - `18` + - Number of unallocated VLANs is below configured threshold in availability zone + * - ``SSVM`` + - `19` + - SSVM stopped unexpectedly + * - ``USAGE_SERVER_RESULT`` + - `20` + - Usage job failed + * - ``STORAGE_DELETE`` + - `21` + - Failed to delete storage pool + * - ``UPDATE_RESOURCE_COUNT`` + - `22` + - Failed to update the resource count + * - ``USAGE_SANITY_RESULT`` + - `23` + - Usage Sanity Check failed + * - ``DIRECT_ATTACHED_PUBLIC_IP`` + - `24` + - Number of unallocated shared Network IPs is low in availability zone + * - ``LOCAL_STORAGE`` + - `25` + - Remaining unallocated Local Storage is below configured threshold + * - ``RESOURCE_LIMIT_EXCEEDED`` + - `26` + - Generated when the resource limit exceeds the limit. Currently used for recurring Snapshots only + + +You can also display the most up to date list by calling the API command ``listAlerts`` or unsing CLoudMonkey ``cmk list alerts``. SNMP Alert Details From d7b4680c3645c004f890cd4a97323975dce317cf Mon Sep 17 00:00:00 2001 From: Davi Torres Date: Wed, 16 Apr 2025 12:39:03 -0400 Subject: [PATCH 10/11] Reordered columns or types --- source/adminguide/management.rst | 112 +++++++++++++++---------------- 1 file changed, 56 insertions(+), 56 deletions(-) diff --git a/source/adminguide/management.rst b/source/adminguide/management.rst index 4621b1f28c..bdaedac062 100644 --- a/source/adminguide/management.rst +++ b/source/adminguide/management.rst @@ -291,89 +291,89 @@ be found by calling listAlerts. .. list-table:: List of Alerts :header-rows: 1 - * - Name - - Default + * - Type Number + - Name - Description - * - ``MEMORY`` - - `0` + * - `0` + - ``MEMORY`` - Available Memory below configured threshold - * - ``CPU`` - - `1` + * - `1` + - ``CPU`` - Unallocated CPU below configured threshold - * - ``STORAGE`` - - `2` + * - `2` + - ``STORAGE`` - Available Storage below configured threshold - * - ``STORAGE_ALLOCATED`` - - `3` + * - `3` + - ``STORAGE_ALLOCATED`` - Remaining unallocated Storage is below configured threshold - * - ``PUBLIC_IP`` - - `4` + * - `4` + - ``PUBLIC_IP`` - Number of unallocated virtual Network public IPs is below configured threshold - * - ``PRIVATE_IP`` - - `5` + * - `5` + - ``PRIVATE_IP`` - Number of unallocated private IPs is below configured threshold - * - ``SECONDARY_STORAGE`` - - `6` + * - `6` + - ``SECONDARY_STORAGE`` - Available Secondary Storage in availability zone is below configured threshold - * - ``HOST`` - - `7` + * - `7` + - ``HOST`` - Host related alerts like host disconnected - * - ``USERVM`` - - `8` + * - `8` + - ``USERVM`` - User Instance stopped unexpectedly - * - ``DOMAIN_ROUTER`` - - `9` + * - `9` + - ``DOMAIN_ROUTER`` - Domain Router VM stopped unexpectedly - * - ``CONSOLE_PROXY`` - - `10` + * - `10` + - ``CONSOLE_PROXY`` - Console Proxy VM stopped unexpectedly - * - ``ROUTING`` - - `11` + * - `11` + - ``ROUTING`` - Lost connection to default route (to the gateway) - * - ``STORAGE_MISC`` - - `12` + * - `12` + - ``STORAGE_MISC`` - Storage issue in system VMs - * - ``USAGE_SERVER`` - - `13` + * - `13` + - ``USAGE_SERVER`` - No usage server process running - * - ``MANAGEMENT_NODE`` - - `14` + * - `14` + - ``MANAGEMENT_NODE`` - Management Network CIDR is not configured originally - * - ``DOMAIN_ROUTER_MIGRATE`` - - `15` + * - `15` + - ``DOMAIN_ROUTER_MIGRATE`` - Domain Router VM Migration was unsuccessful - * - ``CONSOLE_PROXY_MIGRATE`` - - `16` + * - `16` + - ``CONSOLE_PROXY_MIGRATE`` - Console Proxy VM Migration was unsuccessful - * - ``USERVM_MIGRATE`` - - `17` + * - `17` + - ``USERVM_MIGRATE`` - User Instance Migration was unsuccessful - * - ``VLAN`` - - `18` + * - `18` + - ``VLAN`` - Number of unallocated VLANs is below configured threshold in availability zone - * - ``SSVM`` - - `19` + * - `19` + - ``SSVM`` - SSVM stopped unexpectedly - * - ``USAGE_SERVER_RESULT`` - - `20` + * - `20` + - ``USAGE_SERVER_RESULT`` - Usage job failed - * - ``STORAGE_DELETE`` - - `21` + * - `21` + - ``STORAGE_DELETE`` - Failed to delete storage pool - * - ``UPDATE_RESOURCE_COUNT`` - - `22` + * - `22` + - ``UPDATE_RESOURCE_COUNT`` - Failed to update the resource count - * - ``USAGE_SANITY_RESULT`` - - `23` + * - `23` + - ``USAGE_SANITY_RESULT`` - Usage Sanity Check failed - * - ``DIRECT_ATTACHED_PUBLIC_IP`` - - `24` + * - `24` + - ``DIRECT_ATTACHED_PUBLIC_IP`` - Number of unallocated shared Network IPs is low in availability zone - * - ``LOCAL_STORAGE`` - - `25` + * - `25` + - ``LOCAL_STORAGE`` - Remaining unallocated Local Storage is below configured threshold - * - ``RESOURCE_LIMIT_EXCEEDED`` - - `26` + * - `26` + - ``RESOURCE_LIMIT_EXCEEDED`` - Generated when the resource limit exceeds the limit. Currently used for recurring Snapshots only From f17684f4e2d4d5bae9f365580b42490c06056725 Mon Sep 17 00:00:00 2001 From: Davi Torres Date: Wed, 16 Apr 2025 12:42:46 -0400 Subject: [PATCH 11/11] clean up --- source/installguide/hypervisor/kvm.rst | 13 +++++++------ .../management-server/_database.rst | 18 +++++++++--------- source/quickinstallationguide/qig.rst | 4 ++-- 3 files changed, 18 insertions(+), 17 deletions(-) diff --git a/source/installguide/hypervisor/kvm.rst b/source/installguide/hypervisor/kvm.rst index 5c969f9707..969730cc26 100644 --- a/source/installguide/hypervisor/kvm.rst +++ b/source/installguide/hypervisor/kvm.rst @@ -1541,17 +1541,18 @@ To open the required ports, execute the following commands: $ ufw allow proto tcp from any to any port 49152:49216 .. note:: - Since Ubuntu 22.04 LTS, the UFW's default policy for forwarding is set to "DROP". - Change it to "ACCEPT". + By default UFW is not enabled on Ubuntu. Executing these commands with the + firewall disabled does not enable the firewall. -.. parsed-literal:: - sudo vi /etc/default/ufw + If you have an issue with ufw while using a bridged connection, + add those two lines at the end of the /etc/ufw/before.rules just before COMMIT .. parsed-literal:: - DEFAULT_FORWARD_POLICY="ACCEPT" + sudo vi /etc/ufw/before.rules .. parsed-literal:: - sudo ufw enable + -A FORWARD -d 192.168.42.11 -j ACCEPT + -A FORWARD -s 192.168.42.11 -j ACCEPT Additional Packages Required for Features diff --git a/source/installguide/management-server/_database.rst b/source/installguide/management-server/_database.rst index 8db4fbd355..ca70a13e8c 100644 --- a/source/installguide/management-server/_database.rst +++ b/source/installguide/management-server/_database.rst @@ -64,20 +64,20 @@ MySQL. See :ref:`install-database-on-separate-node`. innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log_bin=mysql-bin - binlog_format=ROW + log-bin=mysql-bin + binlog-format = 'ROW' .. note:: - For Ubuntu 16.04 and later, make sure you specify a ``server_id`` in your ``/etc/mysql/mysql.conf.d/mysqld.cnf`` file for binary logging. Set the ``server_id`` according to your database setup. + For Ubuntu 16.04 and later, make sure you specify a ``server-id`` in your ``.cnf`` file for binary logging. Set the ``server-id`` according to your database setup. .. parsed-literal:: - server_id=source-01 + server-id=source-01 innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log_bin=mysql-bin - binlog_format=ROW + log-bin=mysql-bin + binlog-format = 'ROW' .. note:: You can also create a file ``/etc/mysql/conf.d/cloudstack.cnf`` @@ -328,9 +328,9 @@ same node for MySQL. See `“Install the Database on the Management Server Node innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=700 - log_bin=mysql-bin - binlog_format=ROW - bind-address=0.0.0.0 + log-bin=mysql-bin + binlog-format = 'ROW' + bind-address = 0.0.0.0 #. Start or restart MySQL to put the new configuration into effect. diff --git a/source/quickinstallationguide/qig.rst b/source/quickinstallationguide/qig.rst index 7f08777b19..da74fe90cf 100644 --- a/source/quickinstallationguide/qig.rst +++ b/source/quickinstallationguide/qig.rst @@ -353,8 +353,8 @@ section: innodb_rollback_on_timeout=1 innodb_lock_wait_timeout=600 max_connections=350 - log_bin=mysql-bin - binlog_format=ROW + log-bin=mysql-bin + binlog-format = 'ROW' Now that MySQL is properly configured we can start it and configure it to