search for: scriptstatus

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just set up a CTDB-Cluster with two nodes. In /var/log/log.ctdb I saw the following error many times: - ---------- ERROR: samba tcp port 445, is not responding - ---------- the command "ctdb scriptstatus" is showing: - ---------- root at fs1:~# ctdb scriptstatus 11 scripts were executed last monitor cycle 00.ctdb Status:OK Duration:0.031 Fri Dec 5 14:00:52 2014 01.reclock Status:OK Duration:0.125 Fri Dec 5 14:00:52 2014 10.interface Status:OK Duration:0.2...

...utexes. To enable set TDBMutexEnabled=1. The setting is per node. * New manual page ctdb-statistics.7. Important bug fixes ------------------- * Verify policy routing configuration when starting up to make sure that policy routing tables do not override default routing tables. * "ctdb scriptstatus" should correctly list the number of scripts executed. * Do not run eventscripts at real-time priority. * Make sure "ctdb restoredb" and "ctdb wipedb" cannot affect an ongoing recovery. * If a readonly record revokation fails, CTDB does not abort anymore. It will re...

...informations in the wiki. Anyways... after some try & error i got it working and since i run the Cluster (non-production environment) had no errors except CTDBs monitoring of the Samba process did'nt work as i would expect it (RPC-Server was dead but CTDB did'nt complain and "ctdb scriptstatus" shown "50.Samba - OK") so there could be a little misconfiguration in my following advices couse i did'nt look further into it yet. Anyways... heres what i did: ## IN /etc/ctdb/script.options ## (this was the most tricky thing for me since i use the sernet build) | CTDB_SAMBA_...

...TDB 2.4 =================== User-visible changes -------------------- * A missing network interface now causes monitoring to fail and the node to become unhealthy. * Changed ctdb command's default control timeout from 3s to 10s. * debug-hung-script.sh now includes the output of "ctdb scriptstatus" to provide more information. Important bug fixes ------------------- * Starting CTDB daemon by running ctdbd directly should not remove existing unix socket unconditionally. * ctdbd once again successfully kills client processes on releasing public IPs. It was checking for them as t...

...ges > -------------------- > > * A missing network interface now causes monitoring to fail and the > node to become unhealthy. > > * Changed ctdb command's default control timeout from 3s to 10s. > > * debug-hung-script.sh now includes the output of "ctdb scriptstatus" > to provide more information. > > Important bug fixes > ------------------- > > * Starting CTDB daemon by running ctdbd directly should not remove > existing unix socket unconditionally. > > * ctdbd once again successfully kills client processes on r...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...so > in the past. > > On the server side, DNS names are now more strictly validated. > > CTDB changes > ------------ > > * "ctdb event" is a new top-level command for interacting with event > scripts > > "ctdb event status" replaces "ctdb scriptstatus" - the latter is > maintained for backward compatibility but the output format has been > cleaned up > > "ctdb event run" replaces "ctdb eventscript" > > "ctdb event script enable" replaces "ctdb enablescript" > > "...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...umber of situations where it was not possible to do so in the past. On the server side, DNS names are now more strictly validated. CTDB changes ------------ * "ctdb event" is a new top-level command for interacting with event scripts "ctdb event status" replaces "ctdb scriptstatus" - the latter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" repla...

...> in the past. > > On the server side, DNS names are now more strictly validated. > > CTDB changes > ------------ > > * "ctdb event" is a new top-level command for interacting with event > scripts > > "ctdb event status" replaces "ctdb scriptstatus" - the latter is > maintained for backward compatibility but the output format has been > cleaned up > > "ctdb event run" replaces "ctdb eventscript" > > "ctdb event script enable" replaces "ctdb enablescript" > > &qu...