LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 11-02-2012, 03:28 PM   #1
eantoranz
Senior Member
 
Registered: Apr 2003
Location: Colombia
Distribution: Kubuntu, Debian, Knoppix
Posts: 1,982
Blog Entries: 1

Rep: Reputation: 83
pacemaker starting resources in disorder


Hi!

I have these pacemaker experiment going on.

I have 5 resources that have to move between 2 servers (all must run on the same server, by the way):
- Floating IP
- SAN resource (postgres data_directory)
- postgres
- pgbouncer
- apache2

I have these rules set in pacemaker:
Code:
order apache_after_pgbouncer inf: apache:start pgbouncer:start
order mount_after_ip inf: datapostgres:start ip_flotante:start
order pgbouncer_after_postgres inf: pgbouncer:start postgres:start
order postgres_after_mount inf: postgres:start datapostgres:start
Why is postgres started before mounting or setting up floating IP?
Code:
Nov  2 15:41:45 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=1:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=pgbouncer_stop_0 )
Nov  2 15:41:45 cluster1 lrmd: [9551]: info: rsc:pgbouncer:7: stop
Nov  2 15:41:45 cluster1 lrmd: [9631]: WARN: For LSB init script, no additional parameters are needed.
Nov  2 15:41:45 cluster1 lrmd: [9551]: info: RA output: (pgbouncer:stop:stdout)  * Stopping pgbouncer
Nov  2 15:41:45 cluster1 lrmd: [9551]: info: RA output: (pgbouncer:stop:stdout)    ...done.
Nov  2 15:41:45 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation pgbouncer_stop_0 (call=7, rc=0, cib-update=12, confirmed=true) ok
Nov  2 15:41:47 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=12:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=apache_start_0 )
Nov  2 15:41:47 cluster1 lrmd: [9551]: info: rsc:apache:8: start
Nov  2 15:41:47 cluster1 lrmd: [9632]: WARN: For LSB init script, no additional parameters are needed.
Nov  2 15:41:47 cluster1 lrmd: [9551]: info: RA output: (apache:start:stdout)  * Starting web server apache2
Nov  2 15:41:47 cluster1 lrmd: [9551]: info: RA output: (apache:start:stderr) apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
Nov  2 15:41:47 cluster1 lrmd: [9551]: info: RA output: (apache:start:stdout)    ...done.
Nov  2 15:41:47 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation apache_start_0 (call=8, rc=0, cib-update=13, confirmed=true) ok
Nov  2 15:41:47 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=10:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=pgbouncer_start_0 )
Nov  2 15:41:47 cluster1 lrmd: [9551]: info: rsc:pgbouncer:9: start
Nov  2 15:41:47 cluster1 lrmd: [9641]: WARN: For LSB init script, no additional parameters are needed.
Nov  2 15:41:48 cluster1 lrmd: [9551]: info: RA output: (pgbouncer:start:stdout)  * Starting pgbouncer
Nov  2 15:41:48 cluster1 lrmd: [9551]: info: RA output: (pgbouncer:start:stdout)    ...done.
Nov  2 15:41:48 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation pgbouncer_start_0 (call=9, rc=0, cib-update=14, confirmed=true) ok
Nov  2 15:41:48 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=8:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=postgres_start_0 )
Nov  2 15:41:48 cluster1 lrmd: [9551]: info: rsc:postgres:10: start
Nov  2 15:41:48 cluster1 lrmd: [9703]: WARN: For LSB init script, no additional parameters are needed.
Nov  2 15:41:48 cluster1 lrmd: [9551]: info: RA output: (postgres:start:stdout)  * Starting PostgreSQL 8.4 database server
Nov  2 15:41:50 cluster1 lrmd: [9551]: info: RA output: (postgres:start:stdout)    ...done.
Nov  2 15:41:50 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation postgres_start_0 (call=10, rc=0, cib-update=15, confirmed=true) ok
Nov  2 15:41:50 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=7:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=datapostgres_start_0 )
Nov  2 15:41:50 cluster1 lrmd: [9551]: info: rsc:datapostgres:11: start
Nov  2 15:41:51 cluster1 Filesystem[9731]: INFO: Running start for /dev/disk/by-uuid/67318124-1978-4dc7-9dd1-0eeac44baffb on /var/lib/postgresql/8.4/main
Nov  2 15:41:51 cluster1 lrmd: [9551]: info: RA output: (datapostgres:start:stderr) FATAL: Module scsi_hostadapter not found.
Nov  2 15:41:51 cluster1 kernel: [24230.022180] kjournald starting.  Commit interval 5 seconds
Nov  2 15:41:51 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation datapostgres_start_0 (call=11, rc=0, cib-update=16, confirmed=true) ok
Nov  2 15:41:51 cluster1 kernel: [24230.036415] EXT3 FS on sdb5, internal journal
Nov  2 15:41:51 cluster1 kernel: [24230.036421] EXT3-fs: mounted filesystem with ordered data mode.
Nov  2 15:41:51 cluster1 crmd: [9554]: info: do_lrm_rsc_op: Performing key=6:43:0:146c57e8-9df9-485a-bcb4-213806636ef1 op=ip_flotante_start_0 )
Nov  2 15:41:51 cluster1 lrmd: [9551]: info: rsc:ip_flotante:12: start
Nov  2 15:41:51 cluster1 IPaddr2[9783]: INFO: ip -f inet addr add 192.168.55.200/24 brd 192.168.55.255 dev eth3
Nov  2 15:41:51 cluster1 IPaddr2[9783]: INFO: ip link set eth3 up
Nov  2 15:41:51 cluster1 IPaddr2[9783]: INFO: /usr/lib/heartbeat/send_arp -i 200 -r 5 -p /var/run/heartbeat/rsctmp/send_arp/send_arp-192.168.55.200 eth3 192.168.55.200 auto not_used not_used
Nov  2 15:41:51 cluster1 crmd: [9554]: info: process_lrm_event: LRM operation ip_flotante_start_0 (call=12, rc=0, cib-update=17, confirmed=true) ok
This is pacemaker/corosync from ubuntu 10.04

Thanks in advance.

PS As a matter of fact, there could be an easier way to tell pacemaker the order in which I want to start the resources? (and in reverse when stopping them)?

Starting:
ip -> mount -> postgres -> pgbouncer -> apache

Stopping
apache -> pgbouncer -> postgres -> mount -> ip
 
Old 11-02-2012, 03:54 PM   #2
eantoranz
Senior Member
 
Registered: Apr 2003
Location: Colombia
Distribution: Kubuntu, Debian, Knoppix
Posts: 1,982
Blog Entries: 1

Original Poster
Rep: Reputation: 83
Apparently a group took care of the two problems:
- resource start order
- keeping them together on the same host

So no more colocation or order rules, just a simple groop one:

Code:
group todo_junto ip_flotante datapostgres postgres pgbouncer apache
 
  


Reply

Tags
crm, order, pacemaker


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Pacemaker restart resources when node joins cluster after failback Khaosmaker Linux - Server 1 04-19-2012 11:56 AM
Multiple Personality Disorder colinstu General 4 03-04-2008 06:52 PM
Non-verbal learning disorder iwasapenguin General 12 01-09-2008 07:23 PM
Help, I have a compulsive idiot disorder Darcane LinuxQuestions.org Member Intro 2 01-27-2007 02:49 AM
Computer seems to have identity disorder The MCP Linux - Software 1 05-01-2005 02:20 PM


All times are GMT -5. The time now is 08:42 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration