API tools faq
paste
Advertisement
Guest User

Secondary logs after primary forceful shutdown

a guest
Jul 4th, 2013
192
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.54 KB | None | 0 0
raw download clone embed print report
  1. ==> /var/log/messages <==
  2. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: PingAck did not arrive in time.
  3. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: peer( Primary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
  4. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: asender terminated
  5. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: Terminating drbd_a_r0
  6. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: Connection closed
  7. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: conn( NetworkFailure -> Unconnected )
  8. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: receiver terminated
  9. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: Restarting receiver thread
  10. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: receiver (re)started
  11. Jul 4 13:25:40 centos6-cluster-test-sec kernel: d-con r0: conn( Unconnected -> WFConnection )
  12.  
  13. ==> /var/log/cluster/corosync.log <==
  14. Jul 04 13:25:44 corosync [TOTEM ] A processor failed, forming new configuration.
  15.  
  16. ==> /var/log/messages <==
  17. Jul 4 13:25:44 centos6-cluster-test-sec corosync[1698]: [TOTEM ] A processor failed, forming new configuration.
  18.  
  19. ==> /var/log/cluster/corosync.log <==
  20. Jul 04 13:25:46 corosync [QUORUM] Members[1]: 2
  21. Jul 04 13:25:46 corosync [TOTEM ] A processor joined or left the membership and a new membership was formed.
  22.  
  23. ==> /var/log/messages <==
  24. Jul 4 13:25:46 centos6-cluster-test-sec corosync[1698]: [QUORUM] Members[1]: 2
  25. Jul 4 13:25:46 centos6-cluster-test-sec corosync[1698]: [TOTEM ] A processor joined or left the membership and a new membership was formed.
  26. Jul 4 13:25:46 centos6-cluster-test-sec kernel: dlm: closing connection to node 1
  27.  
  28. ==> /var/log/cluster/corosync.log <==
  29. Jul 04 13:25:46 corosync [CPG ] chosen downlist: sender r(0) ip(172.20.180.102) ; members(old:2 left:1)
  30.  
  31. ==> /var/log/messages <==
  32. Jul 4 13:25:46 centos6-cluster-test-sec corosync[1698]: [CPG ] chosen downlist: sender r(0) ip(172.20.180.102) ; members(old:2 left:1)
  33.  
  34. ==> /var/log/cluster/corosync.log <==
  35. Jul 04 13:25:46 corosync [MAIN ] Completed service synchronization, ready to provide service.
  36.  
  37. ==> /var/log/messages <==
  38. Jul 4 13:25:46 centos6-cluster-test-sec corosync[1698]: [MAIN ] Completed service synchronization, ready to provide service.
  39.  
  40. ==> /var/log/cluster/rgmanager.log <==
  41. Jul 04 13:25:46 rgmanager State change: centos6-cluster-test-pri DOWN
  42.  
  43. ==> /var/log/messages <==
  44. Jul 4 13:25:46 centos6-cluster-test-sec rgmanager[1971]: State change: centos6-cluster-test-pri DOWN
  45.  
  46. ==> /var/log/cluster/fenced.log <==
  47. Jul 04 13:25:46 fenced fencing node centos6-cluster-test-pri
  48.  
  49. ==> /var/log/messages <==
  50. Jul 4 13:25:46 centos6-cluster-test-sec fenced[1764]: fencing node centos6-cluster-test-pri
  51.  
  52. ==> /var/log/cluster/fenced.log <==
  53. Jul 04 13:25:46 fenced fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  54. Jul 04 13:25:46 fenced fence centos6-cluster-test-pri failed
  55.  
  56. ==> /var/log/messages <==
  57. Jul 4 13:25:46 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  58. Jul 4 13:25:46 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri failed
  59.  
  60. ==> /var/log/cluster/fenced.log <==
  61. Jul 04 13:25:49 fenced fencing node centos6-cluster-test-pri
  62.  
  63. ==> /var/log/messages <==
  64. Jul 4 13:25:49 centos6-cluster-test-sec fenced[1764]: fencing node centos6-cluster-test-pri
  65.  
  66. ==> /var/log/cluster/fenced.log <==
  67. Jul 04 13:25:49 fenced fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  68. Jul 04 13:25:49 fenced fence centos6-cluster-test-pri failed
  69.  
  70. ==> /var/log/messages <==
  71. Jul 4 13:25:49 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  72. Jul 4 13:25:49 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri failed
  73.  
  74. ==> /var/log/cluster/fenced.log <==
  75. Jul 04 13:25:52 fenced fencing node centos6-cluster-test-pri
  76.  
  77. ==> /var/log/messages <==
  78. Jul 4 13:25:52 centos6-cluster-test-sec fenced[1764]: fencing node centos6-cluster-test-pri
  79.  
  80. ==> /var/log/cluster/fenced.log <==
  81. Jul 04 13:25:53 fenced fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  82. Jul 04 13:25:53 fenced fence centos6-cluster-test-pri failed
  83.  
  84. ==> /var/log/messages <==
  85. Jul 4 13:25:53 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri dev 0.0 agent none result: error no method
  86. Jul 4 13:25:53 centos6-cluster-test-sec fenced[1764]: fence centos6-cluster-test-pri failed
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!