[Pacemaker] Failed actions: ...not installed
Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed The resource script “mysql” IS installed, it’s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There’s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here’s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hi Andreas, I would give it a try from shell. Set all required environment variables, such as (as in your cib) export OCF_ROOT=/usr/lib/ocf export OCF_RESKEY_binary=/usr/bin/mysqld_safe export OCF_RESKEY_config=/etc/mysql/my.cnf export OCF_RESKEY_datadir=/var/lib/mysql export OCF_RESKEY_user=mysql export OCF_RESKEY_pid=/var/run/mysqld/mysqld.pid export OCF_RESKEY_socket=/var/run/mysqld/mysqld.sock …. and then execute the RA from its local directory. (e.g. ./mysql monitor or ./mysql start ) You may see why it fails, or add some logging into the RA itself. Cheers, Attila From: Stallmann, Andreas [mailto:astallm...@conet.de] Sent: 2012. január 24. 9:46 To: pacemaker@oss.clusterlabs.org Subject: [Pacemaker] Failed actions: ...not installed Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed The resource script “mysql” IS installed, it’s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There’s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here’s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hi Attila, the strange thing is: Running it from shell works just fine: /usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[21716]: INFO: MySQL is not running /usr/lib/ocf/resource.d/heartbeat # ./mysql start mysql[21771]: INFO: MySQL is not running mysql[21771]: INFO: MySQL is not running mysql[21771]: DEBUG: MySQL monitor succeeded mysql[21771]: INFO: MySQL started usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[22142]: DEBUG: MySQL monitor succeeded /usr/lib/ocf/resource.d/heartbeat # echo $? 0 /usr/lib/ocf/resource.d/heartbeat # ps -ef | grep mysql root 21855 1 0 13:17 pts/000:00:00 /bin/sh /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --datadir=/var/lib/mysql --user=mysql usr/lib/ocf/resource.d/heartbeat # ./mysql stop mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL is not running mysql[24557]: INFO: MySQL is not running mysql[24557]: INFO: MySQL stopped /usr/lib/ocf/resource.d/heartbeat # echo $? 0 /usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[24816]: INFO: MySQL is not running Any further ideas? Thank you so far, Andreas Von: Attila Megyeri [mailto:amegy...@minerva-soft.com] Gesendet: Dienstag, 24. Januar 2012 10:03 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Failed actions: ...not installed Hi Andreas, I would give it a try from shell. Set all required environment variables, such as (as in your cib) export OCF_ROOT=/usr/lib/ocf export OCF_RESKEY_binary=/usr/bin/mysqld_safe export OCF_RESKEY_config=/etc/mysql/my.cnf export OCF_RESKEY_datadir=/var/lib/mysql export OCF_RESKEY_user=mysql export OCF_RESKEY_pid=/var/run/mysqld/mysqld.pid export OCF_RESKEY_socket=/var/run/mysqld/mysqld.sock …. and then execute the RA from its local directory. (e.g. ./mysql monitor or ./mysql start ) You may see why it fails, or add some logging into the RA itself. Cheers, Attila From: Stallmann, Andreas [mailto:astallm...@conet.de]mailto:[mailto:astallm...@conet.de] Sent: 2012. január 24. 9:46 To: pacemaker@oss.clusterlabs.orgmailto:pacemaker@oss.clusterlabs.org Subject: [Pacemaker] Failed actions: ...not installed Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed The resource script “mysql” IS installed, it’s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There’s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here’s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 24.1.2012 09:46, Stallmann, Andreas napsal(a): Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed Hi. Just a thought. I was dealing with that problem as well, so maybe it could solve your issue. I guess that you also use disk which is mounted to /var/lib/mysql... Did you try start and stop of mysql on machine, where was that disk mounted? After i did that, my problems disappeared. The resource script ?mysql? IS installed, it?s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There?s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here?s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPHqV+AAoJEG+ytY6bjOobR9YH/iNYKUOntYY0Tu33seKNJg2W DIequ5Yi/yeoiUeXQg5Oi4JVQOiOrvuQMGD6Qy22ptczjIyQSNjM4lhD3oF58Gj3 Zh9AOx1ZNh2fffYklKOWZEr13Bxhlz1v/9ag8TYLmmPxkh4aZiBjZ9InLtkoQeSi 26HUcw35nRoSDj5e97xU6OlNNY3XbXfa/voFDzsC2Y8yh5MNHR49MKsLmcXmIFRn jJW+NMyVeOU7UboiKnDh3wgS3jVmr7iZE9kiwhMKKkvH8UW1IwRjKjMVZxSf/TvL uDrJTwvctf0SqMxq6HHL9adYfOV1Z4HRIa6kGBGs88HJbZVjho98RYRh5ssmulQ= =2813 -END PGP SIGNATURE- ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Le 24/01/2012 13:21, Stallmann, Andreas a écrit : Any ideas on how to get this running? If you want to debug what pacemaker does with your RA, I'd suggest you insert set -x at the top of /usr/lib/ocf/resource.d/heartbeat/mysql and read the (now flooded) logs. Cheers, Florian. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hi Vit! I guess that you also use disk which is mounted to /var/lib/mysql... Well, no. The disk is mounted to /var, not to /var/lib/mysql, see output from mount: /dev/sda5 on /var type ext4 (rw,acl,user_xattr) Did you try start and stop of mysql on machine, where was that disk mounted? The disk is no shared volume, if that's what your suggesting. Starting and stopping mysql works just fine, if done from the shell, on either of the two nodes. MySQL was stopped (for sure) before I tried to start it from within crm. Conflicting access to /var/lib/mysql is not the problem here. After i did that, my problems disappeared. Mine didn't. :-( Still, thanks for your suggestions. Andreas - CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Gesch?ftsf?hrer/Managing Directors: J?rgen Zender (Sprecher/Chairman), Anke H?fer - ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hello, On 01/24/2012 01:21 PM, Stallmann, Andreas wrote: Hi Attila, the strange thing is: Running it from shell works just fine: Typically you should find a lot of logging information in /var/log/messages or/and /var/log/syslog or daemon.log ... depending on your distribution and syslog configuration. To get a hint what might be causing that error have look at the RA and search for OCF_ERR_INSTALLED in the code. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now /usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[21716]: INFO: MySQL is not running /usr/lib/ocf/resource.d/heartbeat # ./mysql start mysql[21771]: INFO: MySQL is not running mysql[21771]: INFO: MySQL is not running mysql[21771]: DEBUG: MySQL monitor succeeded mysql[21771]: INFO: MySQL started usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[22142]: DEBUG: MySQL monitor succeeded /usr/lib/ocf/resource.d/heartbeat # echo $? 0 /usr/lib/ocf/resource.d/heartbeat # ps -ef | grep mysql root 21855 1 0 13:17 pts/000:00:00 /bin/sh /usr/bin/mysqld_safe --defaults-file=/etc/my.cnf --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --datadir=/var/lib/mysql --user=mysql usr/lib/ocf/resource.d/heartbeat # ./mysql stop mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL still hasn't stopped yet. Waiting... mysql[24557]: INFO: MySQL is not running mysql[24557]: INFO: MySQL is not running mysql[24557]: INFO: MySQL stopped /usr/lib/ocf/resource.d/heartbeat # echo $? 0 /usr/lib/ocf/resource.d/heartbeat # ./mysql monitor mysql[24816]: INFO: MySQL is not running Any further ideas? Thank you so far, Andreas *Von:*Attila Megyeri [mailto:amegy...@minerva-soft.com] *Gesendet:* Dienstag, 24. Januar 2012 10:03 *An:* The Pacemaker cluster resource manager *Betreff:* Re: [Pacemaker] Failed actions: ...not installed Hi Andreas, I would give it a try from shell. Set all required environment variables, such as(as in your cib) export OCF_ROOT=/usr/lib/ocf export OCF_RESKEY_binary=/usr/bin/mysqld_safe export OCF_RESKEY_config=/etc/mysql/my.cnf export OCF_RESKEY_datadir=/var/lib/mysql export OCF_RESKEY_user=mysql export OCF_RESKEY_pid=/var/run/mysqld/mysqld.pid export OCF_RESKEY_socket=/var/run/mysqld/mysqld.sock …. and then execute the RA from its local directory. (e.g. ./mysql monitor or ./mysql start ) You may see why it fails, or add some logging into the RA itself. Cheers, Attila *From:*Stallmann, Andreas [mailto:astallm...@conet.de] mailto:[mailto:astallm...@conet.de] *Sent:* 2012. január 24. 9:46 *To:* pacemaker@oss.clusterlabs.org mailto:pacemaker@oss.clusterlabs.org *Subject:* [Pacemaker] Failed actions: ...not installed Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed The resource script “mysql” IS installed, it’s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There’s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here’s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer
Re: [Pacemaker] Failed actions: ...not installed
Hi Attila, On Tue, Jan 24, 2012 at 10:03:17AM +0100, Attila Megyeri wrote: Hi Andreas, I would give it a try from shell. Set all required environment variables, such as (as in your cib) export OCF_ROOT=/usr/lib/ocf export OCF_RESKEY_binary=/usr/bin/mysqld_safe export OCF_RESKEY_config=/etc/mysql/my.cnf export OCF_RESKEY_datadir=/var/lib/mysql export OCF_RESKEY_user=mysql export OCF_RESKEY_pid=/var/run/mysqld/mysqld.pid export OCF_RESKEY_socket=/var/run/mysqld/mysqld.sock …. and then execute the RA from its local directory. (e.g. ./mysql monitor or ./mysql start ) You may see why it fails, or add some logging into the RA itself. It is better to try with ocf-tester: Usage: ocf-tester [-Lh] -n resource_name [-o name=value]* /full/path/to/resource/agent It will make RA do all the possible stuff and check if the outcome is sane. The log messages will be printed to stderr (or was it stdout?). Use -v to get more output. Cheers, Dejan Cheers, Attila From: Stallmann, Andreas [mailto:astallm...@conet.de] Sent: 2012. január 24. 9:46 To: pacemaker@oss.clusterlabs.org Subject: [Pacemaker] Failed actions: ...not installed Hi there, What does the following error mean: Failed actions: p_mysql:1_start_0 (node=int-ipfuie-mgmt02, call=15, rc=5, status=complete): not installed p_mysql:0_start_0 (node=int-ipfuie-mgmt01, call=15, rc=5, status=complete): not installed The resource script “mysql” IS installed, it’s where all the other scripts are: /usr/lib/ocf/resource.d/heartbeat # ls -lh mysql -rwxr-xr-x 1 root root 43K Jan 23 16:36 mysql There’s nothing (at least nothing obvious) in /var/log/messages, that reveals any further information. Here’s my configuration (for the primitive and for the M/S setup): primitive p_mysql ocf:heartbeat:mysql \ params config=/etc/my.cnf pid=/var/run/mysql/mysql.pid socket=/var/run/mysql/mysql.sock replication_user=repl replication_passwd=blafasel max_slave_lag=15 evict_outdated_slaves=false binary=/usr/bin/mysqld_safe test_user=root test_passwd=blafasel \ op start interval=0 timeout=120s \ op stop interval=0 timeout=300s \ op monitor interval=5s role=Master timeout=30s OCF_CHECK_LEVEL=1 \ op monitor interval=2s role=Slave timeout=30s OCF_CHECK_LEVEL=1 primitive pingy_res ocf:pacemaker:ping \ params dampen=5s multiplier=1000 host_list=10.30.0.41 10.30.0.42 10.30.0.1 \ op monitor interval=15s timeout=20s \ op start interval=0 timeout=60s ms ms_MySQL p_mysql \ meta master-max=1 master-node-max=1 clone-max=2 notify=true target-role=Started Any ideas on how to get this running? Thanks, Andreas CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Director: Anke Höfer ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hi there, thanks for all your suggestions. The problem, as we figured out (with your help!) was (and somehow still is), that the mysql monitoring with the test_user and test_passwd does not work. If you omit those parameters, the monitoring works and so does the resource. It seems, that the script does an initial check on the database (tries to select from a mysql table), before the database is actually started. This (naturally) fails (because you can't select from any database before the DMB is up, right. But that's just a wild guess. Anyway, the resource script works (as long as one omits the extensive alive-check), and that's something good (I think). Thank you all, Andreas - CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Directors: Jürgen Zender (Sprecher/Chairman), Anke Höfer - ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Failed actions: ...not installed
Hi, On Tue, Jan 24, 2012 at 03:57:05PM +, Stallmann, Andreas wrote: Hi there, thanks for all your suggestions. The problem, as we figured out (with your help!) was (and somehow still is), that the mysql monitoring with the test_user and test_passwd does not work. If you omit those parameters, the monitoring works and so does the resource. It seems, that the script does an initial check on the database (tries to select from a mysql table), before the database is actually started. This (naturally) fails (because you can't select from any database before the DMB is up, right. But that's just a wild guess. The start action ends in a monitor loop, so it'll wait until the database is up. Anyway, the error crm_mon reported was OCF_ERR_INSTALLED (exit code 5). Though it is very surprising that the RA works from the command line. I guess that the configuration is not exactly the same as the one in the cluster. You should really check the logs (messages from mysql or lrmd). If you have a newer version of the crm shell, it can dig the logs out for you if you do, say, crm history resource myrscname. Thanks, Dejan Anyway, the resource script works (as long as one omits the extensive alive-check), and that's something good (I think). Thank you all, Andreas - CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef. Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136) Geschäftsführer/Managing Directors: Jürgen Zender (Sprecher/Chairman), Anke Höfer - ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
