API tools faq
paste
Advertisement
Max13

corosync_pve1_oct.log

Max13
Oct 13th, 2024
26
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 227.49 KB | None | 0 0
raw download clone embed print report
  1. Oct 10 00:03:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  2. Oct 10 00:03:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  3. Oct 10 00:18:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  4. Oct 10 00:18:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  5. Oct 10 00:32:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  6. Oct 10 00:32:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  7. Oct 10 00:46:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  8. Oct 10 00:46:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  9. Oct 10 01:00:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  10. Oct 10 01:00:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  11. Oct 10 01:14:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  12. Oct 10 01:14:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  13. Oct 10 01:28:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  14. Oct 10 01:28:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  15. Oct 10 01:43:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  16. Oct 10 01:43:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  17. Oct 10 01:57:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  18. Oct 10 01:57:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  19. Oct 10 02:11:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  20. Oct 10 02:11:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  21. Oct 10 02:25:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  22. Oct 10 02:25:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  23. Oct 10 02:39:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  24. Oct 10 02:39:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  25. Oct 10 02:53:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  26. Oct 10 02:53:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  27. Oct 10 03:08:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  28. Oct 10 03:08:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  29. Oct 10 03:22:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  30. Oct 10 03:22:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  31. Oct 10 03:36:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  32. Oct 10 03:36:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  33. Oct 10 03:50:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  34. Oct 10 03:50:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  35. Oct 10 04:04:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  36. Oct 10 04:04:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  37. Oct 10 04:18:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  38. Oct 10 04:18:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  39. Oct 10 04:33:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  40. Oct 10 04:33:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  41. Oct 10 04:47:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  42. Oct 10 04:47:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  43. Oct 10 05:01:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  44. Oct 10 05:01:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  45. Oct 10 05:15:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  46. Oct 10 05:15:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  47. Oct 10 05:29:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  48. Oct 10 05:29:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  49. Oct 10 05:43:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  50. Oct 10 05:43:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  51. Oct 10 05:58:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  52. Oct 10 05:58:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  53. Oct 10 06:12:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  54. Oct 10 06:12:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  55. Oct 10 06:26:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  56. Oct 10 06:26:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  57. Oct 10 06:40:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  58. Oct 10 06:40:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  59. Oct 10 06:54:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  60. Oct 10 06:54:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  61. Oct 10 07:08:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  62. Oct 10 07:08:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  63. Oct 10 07:23:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  64. Oct 10 07:23:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  65. Oct 10 07:37:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  66. Oct 10 07:37:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  67. Oct 10 07:51:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  68. Oct 10 07:51:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  69. Oct 10 08:05:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  70. Oct 10 08:05:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  71. Oct 10 08:19:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  72. Oct 10 08:19:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  73. Oct 10 08:33:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  74. Oct 10 08:33:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  75. Oct 10 08:48:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  76. Oct 10 08:48:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  77. Oct 10 09:02:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  78. Oct 10 09:02:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  79. Oct 10 09:16:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  80. Oct 10 09:16:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  81. Oct 10 09:30:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  82. Oct 10 09:30:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  83. Oct 10 09:44:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  84. Oct 10 09:44:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  85. Oct 10 09:58:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  86. Oct 10 09:58:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  87. Oct 10 10:13:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  88. Oct 10 10:13:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  89. Oct 10 10:27:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  90. Oct 10 10:27:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  91. Oct 10 10:41:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  92. Oct 10 10:41:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  93. Oct 10 10:55:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  94. Oct 10 10:55:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  95. Oct 10 11:09:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  96. Oct 10 11:09:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  97. Oct 10 11:23:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  98. Oct 10 11:23:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  99. Oct 10 11:38:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  100. Oct 10 11:38:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  101. Oct 10 11:52:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  102. Oct 10 11:52:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  103. Oct 10 12:00:28 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  104. Oct 10 12:00:28 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  105. Oct 10 12:00:28 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  106. Oct 10 12:00:29 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  107. Oct 10 12:00:29 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  108. Oct 10 12:00:29 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  109. Oct 10 12:41:47 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  110. Oct 10 12:41:47 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  111. Oct 10 12:50:52 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1349
  112. Oct 10 12:55:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  113. Oct 10 12:55:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  114. Oct 10 13:10:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  115. Oct 10 13:10:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  116. Oct 10 13:24:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  117. Oct 10 13:24:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  118. Oct 10 13:38:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  119. Oct 10 13:38:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  120. Oct 10 13:52:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  121. Oct 10 13:52:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  122. Oct 10 14:06:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  123. Oct 10 14:06:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  124. Oct 10 14:21:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  125. Oct 10 14:21:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  126. Oct 10 14:35:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  127. Oct 10 14:35:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  128. Oct 10 14:49:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  129. Oct 10 14:49:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  130. Oct 10 15:03:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  131. Oct 10 15:03:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  132. Oct 10 15:17:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  133. Oct 10 15:17:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  134. Oct 10 15:31:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  135. Oct 10 15:31:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  136. Oct 10 15:34:44 pve1 corosync[1596]: [TOTEM ] Token has not been received in 3225 ms
  137. Oct 10 15:42:38 pve1 corosync[1596]: [TOTEM ] Retransmit List: 26afb6
  138. Oct 10 15:42:38 pve1 corosync[1596]: [TOTEM ] Retransmit List: 26afb6
  139. Oct 10 15:42:38 pve1 corosync[1596]: [TOTEM ] Retransmit List: 26afb7
  140. Oct 10 15:42:39 pve1 corosync[1596]: [TOTEM ] Retransmit List: 26afbb
  141. Oct 10 15:46:07 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  142. Oct 10 15:46:07 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  143. Oct 10 16:00:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  144. Oct 10 16:00:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  145. Oct 10 16:14:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  146. Oct 10 16:14:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  147. Oct 10 16:28:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  148. Oct 10 16:28:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  149. Oct 10 16:42:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  150. Oct 10 16:42:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  151. Oct 10 16:57:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  152. Oct 10 16:57:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  153. Oct 10 17:00:26 pve1 corosync[1596]: [TOTEM ] Retransmit List: 27016c
  154. Oct 10 17:00:26 pve1 corosync[1596]: [TOTEM ] Retransmit List: 27016e
  155. Oct 10 17:00:27 pve1 corosync[1596]: [TOTEM ] Retransmit List: 27016f
  156. Oct 10 17:00:27 pve1 corosync[1596]: [TOTEM ] Retransmit List: 270171
  157. Oct 10 17:00:27 pve1 corosync[1596]: [TOTEM ] Retransmit List: 270171
  158. Oct 10 17:11:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  159. Oct 10 17:11:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  160. Oct 10 17:25:26 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  161. Oct 10 17:25:26 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  162. Oct 10 17:39:36 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  163. Oct 10 17:39:36 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  164. Oct 10 17:53:46 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  165. Oct 10 17:53:46 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  166. Oct 10 18:07:56 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  167. Oct 10 18:07:56 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  168. Oct 10 18:22:06 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  169. Oct 10 18:22:06 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  170. Oct 10 18:36:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  171. Oct 10 18:36:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  172. Oct 10 18:50:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  173. Oct 10 18:50:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  174. Oct 10 19:04:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  175. Oct 10 19:04:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  176. Oct 10 19:18:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  177. Oct 10 19:18:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  178. Oct 10 19:32:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  179. Oct 10 19:32:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  180. Oct 10 19:47:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  181. Oct 10 19:47:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  182. Oct 10 20:01:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  183. Oct 10 20:01:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  184. Oct 10 20:15:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  185. Oct 10 20:15:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  186. Oct 10 20:29:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  187. Oct 10 20:29:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  188. Oct 10 20:43:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  189. Oct 10 20:43:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  190. Oct 10 20:57:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  191. Oct 10 20:57:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  192. Oct 10 21:12:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  193. Oct 10 21:12:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  194. Oct 10 21:26:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  195. Oct 10 21:26:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  196. Oct 10 21:40:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  197. Oct 10 21:40:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  198. Oct 10 21:54:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  199. Oct 10 21:54:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  200. Oct 10 22:08:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  201. Oct 10 22:08:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  202. Oct 10 22:22:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  203. Oct 10 22:22:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  204. Oct 10 22:37:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  205. Oct 10 22:37:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  206. Oct 10 22:51:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  207. Oct 10 22:51:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  208. Oct 10 23:00:26 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  209. Oct 10 23:00:26 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  210. Oct 10 23:00:26 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  211. Oct 10 23:00:26 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  212. Oct 10 23:00:27 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  213. Oct 10 23:00:27 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  214. Oct 10 23:00:28 pve1 corosync[1596]: [TOTEM ] Retransmit List: 287b6c
  215. Oct 10 23:41:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  216. Oct 10 23:41:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  217. Oct 10 23:50:48 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1349
  218. Oct 10 23:55:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  219. Oct 10 23:55:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  220. Oct 11 00:10:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  221. Oct 11 00:10:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  222. Oct 11 00:24:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  223. Oct 11 00:24:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  224. Oct 11 00:30:25 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  225. Oct 11 00:30:25 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  226. Oct 11 00:30:25 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  227. Oct 11 00:30:25 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  228. Oct 11 00:30:26 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  229. Oct 11 00:30:26 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  230. Oct 11 01:11:44 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  231. Oct 11 01:11:44 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  232. Oct 11 01:20:47 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1349
  233. Oct 11 01:25:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  234. Oct 11 01:25:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  235. Oct 11 01:40:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  236. Oct 11 01:40:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  237. Oct 11 01:54:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  238. Oct 11 01:54:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  239. Oct 11 02:08:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  240. Oct 11 02:08:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  241. Oct 11 02:22:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  242. Oct 11 02:22:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  243. Oct 11 02:36:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  244. Oct 11 02:36:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  245. Oct 11 02:50:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  246. Oct 11 02:50:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  247. Oct 11 03:05:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  248. Oct 11 03:05:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  249. Oct 11 03:19:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  250. Oct 11 03:19:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  251. Oct 11 03:33:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  252. Oct 11 03:33:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  253. Oct 11 03:47:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  254. Oct 11 03:47:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  255. Oct 11 04:01:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  256. Oct 11 04:01:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  257. Oct 11 04:15:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  258. Oct 11 04:15:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  259. Oct 11 04:30:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  260. Oct 11 04:30:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  261. Oct 11 04:44:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  262. Oct 11 04:44:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  263. Oct 11 04:58:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  264. Oct 11 04:58:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  265. Oct 11 05:12:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  266. Oct 11 05:12:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  267. Oct 11 05:26:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  268. Oct 11 05:26:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  269. Oct 11 05:40:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  270. Oct 11 05:40:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  271. Oct 11 05:55:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  272. Oct 11 05:55:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  273. Oct 11 06:09:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  274. Oct 11 06:09:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  275. Oct 11 06:23:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  276. Oct 11 06:23:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  277. Oct 11 06:37:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  278. Oct 11 06:37:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  279. Oct 11 06:51:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  280. Oct 11 06:51:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  281. Oct 11 07:05:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  282. Oct 11 07:05:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  283. Oct 11 07:20:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  284. Oct 11 07:20:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  285. Oct 11 07:34:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  286. Oct 11 07:34:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  287. Oct 11 07:48:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  288. Oct 11 07:48:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  289. Oct 11 08:02:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  290. Oct 11 08:02:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  291. Oct 11 08:16:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  292. Oct 11 08:16:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  293. Oct 11 08:30:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  294. Oct 11 08:30:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  295. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  296. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  297. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  298. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  299. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  300. Oct 11 08:37:36 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  301. Oct 11 09:18:54 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  302. Oct 11 09:18:54 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  303. Oct 11 09:27:58 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1349
  304. Oct 11 09:33:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  305. Oct 11 09:33:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  306. Oct 11 09:47:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  307. Oct 11 09:47:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  308. Oct 11 10:01:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  309. Oct 11 10:01:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  310. Oct 11 10:15:33 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  311. Oct 11 10:15:33 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  312. Oct 11 10:29:43 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  313. Oct 11 10:29:43 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  314. Oct 11 10:43:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  315. Oct 11 10:43:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  316. Oct 11 10:58:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  317. Oct 11 10:58:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  318. Oct 11 11:12:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  319. Oct 11 11:12:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  320. Oct 11 11:26:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  321. Oct 11 11:26:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  322. Oct 11 11:40:33 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  323. Oct 11 11:40:33 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  324. Oct 11 11:54:43 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  325. Oct 11 11:54:43 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  326. Oct 11 12:08:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  327. Oct 11 12:08:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  328. Oct 11 12:23:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  329. Oct 11 12:23:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  330. Oct 11 12:37:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  331. Oct 11 12:37:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  332. Oct 11 12:51:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  333. Oct 11 12:51:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  334. Oct 11 13:05:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  335. Oct 11 13:05:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  336. Oct 11 13:19:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  337. Oct 11 13:19:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  338. Oct 11 13:30:13 pve1 corosync[1596]: [TOTEM ] Retransmit List: 2c13c0
  339. Oct 11 13:33:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  340. Oct 11 13:33:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  341. Oct 11 13:48:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  342. Oct 11 13:48:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  343. Oct 11 14:02:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  344. Oct 11 14:02:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  345. Oct 11 14:16:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  346. Oct 11 14:16:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  347. Oct 11 14:30:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  348. Oct 11 14:30:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  349. Oct 11 14:44:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  350. Oct 11 14:44:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  351. Oct 11 14:58:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  352. Oct 11 14:58:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  353. Oct 11 15:13:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  354. Oct 11 15:13:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  355. Oct 11 15:27:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  356. Oct 11 15:27:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  357. Oct 11 15:41:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  358. Oct 11 15:41:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  359. Oct 11 15:55:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  360. Oct 11 15:55:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  361. Oct 11 16:09:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  362. Oct 11 16:09:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  363. Oct 11 16:23:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  364. Oct 11 16:23:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  365. Oct 11 16:38:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  366. Oct 11 16:38:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  367. Oct 11 16:52:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  368. Oct 11 16:52:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  369. Oct 11 17:06:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  370. Oct 11 17:06:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  371. Oct 11 17:20:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  372. Oct 11 17:20:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  373. Oct 11 17:34:40 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  374. Oct 11 17:34:40 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  375. Oct 11 17:48:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  376. Oct 11 17:48:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  377. Oct 11 18:03:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  378. Oct 11 18:03:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  379. Oct 11 18:17:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  380. Oct 11 18:17:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  381. Oct 11 18:31:20 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  382. Oct 11 18:31:20 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  383. Oct 11 18:45:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  384. Oct 11 18:45:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  385. Oct 11 18:59:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  386. Oct 11 18:59:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  387. Oct 11 19:13:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  388. Oct 11 19:13:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  389. Oct 11 19:27:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  390. Oct 11 19:27:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  391. Oct 11 19:42:09 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  392. Oct 11 19:42:09 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  393. Oct 11 19:56:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  394. Oct 11 19:56:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  395. Oct 11 20:10:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  396. Oct 11 20:10:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  397. Oct 11 20:24:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  398. Oct 11 20:24:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  399. Oct 11 20:38:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  400. Oct 11 20:38:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  401. Oct 11 20:52:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  402. Oct 11 20:52:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  403. Oct 11 21:07:09 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  404. Oct 11 21:07:09 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  405. Oct 11 21:21:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  406. Oct 11 21:21:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  407. Oct 11 21:35:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  408. Oct 11 21:35:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  409. Oct 11 21:49:38 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  410. Oct 11 21:49:38 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  411. Oct 11 22:00:22 pve1 corosync[1596]: [TOTEM ] Token has not been received in 3225 ms
  412. Oct 11 22:00:23 pve1 corosync[1596]: [QUORUM] Sync members[4]: 1 2 3 4
  413. Oct 11 22:00:23 pve1 corosync[1596]: [TOTEM ] A new membership (1.19f21) was formed. Members
  414. Oct 11 22:00:23 pve1 corosync[1596]: [QUORUM] Members[4]: 1 2 3 4
  415. Oct 11 22:00:23 pve1 corosync[1596]: [MAIN ] Completed service synchronization, ready to provide service.
  416. Oct 11 22:03:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  417. Oct 11 22:03:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  418. Oct 11 22:17:58 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  419. Oct 11 22:17:58 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  420. Oct 11 22:32:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  421. Oct 11 22:32:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  422. Oct 11 22:46:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  423. Oct 11 22:46:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  424. Oct 11 23:00:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  425. Oct 11 23:00:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  426. Oct 11 23:14:38 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  427. Oct 11 23:14:38 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  428. Oct 11 23:28:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  429. Oct 11 23:28:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  430. Oct 11 23:42:58 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  431. Oct 11 23:42:58 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  432. Oct 11 23:57:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  433. Oct 11 23:57:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  434. Oct 12 00:11:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  435. Oct 12 00:11:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  436. Oct 12 00:25:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  437. Oct 12 00:25:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  438. Oct 12 00:39:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  439. Oct 12 00:39:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  440. Oct 12 00:53:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  441. Oct 12 00:53:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  442. Oct 12 01:07:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  443. Oct 12 01:07:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  444. Oct 12 01:22:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  445. Oct 12 01:22:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  446. Oct 12 01:36:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  447. Oct 12 01:36:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  448. Oct 12 01:50:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  449. Oct 12 01:50:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  450. Oct 12 02:04:38 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  451. Oct 12 02:04:38 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  452. Oct 12 02:18:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  453. Oct 12 02:18:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  454. Oct 12 02:32:58 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  455. Oct 12 02:32:58 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  456. Oct 12 02:47:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  457. Oct 12 02:47:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  458. Oct 12 03:01:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  459. Oct 12 03:01:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  460. Oct 12 03:15:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  461. Oct 12 03:15:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  462. Oct 12 03:29:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  463. Oct 12 03:29:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  464. Oct 12 03:43:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  465. Oct 12 03:43:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  466. Oct 12 03:57:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  467. Oct 12 03:57:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  468. Oct 12 04:03:46 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  469. Oct 12 04:03:46 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  470. Oct 12 04:03:46 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  471. Oct 12 04:03:46 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  472. Oct 12 04:03:47 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  473. Oct 12 04:03:47 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  474. Oct 12 04:03:47 pve1 corosync[1596]: [TOTEM ] Retransmit List: 17fb2
  475. Oct 12 04:05:38 pve1 corosync[1596]: [TOTEM ] Retransmit List: 181a3
  476. Oct 12 04:05:38 pve1 corosync[1596]: [TOTEM ] Retransmit List: 181a3
  477. Oct 12 04:12:35 pve1 corosync[1596]: [TOTEM ] Retransmit List: 1888b
  478. Oct 12 04:45:05 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  479. Oct 12 04:45:05 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  480. Oct 12 04:54:11 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1349
  481. Oct 12 04:59:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  482. Oct 12 04:59:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  483. Oct 12 05:13:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  484. Oct 12 05:13:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  485. Oct 12 05:27:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  486. Oct 12 05:27:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  487. Oct 12 05:41:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  488. Oct 12 05:41:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  489. Oct 12 05:56:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  490. Oct 12 05:56:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  491. Oct 12 06:00:19 pve1 corosync[1596]: [QUORUM] Sync members[4]: 1 2 3 4
  492. Oct 12 06:00:19 pve1 corosync[1596]: [TOTEM ] A new membership (1.19f25) was formed. Members
  493. Oct 12 06:00:20 pve1 corosync[1596]: [QUORUM] Members[4]: 1 2 3 4
  494. Oct 12 06:00:20 pve1 corosync[1596]: [MAIN ] Completed service synchronization, ready to provide service.
  495. Oct 12 06:10:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  496. Oct 12 06:10:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  497. Oct 12 06:24:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  498. Oct 12 06:24:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  499. Oct 12 06:38:33 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  500. Oct 12 06:38:33 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  501. Oct 12 06:52:43 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  502. Oct 12 06:52:43 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  503. Oct 12 07:06:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  504. Oct 12 07:06:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  505. Oct 12 07:21:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  506. Oct 12 07:21:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  507. Oct 12 07:35:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  508. Oct 12 07:35:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  509. Oct 12 07:49:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  510. Oct 12 07:49:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  511. Oct 12 08:03:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  512. Oct 12 08:03:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  513. Oct 12 08:17:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  514. Oct 12 08:17:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  515. Oct 12 08:31:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  516. Oct 12 08:31:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  517. Oct 12 08:46:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  518. Oct 12 08:46:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  519. Oct 12 09:00:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  520. Oct 12 09:00:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  521. Oct 12 09:14:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  522. Oct 12 09:14:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  523. Oct 12 09:28:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  524. Oct 12 09:28:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  525. Oct 12 09:42:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  526. Oct 12 09:42:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  527. Oct 12 09:56:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  528. Oct 12 09:56:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  529. Oct 12 10:11:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  530. Oct 12 10:11:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  531. Oct 12 10:25:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  532. Oct 12 10:25:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  533. Oct 12 10:39:20 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  534. Oct 12 10:39:20 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  535. Oct 12 10:53:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  536. Oct 12 10:53:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  537. Oct 12 11:07:40 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  538. Oct 12 11:07:40 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  539. Oct 12 11:21:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  540. Oct 12 11:21:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  541. Oct 12 11:36:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  542. Oct 12 11:36:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  543. Oct 12 11:50:09 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  544. Oct 12 11:50:09 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  545. Oct 12 12:04:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  546. Oct 12 12:04:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  547. Oct 12 12:18:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  548. Oct 12 12:18:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  549. Oct 12 12:32:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  550. Oct 12 12:32:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  551. Oct 12 12:46:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  552. Oct 12 12:46:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  553. Oct 12 13:00:58 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  554. Oct 12 13:00:58 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  555. Oct 12 13:15:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  556. Oct 12 13:15:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  557. Oct 12 13:29:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  558. Oct 12 13:29:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  559. Oct 12 13:43:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  560. Oct 12 13:43:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  561. Oct 12 13:57:38 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  562. Oct 12 13:57:38 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  563. Oct 12 14:11:47 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  564. Oct 12 14:11:47 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  565. Oct 12 14:25:57 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  566. Oct 12 14:25:57 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  567. Oct 12 14:40:07 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  568. Oct 12 14:40:07 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  569. Oct 12 14:54:17 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  570. Oct 12 14:54:17 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  571. Oct 12 15:08:27 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  572. Oct 12 15:08:27 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  573. Oct 12 15:22:36 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  574. Oct 12 15:22:36 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  575. Oct 12 15:36:46 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  576. Oct 12 15:36:46 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  577. Oct 12 15:50:56 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  578. Oct 12 15:50:56 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  579. Oct 12 16:05:06 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  580. Oct 12 16:05:06 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  581. Oct 12 16:19:15 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  582. Oct 12 16:19:15 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  583. Oct 12 16:33:25 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  584. Oct 12 16:33:25 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  585. Oct 12 16:47:35 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  586. Oct 12 16:47:35 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  587. Oct 12 17:01:45 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  588. Oct 12 17:01:45 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  589. Oct 12 17:15:55 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  590. Oct 12 17:15:55 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  591. Oct 12 17:30:04 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  592. Oct 12 17:30:04 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  593. Oct 12 17:44:14 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  594. Oct 12 17:44:14 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  595. Oct 12 17:58:24 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  596. Oct 12 17:58:24 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  597. Oct 12 18:12:34 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  598. Oct 12 18:12:34 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  599. Oct 12 18:26:43 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  600. Oct 12 18:26:43 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  601. Oct 12 18:40:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  602. Oct 12 18:40:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  603. Oct 12 18:55:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  604. Oct 12 18:55:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  605. Oct 12 19:09:13 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  606. Oct 12 19:09:13 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  607. Oct 12 19:23:23 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  608. Oct 12 19:23:23 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  609. Oct 12 19:37:33 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  610. Oct 12 19:37:33 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  611. Oct 12 19:51:43 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  612. Oct 12 19:51:43 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  613. Oct 12 20:05:53 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  614. Oct 12 20:05:53 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  615. Oct 12 20:20:03 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  616. Oct 12 20:20:03 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  617. Oct 12 20:34:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  618. Oct 12 20:34:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  619. Oct 12 20:48:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  620. Oct 12 20:48:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  621. Oct 12 21:02:32 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  622. Oct 12 21:02:32 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  623. Oct 12 21:16:42 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  624. Oct 12 21:16:42 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  625. Oct 12 21:30:52 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  626. Oct 12 21:30:52 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  627. Oct 12 21:45:02 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  628. Oct 12 21:45:02 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  629. Oct 12 21:59:12 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  630. Oct 12 21:59:12 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  631. Oct 12 22:13:22 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  632. Oct 12 22:13:22 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  633. Oct 12 22:27:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  634. Oct 12 22:27:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  635. Oct 12 22:41:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  636. Oct 12 22:41:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  637. Oct 12 22:55:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  638. Oct 12 22:55:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  639. Oct 12 23:10:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  640. Oct 12 23:10:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  641. Oct 12 23:24:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  642. Oct 12 23:24:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  643. Oct 12 23:38:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  644. Oct 12 23:38:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  645. Oct 12 23:52:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  646. Oct 12 23:52:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  647. Oct 13 00:06:40 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  648. Oct 13 00:06:40 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  649. Oct 13 00:20:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  650. Oct 13 00:20:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  651. Oct 13 00:35:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  652. Oct 13 00:35:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  653. Oct 13 00:49:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  654. Oct 13 00:49:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  655. Oct 13 01:03:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  656. Oct 13 01:03:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  657. Oct 13 01:17:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  658. Oct 13 01:17:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  659. Oct 13 01:31:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  660. Oct 13 01:31:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  661. Oct 13 01:45:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  662. Oct 13 01:45:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  663. Oct 13 01:59:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  664. Oct 13 01:59:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  665. Oct 13 02:14:09 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  666. Oct 13 02:14:09 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  667. Oct 13 02:15:15 pve1 corosync[1596]: [TOTEM ] Retransmit List: 4ff8c
  668. Oct 13 02:28:20 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  669. Oct 13 02:28:20 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  670. Oct 13 02:42:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  671. Oct 13 02:42:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  672. Oct 13 02:56:40 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  673. Oct 13 02:56:40 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  674. Oct 13 03:10:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  675. Oct 13 03:10:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  676. Oct 13 03:25:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  677. Oct 13 03:25:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  678. Oct 13 03:39:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  679. Oct 13 03:39:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  680. Oct 13 03:53:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  681. Oct 13 03:53:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  682. Oct 13 04:07:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  683. Oct 13 04:07:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  684. Oct 13 04:21:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  685. Oct 13 04:21:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  686. Oct 13 04:35:51 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  687. Oct 13 04:35:51 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  688. Oct 13 04:50:01 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  689. Oct 13 04:50:01 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  690. Oct 13 05:04:11 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  691. Oct 13 05:04:11 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  692. Oct 13 05:18:21 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  693. Oct 13 05:18:21 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  694. Oct 13 05:32:31 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  695. Oct 13 05:32:31 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  696. Oct 13 05:46:41 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  697. Oct 13 05:46:41 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  698. Oct 13 06:00:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  699. Oct 13 06:00:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  700. Oct 13 06:15:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  701. Oct 13 06:15:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  702. Oct 13 06:29:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  703. Oct 13 06:29:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  704. Oct 13 06:43:20 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  705. Oct 13 06:43:20 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  706. Oct 13 06:57:30 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  707. Oct 13 06:57:30 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  708. Oct 13 07:11:40 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  709. Oct 13 07:11:40 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  710. Oct 13 07:25:50 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  711. Oct 13 07:25:50 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  712. Oct 13 07:40:00 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  713. Oct 13 07:40:00 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  714. Oct 13 07:54:10 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  715. Oct 13 07:54:10 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  716. Oct 13 08:08:20 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  717. Oct 13 08:08:20 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  718. Oct 13 08:22:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  719. Oct 13 08:22:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  720. Oct 13 08:36:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  721. Oct 13 08:36:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  722. Oct 13 08:50:49 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  723. Oct 13 08:50:49 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  724. Oct 13 09:04:59 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  725. Oct 13 09:04:59 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  726. Oct 13 09:19:09 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  727. Oct 13 09:19:09 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  728. Oct 13 09:33:19 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  729. Oct 13 09:33:19 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  730. Oct 13 09:47:29 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  731. Oct 13 09:47:29 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  732. Oct 13 10:01:39 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  733. Oct 13 10:01:39 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  734. Oct 13 10:15:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  735. Oct 13 10:15:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  736. Oct 13 10:29:58 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  737. Oct 13 10:29:58 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  738. Oct 13 10:44:08 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  739. Oct 13 10:44:08 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  740. Oct 13 10:58:18 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  741. Oct 13 10:58:18 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  742. Oct 13 11:12:28 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  743. Oct 13 11:12:28 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  744. Oct 13 11:26:38 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  745. Oct 13 11:26:38 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  746. Oct 13 11:40:48 pve1 corosync[1596]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  747. Oct 13 11:40:48 pve1 corosync[1596]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  748. Oct 13 11:46:12 pve1 corosync[1596]: [KNET ] link: host: 3 link: 0 is down
  749. Oct 13 11:46:12 pve1 corosync[1596]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  750. Oct 13 11:46:12 pve1 corosync[1596]: [KNET ] host: host: 3 has no active links
  751. Oct 13 11:46:13 pve1 corosync[1596]: [KNET ] pmtud: Global data MTU changed to: 1397
  752. Oct 13 11:46:13 pve1 corosync[1596]: [TOTEM ] Token has not been received in 3225 ms
  753. Oct 13 11:46:14 pve1 corosync[1596]: [TOTEM ] A processor failed, forming new configuration: token timed out (4300ms), waiting 5160ms for consensus.
  754. Oct 13 11:46:19 pve1 corosync[1596]: [QUORUM] Sync members[3]: 1 2 4
  755. Oct 13 11:46:19 pve1 corosync[1596]: [QUORUM] Sync left[1]: 3
  756. Oct 13 11:46:19 pve1 corosync[1596]: [TOTEM ] A new membership (1.19f29) was formed. Members left: 3
  757. Oct 13 11:46:19 pve1 corosync[1596]: [TOTEM ] Failed to receive the leave message. failed: 3
  758. Oct 13 11:46:19 pve1 corosync[1596]: [QUORUM] Members[3]: 1 2 4
  759. Oct 13 11:46:19 pve1 corosync[1596]: [MAIN ] Completed service synchronization, ready to provide service.
  760. Oct 13 11:50:10 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  761. Oct 13 11:50:11 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  762. Oct 13 11:50:12 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  763. Oct 13 11:50:13 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  764. Oct 13 11:50:15 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  765. [...]
  766. Oct 13 18:48:54 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  767. Oct 13 18:48:55 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  768. Oct 13 18:48:56 pve1 corosync[1596]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE4:5405
  769. Oct 13 18:49:02 pve1 systemd[1]: Stopping corosync.service - Corosync Cluster Engine...
  770. Oct 13 18:49:02 pve1 corosync-cfgtool[3894001]: Shutting down corosync
  771. Oct 13 18:49:02 pve1 corosync[1596]: [MAIN ] Node was shut down by a signal
  772. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Unloading all Corosync service engines.
  773. Oct 13 18:49:02 pve1 corosync[1596]: [QB ] withdrawing server sockets
  774. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync vote quorum service v1.0
  775. Oct 13 18:49:02 pve1 corosync[1596]: [CFG ] Node 4 was shut down by sysadmin
  776. Oct 13 18:49:02 pve1 corosync[1596]: [QB ] withdrawing server sockets
  777. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync configuration map access
  778. Oct 13 18:49:02 pve1 corosync[1596]: [QB ] withdrawing server sockets
  779. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync configuration service
  780. Oct 13 18:49:02 pve1 corosync[1596]: [QB ] withdrawing server sockets
  781. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync cluster closed process group service v1.01
  782. Oct 13 18:49:02 pve1 corosync[1596]: [QB ] withdrawing server sockets
  783. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync cluster quorum service v0.1
  784. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync profile loading service
  785. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync resource monitoring service
  786. Oct 13 18:49:02 pve1 corosync[1596]: [SERV ] Service engine unloaded: corosync watchdog service
  787. Oct 13 18:49:03 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  788. Oct 13 18:49:03 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  789. Oct 13 18:49:03 pve1 corosync[1596]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  790. Oct 13 18:49:03 pve1 corosync[1596]: [MAIN ] Corosync Cluster Engine exiting normally
  791. Oct 13 18:49:03 pve1 systemd[1]: corosync.service: Deactivated successfully.
  792. Oct 13 18:49:03 pve1 systemd[1]: Stopped corosync.service - Corosync Cluster Engine.
  793. Oct 13 18:49:03 pve1 systemd[1]: corosync.service: Consumed 2h 23min 55.786s CPU time.
  794. Oct 13 18:49:18 pve1 systemd[1]: Starting corosync.service - Corosync Cluster Engine...
  795. Oct 13 18:49:18 pve1 corosync[3894011]: [MAIN ] Corosync Cluster Engine starting up
  796. Oct 13 18:49:18 pve1 corosync[3894011]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vqsim nozzle snmp pie relro bindnow
  797. Oct 13 18:49:18 pve1 corosync[3894011]: [TOTEM ] Initializing transport (Kronosnet).
  798. Oct 13 18:49:19 pve1 corosync[3894011]: [TOTEM ] totemknet initialized
  799. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] pmtud: MTU manually set to: 0
  800. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
  801. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync configuration map access [0]
  802. Oct 13 18:49:19 pve1 corosync[3894011]: [QB ] server name: cmap
  803. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync configuration service [1]
  804. Oct 13 18:49:19 pve1 corosync[3894011]: [QB ] server name: cfg
  805. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
  806. Oct 13 18:49:19 pve1 corosync[3894011]: [QB ] server name: cpg
  807. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync profile loading service [4]
  808. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
  809. Oct 13 18:49:19 pve1 corosync[3894011]: [WD ] Watchdog not enabled by configuration
  810. Oct 13 18:49:19 pve1 corosync[3894011]: [WD ] resource load_15min missing a recovery key.
  811. Oct 13 18:49:19 pve1 corosync[3894011]: [WD ] resource memory_used missing a recovery key.
  812. Oct 13 18:49:19 pve1 corosync[3894011]: [WD ] no resources configured.
  813. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync watchdog service [7]
  814. Oct 13 18:49:19 pve1 corosync[3894011]: [QUORUM] Using quorum provider corosync_votequorum
  815. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
  816. Oct 13 18:49:19 pve1 corosync[3894011]: [QB ] server name: votequorum
  817. Oct 13 18:49:19 pve1 corosync[3894011]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
  818. Oct 13 18:49:19 pve1 corosync[3894011]: [QB ] server name: quorum
  819. Oct 13 18:49:19 pve1 corosync[3894011]: [TOTEM ] Configuring link 0
  820. Oct 13 18:49:19 pve1 corosync[3894011]: [TOTEM ] Configured link number 0: local addr: 10.190.0.4, port=5405
  821. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  822. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  823. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 has no active links
  824. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  825. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 has no active links
  826. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  827. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 2 has no active links
  828. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 0)
  829. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 has no active links
  830. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  831. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 has no active links
  832. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  833. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 1 has no active links
  834. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  835. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 has no active links
  836. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  837. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 has no active links
  838. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  839. Oct 13 18:49:19 pve1 corosync[3894011]: [KNET ] host: host: 3 has no active links
  840. Oct 13 18:49:19 pve1 corosync[3894011]: [QUORUM] Sync members[1]: 4
  841. Oct 13 18:49:19 pve1 corosync[3894011]: [QUORUM] Sync joined[1]: 4
  842. Oct 13 18:49:19 pve1 corosync[3894011]: [TOTEM ] A new membership (4.19f2e) was formed. Members joined: 4
  843. Oct 13 18:49:19 pve1 corosync[3894011]: [QUORUM] Members[1]: 4
  844. Oct 13 18:49:19 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  845. Oct 13 18:49:19 pve1 systemd[1]: Started corosync.service - Corosync Cluster Engine.
  846. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] rx: host: 2 link: 0 is up
  847. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  848. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] rx: host: 1 link: 0 is up
  849. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  850. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  851. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  852. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] rx: host: 3 link: 0 is up
  853. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  854. Oct 13 18:49:21 pve1 corosync[3894011]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
  855. Oct 13 18:49:21 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  856. Oct 13 18:49:21 pve1 corosync[3894011]: [QUORUM] Sync joined[2]: 1 2
  857. Oct 13 18:49:21 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f32) was formed. Members joined: 1 2
  858. Oct 13 18:49:21 pve1 corosync[3894011]: [QUORUM] This node is within the primary component and will provide service.
  859. Oct 13 18:49:21 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  860. Oct 13 18:49:21 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  861. Oct 13 18:49:27 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  862. Oct 13 18:49:27 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f36) was formed. Members
  863. Oct 13 18:49:32 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  864. Oct 13 18:49:32 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f3a) was formed. Members
  865. Oct 13 18:49:37 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  866. Oct 13 18:49:37 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f3e) was formed. Members
  867. Oct 13 18:49:42 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  868. Oct 13 18:49:42 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f42) was formed. Members
  869. Oct 13 18:49:47 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  870. Oct 13 18:49:47 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f46) was formed. Members
  871. Oct 13 18:49:52 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  872. Oct 13 18:49:52 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f4a) was formed. Members
  873. Oct 13 18:49:58 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  874. Oct 13 18:49:58 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f4e) was formed. Members
  875. Oct 13 18:50:03 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  876. Oct 13 18:50:03 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f52) was formed. Members
  877. Oct 13 18:50:08 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  878. Oct 13 18:50:08 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f56) was formed. Members
  879. Oct 13 18:50:13 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  880. Oct 13 18:50:13 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f5a) was formed. Members
  881. Oct 13 18:50:18 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  882. Oct 13 18:50:18 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f5e) was formed. Members
  883. Oct 13 18:50:23 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  884. Oct 13 18:50:23 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f62) was formed. Members
  885. Oct 13 18:50:29 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  886. Oct 13 18:50:29 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f66) was formed. Members
  887. Oct 13 18:50:34 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  888. Oct 13 18:50:34 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f6a) was formed. Members
  889. Oct 13 18:50:39 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  890. Oct 13 18:50:39 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f6e) was formed. Members
  891. Oct 13 18:50:44 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  892. Oct 13 18:50:44 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f72) was formed. Members
  893. Oct 13 18:50:49 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  894. Oct 13 18:50:49 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f76) was formed. Members
  895. Oct 13 18:50:54 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  896. Oct 13 18:50:54 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f7a) was formed. Members
  897. Oct 13 18:51:00 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  898. Oct 13 18:51:00 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f7e) was formed. Members
  899. Oct 13 18:51:05 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  900. Oct 13 18:51:05 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f82) was formed. Members
  901. Oct 13 18:51:10 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  902. Oct 13 18:51:10 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f86) was formed. Members
  903. Oct 13 18:51:15 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  904. Oct 13 18:51:15 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f8a) was formed. Members
  905. Oct 13 18:51:20 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  906. Oct 13 18:51:20 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f8e) was formed. Members
  907. Oct 13 18:51:26 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  908. Oct 13 18:51:26 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f92) was formed. Members
  909. Oct 13 18:51:31 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  910. Oct 13 18:51:31 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f96) was formed. Members
  911. Oct 13 18:51:36 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  912. Oct 13 18:51:36 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f9a) was formed. Members
  913. Oct 13 18:51:41 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  914. Oct 13 18:51:41 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19f9e) was formed. Members
  915. Oct 13 18:51:46 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  916. Oct 13 18:51:46 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fa2) was formed. Members
  917. Oct 13 18:51:51 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  918. Oct 13 18:51:51 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fa6) was formed. Members
  919. Oct 13 18:51:57 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  920. Oct 13 18:51:57 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19faa) was formed. Members
  921. Oct 13 18:52:02 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  922. Oct 13 18:52:02 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fae) was formed. Members
  923. Oct 13 18:52:07 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  924. Oct 13 18:52:07 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fb2) was formed. Members
  925. Oct 13 18:52:12 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  926. Oct 13 18:52:12 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fb6) was formed. Members
  927. Oct 13 18:52:17 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  928. Oct 13 18:52:17 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fba) was formed. Members
  929. Oct 13 18:52:22 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  930. Oct 13 18:52:22 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fbe) was formed. Members
  931. Oct 13 18:52:22 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  932. Oct 13 18:52:22 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  933. Oct 13 18:52:33 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  934. Oct 13 18:52:33 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fc2) was formed. Members
  935. Oct 13 18:52:38 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  936. Oct 13 18:52:38 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fc6) was formed. Members
  937. Oct 13 18:52:43 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  938. Oct 13 18:52:43 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fca) was formed. Members
  939. Oct 13 18:52:48 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  940. Oct 13 18:52:48 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fce) was formed. Members
  941. Oct 13 18:52:53 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  942. Oct 13 18:52:53 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fd2) was formed. Members
  943. Oct 13 18:52:59 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  944. Oct 13 18:52:59 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fd6) was formed. Members
  945. Oct 13 18:53:04 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  946. Oct 13 18:53:04 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fda) was formed. Members
  947. Oct 13 18:53:04 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  948. Oct 13 18:53:04 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  949. Oct 13 18:53:14 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  950. Oct 13 18:53:14 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fde) was formed. Members
  951. Oct 13 18:53:19 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  952. Oct 13 18:53:19 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fe2) was formed. Members
  953. Oct 13 18:53:24 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  954. Oct 13 18:53:24 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fe6) was formed. Members
  955. Oct 13 18:53:30 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  956. Oct 13 18:53:30 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fea) was formed. Members
  957. Oct 13 18:53:35 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  958. Oct 13 18:53:35 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19fee) was formed. Members
  959. Oct 13 18:53:40 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  960. Oct 13 18:53:40 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19ff2) was formed. Members
  961. Oct 13 18:53:45 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  962. Oct 13 18:53:45 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19ff6) was formed. Members
  963. Oct 13 18:53:50 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  964. Oct 13 18:53:50 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19ffa) was formed. Members
  965. Oct 13 18:53:55 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  966. Oct 13 18:53:55 pve1 corosync[3894011]: [TOTEM ] A new membership (1.19ffe) was formed. Members
  967. Oct 13 18:54:01 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  968. Oct 13 18:54:01 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a002) was formed. Members
  969. Oct 13 18:54:06 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  970. Oct 13 18:54:06 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a006) was formed. Members
  971. Oct 13 18:54:11 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  972. Oct 13 18:54:11 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a00a) was formed. Members
  973. Oct 13 18:54:16 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  974. Oct 13 18:54:16 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a00e) was formed. Members
  975. Oct 13 18:54:21 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  976. Oct 13 18:54:21 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a012) was formed. Members
  977. Oct 13 18:54:27 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  978. Oct 13 18:54:27 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a016) was formed. Members
  979. Oct 13 18:54:32 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  980. Oct 13 18:54:32 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a01a) was formed. Members
  981. Oct 13 18:54:37 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  982. Oct 13 18:54:37 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a01e) was formed. Members
  983. Oct 13 18:54:42 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  984. Oct 13 18:54:42 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a022) was formed. Members
  985. Oct 13 18:54:47 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  986. Oct 13 18:54:47 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a026) was formed. Members
  987. Oct 13 18:54:52 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  988. Oct 13 18:54:52 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a02a) was formed. Members
  989. Oct 13 18:54:58 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  990. Oct 13 18:54:58 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a02e) was formed. Members
  991. Oct 13 18:55:03 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  992. Oct 13 18:55:03 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a032) was formed. Members
  993. Oct 13 18:55:08 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  994. Oct 13 18:55:08 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a036) was formed. Members
  995. Oct 13 18:55:13 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  996. Oct 13 18:55:13 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a03a) was formed. Members
  997. Oct 13 18:55:18 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  998. Oct 13 18:55:18 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a03e) was formed. Members
  999. Oct 13 18:55:23 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1000. Oct 13 18:55:23 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a042) was formed. Members
  1001. Oct 13 18:55:29 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1002. Oct 13 18:55:29 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a046) was formed. Members
  1003. Oct 13 18:55:34 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1004. Oct 13 18:55:34 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a04a) was formed. Members
  1005. Oct 13 18:55:39 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1006. Oct 13 18:55:39 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a04e) was formed. Members
  1007. Oct 13 18:55:44 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1008. Oct 13 18:55:44 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a052) was formed. Members
  1009. Oct 13 18:55:49 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1010. Oct 13 18:55:49 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a056) was formed. Members
  1011. Oct 13 18:55:55 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1012. Oct 13 18:55:55 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a05a) was formed. Members
  1013. Oct 13 18:56:00 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1014. Oct 13 18:56:00 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a05e) was formed. Members
  1015. Oct 13 18:56:05 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1016. Oct 13 18:56:05 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a062) was formed. Members
  1017. Oct 13 18:56:10 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1018. Oct 13 18:56:10 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a066) was formed. Members
  1019. Oct 13 18:56:15 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1020. Oct 13 18:56:15 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a06a) was formed. Members
  1021. Oct 13 18:56:20 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1022. Oct 13 18:56:20 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a06e) was formed. Members
  1023. Oct 13 18:56:26 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1024. Oct 13 18:56:26 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a072) was formed. Members
  1025. Oct 13 18:56:31 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1026. Oct 13 18:56:31 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a076) was formed. Members
  1027. Oct 13 18:56:36 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1028. Oct 13 18:56:36 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a07a) was formed. Members
  1029. Oct 13 18:56:41 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1030. Oct 13 18:56:41 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a07e) was formed. Members
  1031. Oct 13 18:56:46 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1032. Oct 13 18:56:46 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a082) was formed. Members
  1033. Oct 13 18:56:51 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1034. Oct 13 18:56:51 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a086) was formed. Members
  1035. Oct 13 18:56:57 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1036. Oct 13 18:56:57 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a08a) was formed. Members
  1037. Oct 13 18:57:02 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1038. Oct 13 18:57:02 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a08e) was formed. Members
  1039. Oct 13 18:57:07 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1040. Oct 13 18:57:07 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a092) was formed. Members
  1041. Oct 13 18:57:12 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1042. Oct 13 18:57:12 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a096) was formed. Members
  1043. Oct 13 18:57:17 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1044. Oct 13 18:57:17 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a09a) was formed. Members
  1045. Oct 13 18:57:23 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1046. Oct 13 18:57:23 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a09e) was formed. Members
  1047. Oct 13 18:57:28 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1048. Oct 13 18:57:28 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0a2) was formed. Members
  1049. Oct 13 18:57:33 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1050. Oct 13 18:57:33 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0a6) was formed. Members
  1051. Oct 13 18:57:33 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1052. Oct 13 18:57:33 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1053. Oct 13 18:57:43 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1054. Oct 13 18:57:43 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0aa) was formed. Members
  1055. Oct 13 18:57:48 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1056. Oct 13 18:57:48 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ae) was formed. Members
  1057. Oct 13 18:57:54 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1058. Oct 13 18:57:54 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0b2) was formed. Members
  1059. Oct 13 18:57:59 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1060. Oct 13 18:57:59 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0b6) was formed. Members
  1061. Oct 13 18:58:04 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1062. Oct 13 18:58:04 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ba) was formed. Members
  1063. Oct 13 18:58:09 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1064. Oct 13 18:58:09 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0be) was formed. Members
  1065. Oct 13 18:58:14 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1066. Oct 13 18:58:14 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0c2) was formed. Members
  1067. Oct 13 18:58:19 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1068. Oct 13 18:58:19 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0c6) was formed. Members
  1069. Oct 13 18:58:25 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1070. Oct 13 18:58:25 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ca) was formed. Members
  1071. Oct 13 18:58:30 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1072. Oct 13 18:58:30 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ce) was formed. Members
  1073. Oct 13 18:58:35 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1074. Oct 13 18:58:35 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0d2) was formed. Members
  1075. Oct 13 18:58:40 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1076. Oct 13 18:58:40 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0d6) was formed. Members
  1077. Oct 13 18:58:45 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1078. Oct 13 18:58:45 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0da) was formed. Members
  1079. Oct 13 18:58:50 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1080. Oct 13 18:58:50 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0de) was formed. Members
  1081. Oct 13 18:58:56 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1082. Oct 13 18:58:56 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0e2) was formed. Members
  1083. Oct 13 18:59:00 pve1 corosync[3894011]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  1084. Oct 13 18:59:00 pve1 corosync[3894011]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  1085. Oct 13 18:59:01 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1086. Oct 13 18:59:01 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0e6) was formed. Members
  1087. Oct 13 18:59:01 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1088. Oct 13 18:59:01 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ea) was formed. Members
  1089. Oct 13 18:59:01 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1090. Oct 13 18:59:01 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1091. Oct 13 18:59:11 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1092. Oct 13 18:59:11 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0ee) was formed. Members
  1093. Oct 13 18:59:16 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1094. Oct 13 18:59:16 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0f2) was formed. Members
  1095. Oct 13 18:59:22 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1096. Oct 13 18:59:22 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0f6) was formed. Members
  1097. Oct 13 18:59:27 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1098. Oct 13 18:59:27 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0fa) was formed. Members
  1099. Oct 13 18:59:32 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1100. Oct 13 18:59:32 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a0fe) was formed. Members
  1101. Oct 13 18:59:37 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1102. Oct 13 18:59:37 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a102) was formed. Members
  1103. Oct 13 18:59:42 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1104. Oct 13 18:59:42 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a106) was formed. Members
  1105. Oct 13 18:59:47 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1106. Oct 13 18:59:47 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a10a) was formed. Members
  1107. Oct 13 18:59:53 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1108. Oct 13 18:59:53 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a10e) was formed. Members
  1109. Oct 13 18:59:58 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1110. Oct 13 18:59:58 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a112) was formed. Members
  1111. Oct 13 19:00:03 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1112. Oct 13 19:00:03 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a116) was formed. Members
  1113. Oct 13 19:00:08 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1114. Oct 13 19:00:08 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a11a) was formed. Members
  1115. Oct 13 19:00:13 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1116. Oct 13 19:00:13 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a11e) was formed. Members
  1117. Oct 13 19:00:13 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1118. Oct 13 19:00:13 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a122) was formed. Members
  1119. Oct 13 19:00:13 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1120. Oct 13 19:00:13 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1121. Oct 13 19:00:24 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1122. Oct 13 19:00:24 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a126) was formed. Members
  1123. Oct 13 19:00:29 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1124. Oct 13 19:00:29 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a12a) was formed. Members
  1125. Oct 13 19:00:34 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1126. Oct 13 19:00:34 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a12e) was formed. Members
  1127. Oct 13 19:00:39 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1128. Oct 13 19:00:39 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a132) was formed. Members
  1129. Oct 13 19:00:44 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1130. Oct 13 19:00:44 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a136) was formed. Members
  1131. Oct 13 19:00:49 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1132. Oct 13 19:00:49 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a13a) was formed. Members
  1133. Oct 13 19:00:55 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1134. Oct 13 19:00:55 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a13e) was formed. Members
  1135. Oct 13 19:01:00 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1136. Oct 13 19:01:00 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a142) was formed. Members
  1137. Oct 13 19:01:05 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1138. Oct 13 19:01:05 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a146) was formed. Members
  1139. Oct 13 19:01:10 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1140. Oct 13 19:01:10 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a14a) was formed. Members
  1141. Oct 13 19:01:15 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1142. Oct 13 19:01:15 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a14e) was formed. Members
  1143. Oct 13 19:01:20 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1144. Oct 13 19:01:20 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a152) was formed. Members
  1145. Oct 13 19:01:26 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1146. Oct 13 19:01:26 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a156) was formed. Members
  1147. Oct 13 19:01:31 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1148. Oct 13 19:01:31 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a15a) was formed. Members
  1149. Oct 13 19:01:36 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1150. Oct 13 19:01:36 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a15e) was formed. Members
  1151. Oct 13 19:01:41 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1152. Oct 13 19:01:41 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a162) was formed. Members
  1153. Oct 13 19:01:46 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1154. Oct 13 19:01:46 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a166) was formed. Members
  1155. Oct 13 19:01:51 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1156. Oct 13 19:01:51 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a16a) was formed. Members
  1157. Oct 13 19:01:57 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1158. Oct 13 19:01:57 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a16e) was formed. Members
  1159. Oct 13 19:02:02 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1160. Oct 13 19:02:02 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a172) was formed. Members
  1161. Oct 13 19:02:07 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1162. Oct 13 19:02:07 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a176) was formed. Members
  1163. Oct 13 19:02:12 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1164. Oct 13 19:02:12 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a17a) was formed. Members
  1165. Oct 13 19:02:17 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1166. Oct 13 19:02:17 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a17e) was formed. Members
  1167. Oct 13 19:02:23 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1168. Oct 13 19:02:23 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a182) was formed. Members
  1169. Oct 13 19:02:28 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1170. Oct 13 19:02:28 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a186) was formed. Members
  1171. Oct 13 19:02:33 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1172. Oct 13 19:02:33 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a18a) was formed. Members
  1173. Oct 13 19:02:38 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1174. Oct 13 19:02:38 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a18e) was formed. Members
  1175. Oct 13 19:02:43 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1176. Oct 13 19:02:43 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a192) was formed. Members
  1177. Oct 13 19:02:48 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1178. Oct 13 19:02:48 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a196) was formed. Members
  1179. Oct 13 19:02:54 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1180. Oct 13 19:02:54 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a19a) was formed. Members
  1181. Oct 13 19:02:59 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1182. Oct 13 19:02:59 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a19e) was formed. Members
  1183. Oct 13 19:03:04 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1184. Oct 13 19:03:04 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1a2) was formed. Members
  1185. Oct 13 19:03:09 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1186. Oct 13 19:03:09 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1a6) was formed. Members
  1187. Oct 13 19:03:14 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1188. Oct 13 19:03:14 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1aa) was formed. Members
  1189. Oct 13 19:03:19 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1190. Oct 13 19:03:19 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ae) was formed. Members
  1191. Oct 13 19:03:25 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1192. Oct 13 19:03:25 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1b2) was formed. Members
  1193. Oct 13 19:03:30 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1194. Oct 13 19:03:30 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1b6) was formed. Members
  1195. Oct 13 19:03:35 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1196. Oct 13 19:03:35 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ba) was formed. Members
  1197. Oct 13 19:03:35 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1198. Oct 13 19:03:35 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1199. Oct 13 19:03:36 pve1 corosync[3894011]: [KNET ] pmtud: PMTUD link change for host: 3 link: 0 from 469 to 1349
  1200. Oct 13 19:03:36 pve1 corosync[3894011]: [KNET ] pmtud: PMTUD link change for host: 1 link: 0 from 469 to 1397
  1201. Oct 13 19:03:36 pve1 corosync[3894011]: [KNET ] pmtud: PMTUD link change for host: 2 link: 0 from 469 to 1397
  1202. Oct 13 19:03:36 pve1 corosync[3894011]: [KNET ] pmtud: Global data MTU changed to: 1349
  1203. Oct 13 19:03:45 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1204. Oct 13 19:03:45 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1be) was formed. Members
  1205. Oct 13 19:03:50 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1206. Oct 13 19:03:50 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1c2) was formed. Members
  1207. Oct 13 19:03:56 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1208. Oct 13 19:03:56 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1c6) was formed. Members
  1209. Oct 13 19:04:01 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1210. Oct 13 19:04:01 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ca) was formed. Members
  1211. Oct 13 19:04:06 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1212. Oct 13 19:04:06 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ce) was formed. Members
  1213. Oct 13 19:04:11 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1214. Oct 13 19:04:11 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1d2) was formed. Members
  1215. Oct 13 19:04:16 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1216. Oct 13 19:04:16 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1d6) was formed. Members
  1217. Oct 13 19:04:22 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1218. Oct 13 19:04:22 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1da) was formed. Members
  1219. Oct 13 19:04:27 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1220. Oct 13 19:04:27 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1de) was formed. Members
  1221. Oct 13 19:04:32 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1222. Oct 13 19:04:32 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1e2) was formed. Members
  1223. Oct 13 19:04:37 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1224. Oct 13 19:04:37 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1e6) was formed. Members
  1225. Oct 13 19:04:42 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1226. Oct 13 19:04:42 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ea) was formed. Members
  1227. Oct 13 19:04:47 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1228. Oct 13 19:04:47 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1ee) was formed. Members
  1229. Oct 13 19:04:53 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1230. Oct 13 19:04:53 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1f2) was formed. Members
  1231. Oct 13 19:04:58 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1232. Oct 13 19:04:58 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1f6) was formed. Members
  1233. Oct 13 19:05:03 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1234. Oct 13 19:05:03 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1fa) was formed. Members
  1235. Oct 13 19:05:08 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1236. Oct 13 19:05:08 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a1fe) was formed. Members
  1237. Oct 13 19:05:13 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1238. Oct 13 19:05:13 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a202) was formed. Members
  1239. Oct 13 19:05:19 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1240. Oct 13 19:05:19 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a206) was formed. Members
  1241. Oct 13 19:05:24 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1242. Oct 13 19:05:24 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a20a) was formed. Members
  1243. Oct 13 19:05:24 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1244. Oct 13 19:05:24 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1245. Oct 13 19:05:34 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1246. Oct 13 19:05:34 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a20e) was formed. Members
  1247. Oct 13 19:05:39 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1248. Oct 13 19:05:39 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a212) was formed. Members
  1249. Oct 13 19:05:44 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1250. Oct 13 19:05:44 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a216) was formed. Members
  1251. Oct 13 19:05:50 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1252. Oct 13 19:05:50 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a21a) was formed. Members
  1253. Oct 13 19:05:55 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1254. Oct 13 19:05:55 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a21e) was formed. Members
  1255. Oct 13 19:06:00 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1256. Oct 13 19:06:00 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a222) was formed. Members
  1257. Oct 13 19:06:05 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1258. Oct 13 19:06:05 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a226) was formed. Members
  1259. Oct 13 19:06:10 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1260. Oct 13 19:06:10 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a22a) was formed. Members
  1261. Oct 13 19:06:16 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1262. Oct 13 19:06:16 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a22e) was formed. Members
  1263. Oct 13 19:06:21 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1264. Oct 13 19:06:21 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a232) was formed. Members
  1265. Oct 13 19:06:26 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1266. Oct 13 19:06:26 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a236) was formed. Members
  1267. Oct 13 19:06:31 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1268. Oct 13 19:06:31 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a23a) was formed. Members
  1269. Oct 13 19:06:36 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1270. Oct 13 19:06:36 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a23e) was formed. Members
  1271. Oct 13 19:06:41 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1272. Oct 13 19:06:41 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a242) was formed. Members
  1273. Oct 13 19:06:47 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1274. Oct 13 19:06:47 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a246) was formed. Members
  1275. Oct 13 19:06:52 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1276. Oct 13 19:06:52 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a24a) was formed. Members
  1277. Oct 13 19:06:57 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1278. Oct 13 19:06:57 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a24e) was formed. Members
  1279. Oct 13 19:07:02 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1280. Oct 13 19:07:02 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a252) was formed. Members
  1281. Oct 13 19:07:07 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1282. Oct 13 19:07:07 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a256) was formed. Members
  1283. Oct 13 19:07:12 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1284. Oct 13 19:07:12 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a25a) was formed. Members
  1285. Oct 13 19:07:18 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1286. Oct 13 19:07:18 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a25e) was formed. Members
  1287. Oct 13 19:07:23 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1288. Oct 13 19:07:23 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a262) was formed. Members
  1289. Oct 13 19:07:28 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1290. Oct 13 19:07:28 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a266) was formed. Members
  1291. Oct 13 19:07:33 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1292. Oct 13 19:07:33 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a26a) was formed. Members
  1293. Oct 13 19:07:38 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1294. Oct 13 19:07:38 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a26e) was formed. Members
  1295. Oct 13 19:07:44 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1296. Oct 13 19:07:44 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a272) was formed. Members
  1297. Oct 13 19:07:44 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1298. Oct 13 19:07:44 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1299. Oct 13 19:07:49 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1300. Oct 13 19:07:49 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a276) was formed. Members
  1301. Oct 13 19:07:54 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1302. Oct 13 19:07:54 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a27a) was formed. Members
  1303. Oct 13 19:07:59 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1304. Oct 13 19:07:59 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a27e) was formed. Members
  1305. Oct 13 19:07:59 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1306. Oct 13 19:07:59 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1307. Oct 13 19:08:09 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1308. Oct 13 19:08:09 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a282) was formed. Members
  1309. Oct 13 19:08:15 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1310. Oct 13 19:08:15 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a286) was formed. Members
  1311. Oct 13 19:08:20 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1312. Oct 13 19:08:20 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a28a) was formed. Members
  1313. Oct 13 19:08:25 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1314. Oct 13 19:08:25 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a28e) was formed. Members
  1315. Oct 13 19:08:30 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1316. Oct 13 19:08:30 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a292) was formed. Members
  1317. Oct 13 19:08:35 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1318. Oct 13 19:08:35 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a296) was formed. Members
  1319. Oct 13 19:08:41 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1320. Oct 13 19:08:41 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a29a) was formed. Members
  1321. Oct 13 19:08:42 pve1 corosync[3894011]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 3 link 0 but the other node is not acknowledging packets of this size.
  1322. Oct 13 19:08:42 pve1 corosync[3894011]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  1323. Oct 13 19:08:46 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1324. Oct 13 19:08:46 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a29e) was formed. Members
  1325. Oct 13 19:08:51 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1326. Oct 13 19:08:51 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2a2) was formed. Members
  1327. Oct 13 19:08:56 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1328. Oct 13 19:08:56 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2a6) was formed. Members
  1329. Oct 13 19:09:01 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1330. Oct 13 19:09:01 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2aa) was formed. Members
  1331. Oct 13 19:09:06 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1332. Oct 13 19:09:06 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ae) was formed. Members
  1333. Oct 13 19:09:12 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1334. Oct 13 19:09:12 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2b2) was formed. Members
  1335. Oct 13 19:09:17 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1336. Oct 13 19:09:17 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2b6) was formed. Members
  1337. Oct 13 19:09:22 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1338. Oct 13 19:09:22 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ba) was formed. Members
  1339. Oct 13 19:09:27 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1340. Oct 13 19:09:27 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2be) was formed. Members
  1341. Oct 13 19:09:32 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1342. Oct 13 19:09:32 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2c2) was formed. Members
  1343. Oct 13 19:09:37 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1344. Oct 13 19:09:37 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2c6) was formed. Members
  1345. Oct 13 19:09:43 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1346. Oct 13 19:09:43 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ca) was formed. Members
  1347. Oct 13 19:09:48 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1348. Oct 13 19:09:48 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ce) was formed. Members
  1349. Oct 13 19:09:53 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1350. Oct 13 19:09:53 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2d2) was formed. Members
  1351. Oct 13 19:09:53 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1352. Oct 13 19:09:53 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1353. Oct 13 19:10:03 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1354. Oct 13 19:10:03 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2d6) was formed. Members
  1355. Oct 13 19:10:09 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1356. Oct 13 19:10:09 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2da) was formed. Members
  1357. Oct 13 19:10:09 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1358. Oct 13 19:10:09 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1359. Oct 13 19:10:19 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1360. Oct 13 19:10:19 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2de) was formed. Members
  1361. Oct 13 19:10:24 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1362. Oct 13 19:10:24 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2e2) was formed. Members
  1363. Oct 13 19:10:29 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1364. Oct 13 19:10:29 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2e6) was formed. Members
  1365. Oct 13 19:10:34 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1366. Oct 13 19:10:34 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ea) was formed. Members
  1367. Oct 13 19:10:40 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1368. Oct 13 19:10:40 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2ee) was formed. Members
  1369. Oct 13 19:10:45 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1370. Oct 13 19:10:45 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2f2) was formed. Members
  1371. Oct 13 19:10:50 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1372. Oct 13 19:10:50 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2f6) was formed. Members
  1373. Oct 13 19:10:55 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1374. Oct 13 19:10:55 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2fa) was formed. Members
  1375. Oct 13 19:10:55 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1376. Oct 13 19:10:55 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1377. Oct 13 19:11:05 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1378. Oct 13 19:11:05 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a2fe) was formed. Members
  1379. Oct 13 19:11:05 pve1 corosync[3894011]: [QUORUM] Members[3]: 1 2 4
  1380. Oct 13 19:11:05 pve1 corosync[3894011]: [MAIN ] Completed service synchronization, ready to provide service.
  1381. Oct 13 19:11:16 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1382. Oct 13 19:11:16 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a302) was formed. Members
  1383. Oct 13 19:11:21 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1384. Oct 13 19:11:21 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a306) was formed. Members
  1385. Oct 13 19:11:26 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1386. Oct 13 19:11:26 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a30a) was formed. Members
  1387. Oct 13 19:11:31 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1388. Oct 13 19:11:31 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a30e) was formed. Members
  1389. Oct 13 19:11:36 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1390. Oct 13 19:11:36 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a312) was formed. Members
  1391. Oct 13 19:11:42 pve1 corosync[3894011]: [QUORUM] Sync members[3]: 1 2 4
  1392. Oct 13 19:11:42 pve1 corosync[3894011]: [TOTEM ] A new membership (1.1a316) was formed. Members
Tags: corosync promox
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!