Hi Horms,
On Thu, Jun 21, 2007 at 12:36:02PM +0900, Horms wrote:
[snip]
Also, I'm not a big fan of declaring variables other inside blocks,
but I'm not sure what the linux-ha guidelines on this are.
Often, I find it preferable. If the function is long,* tracing a
variable which has nothing to
are these the only two processes growing?
There are other (smaller) increments as well.
Here is the complete list:
RSS VSZRSS VSZ
1708 4496 1708 4496 /usr/sfw/lib/python2.3/heartbeat/ha_logd
1316 4396 1316 4396 /usr/sfw/lib/python2.3/heartbeat/ha_logd
9204 12788 9204 12788
On 6/22/07, Otte, Joerg [EMAIL PROTECTED] wrote:
are these the only two processes growing?
There are other (smaller) increments as well.
Here is the complete list:
RSS VSZRSS VSZ
1708 4496 1708 4496 /usr/sfw/lib/python2.3/heartbeat/ha_logd
1316 4396 1316 4396
On Fri, 22 Jun 2007, Otte, Joerg wrote:
[...]
are there any tools on solaris to show where the leaks are coming
from? (on linux we have valgrind, support for which is easily enabled
in heartbeat)
I don't know of any tool which comes for free.
Joerg: I've just done a quick Google search
one more question... was the cluster very active during that time?
ie. moving resources around?
Yes, the resource group (and contained 7 resources) were moved once per
Minute - (to see if this works was the primary goal of the testcase).
-Ursprüngliche Nachricht-
Von: [EMAIL
On 6/22/07, Otte, Joerg [EMAIL PROTECTED] wrote:
one more question... was the cluster very active during that time?
ie. moving resources around?
Yes, the resource group (and contained 7 resources) were moved once per
Minute - (to see if this works was the primary goal of the testcase).
ok -
Hi there,
just to make you all aware of it.
sometimes Filesystem stop cannot umount the file system,
and fuser does not kill anybody.
and this time it it not NFS, for a change.
fuser misses unix domain sockets!
this is a long known issue, but it just recently hit me again
during a failover, so
On 2007-06-22T14:33:34, Lars Ellenberg [EMAIL PROTECTED] wrote:
so we may want to complement the $FUSER -a -k -v -m with
something like
lsof -U | awk '/ \/'$mountpoint'\// { print $2 }' | xargs -- kill
comments?
Clearly correct. Thanks for pointing that out, and I've got to admit I
missed
On Fri, Jun 22, 2007 at 05:32:32PM +0200, Lars Marowsky-Bree wrote:
On 2007-06-22T14:33:34, Lars Ellenberg [EMAIL PROTECTED] wrote:
so we may want to complement the $FUSER -a -k -v -m with
something like
lsof -U | awk '/ \/'$mountpoint'\// { print $2 }' | xargs -- kill
comments?
On 6/21/07, Madison Kelly [EMAIL PROTECTED] wrote:
Andrew Beekhof wrote:
Its a regular debian repository so you should just be able to run
apt-update against it to see any new package.
(alas that feature was broken yesterday but i was told it would be
fixed by today - if its not please do
I forgot to include my 'drbd.conf' file (comments stripped):
-=-=-] /etc/drbd.conf [-=-=-
global {
usage-count yes;
}
common {
syncer { rate 10M; }
}
resource r0 {
protocol C;
handlers {
pri-on-incon-degr echo O /proc/sysrq-trigger ;
On 2007-06-22T17:33:39, Ben Clewett [EMAIL PROTECTED] wrote:
Dear Linux-ha,
I have had terrible results from running V2.0.8 using the GUI.
Well, as frequently mentioned, the upstream 2.0.8 is a bit dated.
However, your list of issues is fairly long.
Quick inspection indicates that some
Hello Madison,
Your drbd configuration seems to work fine, but keep in mind that you
can only mount a drbd device that is in prmary state. So you have to
umount the filesystem on the master, switch drbd devices to secondary
mode and switch to primary mode on the slave ... but that can make
Andreas Kurz wrote:
Hello Madison,
Your drbd configuration seems to work fine, but keep in mind that you
can only mount a drbd device that is in prmary state. So you have to
umount the filesystem on the master, switch drbd devices to secondary
mode and switch to primary mode on the slave ...
14 matches
Mail list logo
