search for: monitortimeoutcount

...t better... Yes, I am quite happy with the ctdb_killtcp. > For ctdb_killtcp, when it was basically rewritten, we considered adding > options for max_attempts, but decided to see if it was foolproof. We > could now add those options. Patches welcome too... I'll have a look. > MonitorTimeoutCount defaults to 20 but can also be changed. > > For this, you should check the output of: > > ctdb event status legacy monitor > All the scripts should be taking less than about 1s. They normally do. But I have missed the MonitorTimeoutCount completely. > If 50.samba is taking...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...vent quorumLoss --parms "disable" > > mmaddcallback ctdb-enable-on-quorumReached \ > --command /usr/bin/ctdb \ > --event quorumReached --parms "enable" > > * The CTDB tunable parameter EventScriptTimeoutCount has been renamed > to MonitorTimeoutCount > > It has only ever been used to limit timed-out monitor events. > > Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will > cause CTDB to fail at startup. Useful messages will be logged. > > * The commandline option "-n all" to CTDB too...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...

...--command /usr/bin/ctdb \ --event quorumLoss --parms "disable" mmaddcallback ctdb-enable-on-quorumReached \ --command /usr/bin/ctdb \ --event quorumReached --parms "enable" * The CTDB tunable parameter EventScriptTimeoutCount has been renamed to MonitorTimeoutCount It has only ever been used to limit timed-out monitor events. Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will cause CTDB to fail at startup. Useful messages will be logged. * The commandline option "-n all" to CTDB tool has been removed. The option w...