Displaying 20 results from an estimated 202 matches for "takeovers".
Did you mean:
takeover
2023 Feb 16
1
ctdb tcp kill: remaining connections
On Thu, 16 Feb 2023 17:30:37 +0000, Ulrich Sibiller
<ulrich.sibiller at 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
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"
On Sat, Aug 8, 2020 at 2:52 AM Martin Schwenke <martin at meltin.net> wrote:
> Hi Bob,
>
> On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com>
> wrote:
>
> > And so we've been rereading the doc on the public addresses file. So it
> may
> > be we have gravely misunderstood the *public_addresses* file, we never
> read
> >
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 knows
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
2020 Aug 06
2
CTDB question about "shared file system"
Very helpful. Thank you, Martin.
I'd like to 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
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 non-zero, ctdb will not perform failover or
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 [
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
2023 Feb 13
1
ctdb tcp kill: remaining connections
...kd: server x.x.253.252 OK
[Mon Feb 13 12:28:50 2023] lockd: server x.x.253.252 OK
(x.x.253.252 is one of 8 IPs that ctdb handles).
_Some_ of the clients fail to get the nfs mounts alive again after those messages. We then have to reboot those or use a lazy umount. We are seeing this at almost all takeovers.
Because of that we currently cannot update/reboot nodes without affecting many users which to some degree defeats the purpose of ctdb which should provide seamless takeovers...
Today I (again) tried to debug these hanging clients and came across this output in the ctdb log:
...
Feb 13 12:27:55...
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
Hi to all,
I'm having a CTDB-Cluster with two nodes (both Ubuntu wit
Sernet-packages 4.17.4). Now I want to replace one of the nodes. The
first step was to bring a new node to the CTDB-Cluster. This time a
Debian 11 but with the same sernet-packages (4.17.4). Adding the new
node to /etc/ctdb/nodes at the end of the list. And the virtual IP to
/etc/ctdb/public_addresses, also at the end
2023 Feb 15
1
ctdb tcp kill: remaining connections
...OK, this part looks kind-of good. It would be interesting to know how
long the entire failover process is taking.
> _Some_ of the clients fail to get the nfs mounts alive again after
> those messages. We then have to reboot those or use a lazy umount. We
> are seeing this at almost all takeovers.
> Because of that we currently cannot update/reboot nodes without
> affecting many users which to some degree defeats the purpose of ctdb
> which should provide seamless takeovers...
:-(
> Today I (again) tried to debug these hanging clients and came across this output in the ctdb...
2008 Feb 12
1
CTDB and LDAP: anyone?
Hi there,
I am looking into using CTDB between a PDC and a BDC. I assume this is
possible!
However I have a few questions:
1: Do I have to use tdb2 as an Idmap backend? Can I not stay with ldap?
(from the CTDB docs:
A clustered Samba install must set some specific configuration
parameters
clustering = yes
idmap backend = tdb2
private dir = /a/directory/on/your/cluster/filesystem
It is
2020 Aug 08
0
CTDB question about "shared file system"
Hi Bob,
On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com>
wrote:
> And so we've been rereading the doc on the public addresses file. So it may
> be we have gravely misunderstood the *public_addresses* file, we never read
> that part of the documentation carefully. The *nodes* file made perfect
> sense, and the point we missed is that CTDB is using
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
Hi.
Is anyone using conntrack-tools to implement gateway failover on a
network with windows clients?
I set it up with ucarp and keepalived, and found that gratuitous ARP
doesn''t always seem to update the cache on Windows machines. 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.
2023 Feb 16
1
ctdb tcp kill: remaining connections
Martin Schwenke schrieb am 15.02.2023 23:23:
> Hi Uli,
>
> [Sorry for slow response, life is busy...]
Thanks for answering anyway!
> On Mon, 13 Feb 2023 15:06:26 +0000, Ulrich Sibiller via samba
> 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
2023 Jan 26
1
ctdb samba and winbind event problem
Hi Stefan,
On Thu, 26 Jan 2023 16:35:59 +0100, Stefan Kania via samba
<samba at lists.samba.org> wrote:
> I'm having a CTDB-Cluster with two nodes (both Ubuntu wit
> Sernet-packages 4.17.4). Now I want to replace one of the nodes. The
> first step was to bring a new node to the CTDB-Cluster. This time a
> Debian 11 but with the same sernet-packages (4.17.4). Adding the