Re: [Linux-ha-dev] [Patch]Mistake of the table name variable.
On 08/30/2011 08:58 AM, renayama19661...@ybb.ne.jp wrote: Hi, I contribute a patch revising the mistake of the variable of the resource agent of mysql. ack. i applied it to my mysql branch: https://github.com/raoulbhatia/resource-agents/commits/mysql thanks, raoul ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] [Patch 1]Change of the monitor log of the resource agent of mysql.
On 08/30/2011 10:19 AM, renayama19661...@ybb.ne.jp wrote: Hi, The log that a resource agent of mysql outputs with a monitor is a noise very much. Aug 11 13:40:01 ib01 mysql[18164]: INFO: COUNT(*) 4 Aug 11 13:40:01 ib01 mysql[18164]: INFO: MySQL monitor succeeded - repeat monitor log. I suggest the next patch. * The addition of the -q option to ocf_run. * Change the log of the monitor completion to debug. I send a patch. Please examine this patch. ack. i applied it to my mysql branch: https://github.com/raoulbhatia/resource-agents/commits/mysql thanks, raoul ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Postfix status
On 06/16/2011 05:48 AM, renayama19661...@ybb.ne.jp wrote:
The postfix ra worked well.
thanks for testing my ra. i'll check the ra and will then issue a
pull request.
However, my patch made a mistake.
I do not seem to get the result of postfix status.
It is necessary to watch log of postfix in the details of the problem after
all.
Therefore, I withdraw the patch of the part of postfix status.
diff -r 19c97e0021f0 postfix
--- a/postfix Thu Jun 16 21:45:53 2011 +0900
+++ b/postfix Thu Jun 16 21:46:01 2011 +0900
@@ -98,12 +98,8 @@
postfix_running() {
# run Postfix status if available
if ocf_is_true $status_support; then
-output=`$binary $OPTION_CONFIG_DIR status 21`
-ret=$?
-if [ $ret -ne 0 ]; then
-ocf_log err Postfix status: '$output'. $ret
-fi
-return $ret
+$binary $OPTION_CONFIG_DIR status 21
+return $?
fi
# manually check Postfix's pid
it's been a while since i looked into the code.
why do you want to issue postfix status if /usr/sbin/postfix
does not support this command?
thanks,
raoul
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] endian oddity in cluster glue
On 09/05/2011 09:02 AM, Pádraig Brady wrote: I was looking at extricating some logic from cluster-glue-libs and noticed strangeness wrt the endianess checking. CONFIG_BIG_ENDIAN is defined on my x86 machine, which is due to configure.ac referencing a non existent byteorder_test.c To fix this I would suggest the following patch. However, I'm wary that this may introduce compatibility issues with generated md5 sums which is the only code that inspects the above defines. If we stick with BIG_ENDIAN always then there will be interoperability issues between x86 and ppc hosts for example (which may not be an issue)? cheers, Pádraig. Strange as it seems, there are some mixed PPC and x86 clusters out there... -- Alan Robertsonal...@unix.sh Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions. - William Wilberforce ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] endian oddity in cluster glue
Well.. There is some reasoning for this extreme mixing of hardware. If there is an OS bug that could take out, say Linux, it isn't likely that the same exploit would work on a totally different hardware architecture. Matthew Soffen Lead Computer Scientist ISO New England - http://www.iso-ne.com/ -Original Message- From: linux-ha-dev-boun...@lists.linux-ha.org [mailto:linux-ha-dev-boun...@lists.linux-ha.org] On Behalf Of Alan Robertson Sent: Tuesday, September 06, 2011 11:15 AM To: High-Availability Linux Development List Subject: Re: [Linux-ha-dev] endian oddity in cluster glue On 09/05/2011 09:02 AM, Pádraig Brady wrote: I was looking at extricating some logic from cluster-glue-libs and noticed strangeness wrt the endianess checking. CONFIG_BIG_ENDIAN is defined on my x86 machine, which is due to configure.ac referencing a non existent byteorder_test.c To fix this I would suggest the following patch. However, I'm wary that this may introduce compatibility issues with generated md5 sums which is the only code that inspects the above defines. If we stick with BIG_ENDIAN always then there will be interoperability issues between x86 and ppc hosts for example (which may not be an issue)? cheers, Pádraig. Strange as it seems, there are some mixed PPC and x86 clusters out there... -- Alan Robertsonal...@unix.sh Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions. - William Wilberforce ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/ ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] [Patch 1]Change of the monitor log of the resource agent of mysql.
Hi Raoul, All right. Thanks!! Hideo Yamauchi. --- On Wed, 2011/9/7, Raoul Bhatia [IPAX] r.bha...@ipax.at wrote: On 08/30/2011 10:19 AM, renayama19661...@ybb.ne.jp wrote: Hi, The log that a resource agent of mysql outputs with a monitor is a noise very much. Aug 11 13:40:01 ib01 mysql[18164]: INFO: COUNT(*) 4 Aug 11 13:40:01 ib01 mysql[18164]: INFO: MySQL monitor succeeded - repeat monitor log. I suggest the next patch. * The addition of the -q option to ocf_run. * Change the log of the monitor completion to debug. I send a patch. Please examine this patch. ack. i applied it to my mysql branch: https://github.com/raoulbhatia/resource-agents/commits/mysql thanks, raoul ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/ ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] [Patch]Mistake of the table name variable.
Hi Raoul, All right. Thanks!! Hideo Yamauchi. --- On Wed, 2011/9/7, Raoul Bhatia [IPAX] r.bha...@ipax.at wrote: On 08/30/2011 08:58 AM, renayama19661...@ybb.ne.jp wrote: Hi, I contribute a patch revising the mistake of the variable of the resource agent of mysql. ack. i applied it to my mysql branch: https://github.com/raoulbhatia/resource-agents/commits/mysql thanks, raoul ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] OCF RA for named
On Thu, Sep 1, 2011 at 6:28 AM, Dejan Muhamedagic de...@suse.de wrote:
Hi Serge,
On Tue, Jul 12, 2011 at 03:50:36PM -0600, Serge Dubrouski wrote:
Hello -
I've created an OCF RA for named (BIND) server. There is an existing one
in
redhat directory but I don't like how it does monitoring and I doubt that
it
can work with pacemaker. So please review the attached RA and see if it
can
be included into the project.
Sorry for the delay. The RA looks quite good, some comments
below.
Cheers,
Dejan
#!/bin/sh
#
# Description: Manages a named (Bind) server as an OCF High-Availability
# resource
#
# Authors: Serge Dubrouski (serge...@gmail.com)
#
# Copyright:2011 Serge Dubrouski serge...@gmail.com
#
# License: GNU General Public License (GPL)
#
###
# Initialization:
: ${OCF_FUNCTIONS_DIR=${OCF_ROOT}/lib/heartbeat}
. ${OCF_FUNCTIONS_DIR}/ocf-shellfuncs
# Used binaries
RNDC=/usr/sbin/rndc
HOST=/usr/bin/host
PIDOF=/sbin/pidof
How about relying on PATH? The RA should have a sane environment
and these are all standard locations. Packagers may have
different ideas which may lead to problems.
Done.
#Defaults
OCF_RESKEY_named_default=/usr/sbin/named
OCF_RESKEY_named_user_default=named
OCF_RESKEY_named_config_default=/etc/named.conf
OCF_RESKEY_named_pidfile_default=/var/run/named/named.pid
OCF_RESKEY_named_rootdir_default=
OCF_RESKEY_named_options_default=
OCF_RESKEY_named_keytab_file_default=
OCF_RESKEY_named_stop_timeout_default=25
OCF_RESKEY_monitor_request_default=localhost
OCF_RESKEY_monitor_response_default=127.0.0.1
OCF_RESKEY_monitor_ip_default=127.0.0.1
: ${OCF_RESKEY_named=${OCF_RESKEY_named_default}}
: ${OCF_RESKEY_named_user=${OCF_RESKEY_named_user_default}}
: ${OCF_RESKEY_named_config=${OCF_RESKEY_named_config_default}}
: ${OCF_RESKEY_named_pidfile=${OCF_RESKEY_named_pidfile_default}}
: ${OCF_RESKEY_named_rootdir=${OCF_RESKEY_named_rootdir_default}}
: ${OCF_RESKEY_named_options=${OCF_RESKEY_named_options_default}}
: ${OCF_RESKEY_named_keytab_file=${OCF_RESKEY_named_keytab_file_default}}
:
${OCF_RESKEY_named_stop_timeout=${OCF_RESKEY_named_stop_timeout_default}}
: ${OCF_RESKEY_monitor_request=${OCF_RESKEY_monitor_request_default}}
: ${OCF_RESKEY_monitor_response=${OCF_RESKEY_monitor_response_default}}
: ${OCF_RESKEY_monitor_ip=${OCF_RESKEY_monitor_ip_default}}
usage() {
cat EOF
usage: $0
start|stop|reload|status|monitor|meta-data|validate-all|methods
$0 manages named (Bind) server as an HA resource.
The 'start' operation starts named server.
The 'stop' operation stops named server.
The 'reload' operation reload named configuration.
The 'status' operation reports whether named is up.
The 'monitor' operation reports whether named is running.
The 'validate-all' operation reports whether parameters are
valid.
The 'methods' operation reports on the methods $0 supports.
EOF
return $OCF_ERR_ARGS
}
named_meta_data() {
cat EOF
?xml version=1.0?
!DOCTYPE resource-agent SYSTEM ra-api-1.dtd
resource-agent name=named
version1.0/version
longdesc lang=en
Resource script for named (Bind) server. It manages named as an HA
resource.
/longdesc
shortdesc lang=enManages a named server/shortdesc
parameters
parameter name=named unique=0 required=0
longdesc lang=en
Path to the named command.
/longdesc
shortdesc lang=ennamed/shortdesc
content type=string default=${OCF_RESKEY_named_default} /
/parameter
parameter name=named_user unique=0 required=0
longdesc lang=en
User that should own named process.
/longdesc
shortdesc lang=ennamed_user/shortdesc
content type=string default=${OCF_RESKEY_named_user_default} /
/parameter
parameter name=named_config unique=0 required=0
longdesc lang=en
Configuration file for named.
/longdesc
shortdesc lang=ennamed_config/shortdesc
content type=string default=${OCF_RESKEY_named_config_default} /
/parameter
This one should be unique.
Done.
parameter name=named_pidfile unique=0 required=0
longdesc lang=en
PIDFILE file for named.
/longdesc
shortdesc lang=ennamed_pidfile/shortdesc
content type=string default=${OCF_RESKEY_named_pidfile_default} /
/parameter
This one too.
Done.
parameter name=named_rootdir unique=0 required=0
longdesc lang=en
Directory that named should use for chroot if any.
/longdesc
shortdesc lang=ennamed_rootdir/shortdesc
content type=string default=${OCF_RESKEY_named_rootdir_default} /
/parameter
This one also? Or do different instances share chroot?
Made it unique too.
parameter name=named_options unique=0 required=0
longdesc lang=en
Options for named process if any.
/longdesc
shortdesc
Re: [Linux-ha-dev] Postfix status
Hi Raoul,
thanks for testing my ra. i'll check the ra and will then issue a
pull request.
Okay.
We hope that a correction is included in the next release of the resource agent.
However, my patch made a mistake.
I do not seem to get the result of postfix status.
It is necessary to watch log of postfix in the details of the problem after
all.
Therefore, I withdraw the patch of the part of postfix status.
diff -r 19c97e0021f0 postfix
--- a/postfix Thu Jun 16 21:45:53 2011 +0900
+++ b/postfix Thu Jun 16 21:46:01 2011 +0900
@@ -98,12 +98,8 @@
postfix_running() {
# run Postfix status if available
if ocf_is_true $status_support; then
-output=`$binary $OPTION_CONFIG_DIR status 21`
-ret=$?
-if [ $ret -ne 0 ]; then
-ocf_log err Postfix status: '$output'. $ret
-fi
-return $ret
+$binary $OPTION_CONFIG_DIR status 21
+return $?
fi
# manually check Postfix's pid
it's been a while since i looked into the code.
why do you want to issue postfix status if /usr/sbin/postfix
does not support this command?
I thought that output could acquire the details of the problem of postfix
status with a former patch.
And I thought the output of the details of the problem to be useful for an
operator.
However, the details of the problem only were really reflected on log of
postfix in the environment that I tried.
Therefore I want to withdraw the suggestion of the patch of this part.
Best Regards,
Hideo Yamauchi.
--- On Wed, 2011/9/7, Raoul Bhatia [IPAX] r.bha...@ipax.at wrote:
On 06/16/2011 05:48 AM, renayama19661...@ybb.ne.jp wrote:
The postfix ra worked well.
thanks for testing my ra. i'll check the ra and will then issue a
pull request.
However, my patch made a mistake.
I do not seem to get the result of postfix status.
It is necessary to watch log of postfix in the details of the problem after
all.
Therefore, I withdraw the patch of the part of postfix status.
diff -r 19c97e0021f0 postfix
--- a/postfix Thu Jun 16 21:45:53 2011 +0900
+++ b/postfix Thu Jun 16 21:46:01 2011 +0900
@@ -98,12 +98,8 @@
postfix_running() {
# run Postfix status if available
if ocf_is_true $status_support; then
- output=`$binary $OPTION_CONFIG_DIR status 21`
- ret=$?
- if [ $ret -ne 0 ]; then
- ocf_log err Postfix status: '$output'. $ret
- fi
- return $ret
+ $binary $OPTION_CONFIG_DIR status 21
+ return $?
fi
# manually check Postfix's pid
it's been a while since i looked into the code.
why do you want to issue postfix status if /usr/sbin/postfix
does not support this command?
thanks,
raoul
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
