search for: onnode

...in this series of failover events. Here's how the situation went down: 1) We saw flapping identical to that described in my original post 2) After about 30 minutes of waiting, CTDB was just spinning with `smbd` repeatedly failing its health checks. 3) We stopped CTDB on the cluster with `onnode all service ctdb stop` 4) We moved the following files out of the way: gencache_notrans.tdb gencache.tdb mutex.tdb 5) We started CTDB again with `onnode all service ctdb start` At that point, the CTDB cluster came back up successfully and all has been quiet since yesterday afternoon. We noti...

Hi All, Are there any special CTDB/SMB configuration settings/dependencies to manage Winbind across CTDB managed servers authenticating via Active Directory(AD)? An example would be Samba's IDMAP backend for Winbind: RID vs. AD or tag Winbind to a primary CTDB node and point other nodes to authenticate from AD via proxy primary CTDB node? /etc/sysconfig/ctdb on all nodes is as follows:

Hi All, My site has two separate clustered Samba instances (managed by two independent CTDB instances) running over GPFS. In the last couple of weeks, we have seen a recurring issue that causes the `smbd` process in *one* of these instances to become unresponsive (as seen by CTDB), which results in flapping of CTDB and multiple IP takeover runs. The symptoms that we observe are: 1) Samba

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...K section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands * The onnode command no longer supports the "recmaster", "lvs" and "natgw" node specifications * Faster resetting of TCP connections to public IP addresses during failover * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ignored *...

...K section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands * The onnode command no longer supports the "recmaster", "lvs" and "natgw" node specifications * Faster resetting of TCP connections to public IP addresses during failover * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ignored *...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...organisational units, however large renames are still not recommended. CTDB changes ============ * nfs-linux-kernel-callout now defaults to using systemd service names The Red Hat service names continue to be the default. Other distributions should patch this file when packaging it. * The onnode -o option has been removed * ctdbd logs when it is using more than 90% of a CPU thread ctdbd is single threaded, so can become saturated if it uses the full capacity of a CPU thread. To help detect this situation, ctdbd now logs messages when CPU utilisation exceeds 90%. Each change in...

...ion in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. * Faster resetting of TCP connections to public IP addresses during failover. * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ign...

...ion in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. * Faster resetting of TCP connections to public IP addresses during failover. * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ign...

...ion in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. * Faster resetting of TCP connections to public IP addresses during failover. * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ign...

...ion in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. * Faster resetting of TCP connections to public IP addresses during failover. * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ign...

...ion in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. * Faster resetting of TCP connections to public IP addresses during failover. * Tunables MaxRedirectCount, ReclockPingPeriod, DeferredRebalanceOnNodeAdd are now obsolete/ign...