Displaying 20 results from an estimated 202 matches for "takeover".
2023 Feb 16
1
ctdb tcp kill: remaining connections
...atos.net> wrote:
> Martin Schwenke schrieb am 15.02.2023 23:23:
> > OK, this part looks kind-of good. It would be interesting to know how
> > long the entire failover process is taking.
>
> What exactly would you define as the begin and end of the failover?
From "Takeover run starting" to "Takeover run completed successfully"
in the logs.
>
> >> The log (which I unfortunately do not have anymore) showed 405 of
>
> Hmm, that node where above output was seen hat released and taken
> that very ip shortly before. And then releas...
2011 Mar 25
1
Likelihood of deviation
Hi,
I have a dataset of 78.903 news articles pertaining to 340 corporate
takeovers.
Mean 231.3871 [articles per takeover]
Std. Dev. 673.6395
I would like to calculate the probability of a certain number of news
articles if I had more takeovers available.
How likely is it to have X articles if I had Y takeovers?
How can I do that?
Thank you very much,
Michael
2020 Aug 08
1
CTDB question about "shared file system"
...e plan to have some authentication between nodes when
> they connect. Most likely a shared secret used to generate something
> from the nodes file.
>
> > [...]
> >
> > And after these changes the logs simply have these messages periodically:
> >
> > Disabling takeover runs for 60 seconds
> > Reenabling takeover runs
> >
> > *Is this normal?*
>
> How frequently are these messages logged? They should occur as nodes
> join but should stop after that. If they continue are there any clues
> indicating why takeover runs occurs? A takeo...
2006 Apr 24
1
Stateful Takeover in a Cluster environment
Hey
I am new to Samba and have a few queries.
How can you archieve "Stateful Takeover" for a Samba Session
My goal is to get a samba service running over a cluster.
For the client it is transparent to witch server he connects.
If a node in the cluster dies, the connection will move with all the states
over to another node.
I know Samba 3 is not clusteraware, perhaps anybody kno...
2014 Jul 21
0
CTDB no secrets.tdb created
Hi
2 node ctdb 2.5.3 on Ubuntu 14.04 nodes
apparmor teardown and firewall and stopped dead
The IP takeover is working fine between the nodes:
Jul 21 14:12:03 uc1 ctdbd: recoverd:Trigger takeoverrun
Jul 21 14:12:03 uc1 ctdbd: recoverd:Takeover run starting
Jul 21 14:12:04 uc1 ctdbd: Takeover of IP 192.168.1.81/24 on interface
bond0
Jul 21 14:12:04 uc1 ctdbd: Takeover of IP 192.168.1.80/24 on interface
bo...
2020 Aug 06
2
CTDB question about "shared file system"
...share the information below with you and solicit your fine
feedback :-)
I provide additional detail in case there is something else you feel
strongly we should consider.
We made some changes last night, let me share those with you.
The error that is repeating itself and causing these failures is:
Takeover run starting
RELEASE_IP 10.200.1.230 failed on node 0, ret=-1
Assigning banning credits to node 0
takeover run failed, ret=-1
ctdb_takeover_run() failed
Takeover run unsuccessful
Node 0 reached 4 banning credits - banning it for 300 seconds
Banning node 0 for 300 seconds
Unassigned IP 10.206.2.124...
2016 Nov 10
1
CTDB IP takeover/failover tunables - do you use them?
I'm currently hacking on CTDB's IP takeover/failover code. For Samba
4.6, I would like to rationalise the IP takeover-related tunable
parameters.
I would like to know if there are any users who set the values of these
tunables to non-default values. The tunables in question are:
DisableIPFailover
Default: 0
When set to...
2017 Jan 24
2
public ip is assigned to us but not on an interface - error
hi all
I had a working cluster, very basic, standard. I'm not sure
if recent updates broke it.
I see these:
2017/01/24 22:20:05.025164 [recoverd: 3474]: Public IP
'10.5.10.51' is assigned to us but not on an interface
2017/01/24 22:20:05.027571 [recoverd: 3474]: Trigger takeoverrun
2017/01/24 22:20:05.053386 [recoverd: 3474]: Takeover run
starting
2017/01/24 22:20:05.106044 [ 3309]: Takeover of IP
10.5.10.51/28 on interface eth0
and I wonder if anybody also has come across it?
many thanks,
L.
2017 Aug 31
0
AST-2017-005: Media takeover in RTP stack
Asterisk Project Security Advisory - AST-2017-005
Product Asterisk
Summary Media takeover in RTP stack
Nature of Advisory Unauthorized data disclosure
Susceptibility Remote Unauthenticated Sessions
Severity Critical
Exploits Known...
2023 Feb 13
1
ctdb tcp kill: remaining connections
Hello,
we are using ctdb 4.15.5 on RHEL8 (Kernel 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8 clients. Whenever an ip takeover happens most clients report something like this:
[Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying
[Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying
[Mon Feb 13 12:22:31 2023] nfs: server x.x.253.252 OK
[Mon Feb 13 12:22:31 2023] nfs: ser...
2005 Jan 18
1
External fax modem takeover of fxo?
Given all the issues with the fax DSP code and reliability, I'm looking
into the option of using an external fax modem instead of trying to
shoehorn asterisk into handling faxes properly...
I'm thinking of hooking up the faxmodem to the line directly, then
hooking the X100P to the modem's Phone port.
Can I enable fax detection and use the fax extension to spawn an external
command
2006 Apr 06
1
RE: Drag and drop events. Or: How I learned to takeover the world.
You should open up dragdrop.js in the scriptaculous directory and take a
look at the interface for Draggables/Draggable. There is an event for
dragStart, dragging, and dragEnd (not by those exact names but you
should see them)... sorry I can''t offer more help than just pointing you
in the right direction... very busy. Good luck, nice start!
The information transmitted in this
2023 Jan 26
1
ctdb samba and winbind event problem
...inbindd failed
2023-01-26T16:14:30.603580+01:00 glfs3 ctdbd[15762]: monitor event
failed - disabling node
2023-01-26T16:14:30.604273+01:00 glfs3 ctdbd[15762]: Node became
UNHEALTHY. Ask recovery master to reallocate IPs
2023-01-26T16:14:31.302861+01:00 glfs3 ctdb-recoverd[15867]: Disabling
takeover runs for 60 seconds
2023-01-26T16:14:31.323234+01:00 glfs3 ctdbd[15762]: Release of IP
192.168.0.227/24 on interface ens18 node:0
2023-01-26T16:14:31.409901+01:00 glfs3 ctdb-recoverd[15867]: Reenabling
takeover runs
2023-01-26T16:14:35.654416+01:00 glfs3 ctdb-eventd[15763]: 49.winbind:
ER...
2023 Feb 15
1
ctdb tcp kill: remaining connections
...,
[Sorry for slow response, life is busy...]
On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba
<samba at lists.samba.org> wrote:
> we are using ctdb 4.15.5 on RHEL8 (Kernel
> 4.18.0-372.32.1.el8_6.x86_64) to provide NFS v3 (via tcp) to RHEL7/8
> clients. Whenever an ip takeover happens most clients report
> something like this:
> [Mon Feb 13 12:21:22 2023] nfs: server x.x.253.252 not responding, still trying
> [Mon Feb 13 12:21:28 2023] nfs: server x.x.253.252 not responding, still trying
> [Mon Feb 13 12:22:31 2023] nfs: server x.x.253.252 OK
> [Mon Feb 1...
2008 Feb 12
1
CTDB and LDAP: anyone?
...ap backend = tdb2
private dir = /a/directory/on/your/cluster/filesystem
It is vital that the private directory is on shared storage.)
2. I have got the git tree as mentioned on the CTDB pages; however it
seems like 3.2.0pre1 will also support this; which should I go with?
3. Do I have to use IP takeover? All I am trying to do in this case is
to consistently provide the home directories and profiles on both the
PDC and BDC (I'm using GFS over iSCSI).
It doesn't matter if the IP address of either box vanishes - since they
are both domain controllers the still-living box should be used anywa...
2020 Aug 08
0
CTDB question about "shared file system"
...n a private network.
In the future we plan to have some authentication between nodes when
they connect. Most likely a shared secret used to generate something
from the nodes file.
> [...]
>
> And after these changes the logs simply have these messages periodically:
>
> Disabling takeover runs for 60 seconds
> Reenabling takeover runs
>
> *Is this normal?*
How frequently are these messages logged? They should occur as nodes
join but should stop after that. If they continue are there any clues
indicating why takeover runs occurs? A takeover run is just what CTDB
current...
2018 May 04
2
CTDB Path
Hello,
at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE!
I compiled samba as follow:
|./configure| |--with-cluster-support
||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad|
The whole SAMBA enviroment is located in /usr/local/samba/.
CTDB is located in /usr/local/samba/etc/ctdb.
I guess right that the correct path of ctdbd.conf (node file, public
address file
2007 Oct 10
3
failover with conntrackd
...hines. It works
the first time, but if a second failover happens, the client continues
to send stuff to the wrong MAC address. Linux machines work fine.
I''ve noticed similar reports from other people, but nothing that seemed
like a solution.
Has anyone experimented with doing MAC address takeover too? That seems
like it ought to work, but I haven''t tried it out because neither ucarp
nor keepalived seem to implement it; and I wondered if I was missing
something. What do other people do?
-- ams
2023 Feb 16
1
ctdb tcp kill: remaining connections
...Yes, I have seen this.
> I doubt it is a timeout issue. The default timeouts have been used
> successfully in very large scale deployments.
Have there been tuning to the tcp networking stack in Linux, maybe?
> The main part of resetting client connections is done by ctdbd on the
> takeover node(s).
>
> The first possible point of failure is that CTDB only updates NFS
> connections in 60.nfs monitor events, every ~15 seconds. If there is a
> lot of unmounting/mounting happening then CTDB could be missing some
> connections on the takeover node. However, this isn'...
2023 Jan 26
1
ctdb samba and winbind event problem
...0.603580+01:00 glfs3 ctdbd[15762]: monitor event
> failed - disabling node
>
> 2023-01-26T16:14:30.604273+01:00 glfs3 ctdbd[15762]: Node became
> UNHEALTHY. Ask recovery master to reallocate IPs
>
> 2023-01-26T16:14:31.302861+01:00 glfs3 ctdb-recoverd[15867]: Disabling
> takeover runs for 60 seconds
>
> 2023-01-26T16:14:31.323234+01:00 glfs3 ctdbd[15762]: Release of IP
> 192.168.0.227/24 on interface ens18 node:0
>
> 2023-01-26T16:14:31.409901+01:00 glfs3 ctdb-recoverd[15867]: Reenabling
> takeover runs
>
> 2023-01-26T16:14:35.654416+01:00 g...