Advertisement
Guest User

corosync 2+pacemker 1.1.12

a guest
Aug 24th, 2015
459
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Aug 24 17:11:55 [1693] pm1 corosync notice [MAIN ] Corosync Cluster Engine ('2.3.5'): started and ready to provide service.
  2. Aug 24 17:11:55 [1693] pm1 corosync info [MAIN ] Corosync built-in features: pie relro bindnow
  3. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] Initializing transport (UDP/IP Unicast).
  4. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] Initializing transmit/receive security (NSS) crypto: none hash: none
  5. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] The network interface [192.168.122.113] is now up.
  6. Aug 24 17:11:55 [1693] pm1 corosync notice [SERV ] Service engine loaded: corosync configuration map access [0]
  7. Aug 24 17:11:55 [1693] pm1 corosync info [QB ] server name: cmap
  8. Aug 24 17:11:55 [1693] pm1 corosync notice [SERV ] Service engine loaded: corosync configuration service [1]
  9. Aug 24 17:11:55 [1693] pm1 corosync info [QB ] server name: cfg
  10. Aug 24 17:11:55 [1693] pm1 corosync notice [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
  11. Aug 24 17:11:55 [1693] pm1 corosync info [QB ] server name: cpg
  12. Aug 24 17:11:55 [1693] pm1 corosync notice [SERV ] Service engine loaded: corosync profile loading service [4]
  13. Aug 24 17:11:55 [1693] pm1 corosync notice [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
  14. Aug 24 17:11:55 [1693] pm1 corosync info [QB ] server name: quorum
  15. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] adding new UDPU member {192.168.122.172}
  16. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] adding new UDPU member {192.168.122.113}
  17. Aug 24 17:11:55 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:720) was formed. Members joined: 3232266865
  18. Aug 24 17:11:55 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  19. Aug 24 17:11:57 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1299.3466 ms (threshold is 800.0000 ms). Consider token timeout increase.
  20. Aug 24 17:11:57 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  21. Aug 24 17:11:57 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:724) was formed. Members
  22. Aug 24 17:11:57 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  23. Aug 24 17:12:05 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:728) was formed. Members joined: 3232266924
  24. Aug 24 17:12:05 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  25. Aug 24 17:12:06 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  26. Aug 24 17:12:07 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:732) was formed. Members
  27. Aug 24 17:12:07 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  28. Aug 24 17:15:50 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1658.8073 ms (threshold is 800.0000 ms). Consider token timeout increase.
  29. Aug 24 17:15:50 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  30. Aug 24 17:15:51 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.7030 ms (threshold is 800.0000 ms). Consider token timeout increase.
  31. Set r/w permissions for uid=108, gid=113 on /var/log/cluster/corosync.log
  32. Aug 24 17:15:51 [1708] pm1 pacemakerd: notice: mcp_read_config: Configured corosync to accept connections from group 113: OK (1)
  33. Aug 24 17:15:51 [1708] pm1 pacemakerd: notice: main: Starting Pacemaker 1.1.12 (Build: 561c4cf): ncurses libqb-logging libqb-ipc lha-fencing nagios corosync-native acls
  34. Aug 24 17:15:51 [1708] pm1 pacemakerd: info: main: Maximum core file size is: 18446744073709551615
  35. Aug 24 17:15:51 [1708] pm1 pacemakerd: info: qb_ipcs_us_publish: server name: pacemakerd
  36. Aug 24 17:15:52 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 997.4534 ms (threshold is 800.0000 ms). Consider token timeout increase.
  37. Aug 24 17:15:53 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.3823 ms (threshold is 800.0000 ms). Consider token timeout increase.
  38. Aug 24 17:15:54 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1003.2664 ms (threshold is 800.0000 ms). Consider token timeout increase.
  39. Aug 24 17:15:54 [1708] pm1 pacemakerd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  40. Aug 24 17:15:54 [1708] pm1 pacemakerd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266865
  41. Aug 24 17:15:54 [1708] pm1 pacemakerd: info: crm_get_peer: Created entry 95ea14a1-9a59-4eea-a4ba-2a76bac35d0d/0x254c7d0 for node (null)/3232266865 (1 total)
  42. Aug 24 17:15:54 [1708] pm1 pacemakerd: info: crm_get_peer: Node 3232266865 has uuid 3232266865
  43. Aug 24 17:15:54 [1708] pm1 pacemakerd: info: crm_update_peer_proc: cluster_connect_cpg: Node (null)[3232266865] - corosync-cpg is now online
  44. Aug 24 17:15:55 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 997.2751 ms (threshold is 800.0000 ms). Consider token timeout increase.
  45. Aug 24 17:15:55 [1708] pm1 pacemakerd: error: cluster_connect_quorum: Corosync quorum is not configured
  46. Aug 24 17:15:56 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1002.6376 ms (threshold is 800.0000 ms). Consider token timeout increase.
  47. Aug 24 17:15:56 [1708] pm1 pacemakerd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  48. Aug 24 17:15:56 [1708] pm1 pacemakerd: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  49. Aug 24 17:15:56 [1708] pm1 pacemakerd: info: crm_get_peer: Node 3232266865 is now known as pm1
  50. Aug 24 17:15:57 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 996.8450 ms (threshold is 800.0000 ms). Consider token timeout increase.
  51. Aug 24 17:15:57 [1708] pm1 pacemakerd: info: start_child: Using uid=108 and group=113 for process cib
  52. Aug 24 17:15:57 [1708] pm1 pacemakerd: info: start_child: Forked child 1714 for process cib
  53. Aug 24 17:15:58 [1714] pm1 cib: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/hacluster
  54. Aug 24 17:15:58 [1714] pm1 cib: info: get_cluster_type: Verifying cluster type: 'corosync'
  55. Aug 24 17:15:58 [1714] pm1 cib: info: get_cluster_type: Assuming an active 'corosync' cluster
  56. Aug 24 17:15:58 [1714] pm1 cib: info: retrieveCib: Reading cluster configuration from: /var/lib/pacemaker/cib/cib.xml (digest: /var/lib/pacemaker/cib/cib.xml.sig)
  57. Aug 24 17:15:58 [1714] pm1 cib: info: validate_with_relaxng: Creating RNG parser context
  58. Aug 24 17:15:58 [1714] pm1 cib: info: startCib: CIB Initialization completed successfully
  59. Aug 24 17:15:58 [1714] pm1 cib: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
  60. Aug 24 17:15:58 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1001.0409 ms (threshold is 800.0000 ms). Consider token timeout increase.
  61. Aug 24 17:15:58 [1708] pm1 pacemakerd: info: start_child: Forked child 1715 for process stonith-ng
  62. Aug 24 17:15:59 [1715] pm1 stonithd: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/root
  63. Aug 24 17:15:59 [1715] pm1 stonithd: info: get_cluster_type: Verifying cluster type: 'corosync'
  64. Aug 24 17:15:59 [1715] pm1 stonithd: info: get_cluster_type: Assuming an active 'corosync' cluster
  65. Aug 24 17:15:59 [1715] pm1 stonithd: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
  66. Aug 24 17:15:59 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.4296 ms (threshold is 800.0000 ms). Consider token timeout increase.
  67. Aug 24 17:16:00 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1003.1309 ms (threshold is 800.0000 ms). Consider token timeout increase.
  68. Aug 24 17:16:00 [1714] pm1 cib: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  69. Aug 24 17:16:00 [1714] pm1 cib: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266865
  70. Aug 24 17:16:00 [1714] pm1 cib: info: crm_get_peer: Created entry 92699f00-9a6a-4da4-9beb-926bcd1842ee/0x2587560 for node (null)/3232266865 (1 total)
  71. Aug 24 17:16:00 [1714] pm1 cib: info: crm_get_peer: Node 3232266865 has uuid 3232266865
  72. Aug 24 17:16:00 [1714] pm1 cib: info: crm_update_peer_proc: cluster_connect_cpg: Node (null)[3232266865] - corosync-cpg is now online
  73. Aug 24 17:16:00 [1714] pm1 cib: info: init_cs_connection_once: Connection to 'corosync': established
  74. Aug 24 17:16:01 [1708] pm1 pacemakerd: info: start_child: Forked child 1716 for process lrmd
  75. Aug 24 17:16:01 [1716] pm1 pacemaker_remoted: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/root
  76. Aug 24 17:16:01 [1716] pm1 pacemaker_remoted: info: qb_ipcs_us_publish: server name: lrmd
  77. Aug 24 17:16:01 [1716] pm1 pacemaker_remoted: info: main: Starting
  78. Aug 24 17:16:01 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 996.0819 ms (threshold is 800.0000 ms). Consider token timeout increase.
  79. Aug 24 17:16:02 [1714] pm1 cib: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  80. Aug 24 17:16:02 [1714] pm1 cib: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  81. Aug 24 17:16:02 [1714] pm1 cib: info: crm_get_peer: Node 3232266865 is now known as pm1
  82. Aug 24 17:16:02 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1003.8615 ms (threshold is 800.0000 ms). Consider token timeout increase.
  83. Aug 24 17:16:02 [1715] pm1 stonithd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  84. Aug 24 17:16:02 [1715] pm1 stonithd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266865
  85. Aug 24 17:16:02 [1715] pm1 stonithd: info: crm_get_peer: Created entry bb09929d-b4d9-4fce-a5e8-f9628629b5e9/0x19f8910 for node (null)/3232266865 (1 total)
  86. Aug 24 17:16:02 [1715] pm1 stonithd: info: crm_get_peer: Node 3232266865 has uuid 3232266865
  87. Aug 24 17:16:02 [1715] pm1 stonithd: info: crm_update_peer_proc: cluster_connect_cpg: Node (null)[3232266865] - corosync-cpg is now online
  88. Aug 24 17:16:02 [1715] pm1 stonithd: info: init_cs_connection_once: Connection to 'corosync': established
  89. Aug 24 17:16:02 [1708] pm1 pacemakerd: info: start_child: Using uid=108 and group=113 for process attrd
  90. Aug 24 17:16:03 [1708] pm1 pacemakerd: info: start_child: Forked child 1717 for process attrd
  91. Aug 24 17:16:02 [1714] pm1 cib: info: qb_ipcs_us_publish: server name: cib_ro
  92. Aug 24 17:16:03 [1714] pm1 cib: info: qb_ipcs_us_publish: server name: cib_rw
  93. Aug 24 17:16:03 [1714] pm1 cib: info: qb_ipcs_us_publish: server name: cib_shm
  94. Aug 24 17:16:03 [1714] pm1 cib: info: cib_init: Starting cib mainloop
  95. Aug 24 17:16:03 [1717] pm1 attrd: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/hacluster
  96. Aug 24 17:16:03 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 996.0749 ms (threshold is 800.0000 ms). Consider token timeout increase.
  97. Aug 24 17:16:03 [1715] pm1 stonithd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  98. Aug 24 17:16:03 [1715] pm1 stonithd: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  99. Aug 24 17:16:03 [1715] pm1 stonithd: info: crm_get_peer: Node 3232266865 is now known as pm1
  100. Aug 24 17:16:04 [1714] pm1 cib: info: write_cib_contents: Archived previous version as /var/lib/pacemaker/cib/cib-4.raw
  101. Aug 24 17:16:03 [1708] pm1 pacemakerd: info: start_child: Using uid=108 and group=113 for process pengine
  102. Aug 24 17:16:04 [1708] pm1 pacemakerd: info: start_child: Forked child 1720 for process pengine
  103. Aug 24 17:16:04 [1717] pm1 attrd: info: main: Starting up
  104. Aug 24 17:16:04 [1717] pm1 attrd: info: get_cluster_type: Verifying cluster type: 'corosync'
  105. Aug 24 17:16:04 [1717] pm1 attrd: info: get_cluster_type: Assuming an active 'corosync' cluster
  106. Aug 24 17:16:04 [1717] pm1 attrd: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
  107. Aug 24 17:16:04 [1720] pm1 pengine: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/hacluster
  108. Aug 24 17:16:04 [1720] pm1 pengine: info: qb_ipcs_us_publish: server name: pengine
  109. Aug 24 17:16:04 [1720] pm1 pengine: info: main: Starting pengine
  110. Aug 24 17:16:04 [1714] pm1 cib: info: write_cib_contents: Wrote version 0.0.0 of the CIB to disk (digest: a50dc6808a619e0e0b3b52e75ae5f073)
  111. Aug 24 17:16:04 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.0859 ms (threshold is 800.0000 ms). Consider token timeout increase.
  112. Aug 24 17:16:05 [1714] pm1 cib: info: retrieveCib: Reading cluster configuration from: /var/lib/pacemaker/cib/cib.3X8wMV (digest: /var/lib/pacemaker/cib/cib.Y7IUDw)
  113. Aug 24 17:16:05 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1003.4465 ms (threshold is 800.0000 ms). Consider token timeout increase.
  114. Aug 24 17:16:05 [1717] pm1 attrd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  115. Aug 24 17:16:05 [1717] pm1 attrd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266865
  116. Aug 24 17:16:05 [1717] pm1 attrd: info: crm_get_peer: Created entry 47f3d029-bab2-4059-b27d-8ad429078031/0x145a440 for node (null)/3232266865 (1 total)
  117. Aug 24 17:16:05 [1717] pm1 attrd: info: crm_get_peer: Node 3232266865 has uuid 3232266865
  118. Aug 24 17:16:05 [1717] pm1 attrd: info: crm_update_peer_proc: cluster_connect_cpg: Node (null)[3232266865] - corosync-cpg is now online
  119. Aug 24 17:16:05 [1717] pm1 attrd: notice: crm_update_peer_state: attrd_peer_change_cb: Node (null)[3232266865] - state is now member (was (null))
  120. Aug 24 17:16:05 [1717] pm1 attrd: info: init_cs_connection_once: Connection to 'corosync': established
  121. Aug 24 17:16:06 [1708] pm1 pacemakerd: info: start_child: Using uid=108 and group=113 for process crmd
  122. Aug 24 17:16:06 [1708] pm1 pacemakerd: info: start_child: Forked child 1723 for process crmd
  123. Aug 24 17:16:06 [1723] pm1 crmd: info: crm_log_init: Changed active directory to /usr/var/lib/heartbeat/cores/hacluster
  124. Aug 24 17:16:06 [1723] pm1 crmd: notice: main: CRM Git Version: 561c4cf
  125. Aug 24 17:16:06 [1723] pm1 crmd: info: do_log: FSA: Input I_STARTUP from crmd_init() received in state S_STARTING
  126. Aug 24 17:16:06 [1723] pm1 crmd: info: get_cluster_type: Verifying cluster type: 'corosync'
  127. Aug 24 17:16:06 [1723] pm1 crmd: info: get_cluster_type: Assuming an active 'corosync' cluster
  128. Aug 24 17:16:06 [1723] pm1 crmd: info: do_cib_control: CIB connection established
  129. Aug 24 17:16:06 [1723] pm1 crmd: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
  130. Aug 24 17:16:06 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 996.5443 ms (threshold is 800.0000 ms). Consider token timeout increase.
  131. Aug 24 17:16:07 [1717] pm1 attrd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  132. Aug 24 17:16:07 [1717] pm1 attrd: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  133. Aug 24 17:16:07 [1717] pm1 attrd: info: crm_get_peer: Node 3232266865 is now known as pm1
  134. Aug 24 17:16:07 [1715] pm1 stonithd: notice: setup_cib: Watching for stonith topology changes
  135. Aug 24 17:16:07 [1715] pm1 stonithd: info: qb_ipcs_us_publish: server name: stonith-ng
  136. Aug 24 17:16:07 [1715] pm1 stonithd: info: main: Starting stonithd mainloop
  137. Aug 24 17:16:07 [1715] pm1 stonithd: info: init_cib_cache_cb: Updating device list from the cib: init
  138. Aug 24 17:16:07 [1715] pm1 stonithd: info: cib_devices_update: Updating devices to version 0.0.0
  139. Aug 24 17:16:07 [1715] pm1 stonithd: info: unpack_nodes: Creating a fake local node
  140. Aug 24 17:16:07 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1002.0618 ms (threshold is 800.0000 ms). Consider token timeout increase.
  141. Aug 24 17:16:07 [1723] pm1 crmd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  142. Aug 24 17:16:07 [1723] pm1 crmd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266865
  143. Aug 24 17:16:07 [1723] pm1 crmd: info: crm_get_peer: Created entry 14f5134b-77d4-4d11-acfa-086ae7305d59/0xe97270 for node (null)/3232266865 (1 total)
  144. Aug 24 17:16:07 [1723] pm1 crmd: info: crm_get_peer: Node 3232266865 has uuid 3232266865
  145. Aug 24 17:16:07 [1723] pm1 crmd: info: crm_update_peer_proc: cluster_connect_cpg: Node (null)[3232266865] - corosync-cpg is now online
  146. Aug 24 17:16:07 [1723] pm1 crmd: info: init_cs_connection_once: Connection to 'corosync': established
  147. Aug 24 17:16:08 [1708] pm1 pacemakerd: info: main: Starting mainloop
  148. Aug 24 17:16:08 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 997.9802 ms (threshold is 800.0000 ms). Consider token timeout increase.
  149. Aug 24 17:16:08 [1723] pm1 crmd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  150. Aug 24 17:16:08 [1723] pm1 crmd: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  151. Aug 24 17:16:08 [1723] pm1 crmd: info: crm_get_peer: Node 3232266865 is now known as pm1
  152. Aug 24 17:16:08 [1723] pm1 crmd: info: peer_update_callback: pm1 is now (null)
  153. Aug 24 17:16:09 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.1227 ms (threshold is 800.0000 ms). Consider token timeout increase.
  154. Aug 24 17:16:09 [1717] pm1 attrd: info: main: Cluster connection active
  155. Aug 24 17:16:09 [1717] pm1 attrd: info: qb_ipcs_us_publish: server name: attrd
  156. Aug 24 17:16:09 [1717] pm1 attrd: info: main: Accepting attribute updates
  157. Aug 24 17:16:10 [1717] pm1 attrd: info: attrd_cib_connect: Connected to the CIB after 1 attempts
  158. Aug 24 17:16:10 [1717] pm1 attrd: info: main: CIB connection active
  159. Aug 24 17:16:10 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.9871 ms (threshold is 800.0000 ms). Consider token timeout increase.
  160. Aug 24 17:16:10 [1723] pm1 crmd: error: cluster_connect_quorum: Corosync quorum is not configured
  161. Aug 24 17:16:11 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.3033 ms (threshold is 800.0000 ms). Consider token timeout increase.
  162. Aug 24 17:16:11 [1723] pm1 crmd: info: do_ha_control: Connected to the cluster
  163. Aug 24 17:16:11 [1723] pm1 crmd: info: lrmd_ipc_connect: Connecting to lrmd
  164. Aug 24 17:16:11 [1714] pm1 cib: info: cib_process_request: Forwarding cib_modify operation for section nodes to master (origin=local/crmd/3)
  165. Aug 24 17:16:12 [1723] pm1 crmd: info: do_lrm_control: LRM connection established
  166. Aug 24 17:16:12 [1723] pm1 crmd: info: do_started: Delaying start, no membership data (0000000000100000)
  167. Aug 24 17:16:12 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.1545 ms (threshold is 800.0000 ms). Consider token timeout increase.
  168. Aug 24 17:16:12 [1714] pm1 cib: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  169. Aug 24 17:16:12 [1714] pm1 cib: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  170. Aug 24 17:16:12 [1723] pm1 crmd: info: do_started: Delaying start, no membership data (0000000000100000)
  171. Aug 24 17:16:12 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:776) was formed. Members
  172. Aug 24 17:16:13 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  173. Aug 24 17:16:13 [1715] pm1 stonithd: info: pcmk_cpg_membership: Joined[0.0] stonithd.3232266865
  174. Aug 24 17:16:13 [1717] pm1 attrd: info: pcmk_cpg_membership: Joined[0.0] attrd.3232266865
  175. Aug 24 17:16:15 [1708] pm1 pacemakerd: info: crm_get_peer: Created entry cb0ab48c-a48f-4f4b-bfd4-6b4f0ff8e4aa/0x25510d0 for node pm2/3232266924 (2 total)
  176. Aug 24 17:16:15 [1708] pm1 pacemakerd: info: crm_get_peer: Node 3232266924 is now known as pm2
  177. Aug 24 17:16:15 [1708] pm1 pacemakerd: info: crm_get_peer: Node 3232266924 has uuid 3232266924
  178. Aug 24 17:16:15 [1714] pm1 cib: info: pcmk_cpg_membership: Joined[0.0] cib.3232266865
  179. Aug 24 17:16:15 [1723] pm1 crmd: info: pcmk_cpg_membership: Joined[0.0] crmd.3232266865
  180. Aug 24 17:16:15 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1999.8571 ms (threshold is 800.0000 ms). Consider token timeout increase.
  181. Aug 24 17:16:15 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  182. Aug 24 17:16:15 [1715] pm1 stonithd: info: pcmk_cpg_membership: Member[0.0] stonithd.3232266865
  183. Aug 24 17:16:15 [1715] pm1 stonithd: info: pcmk_cpg_membership: Joined[1.0] stonithd.3232266924
  184. Aug 24 17:16:16 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.8535 ms (threshold is 800.0000 ms). Consider token timeout increase.
  185. Aug 24 17:16:16 [1717] pm1 attrd: info: pcmk_cpg_membership: Member[0.0] attrd.3232266865
  186. Aug 24 17:16:17 [1717] pm1 attrd: info: pcmk_cpg_membership: Joined[1.0] attrd.3232266924
  187. Aug 24 17:16:17 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.3574 ms (threshold is 800.0000 ms). Consider token timeout increase.
  188. Aug 24 17:16:17 [1715] pm1 stonithd: info: pcmk_cpg_membership: Member[1.0] stonithd.3232266865
  189. Aug 24 17:16:18 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.4658 ms (threshold is 800.0000 ms). Consider token timeout increase.
  190. Aug 24 17:16:18 [1714] pm1 cib: info: pcmk_cpg_membership: Member[0.0] cib.3232266865
  191. Aug 24 17:16:19 [1723] pm1 crmd: info: pcmk_cpg_membership: Member[0.0] crmd.3232266865
  192. Aug 24 17:16:19 [1723] pm1 crmd: info: pcmk_cpg_membership: Joined[1.0] crmd.3232266924
  193. Aug 24 17:16:19 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1003.1968 ms (threshold is 800.0000 ms). Consider token timeout increase.
  194. Aug 24 17:16:19 [1715] pm1 stonithd: info: corosync_node_name: Unable to get node name for nodeid 3232266924
  195. Aug 24 17:16:19 [1715] pm1 stonithd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266924
  196. Aug 24 17:16:19 [1715] pm1 stonithd: info: crm_get_peer: Created entry e97fec63-5f0d-4a63-a673-2d5fd54b1414/0x1a83970 for node (null)/3232266924 (2 total)
  197. Aug 24 17:16:19 [1715] pm1 stonithd: info: crm_get_peer: Node 3232266924 has uuid 3232266924
  198. Aug 24 17:16:19 [1715] pm1 stonithd: info: pcmk_cpg_membership: Member[1.1] stonithd.3232266924
  199. Aug 24 17:16:19 [1715] pm1 stonithd: info: crm_update_peer_proc: pcmk_cpg_membership: Node (null)[3232266924] - corosync-cpg is now online
  200. Aug 24 17:16:19 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:788) was formed. Members
  201. Aug 24 17:16:19 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  202. Aug 24 17:16:19 [1714] pm1 cib: info: cib_process_request: Completed cib_modify operation for section nodes: OK (rc=0, origin=pm1/crmd/3, version=0.0.0)
  203. Aug 24 17:16:19 [1714] pm1 cib: info: pcmk_cpg_membership: Joined[1.0] cib.3232266924
  204. Aug 24 17:16:20 [1717] pm1 attrd: info: pcmk_cpg_membership: Member[1.0] attrd.3232266865
  205. Aug 24 17:16:20 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 997.1684 ms (threshold is 800.0000 ms). Consider token timeout increase.
  206. Aug 24 17:16:20 [1723] pm1 crmd: info: pcmk_cpg_membership: Member[1.0] crmd.3232266865
  207. Aug 24 17:16:21 [1715] pm1 stonithd: info: corosync_node_name: Unable to get node name for nodeid 3232266865
  208. Aug 24 17:16:21 [1715] pm1 stonithd: notice: get_node_name: Defaulting to uname -n for the local corosync node name
  209. Aug 24 17:16:21 [1715] pm1 stonithd: info: crm_get_peer: Node 3232266924 is now known as pm2
  210. Aug 24 17:16:21 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  211. Aug 24 17:16:21 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.0273 ms (threshold is 800.0000 ms). Consider token timeout increase.
  212. Aug 24 17:16:22 [1717] pm1 attrd: info: corosync_node_name: Unable to get node name for nodeid 3232266924
  213. Aug 24 17:16:22 [1717] pm1 attrd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266924
  214. Aug 24 17:16:22 [1717] pm1 attrd: info: crm_get_peer: Created entry b7d25830-99b1-4faf-9284-2afccec557ff/0x14dc630 for node (null)/3232266924 (2 total)
  215. Aug 24 17:16:22 [1717] pm1 attrd: info: crm_get_peer: Node 3232266924 has uuid 3232266924
  216. Aug 24 17:16:22 [1717] pm1 attrd: info: pcmk_cpg_membership: Member[1.1] attrd.3232266924
  217. Aug 24 17:16:22 [1717] pm1 attrd: info: crm_update_peer_proc: pcmk_cpg_membership: Node (null)[3232266924] - corosync-cpg is now online
  218. Aug 24 17:16:22 [1717] pm1 attrd: notice: crm_update_peer_state: attrd_peer_change_cb: Node (null)[3232266924] - state is now member (was (null))
  219. Aug 24 17:16:22 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.3059 ms (threshold is 800.0000 ms). Consider token timeout increase.
  220. Aug 24 17:16:22 [1714] pm1 cib: info: pcmk_cpg_membership: Member[1.0] cib.3232266865
  221. Aug 24 17:16:22 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:792) was formed. Members
  222. Aug 24 17:16:22 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  223. Aug 24 17:16:23 [1723] pm1 crmd: info: corosync_node_name: Unable to get node name for nodeid 3232266924
  224. Aug 24 17:16:23 [1723] pm1 crmd: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266924
  225. Aug 24 17:16:23 [1723] pm1 crmd: info: crm_get_peer: Created entry ee0e47f8-631d-43f2-ac44-abfaf5862cf2/0xfdc900 for node (null)/3232266924 (2 total)
  226. Aug 24 17:16:23 [1723] pm1 crmd: info: crm_get_peer: Node 3232266924 has uuid 3232266924
  227. Aug 24 17:16:23 [1723] pm1 crmd: info: pcmk_cpg_membership: Member[1.1] crmd.3232266924
  228. Aug 24 17:16:23 [1723] pm1 crmd: info: crm_update_peer_proc: pcmk_cpg_membership: Node (null)[3232266924] - corosync-cpg is now online
  229. Aug 24 17:16:23 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.1786 ms (threshold is 800.0000 ms). Consider token timeout increase.
  230. Aug 24 17:16:24 [1714] pm1 cib: info: corosync_node_name: Unable to get node name for nodeid 3232266924
  231. Aug 24 17:16:24 [1714] pm1 cib: notice: get_node_name: Could not obtain a node name for corosync nodeid 3232266924
  232. Aug 24 17:16:24 [1714] pm1 cib: info: crm_get_peer: Created entry dc582edb-709f-43dc-8162-0c7d8da06819/0x2716960 for node (null)/3232266924 (2 total)
  233. Aug 24 17:16:24 [1714] pm1 cib: info: crm_get_peer: Node 3232266924 has uuid 3232266924
  234. Aug 24 17:16:24 [1714] pm1 cib: info: pcmk_cpg_membership: Member[1.1] cib.3232266924
  235. Aug 24 17:16:24 [1714] pm1 cib: info: crm_update_peer_proc: pcmk_cpg_membership: Node (null)[3232266924] - corosync-cpg is now online
  236. Aug 24 17:16:24 [1714] pm1 cib: info: crm_get_peer: Node 3232266924 is now known as pm2
  237. Aug 24 17:16:24 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.4242 ms (threshold is 800.0000 ms). Consider token timeout increase.
  238. Aug 24 17:16:24 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  239. Aug 24 17:16:25 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.7529 ms (threshold is 800.0000 ms). Consider token timeout increase.
  240. Aug 24 17:16:25 [1714] pm1 cib: info: cib_process_request: Completed cib_modify operation for section nodes: OK (rc=0, origin=pm2/crmd/3, version=0.0.0)
  241. Aug 24 17:16:26 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1000.1479 ms (threshold is 800.0000 ms). Consider token timeout increase.
  242. Aug 24 17:16:27 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 999.6521 ms (threshold is 800.0000 ms). Consider token timeout increase.
  243. Aug 24 17:16:27 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:808) was formed. Members
  244. Aug 24 17:16:27 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  245. Aug 24 17:17:41 [1693] pm1 corosync warning [MAIN ] Corosync main process was not scheduled for 1332.8293 ms (threshold is 800.0000 ms). Consider token timeout increase.
  246. Aug 24 17:17:41 [1693] pm1 corosync notice [TOTEM ] A processor failed, forming new configuration.
  247. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: Diff: --- 0.0.0 2
  248. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: Diff: +++ 0.2.0 815d3dfce58d03d59ecbe591a21bde68
  249. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: + /cib: @epoch=2, @cib-last-written=Mon Aug 24 17:02:28 2015
  250. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: ++ /cib/configuration/crm_config: <cluster_property_set id="cib-bootstrap-options"/>
  251. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: ++ <nvpair name="no-quorum-policy" value="ignore" id="cib-bootstrap-options-no-quorum-policy"/>
  252. Aug 24 17:17:41 [1714] pm1 cib: info: cib_perform_op: ++ </cluster_property_set>
  253. Aug 24 17:17:41 [1714] pm1 cib: info: cib_process_request: Completed cib_apply_diff operation for section 'all': OK (rc=0, origin=pm2/cibadmin/2, version=0.2.0)
  254. Aug 24 17:17:41 [1714] pm1 cib: info: write_cib_contents: Archived previous version as /var/lib/pacemaker/cib/cib-5.raw
  255. Aug 24 17:17:41 [1693] pm1 corosync notice [TOTEM ] A new membership (192.168.122.113:812) was formed. Members
  256. Aug 24 17:17:41 [1693] pm1 corosync notice [MAIN ] Completed service synchronization, ready to provide service.
  257. Aug 24 17:17:41 [1714] pm1 cib: info: write_cib_contents: Wrote version 0.2.0 of the CIB to disk (digest: fb6d6f937a22c3581ddd988192da1edf)
  258. Aug 24 17:17:41 [1714] pm1 cib: info: retrieveCib: Reading cluster configuration from: /var/lib/pacemaker/cib/cib.RofoTk (digest: /var/lib/pacemaker/cib/cib.k3vwBd)
Advertisement
RAW Paste Data Copied
Advertisement