digimer

Untitled

Jan 1st, 2012
235
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.55 KB | None | 0 0
  1. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Corosync Cluster Engine ('1.4.1'): started and ready to provide service.
  2. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Corosync built-in features: nss dbus rdma snmp
  3. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Successfully read config from /etc/cluster/cluster.conf
  4. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Successfully parsed cman config
  5. Jan 1 15:23:54 an-node02 corosync[1884]: [TOTEM ] Initializing transport (UDP/IP Multicast).
  6. Jan 1 15:23:54 an-node02 corosync[1884]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
  7. Jan 1 15:23:54 an-node02 corosync[1884]: [TOTEM ] The network interface [10.20.0.2] is now up.
  8. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Using quorum provider quorum_cman
  9. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1
  10. Jan 1 15:23:54 an-node02 corosync[1884]: [CMAN ] CMAN 3.0.12.1 (built Sep 30 2011 03:17:43) started
  11. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync CMAN membership service 2.90
  12. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: openais checkpoint service B.01.01
  13. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync extended virtual synchrony service
  14. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync configuration service
  15. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01
  16. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync cluster config database access v1.01
  17. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync profile loading service
  18. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Using quorum provider quorum_cman
  19. Jan 1 15:23:54 an-node02 corosync[1884]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1
  20. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Compatibility mode set to whitetank. Using V1 and V2 of the synchronization engine.
  21. Jan 1 15:23:54 an-node02 corosync[1884]: [TOTEM ] A processor joined or left the membership and a new membership was formed.
  22. Jan 1 15:23:54 an-node02 corosync[1884]: [CMAN ] quorum regained, resuming activity
  23. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] This node is within the primary component and will provide service.
  24. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Members[1]: 2
  25. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Members[1]: 2
  26. Jan 1 15:23:54 an-node02 corosync[1884]: [CPG ] chosen downlist: sender r(0) ip(10.20.0.2) ; members(old:0 left:0)
  27. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Completed service synchronization, ready to provide service.
  28. Jan 1 15:23:54 an-node02 corosync[1884]: [TOTEM ] A processor joined or left the membership and a new membership was formed.
  29. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Members[2]: 1 2
  30. Jan 1 15:23:54 an-node02 corosync[1884]: [QUORUM] Members[2]: 1 2
  31. Jan 1 15:23:54 an-node02 corosync[1884]: [CPG ] chosen downlist: sender r(0) ip(10.20.0.1) ; members(old:1 left:0)
  32. Jan 1 15:23:54 an-node02 corosync[1884]: [MAIN ] Completed service synchronization, ready to provide service.
  33. Jan 1 15:23:58 an-node02 fenced[1944]: fenced 3.0.12.1 started
  34. Jan 1 15:23:58 an-node02 fenced[1944]: failed to get dbus connection
  35. Jan 1 15:23:58 an-node02 dlm_controld[1970]: dlm_controld 3.0.12.1 started
  36. Jan 1 15:23:59 an-node02 gfs_controld[2019]: gfs_controld 3.0.12.1 started
  37. Jan 1 15:24:02 an-node02 rgmanager[2436]: I am node #2
  38. Jan 1 15:24:02 an-node02 rgmanager[2436]: Resource Group Manager Starting
  39. Jan 1 15:24:05 an-node02 rgmanager[3562]: [vm] Could not determine Hypervisor
  40. Jan 1 15:24:05 an-node02 rgmanager[2436]: stop on vm "vm0002-web" returned 2 (invalid argument(s))
  41. Jan 1 15:24:05 an-node02 rgmanager[3563]: [vm] Could not determine Hypervisor
  42. Jan 1 15:24:05 an-node02 rgmanager[2436]: stop on vm "vm0003-db" returned 2 (invalid argument(s))
  43. Jan 1 15:24:05 an-node02 rgmanager[3615]: [vm] Could not determine Hypervisor
  44. Jan 1 15:24:05 an-node02 rgmanager[2436]: stop on vm "vm0004-ms" returned 2 (invalid argument(s))
  45. Jan 1 15:24:06 an-node02 kernel: vbr2: port 1(bond2) entering forwarding state
  46. Jan 1 15:24:09 an-node02 rgmanager[3644]: [vm] Could not determine Hypervisor
  47. Jan 1 15:24:09 an-node02 rgmanager[2436]: stop on vm "vm0001-dev" returned 2 (invalid argument(s))
Advertisement
Add Comment
Please, Sign In to add comment