Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Nov 4 18:06:55 xenmaster004 kernel: DLM (built Oct 10 2010 20:43:00) installed
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Corosync Cluster Engine ('1.2.8'): started and ready to provide service.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Corosync built-in features: nss rdma
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Successfully read config from /etc/cluster/cluster.conf
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Successfully parsed cman config
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Successfully configured openais services to load
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [TOTEM ] Initializing transport (UDP/IP).
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [TOTEM ] The network interface [10.255.129.4] is now up.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Using quorum provider quorum_cman
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CMAN ] CMAN 3.0.17 (built Oct 7 2010 06:54:58) started
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync CMAN membership service 2.90
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais cluster membership service B.01.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais event service B.01.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais checkpoint service B.01.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais message service B.03.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais distributed locking service B.03.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: openais timer service A.01.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync extended virtual synchrony service
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync configuration service
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync cluster config database access v1.01
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync profile loading service
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Using quorum provider quorum_cman
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] CLM CONFIGURATION CHANGE
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] New Configuration:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Left:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Joined:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] CLM CONFIGURATION CHANGE
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] New Configuration:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.4)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Left:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Joined:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.4)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [TOTEM ] A processor joined or left the membership and a new membership was formed.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CMAN ] quorum regained, resuming activity
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] This node is within the primary component and will provide service.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Members[1]: 2
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Members[1]: 2
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Completed service synchronization, ready to provide service.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] CLM CONFIGURATION CHANGE
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] New Configuration:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.4)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Left:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Joined:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] CLM CONFIGURATION CHANGE
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] New Configuration:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.3)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.4)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Left:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] Members Joined:
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [CLM ] #011r(0) ip(10.255.129.3)
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [TOTEM ] A processor joined or left the membership and a new membership was formed.
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Members[2]: 1 2
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [QUORUM] Members[2]: 1 2
- Nov 4 18:06:56 xenmaster004 corosync[2327]: [MAIN ] Completed service synchronization, ready to provide service.
- Nov 4 18:07:00 xenmaster004 fenced[2380]: fenced 3.0.17 started
- Nov 4 18:07:00 xenmaster004 dlm_controld[2395]: dlm_controld 3.0.17 started
- Nov 4 18:07:00 xenmaster004 gfs_controld[2433]: gfs_controld 3.0.17 started
- Nov 4 18:07:55 xenmaster004 kernel: dlm: Using SCTP for communications
- Nov 4 18:07:55 xenmaster004 kernel: SCTP: Hash tables configured (established 65536 bind 65536)
- Nov 4 18:07:55 xenmaster004 kernel: dlm: connecting to 1 sctp association 1
- Nov 4 18:07:56 xenmaster004 clvmd: Cluster LVM daemon started - connected to CMAN
- Nov 4 18:11:10 xenmaster004 kernel: INFO: task clvmd:2577 blocked for more than 120 seconds.
- Nov 4 18:11:10 xenmaster004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
- Nov 4 18:11:10 xenmaster004 kernel: clvmd D ffff88003a1ebb80 0 2577 1 0x00000080
- Nov 4 18:11:10 xenmaster004 kernel: ffff880028c93cc0 0000000000000282 0000000000000000 ffff880028c93fd8
- Nov 4 18:11:10 xenmaster004 kernel: 0000000000011cb0 0000000000000001 ffff880028c93fd8 ffff880028c93fd8
- Nov 4 18:11:10 xenmaster004 kernel: ffff8800032cb270 000000000000f980 0000000000015740 ffff8800032cb270
- Nov 4 18:11:10 xenmaster004 kernel: Call Trace:
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8145ccc1>] rwsem_down_failed_common+0x84/0xa1
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8145cd2e>] rwsem_down_read_failed+0x26/0x30
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff81231bc4>] call_rwsem_down_read_failed+0x14/0x30
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8145c43a>] ? down_read+0x37/0x3b
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffffa01bfe49>] dlm_user_request+0x46/0x1d9 [dlm]
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8100f6af>] ? xen_restore_fl_direct_end+0x0/0x1
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8110f556>] ? kmem_cache_alloc_notrace+0x9b/0xbf
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffffa01c7f5b>] device_write+0x362/0x697 [dlm]
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff811f2200>] ? selinux_file_permission+0x5c/0xb3
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff811e8535>] ? security_file_permission+0x16/0x18
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8111d864>] vfs_write+0xae/0x10b
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff8111d981>] sys_write+0x4a/0x6e
- Nov 4 18:11:10 xenmaster004 kernel: [<ffffffff81012d32>] system_call_fastpath+0x16/0x1b
- Nov 4 18:13:10 xenmaster004 kernel: INFO: task clvmd:2577 blocked for more than 120 seconds.
- Nov 4 18:13:10 xenmaster004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
- Nov 4 18:13:10 xenmaster004 kernel: clvmd D ffff88003a1ebb80 0 2577 1 0x00000080
- Nov 4 18:13:10 xenmaster004 kernel: ffff880028c93cc0 0000000000000282 0000000000000000 ffff880028c93fd8
- Nov 4 18:13:10 xenmaster004 kernel: 0000000000011cb0 0000000000000001 ffff880028c93fd8 ffff880028c93fd8
- Nov 4 18:13:10 xenmaster004 kernel: ffff8800032cb270 000000000000f980 0000000000015740 ffff8800032cb270
- Nov 4 18:13:10 xenmaster004 kernel: Call Trace:
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8145ccc1>] rwsem_down_failed_common+0x84/0xa1
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8145cd2e>] rwsem_down_read_failed+0x26/0x30
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff81231bc4>] call_rwsem_down_read_failed+0x14/0x30
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8145c43a>] ? down_read+0x37/0x3b
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffffa01bfe49>] dlm_user_request+0x46/0x1d9 [dlm]
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8100f6af>] ? xen_restore_fl_direct_end+0x0/0x1
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8110f556>] ? kmem_cache_alloc_notrace+0x9b/0xbf
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffffa01c7f5b>] device_write+0x362/0x697 [dlm]
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff811f2200>] ? selinux_file_permission+0x5c/0xb3
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff811e8535>] ? security_file_permission+0x16/0x18
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8111d864>] vfs_write+0xae/0x10b
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff8111d981>] sys_write+0x4a/0x6e
- Nov 4 18:13:10 xenmaster004 kernel: [<ffffffff81012d32>] system_call_fastpath+0x16/0x1b
- Nov 4 18:15:00 xenmaster004 kernel: dlm: writequeue empty for nodeid 1
- Nov 4 18:15:10 xenmaster004 kernel: INFO: task clvmd:2577 blocked for more than 120 seconds.
- Nov 4 18:15:10 xenmaster004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
- Nov 4 18:15:10 xenmaster004 kernel: clvmd D ffff88003a1ebb80 0 2577 1 0x00000080
- Nov 4 18:15:10 xenmaster004 kernel: ffff880028c93cc0 0000000000000282 0000000000000000 ffff880028c93fd8
- Nov 4 18:15:10 xenmaster004 kernel: 0000000000011cb0 0000000000000001 ffff880028c93fd8 ffff880028c93fd8
- Nov 4 18:15:10 xenmaster004 kernel: ffff8800032cb270 000000000000f980 0000000000015740 ffff8800032cb270
- Nov 4 18:15:10 xenmaster004 kernel: Call Trace:
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8145ccc1>] rwsem_down_failed_common+0x84/0xa1
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8145cd2e>] rwsem_down_read_failed+0x26/0x30
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff81231bc4>] call_rwsem_down_read_failed+0x14/0x30
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8145c43a>] ? down_read+0x37/0x3b
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffffa01bfe49>] dlm_user_request+0x46/0x1d9 [dlm]
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8100ef91>] ? xen_force_evtchn_callback+0xd/0xf
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8100f6af>] ? xen_restore_fl_direct_end+0x0/0x1
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8110f556>] ? kmem_cache_alloc_notrace+0x9b/0xbf
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffffa01c7f5b>] device_write+0x362/0x697 [dlm]
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff811f2200>] ? selinux_file_permission+0x5c/0xb3
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff811e8535>] ? security_file_permission+0x16/0x18
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8111d864>] vfs_write+0xae/0x10b
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff8111d981>] sys_write+0x4a/0x6e
- Nov 4 18:15:10 xenmaster004 kernel: [<ffffffff81012d32>] system_call_fastpath+0x16/0x1b
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement