search for: noiphostonalldisabled

...to the new nodes. An unbalanced cluster will therefore remain unbalanced until there is manual intervention from the administrator. When this parameter is set, you can manually fail public IP addresses over to the new node(s) using the 'ctdb moveip' command. NoIPHostOnAllDisabled Default: 0 If no nodes are HEALTHY then by default ctdb will happily host public IPs on disabled (unhealthy or administratively disabled) nodes. This can cause problems, for example if the underlying cluster filesystem is not mounted. When set to 1 on a node and...

...ipt * The 60.nfs eventscript now uses configuration files in /etc/ctdb/nfs-rpc-checks.d/ for timeouts and actions instead of hardcoding them into the script. * Notification handler scripts can now be dropped into /etc/ctdb/notify.d/. * The NoIPTakeoverOnDisabled tunable has been renamed to NoIPHostOnAllDisabled and now works properly when set on individual nodes. * New ctdb subcommand "runstate" prints the current internal runstate. Runstates are used for serialising startup. Important bug fixes ------------------- * The Unix domain socket is now set to non-blocking after the connection...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...en removed This feature has not been implemented in the new configuration system. If this is desired then a tmpfs filesystem should be manually mounted on the directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...

...he directory pointed to by the "volatile database directory" option. See ctdb.conf(5) for more details. * The following tunable options are now ctdb.conf options: DisabledIPFailover failover -> disabled TDBMutexEnabled database -> tdb mutexes * Support for the NoIPHostOnAllDisabled tunable has been removed If all nodes are unhealthy or disabled then CTDB will not host public IP addresses. That is, CTDB now behaves as if NoIPHostOnAllDisabled were set to 1. * The onnode command's CTDB_NODES_FILE environment variable has been removed The -f option can still be...