| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
update nfs to try to restart the service after 10 consecutive failures
and to flag the node unhealthy after 15
add similar function to mountd
(This used to be ctdb commit 1569a54bb82fc433895ed68f816cf48399ad9d40)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rename loadconfig() to _loadconfig(). Add a new loadconfig() that
simply calls _loadconfig().
This makes it easy for the test suite to override loadconfig().
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 1d77a3adfff893b3c01b87f791e72c0d3148425c)
|
| |
| |
| |
| |
| |
| | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 26077e6c8eb126584af587e7416154ea4858aea2)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These failures are sometimes the result of slow restarts so we want to
avoid dirtying the logs or marking a node unhealthy because of them,
unless they are excessive.
For these 2 cases we use the existing fail counting code but hack a
temporary service_name in a subshell to allow separate fail counts.
We also update ctdb_check_rpc() so that it captures the error output
from rpcinfo and we add a message including the service name to the
beginning. The error is printed to stdout but is also stored in
ctdb_check_rpc_out to allow it to be conditionally used by the caller.
This function also now returns non-zero rather than exiting on
failure.
Other direct rpcinfo calls are relaced by called to ctdb_check_rpc()
for consistency.
Option handling code for service restarts is cleaned up so that fits
in 80 columns. A more informative restart messageis now used in all
cases, printing the exact command being used to start a service.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 79c25fe241cf5d8f92e23d3736823ebaf4e1769d)
|
| |
| |
| |
| |
| |
| | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit ad18bfa398e582474afe25340368e39d4e74e3c6)
|
| |
| |
| |
| |
| |
| | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit a9f5ae2a548e1096c086888adc886cb604d372fa)
|
| |
| |
| |
| |
| |
| | |
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 9e88466a99b5245d5f0ebab553be8d2b9b9a58e2)
|
| |
| |
| |
| |
| |
| | |
this makes "ctdb statistics" show correct "start of starts collection"
(This used to be ctdb commit 7303058616fdb1d7f58cce2349c034e9f611275e)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
since if they are the same for whatever reason this triggers the system
to go into an infinite loop and is unrobust
The scriptds have been changed instead to be able to cope with this
situation for enhanced robustness
During takeover_run and when merging all ip allocations across the cluster
try to kepe track of when and which node currently hosts an ip address
so that we avoid extra ip failovers between nodes
(This used to be ctdb commit cf778b5aaf6356401e3985acccc7df9e08ab6930)
|
| |
| |
| |
| | |
(This used to be ctdb commit cd09c3f8fd9700261f77779aee9cf71dbd4e441e)
|
| |
| |
| |
| | |
(This used to be ctdb commit 441ad00af842a8b7b5291de60d8ab08a064f5327)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
loops
on any kind of tiny unexpected error
unconditionally try to remove ip addresses from both old and new interface
before trying to add it to the new interface to make it less
fragile
(This used to be ctdb commit 80acca2c91c9053c799365bae918db7ed8bdc56f)
|
| |
| |
| |
| |
| |
| |
| | |
this stops the script from failing with an error if
both interfaces are specified as the same, which otherwise breaks and leads to an infinite recovery loop
(This used to be ctdb commit 565de03a784ed441490f8cd0b137b5cec8716d55)
|
| |
| |
| |
| |
| |
| | |
transport and discovered ouw own pnn number
(This used to be ctdb commit 1b57fc866fc836b5dbd3ef7b646e5a0f4280e81e)
|
| |
| |
| |
| |
| |
| | |
already hosting the public address, if so, set ourselves up as the pnn for that address
(This used to be ctdb commit 0f2a2dac91a61be188c3578c8bb89d47cbf9a0f8)
|
| |
| |
| |
| |
| |
| | |
when public ips have been disabled
(This used to be ctdb commit 7d07a74dc7f907ac757d20626f68e257d7ba16be)
|
| |
| |
| |
| |
| |
| | |
will stopp any ip reallocations at all from happening.
(This used to be ctdb commit d8d37493478a26c5f1809a5f3df89ffd6e149281)
|
| |
| |
| |
| | |
(This used to be ctdb commit e5f03346133157734b4759d43c3ab8203028d5c2)
|
| |
| |
| |
| |
| |
| | |
leave any ips as they are and let the recovery daemon remove them as required
(This used to be ctdb commit 8ab311719857847b4cf327507b0af1793551e73c)
|
| |
| |
| |
| |
| |
| | |
interface specified
(This used to be ctdb commit 4308935ba48ac7a29e7523315acf580019715f0f)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ctdb can also be configured to ignore checking for knfsd and if it is alive.
In that situation, no attempt will be made to restart nfs, and sicne nfs is not running, lockd can not be restarted either.
To workaround this, everytime we try to restart the lockmanager, also try to restart nfsd
(This used to be ctdb commit 953dbfbddad656a64e30a6aca115cb1479d11573)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
from all other nodes but before we have stopped all processing.
During this window we may still hit asynchronous events that will fail because we can not send/receive packets from other nodes.
These messages are logged as ... Transport is DOWN. To help indicate that they are benign messages related to the process of shutting down.
These messages spam the syslog during normal shutdown, so this patch will drop the loglevel of these messages to DEBUG, so that they will not appear in or spam the syslog.
(This used to be ctdb commit 8275d265d2ae19b765e30ecf18f6b6319b6e6453)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
even if we are not currently the natgw master.
This adds extra reliability in case we have stopped previously without removing it proper,
but does add spam messages to syslog everytime we shutdowm.
Remove these spam messages from pulluting the syslog upon normal shutdown
(This used to be ctdb commit cd84da6f247ee46bbab8318298d1cd3cfc87aba9)
|
| |
| |
| |
| |
| |
| |
| | |
Normally, the config.tdb database would not exist, so we do not need
to spam syslog with a "config.tdb does not exist" message every time we start ctdb
(This used to be ctdb commit 5792809b72e534161c5ca9ef5c9897abcb3b899c)
|
| |
| |
| |
| |
| |
| | |
so that we dont spam the logs with this normal benign message.
(This used to be ctdb commit dc57df549854e329b453ef14cff5cd352632ef73)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SRVID for the control to attach to a database is used to pass
tdb flags from samba to ctdb when samba attached to a database.
This has been used earlier for TDB_NOSYNC flag.
Add TDB_INCOMPATIBLE_HASH as a supported tdb flag to store in the
SRVID field when attaching to a database.
This allows samba to control if ctdb should create databases using the
new jenkins hash, or using the old hash.
This only affects new databases when they are initially created.
Existing databases remain using the old hash when attached to.
(This used to be ctdb commit e0eda175ac979828b376e8a6779b4608af52eb32)
|
| |
| |
| |
| | |
(This used to be ctdb commit 401ad5bb3c4d2f34e34c4b61649c77391ac2f791)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 70e92ccc4e0afb8c166d40d09ccad1cdc145892c)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 4cb12fa01749aabd5ad6c73defba8a0204b54978)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit ad4619f1eb1c7c8881fd6e65cdce3b9ed15ce0dd)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 6f41dd35bda6de0501fa48a75148bb818ffdceed)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 63ad4a7fe7bd7c9597a4f5573e87f66e5234eb48)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 7a5790de22e8370b2812414aa1adef8201e8b269)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 4ec99c1eeab529865ac790ef554f3b099a14faf1)
|
| |
| |
| |
| |
| |
| | |
metze
(This used to be ctdb commit 034635418c7e5274d6bdf4cccc7a10e3b631e2d4)
|
| |
| |
| |
| |
| |
| | |
print errno so we get some idea of why this failed.
(This used to be ctdb commit 3695462ade497356d1b86c6fd1bc1765f1d11e57)
|
| |
| |
| |
| | |
(This used to be ctdb commit 2913cc93a9a172caf9e0d6675cfa4de4cc957b13)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
from the ctdb command.
This is a debugging message and is normal tro tigger on a busy system.
It should not be logged as ERROR.
(This used to be ctdb commit 9ddf89e01f1845eec1712d75fb811240e8bb0e37)
|
| |
| |
| |
| |
| |
| |
| |
| | |
"update trigger" file.
CQ 1020344
(This used to be ctdb commit 171f98f6f7ce7d01f47c44043ad599702711b12d)
|
| |
| |
| |
| |
| |
| | |
into its own function
(This used to be ctdb commit 2d478a39ed8303b0371112d61630660d12b7db2c)
|
| |
| |
| |
| | |
(This used to be ctdb commit 1919e949af4641ffe919123e44b02fb87c13ab9f)
|
| |
| |
| |
| |
| |
| |
| | |
This can sometimes improve performance for environments where very many
files are touched in rapid succession
(This used to be ctdb commit 15455a13863105a87d2cae9f06eed7435898c30b)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f7e91ae905cd61249028e15f2cb509ea69f10b9e.
This may require a change to the ctdb protocol, or a mechanism
to negotiate/verify that we dont run with different hash fucntions
across the cluster.
Reverting the change until we decide how to solve this in the master
version.
(This used to be ctdb commit 2a2a7a201c90462295544ca23c8a3e215f140622)
|
| |
| |
| |
| |
| |
| | |
continue the loop to process all other interfaces too
(This used to be ctdb commit 500ade4e6a58ea786a665f6be7cf30f43c882570)
|
| |
| |
| |
| |
| |
| |
| | |
Add a missing $
so we delete $_ip and not _ip
(This used to be ctdb commit e9d04c5f419eaa0338a3beefba32c52be00242a8)
|
| |
| |
| |
| |
| |
| |
| |
| | |
from the tdb library
cq S1020233
(This used to be ctdb commit f7e91ae905cd61249028e15f2cb509ea69f10b9e)
|
| |\
| | |
| | |
| | | |
(This used to be ctdb commit 23510bf858c06a3710d1cc741d32bad3675fd97e)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Right-shifting signed integers in undefined; indeed it seems that on
AIX with their compiler, doing a 30-bit shift on (INT_MAX-200) gives
0, not 1 as we might expect.
The obvious fix is to make id and oid unsigned: l (level count) is also
logically unsigned.
(Note: Samba doesn't generally get to ids > 1 billion, but ctdb does)
Reported-by: Chris Cowan <cc@us.ibm.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Autobuild-User: Rusty Russell <rusty@samba.org>
Autobuild-Date: Wed Oct 6 08:31:09 UTC 2010 on sn-devel-104
(This used to be ctdb commit 53d49df2d4519c35b270c30660e2504af2a5ed5c)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 2b81314eb94d31f4efadd2a3dcf2f6e176338d3f)
|
| | |
| | |
| | |
| | | |
(This used to be ctdb commit 247dacde0d0de1358cc2c27d08914be605272023)
|