Attachment 686935 Details for Bug 903763 – File: var_log_messages

File: var_log_messages

var_log_messages (text/plain), 10.65 KB, created by Franck C. on 2013-01-24 19:38:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Franck C.

Created: 2013-01-24 19:38:48 UTC

Size: 10.65 KB

patch

obsolete

>Jan 23 09:07:36 node140 corosync[19316]:   [QB    ] server name: votequorum
>Jan 23 09:07:36 node140 corosync[19316]:   [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
>Jan 23 09:07:36 node140 corosync[19316]:   [QB    ] server name: quorum
>Jan 23 09:07:36 node140 corosync[19316]:   [QUORUM] Members[1]: -1940861629
>Jan 23 09:07:36 node140 corosync[19316]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.140:70344) was formed.
>Jan 23 09:07:36 node140 corosync[19316]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:07:36 node140 corosync[19316]:   [QUORUM] Members[3]: -1940861629 -1907307197 -1823421117
>Jan 23 09:07:36 node140 corosync[19316]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.140:70348) was formed.
>Jan 23 09:07:36 node140 corosync[19316]:   [QUORUM] This node is within the primary component and will provide service.
>Jan 23 09:07:36 node140 corosync[19316]:   [QUORUM] Members[3]: -1940861629 -1907307197 -1823421117
>Jan 23 09:07:36 node140 corosync[19316]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:07:37 node140 corosync[19252]: Starting Corosync Cluster Engine (corosync): [  OK  ]
>Jan 23 09:07:38 node140 pacemakerd[19399]:     info: get_cluster_type: Detected an active 'corosync' cluster
>Jan 23 09:07:38 node140 pacemakerd[19399]:     info: read_config: Reading configure for stack: corosync
>Jan 23 09:07:38 node140 pacemakerd[19399]:   notice: main: Starting Pacemaker 1.1.7-2.fc17 (Build: ee0730e13d124c3d58f00016c3376a1de5323cff):  generated-manpages agent-manpages ascii-docs publican-docs ncurses libqb-logging  corosync-native
>Jan 23 09:07:38 node140 stonith-ng[19402]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:07:38 node140 stonith-ng[19402]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:07:38 node140 attrd[19404]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:07:38 node140 cib[19401]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:07:38 node140 cib[19401]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:07:38 node140 stonith-ng[19402]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:07:38 node140 cib[19401]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:07:39 node140 crmd[19406]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:07:39 node140 crmd[19406]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:07:39 node140 crmd[19406]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:07:47 node140 corosync[19316]:   [QUORUM] Members[4]: -2024747709 -1940861629 -1907307197 -1823421117
>Jan 23 09:07:47 node140 corosync[19316]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70352) was formed.
>Jan 23 09:07:47 node140 corosync[19316]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:34:37 node140 corosync[19316]:   [QUORUM] Members[3]: -2024747709 -1940861629 -1823421117
>Jan 23 09:34:37 node140 corosync[19316]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70356) was formed.
>Jan 23 09:34:37 node140 crmd[19406]:   notice: corosync_mark_unseen_peer_dead: Node -1907307197/node142 was not seen in the previous transition
>Jan 23 09:34:37 node140 corosync[19316]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:36:51 node140 stonith-ng[20311]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:36:51 node140 stonith-ng[20311]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:36:51 node140 stonith-ng[20311]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:42:05 node140 corosync[19316]:   [QUORUM] Members[4]: -2024747709 -1940861629 -1907307197 -1823421117
>Jan 23 09:42:05 node140 corosync[19316]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70452) was formed.
>Jan 23 09:42:05 node140 corosync[19316]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:42:28 node140 corosync[27127]: Signaling Corosync Cluster Engine (corosync) to terminate: [  OK  ]
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Unloading all Corosync service engines.
>Jan 23 09:42:28 node140 corosync[19316]:   [QB    ] withdrawing server sockets
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync vote quorum service v1.0
>Jan 23 09:42:28 node140 corosync[19316]:   [QB    ] withdrawing server sockets
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync configuration map access
>Jan 23 09:42:28 node140 corosync[19316]:   [QB    ] withdrawing server sockets
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync configuration service
>Jan 23 09:42:28 node140 corosync[19316]:   [QB    ] withdrawing server sockets
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync cluster closed process group service v1.01
>Jan 23 09:42:28 node140 corosync[19316]:   [QB    ] withdrawing server sockets
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync cluster quorum service v0.1
>Jan 23 09:42:28 node140 corosync[19316]:   [SERV  ] Service engine unloaded: corosync profile loading service
>Jan 23 09:42:28 node140 corosync[19316]:   [MAIN  ] Corosync Cluster Engine exiting normally
>Jan 23 09:42:29 node140 corosync[27127]: Waiting for corosync services to unload:.[  OK  ]
>Jan 23 09:52:35 node140 corosync[6997]:   [TOTEM ] Initializing transport (UDP/IP Multicast).
>Jan 23 09:52:35 node140 corosync[6997]:   [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
>Jan 23 09:52:35 node140 corosync[6997]:   [TOTEM ] The network interface [67.205.80.140] is now up.
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync configuration map access [0]
>Jan 23 09:52:35 node140 corosync[6997]:   [QB    ] server name: cmap
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync configuration service [1]
>Jan 23 09:52:35 node140 corosync[6997]:   [QB    ] server name: cfg
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
>Jan 23 09:52:35 node140 corosync[6997]:   [QB    ] server name: cpg
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync profile loading service [4]
>Jan 23 09:52:35 node140 corosync[6997]:   [QUORUM] Using quorum provider corosync_votequorum
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
>Jan 23 09:52:35 node140 corosync[6997]:   [QB    ] server name: votequorum
>Jan 23 09:52:35 node140 corosync[6997]:   [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
>Jan 23 09:52:35 node140 corosync[6997]:   [QB    ] server name: quorum
>Jan 23 09:52:35 node140 corosync[6997]:   [QUORUM] Members[1]: -1940861629
>Jan 23 09:52:35 node140 corosync[6997]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.140:70456) was formed.
>Jan 23 09:52:35 node140 corosync[6997]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:52:36 node140 corosync[6956]: Starting Corosync Cluster Engine (corosync): [  OK  ]
>Jan 23 09:52:36 node140 pacemakerd[7031]:     info: get_cluster_type: Detected an active 'corosync' cluster
>Jan 23 09:52:36 node140 pacemakerd[7031]:     info: read_config: Reading configure for stack: corosync
>Jan 23 09:52:36 node140 pacemakerd[7031]:   notice: main: Starting Pacemaker 1.1.7-2.fc17 (Build: ee0730e13d124c3d58f00016c3376a1de5323cff):  generated-manpages agent-manpages ascii-docs publican-docs ncurses libqb-logging  corosync-native
>Jan 23 09:52:37 node140 stonith-ng[7033]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:52:37 node140 stonith-ng[7033]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:52:37 node140 attrd[7035]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:52:37 node140 cib[7032]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:52:37 node140 cib[7032]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:52:37 node140 stonith-ng[7033]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:52:37 node140 cib[7032]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:52:38 node140 crmd[7037]:     info: get_cluster_type: Cluster type is: 'corosync'
>Jan 23 09:52:38 node140 crmd[7037]:   notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync
>Jan 23 09:52:38 node140 crmd[7037]:     info: init_ais_connection_once: Connection to 'corosync': established
>Jan 23 09:52:41 node140 corosync[6997]:   [QUORUM] Members[2]: -2024747709 -1940861629
>Jan 23 09:52:41 node140 corosync[6997]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70460) was formed.
>Jan 23 09:52:41 node140 corosync[6997]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:53:34 node140 corosync[6997]:   [QUORUM] Members[3]: -2024747709 -1940861629 -1907307197
>Jan 23 09:53:34 node140 corosync[6997]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70464) was formed.
>Jan 23 09:53:34 node140 corosync[6997]:   [QUORUM] This node is within the primary component and will provide service.
>Jan 23 09:53:34 node140 corosync[6997]:   [QUORUM] Members[3]: -2024747709 -1940861629 -1907307197
>Jan 23 09:53:34 node140 corosync[6997]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:53:38 node140 corosync[6997]:   [QUORUM] Members[4]: -2024747709 -1940861629 -1907307197 -1823421117
>Jan 23 09:53:38 node140 corosync[6997]:   [TOTEM ] A processor joined or left the membership and a new membership (67.205.80.135:70468) was formed.
>Jan 23 09:53:38 node140 corosync[6997]:   [MAIN  ] Completed service synchronization, ready to provide service.
>Jan 23 09:59:26 node140 abrt[15028]: Saved core dump of pid 6997 (/usr/sbin/corosync) to /var/spool/abrt/ccpp-2013-01-23-09:59:26-6997 (27688960 bytes)
>Jan 23 09:59:27 node140 systemd[1]: corosync.service: main process exited, code=dumped, status=7
>Jan 23 09:59:27 node140 systemd[1]: Unit corosync.service entered failed state.

Actions: View

Attachments on bug 903763: 686925 | 686926 | 686927 | 686928 | 686929 | 686930 | 686931 | 686932 | 686933 | 686934 | 686935