API tools faq
paste
Advertisement
Max13

corosync_pve4_oct.log

Max13
Oct 13th, 2024
37
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 200.75 KB | None | 0 0
raw download clone embed print report
  1. Oct 10 00:08:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  2. Oct 10 00:08:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:22:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  4. Oct 10 00:22:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:35:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  6. Oct 10 00:35:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:49:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  8. Oct 10 00:49:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:03:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  10. Oct 10 01:03:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:16:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  12. Oct 10 01:16:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:30:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  14. Oct 10 01:30:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:44:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  16. Oct 10 01:44:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  18. Oct 10 01:57:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  20. Oct 10 02:11:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  22. Oct 10 02:25:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:38:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  24. Oct 10 02:38:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:52:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  26. Oct 10 02:52:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:06:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  28. Oct 10 03:06:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:19:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  30. Oct 10 03:19:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:33:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  32. Oct 10 03:33:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:47:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  34. Oct 10 03:47:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:00:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  36. Oct 10 04:00:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:14:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  38. Oct 10 04:14:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:28:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  40. Oct 10 04:28:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:41:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  42. Oct 10 04:41:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:55:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  44. Oct 10 04:55:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:09:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  46. Oct 10 05:09:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:22:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  48. Oct 10 05:22:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:36:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  50. Oct 10 05:36:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:50:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  52. Oct 10 05:50:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:03:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  54. Oct 10 06:03:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:17:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  56. Oct 10 06:17:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:31:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  58. Oct 10 06:31:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:44:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  60. Oct 10 06:44:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:58:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  62. Oct 10 06:58:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:11:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  64. Oct 10 07:11:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:25:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  66. Oct 10 07:25:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:39:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  68. Oct 10 07:39:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:52:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  70. Oct 10 07:52:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:06:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  72. Oct 10 08:06:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:20:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  74. Oct 10 08:20:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:33:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  76. Oct 10 08:33:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 08:47:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  78. Oct 10 08:47:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:01:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  80. Oct 10 09:01:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:14:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  82. Oct 10 09:14:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:28:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  84. Oct 10 09:28:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:42:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  86. Oct 10 09:42:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 09:55:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  88. Oct 10 09:55:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:09:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  90. Oct 10 10:09:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:23:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  92. Oct 10 10:23:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:36:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  94. Oct 10 10:36:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 10:50:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  96. Oct 10 10:50:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:04:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  98. Oct 10 11:04:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:17:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  100. Oct 10 11:17:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:31:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  102. Oct 10 11:31:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11:45:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  104. Oct 10 11:45:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  105. Oct 10 11:58:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  106. Oct 10 11:58:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  107. Oct 10 12:12:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  108. Oct 10 12:12:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  109. Oct 10 12:26:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  110. Oct 10 12:26:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:39:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  112. Oct 10 12:39:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  113. Oct 10 12:53:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  114. Oct 10 12:53:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  115. Oct 10 13:07:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  116. Oct 10 13:07:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  117. Oct 10 13:21:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  118. Oct 10 13:21:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  119. Oct 10 13:34:43 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  120. Oct 10 13:34:43 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  121. Oct 10 13:48:23 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  122. Oct 10 13:48:23 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  123. Oct 10 14:02:03 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  124. Oct 10 14:02:03 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  125. Oct 10 14:15:43 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  126. Oct 10 14:15:43 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  127. Oct 10 14:29:23 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  128. Oct 10 14:29:23 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  129. Oct 10 14:43:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  130. Oct 10 14:43:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  131. Oct 10 14:56:45 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  132. Oct 10 14:56:45 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  133. Oct 10 15:10:25 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  134. Oct 10 15:10:25 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  135. Oct 10 15:24:06 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  136. Oct 10 15:24:06 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  137. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  138. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  139. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  140. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  141. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  142. Oct 10 15:27:34 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  143. Oct 10 15:27:36 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  144. Oct 10 15:27:36 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  145. Oct 10 15:27:37 pve4 corosync[864]: [KNET ] rx: host: 4 link: 0 is up
  146. Oct 10 15:27:37 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  147. Oct 10 15:27:37 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  148. Oct 10 15:32:14 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  149. Oct 10 15:32:14 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  150. Oct 10 15:34:44 pve4 corosync[864]: [TOTEM ] Token has not been received in 3225 ms
  151. Oct 10 15:45:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  152. Oct 10 15:45:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 16:01:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  154. Oct 10 16:01:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  155. Oct 10 16:06:34 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  156. Oct 10 16:11:11 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  157. Oct 10 16:11:11 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  158. Oct 10 16:24:52 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  159. Oct 10 16:24:52 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 16:38:34 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  161. Oct 10 16:38:34 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 16:52:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  163. Oct 10 16:52:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:05:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  165. Oct 10 17:05:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 17:19:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  167. Oct 10 17:19:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 17:33:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  169. Oct 10 17:33:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 17:46:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  171. Oct 10 17:46:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:00:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  173. Oct 10 18:00:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 18:14:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  175. Oct 10 18:14:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 18:27:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  177. Oct 10 18:27:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 18:41:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  179. Oct 10 18:41:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 18:55:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  181. Oct 10 18:55:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 19:08:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  183. Oct 10 19:08:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 19:22:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  185. Oct 10 19:22:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 19:36:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  187. Oct 10 19:36:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 19:49:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  189. Oct 10 19:49:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:03:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  191. Oct 10 20:03:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 20:17:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  193. Oct 10 20:17:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 20:30:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  195. Oct 10 20:30:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 20:44:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  197. Oct 10 20:44:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 20:58:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  199. Oct 10 20:58:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 21:11:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  201. Oct 10 21:11:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 21:25:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  203. Oct 10 21:25:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 21:39:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  205. Oct 10 21:39:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 21:52:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  207. Oct 10 21:52:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 22:06:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  209. Oct 10 22:06:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  210. Oct 10 22:20:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  211. Oct 10 22:20:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  212. Oct 10 22:33:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  213. Oct 10 22:33:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  214. Oct 10 22:46:02 pve4 corosync[864]: [TOTEM ] Retransmit List: 286c29
  215. Oct 10 22:47:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  216. Oct 10 22:47:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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:00:27 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  218. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  219. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  220. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  221. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  222. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  223. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  224. Oct 10 23:00:27 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  225. Oct 10 23:00:28 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  226. Oct 10 23:00:28 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  227. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  228. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  229. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  230. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  231. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  232. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  233. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  234. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  235. Oct 10 23:02:59 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  236. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  237. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  238. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  239. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  240. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  241. Oct 10 23:03:00 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  242. Oct 10 23:44:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  243. Oct 10 23:44:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  244. Oct 10 23:57:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  245. Oct 10 23:57:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  246. Oct 11 00:11:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  247. Oct 11 00:11:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  248. Oct 11 00:20:42 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  249. Oct 11 00:25:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  250. Oct 11 00:25:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:38:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  252. Oct 11 00:38:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:52:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  254. Oct 11 00:52:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:06:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  256. Oct 11 01:06:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:19:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  258. Oct 11 01:19:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:33:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  260. Oct 11 01:33:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:47:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  262. Oct 11 01:47:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:00:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  264. Oct 11 02:00:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:14:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  266. Oct 11 02:14:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:28:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  268. Oct 11 02:28:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:41:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  270. Oct 11 02:41:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:55:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  272. Oct 11 02:55:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:09:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  274. Oct 11 03:09:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:22:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  276. Oct 11 03:22:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:36:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  278. Oct 11 03:36:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:50:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  280. Oct 11 03:50:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:03:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  282. Oct 11 04:03:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:17:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  284. Oct 11 04:17:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:31:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  286. Oct 11 04:31:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:44:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  288. Oct 11 04:44:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:58:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  290. Oct 11 04:58:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:00:27 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  292. Oct 11 05:00:27 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  293. Oct 11 05:00:27 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  294. Oct 11 05:00:27 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  295. Oct 11 05:00:27 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  296. Oct 11 05:00:27 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  297. Oct 11 05:00:28 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  298. Oct 11 05:00:28 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  299. Oct 11 05:00:28 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  300. Oct 11 05:00:28 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  301. Oct 11 05:37:11 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  302. Oct 11 05:37:11 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:50:51 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  304. Oct 11 05:50:51 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  305. Oct 11 06:07:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  306. Oct 11 06:07:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  307. Oct 11 06:12:34 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  308. Oct 11 06:17:10 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  309. Oct 11 06:17:10 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:30:50 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  311. Oct 11 06:30:50 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:44:29 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  313. Oct 11 06:44:29 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:58:09 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  315. Oct 11 06:58:09 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:11:49 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  317. Oct 11 07:11:49 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:25:29 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  319. Oct 11 07:25:29 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:39:09 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  321. Oct 11 07:39:09 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:52:49 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  323. Oct 11 07:52:49 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:53:55 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  325. Oct 11 07:53:55 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  326. Oct 11 07:53:55 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  327. Oct 11 07:53:57 pve4 corosync[864]: [KNET ] rx: host: 4 link: 0 is up
  328. Oct 11 07:53:57 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  329. Oct 11 07:53:57 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  330. Oct 11 07:58:34 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  331. Oct 11 07:58:34 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 08:15:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  333. Oct 11 08:15:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 08:24:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  335. Oct 11 08:24:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 08:33:57 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  337. Oct 11 08:38:34 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  338. Oct 11 08:38:34 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  339. Oct 11 08:52:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  340. Oct 11 08:52:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 09:00:21 pve4 corosync[864]: [TOTEM ] Retransmit List: 2af62f
  342. Oct 11 09:05:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  343. Oct 11 09:05:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  344. Oct 11 09:19:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  345. Oct 11 09:19:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  346. Oct 11 09:33:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  347. Oct 11 09:33:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  348. Oct 11 09:46:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  349. Oct 11 09:46:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  350. Oct 11 10:00:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  351. Oct 11 10:00:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  352. Oct 11 10:14:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  353. Oct 11 10:14:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  354. Oct 11 10:27:00 pve4 corosync[864]: [TOTEM ] Retransmit List: 2b51ec
  355. Oct 11 10:27:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  356. Oct 11 10:27:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 10:41:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  358. Oct 11 10:41:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 10:55:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  360. Oct 11 10:55:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11:08:52 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  362. Oct 11 11:08:52 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11:22:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  364. Oct 11 11:22:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11:36:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  366. Oct 11 11:36:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11:49:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  368. Oct 11 11:49:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12:03:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  370. Oct 11 12:03:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12:17:13 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  372. Oct 11 12:17:13 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12:30:53 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  374. Oct 11 12:30:53 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12:44:33 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  376. Oct 11 12:44:33 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12:58:12 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  378. Oct 11 12:58:12 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 13:11:52 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  380. Oct 11 13:11:52 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 13:25:32 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  382. Oct 11 13:25:32 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 13:30:12 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  384. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  385. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  386. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  387. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  388. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  389. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  390. Oct 11 13:30:12 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  391. Oct 11 13:30:13 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  392. Oct 11 13:30:13 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  393. Oct 11 14:11:31 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  394. Oct 11 14:11:31 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 14:25:11 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  396. Oct 11 14:25:11 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 14:38:50 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  398. Oct 11 14:38:50 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 14:47:54 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  400. Oct 11 14:52:30 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  401. Oct 11 14:52:30 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  402. Oct 11 15:06:10 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  403. Oct 11 15:06:10 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  404. Oct 11 15:19:50 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  405. Oct 11 15:19:50 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  406. Oct 11 15:33:30 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  407. Oct 11 15:33:30 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  408. Oct 11 15:47:10 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  409. Oct 11 15:47:10 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  410. Oct 11 16:00:50 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  411. Oct 11 16:00:50 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  412. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  413. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  414. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  415. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  416. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  417. Oct 11 16:05:33 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  418. Oct 11 16:05:34 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  419. Oct 11 16:05:34 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  420. Oct 11 16:05:34 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  421. Oct 11 16:05:34 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  422. Oct 11 16:42:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  423. Oct 11 16:42:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 16:55:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  425. Oct 11 16:55:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 17:09:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  427. Oct 11 17:09:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 17:18:40 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  429. Oct 11 17:23:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  430. Oct 11 17:23:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  431. Oct 11 17:36:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  432. Oct 11 17:36:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  433. Oct 11 17:50:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  434. Oct 11 17:50:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  435. Oct 11 18:04:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  436. Oct 11 18:04:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  437. Oct 11 18:17:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  438. Oct 11 18:17:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  439. Oct 11 18:31:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  440. Oct 11 18:31:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  441. Oct 11 18:45:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  442. Oct 11 18:45:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  443. Oct 11 18:58:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  444. Oct 11 18:58:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  445. Oct 11 19:12:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  446. Oct 11 19:12:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  447. Oct 11 19:26:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  448. Oct 11 19:26:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  449. Oct 11 19:39:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  450. Oct 11 19:39:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  451. Oct 11 19:53:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  452. Oct 11 19:53:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  453. Oct 11 20:07:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  454. Oct 11 20:07:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  455. Oct 11 20:20:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  456. Oct 11 20:20:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  457. Oct 11 20:34:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  458. Oct 11 20:34:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  459. Oct 11 20:48:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  460. Oct 11 20:48:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  461. Oct 11 21:01:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  462. Oct 11 21:01:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  463. Oct 11 21:15:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  464. Oct 11 21:15:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  465. Oct 11 21:29:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  466. Oct 11 21:29:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  467. Oct 11 21:42:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  468. Oct 11 21:42:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  469. Oct 11 21:56:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  470. Oct 11 21:56:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  471. Oct 11 22:00:16 pve4 corosync[864]: [TOTEM ] Retransmit List: 2e30a8
  472. Oct 11 22:00:21 pve4 corosync[864]: [TOTEM ] Token has not been received in 3225 ms
  473. Oct 11 22:00:22 pve4 corosync[864]: [TOTEM ] A processor failed, forming new configuration: token timed out (4300ms), waiting 5160ms for consensus.
  474. Oct 11 22:00:23 pve4 corosync[864]: [QUORUM] Sync members[4]: 1 2 3 4
  475. Oct 11 22:00:23 pve4 corosync[864]: [TOTEM ] A new membership (1.19f21) was formed. Members
  476. Oct 11 22:00:23 pve4 corosync[864]: [QUORUM] Members[4]: 1 2 3 4
  477. Oct 11 22:00:23 pve4 corosync[864]: [MAIN ] Completed service synchronization, ready to provide service.
  478. Oct 11 22:10:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  479. Oct 11 22:10:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 22:15:07 pve4 corosync[864]: [TOTEM ] Retransmit List: f88
  481. Oct 11 22:23:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  482. Oct 11 22:23:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 22:37:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  484. Oct 11 22:37:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 22:51:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  486. Oct 11 22:51:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 23:04:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  488. Oct 11 23:04:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 23:18:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  490. Oct 11 23:18:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 11 23:32:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  492. Oct 11 23:32:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  493. Oct 11 23:45:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  494. Oct 11 23:45:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  495. Oct 11 23:59:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  496. Oct 11 23:59:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:13:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  498. Oct 12 00:13:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:27:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  500. Oct 12 00:27:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:40:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  502. Oct 12 00:40:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 00:54:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  504. Oct 12 00:54:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:08:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  506. Oct 12 01:08:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:21:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  508. Oct 12 01:21:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:35:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  510. Oct 12 01:35:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 01:49:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  512. Oct 12 01:49:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:02:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  514. Oct 12 02:02:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:16:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  516. Oct 12 02:16:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:30:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  518. Oct 12 02:30:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:43:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  520. Oct 12 02:43:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 02:57:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  522. Oct 12 02:57:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:11:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  524. Oct 12 03:11:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:24:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  526. Oct 12 03:24:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:38:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  528. Oct 12 03:38:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 03:52:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  530. Oct 12 03:52:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:05:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  532. Oct 12 04:05:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:19:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  534. Oct 12 04:19:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:33:09 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  536. Oct 12 04:33:09 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 04:46:54 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  538. Oct 12 04:46:54 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:00:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  540. Oct 12 05:00:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:14:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  542. Oct 12 05:14:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:28:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  544. Oct 12 05:28:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:41:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  546. Oct 12 05:41:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 05:55:23 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  548. Oct 12 05:55:23 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:00:14 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  550. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  551. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  552. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  553. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  554. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  555. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  556. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  557. Oct 12 06:00:14 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  558. Oct 12 06:00:15 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  559. Oct 12 06:00:15 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  560. Oct 12 06:00:15 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  561. Oct 12 06:00:15 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  562. Oct 12 06:00:16 pve4 corosync[864]: [KNET ] rx: host: 4 link: 0 is up
  563. Oct 12 06:00:16 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  564. Oct 12 06:00:16 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  565. Oct 12 06:00:18 pve4 corosync[864]: [TOTEM ] Token has not been received in 3225 ms
  566. Oct 12 06:00:19 pve4 corosync[864]: [TOTEM ] A processor failed, forming new configuration: token timed out (4300ms), waiting 5160ms for consensus.
  567. Oct 12 06:00:19 pve4 corosync[864]: [QUORUM] Sync members[4]: 1 2 3 4
  568. Oct 12 06:00:19 pve4 corosync[864]: [TOTEM ] A new membership (1.19f25) was formed. Members
  569. Oct 12 06:00:20 pve4 corosync[864]: [QUORUM] Members[4]: 1 2 3 4
  570. Oct 12 06:00:20 pve4 corosync[864]: [MAIN ] Completed service synchronization, ready to provide service.
  571. Oct 12 06:32:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  572. Oct 12 06:32:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:46:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  574. Oct 12 06:46:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 06:59:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  576. Oct 12 06:59:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 07:08:48 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  578. Oct 12 07:13:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  579. Oct 12 07:13:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  580. Oct 12 07:27:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  581. Oct 12 07:27:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  582. Oct 12 07:40:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  583. Oct 12 07:40:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  584. Oct 12 07:54:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  585. Oct 12 07:54:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  586. Oct 12 08:08:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  587. Oct 12 08:08:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  588. Oct 12 08:21:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  589. Oct 12 08:21:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  590. Oct 12 08:35:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  591. Oct 12 08:35:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  592. Oct 12 08:49:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  593. Oct 12 08:49:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  594. Oct 12 09:02:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  595. Oct 12 09:02:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  596. Oct 12 09:16:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  597. Oct 12 09:16:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  598. Oct 12 09:30:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  599. Oct 12 09:30:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  600. Oct 12 09:43:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  601. Oct 12 09:43:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  602. Oct 12 09:57:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  603. Oct 12 09:57:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  604. Oct 12 10:11:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  605. Oct 12 10:11:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  606. Oct 12 10:24:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  607. Oct 12 10:24:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  608. Oct 12 10:38:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  609. Oct 12 10:38:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  610. Oct 12 10:52:04 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  611. Oct 12 10:52:04 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  612. Oct 12 11:05:44 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  613. Oct 12 11:05:44 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  614. Oct 12 11:19:24 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  615. Oct 12 11:19:24 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  616. Oct 12 11:33:03 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  617. Oct 12 11:33:03 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  618. Oct 12 11:46:43 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  619. Oct 12 11:46:43 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  620. Oct 12 12:00:23 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  621. Oct 12 12:00:23 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  622. Oct 12 12:14:03 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  623. Oct 12 12:14:03 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  624. Oct 12 12:27:43 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  625. Oct 12 12:27:43 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  626. Oct 12 12:41:23 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  627. Oct 12 12:41:23 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  628. Oct 12 12:55:03 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  629. Oct 12 12:55:03 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  630. Oct 12 13:08:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  631. Oct 12 13:08:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  632. Oct 12 13:22:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  633. Oct 12 13:22:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  634. Oct 12 13:36:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  635. Oct 12 13:36:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  636. Oct 12 13:49:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  637. Oct 12 13:49:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  638. Oct 12 14:03:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  639. Oct 12 14:03:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  640. Oct 12 14:17:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  641. Oct 12 14:17:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  642. Oct 12 14:30:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  643. Oct 12 14:30:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  644. Oct 12 14:44:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  645. Oct 12 14:44:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  646. Oct 12 14:58:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  647. Oct 12 14:58:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  648. Oct 12 15:11:42 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  649. Oct 12 15:11:42 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  650. Oct 12 15:25:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  651. Oct 12 15:25:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  652. Oct 12 15:39:02 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  653. Oct 12 15:39:02 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  654. Oct 12 15:52:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  655. Oct 12 15:52:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  656. Oct 12 16:06:22 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  657. Oct 12 16:06:22 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  658. Oct 12 16:20:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  659. Oct 12 16:20:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  660. Oct 12 16:33:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  661. Oct 12 16:33:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  662. Oct 12 16:47:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  663. Oct 12 16:47:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  664. Oct 12 17:01:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  665. Oct 12 17:01:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  666. Oct 12 17:14:41 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  667. Oct 12 17:14:41 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  668. Oct 12 17:28:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  669. Oct 12 17:28:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12 17:42:01 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  671. Oct 12 17:42:01 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not 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 12 17:45:06 pve4 corosync[864]: [TOTEM ] Retransmit List: 2e635
  673. Oct 12 17:55:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  674. Oct 12 17:55:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  675. Oct 12 18:09:21 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  676. Oct 12 18:09:21 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  677. Oct 12 18:23:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  678. Oct 12 18:23:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  679. Oct 12 18:36:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  680. Oct 12 18:36:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  681. Oct 12 18:50:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  682. Oct 12 18:50:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  683. Oct 12 19:04:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  684. Oct 12 19:04:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  685. Oct 12 19:17:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  686. Oct 12 19:17:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  687. Oct 12 19:31:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  688. Oct 12 19:31:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  689. Oct 12 19:45:00 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  690. Oct 12 19:45:00 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  691. Oct 12 19:58:40 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  692. Oct 12 19:58:40 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  693. Oct 12 20:12:20 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  694. Oct 12 20:12:20 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  695. Oct 12 20:25:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  696. Oct 12 20:25:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  697. Oct 12 20:39:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  698. Oct 12 20:39:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  699. Oct 12 20:53:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  700. Oct 12 20:53:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  701. Oct 12 21:06:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  702. Oct 12 21:06:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  703. Oct 12 21:20:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  704. Oct 12 21:20:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  705. Oct 12 21:34:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  706. Oct 12 21:34:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  707. Oct 12 21:47:59 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  708. Oct 12 21:47:59 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  709. Oct 12 22:01:39 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  710. Oct 12 22:01:39 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  711. Oct 12 22:15:19 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  712. Oct 12 22:15:19 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  713. Oct 12 22:28:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  714. Oct 12 22:28:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  715. Oct 12 22:42:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  716. Oct 12 22:42:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  717. Oct 12 22:56:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  718. Oct 12 22:56:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  719. Oct 12 23:09:58 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  720. Oct 12 23:09:58 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  721. Oct 12 23:23:38 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  722. Oct 12 23:23:38 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  723. Oct 12 23:37:18 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  724. Oct 12 23:37:18 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  725. Oct 12 23:50:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  726. Oct 12 23:50:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  727. Oct 13 00:04:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  728. Oct 13 00:04:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  729. Oct 13 00:18:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  730. Oct 13 00:18:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  731. Oct 13 00:31:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  732. Oct 13 00:31:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  733. Oct 13 00:45:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  734. Oct 13 00:45:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  735. Oct 13 00:59:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  736. Oct 13 00:59:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  737. Oct 13 01:12:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  738. Oct 13 01:12:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  739. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  740. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  741. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  742. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  743. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  744. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  745. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  746. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  747. Oct 13 01:20:04 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  748. Oct 13 01:20:05 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
  749. Oct 13 01:20:05 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  750. Oct 13 01:20:06 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 1 joined
  751. Oct 13 01:20:06 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  752. Oct 13 01:20:07 pve4 corosync[864]: [KNET ] rx: host: 4 link: 0 is up
  753. Oct 13 01:20:07 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  754. Oct 13 01:20:07 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  755. Oct 13 01:52:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  756. Oct 13 01:52:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  757. Oct 13 02:05:55 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  758. Oct 13 02:05:55 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  759. Oct 13 02:19:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  760. Oct 13 02:19:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  761. Oct 13 02:28:39 pve4 corosync[864]: [KNET ] pmtud: Global data MTU changed to: 1349
  762. Oct 13 02:33:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  763. Oct 13 02:33:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  764. Oct 13 02:46:55 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  765. Oct 13 02:46:55 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  766. Oct 13 03:00:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  767. Oct 13 03:00:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  768. Oct 13 03:14:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  769. Oct 13 03:14:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  770. Oct 13 03:27:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  771. Oct 13 03:27:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  772. Oct 13 03:41:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  773. Oct 13 03:41:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  774. Oct 13 03:55:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  775. Oct 13 03:55:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  776. Oct 13 04:08:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  777. Oct 13 04:08:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  778. Oct 13 04:22:37 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  779. Oct 13 04:22:37 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  780. Oct 13 04:36:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  781. Oct 13 04:36:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  782. Oct 13 04:49:57 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  783. Oct 13 04:49:57 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  784. Oct 13 05:03:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  785. Oct 13 05:03:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  786. Oct 13 05:17:17 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  787. Oct 13 05:17:17 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  788. Oct 13 05:30:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  789. Oct 13 05:30:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  790. Oct 13 05:44:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  791. Oct 13 05:44:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  792. Oct 13 05:58:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  793. Oct 13 05:58:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  794. Oct 13 06:11:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  795. Oct 13 06:11:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  796. Oct 13 06:25:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  797. Oct 13 06:25:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  798. Oct 13 06:39:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  799. Oct 13 06:39:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  800. Oct 13 06:52:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  801. Oct 13 06:52:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  802. Oct 13 07:06:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  803. Oct 13 07:06:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  804. Oct 13 07:20:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  805. Oct 13 07:20:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  806. Oct 13 07:33:56 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  807. Oct 13 07:33:56 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  808. Oct 13 07:47:36 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  809. Oct 13 07:47:36 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  810. Oct 13 08:01:16 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  811. Oct 13 08:01:16 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  812. Oct 13 08:14:55 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  813. Oct 13 08:14:55 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  814. Oct 13 08:28:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  815. Oct 13 08:28:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  816. Oct 13 08:33:42 pve4 corosync[864]: [TOTEM ] Retransmit List: 69085
  817. Oct 13 08:42:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  818. Oct 13 08:42:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  819. Oct 13 08:55:55 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  820. Oct 13 08:55:55 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  821. Oct 13 09:09:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  822. Oct 13 09:09:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  823. Oct 13 09:23:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  824. Oct 13 09:23:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  825. Oct 13 09:36:55 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  826. Oct 13 09:36:55 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  827. Oct 13 09:50:35 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  828. Oct 13 09:50:35 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  829. Oct 13 10:04:15 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  830. Oct 13 10:04:15 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  831. Oct 13 10:17:54 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  832. Oct 13 10:17:54 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  833. Oct 13 10:31:34 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  834. Oct 13 10:31:34 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  835. Oct 13 10:45:14 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  836. Oct 13 10:45:14 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  837. Oct 13 10:58:54 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  838. Oct 13 10:58:54 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  839. Oct 13 11:12:34 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 4 link 0 but the other node is not acknowledging packets of this size.
  840. Oct 13 11:12:34 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  841. Oct 13 11:26:14 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 1 link 0 but the other node is not acknowledging packets of this size.
  842. Oct 13 11:26:14 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  843. Oct 13 11:39:54 pve4 corosync[864]: [KNET ] pmtud: possible MTU misconfiguration detected. kernel is reporting MTU: 1500 bytes for host 2 link 0 but the other node is not acknowledging packets of this size.
  844. Oct 13 11:39:54 pve4 corosync[864]: [KNET ] pmtud: This can be caused by this node interface MTU too big or a network device that does not support or has been misconfigured to manage MTU of this size, or packet loss. knet will continue to run but performances might be affected.
  845. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] link: host: 1 link: 0 is down
  846. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] link: host: 2 link: 0 is down
  847. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] link: host: 4 link: 0 is down
  848. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  849. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 1 has no active links
  850. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  851. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 2 has no active links
  852. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  853. Oct 13 11:46:12 pve4 corosync[864]: [KNET ] host: host: 4 has no active links
  854. Oct 13 11:46:13 pve4 corosync[864]: [TOTEM ] Token has not been received in 3225 ms
  855. Oct 13 11:46:14 pve4 corosync[864]: [TOTEM ] A processor failed, forming new configuration: token timed out (4300ms), waiting 5160ms for consensus.
  856. Oct 13 11:46:19 pve4 corosync[864]: [QUORUM] Sync members[1]: 3
  857. Oct 13 11:46:19 pve4 corosync[864]: [QUORUM] Sync left[3]: 1 2 4
  858. Oct 13 11:46:19 pve4 corosync[864]: [TOTEM ] A new membership (3.19f29) was formed. Members left: 1 2 4
  859. Oct 13 11:46:19 pve4 corosync[864]: [TOTEM ] Failed to receive the leave message. failed: 1 2 4
  860. Oct 13 11:46:19 pve4 corosync[864]: [QUORUM] This node is within the non-primary component and will NOT provide any services.
  861. Oct 13 11:46:19 pve4 corosync[864]: [QUORUM] Members[1]: 3
  862. Oct 13 11:46:19 pve4 corosync[864]: [MAIN ] Completed service synchronization, ready to provide service.
  863. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  864. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  865. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  866. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  867. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  868. Oct 13 11:47:09 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  869.  
  870.  
  871. [...]
  872.  
  873.  
  874. Oct 13 18:48:50 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  875. Oct 13 18:48:50 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  876. Oct 13 18:48:51 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  877. Oct 13 18:48:51 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  878. Oct 13 18:48:51 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  879. Oct 13 18:48:52 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  880. Oct 13 18:48:52 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  881. Oct 13 18:48:52 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  882. Oct 13 18:48:53 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  883. Oct 13 18:48:53 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  884. Oct 13 18:48:53 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  885. Oct 13 18:48:54 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  886. Oct 13 18:48:54 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  887. Oct 13 18:48:55 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  888. Oct 13 18:48:55 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  889. Oct 13 18:48:56 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:31236
  890. Oct 13 18:48:56 pve4 corosync[864]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  891. Oct 13 18:48:56 pve4 systemd[1]: Stopping corosync.service - Corosync Cluster Engine...
  892. Oct 13 18:48:56 pve4 corosync-cfgtool[4146974]: Shutting down corosync
  893. Oct 13 18:48:56 pve4 corosync[864]: [MAIN ] Node was shut down by a signal
  894. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Unloading all Corosync service engines.
  895. Oct 13 18:48:56 pve4 corosync[864]: [QB ] withdrawing server sockets
  896. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync vote quorum service v1.0
  897. Oct 13 18:48:56 pve4 corosync[864]: [CFG ] Node 3 was shut down by sysadmin
  898. Oct 13 18:48:56 pve4 corosync[864]: [QB ] withdrawing server sockets
  899. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync configuration map access
  900. Oct 13 18:48:56 pve4 corosync[864]: [QB ] withdrawing server sockets
  901. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync configuration service
  902. Oct 13 18:48:56 pve4 corosync[864]: [QB ] withdrawing server sockets
  903. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync cluster closed process group service v1.01
  904. Oct 13 18:48:56 pve4 corosync[864]: [QB ] withdrawing server sockets
  905. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync cluster quorum service v0.1
  906. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync profile loading service
  907. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync resource monitoring service
  908. Oct 13 18:48:56 pve4 corosync[864]: [SERV ] Service engine unloaded: corosync watchdog service
  909. Oct 13 18:48:57 pve4 corosync[864]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  910. Oct 13 18:48:57 pve4 corosync[864]: [MAIN ] Corosync Cluster Engine exiting normally
  911. Oct 13 18:48:57 pve4 systemd[1]: corosync.service: Deactivated successfully.
  912. Oct 13 18:48:57 pve4 systemd[1]: Stopped corosync.service - Corosync Cluster Engine.
  913. Oct 13 18:48:57 pve4 systemd[1]: corosync.service: Consumed 2h 47min 39.814s CPU time.
  914. Oct 13 18:49:08 pve4 systemd[1]: Starting corosync.service - Corosync Cluster Engine...
  915. Oct 13 18:49:08 pve4 corosync[4146982]: [MAIN ] Corosync Cluster Engine starting up
  916. Oct 13 18:49:08 pve4 corosync[4146982]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vqsim nozzle snmp pie relro bindnow
  917. Oct 13 18:49:08 pve4 corosync[4146982]: [TOTEM ] Initializing transport (Kronosnet).
  918. Oct 13 18:49:08 pve4 corosync[4146982]: [TOTEM ] totemknet initialized
  919. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] pmtud: MTU manually set to: 0
  920. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
  921. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync configuration map access [0]
  922. Oct 13 18:49:08 pve4 corosync[4146982]: [QB ] server name: cmap
  923. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync configuration service [1]
  924. Oct 13 18:49:08 pve4 corosync[4146982]: [QB ] server name: cfg
  925. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
  926. Oct 13 18:49:08 pve4 corosync[4146982]: [QB ] server name: cpg
  927. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync profile loading service [4]
  928. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
  929. Oct 13 18:49:08 pve4 corosync[4146982]: [WD ] Watchdog not enabled by configuration
  930. Oct 13 18:49:08 pve4 corosync[4146982]: [WD ] resource load_15min missing a recovery key.
  931. Oct 13 18:49:08 pve4 corosync[4146982]: [WD ] resource memory_used missing a recovery key.
  932. Oct 13 18:49:08 pve4 corosync[4146982]: [WD ] no resources configured.
  933. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync watchdog service [7]
  934. Oct 13 18:49:08 pve4 corosync[4146982]: [QUORUM] Using quorum provider corosync_votequorum
  935. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
  936. Oct 13 18:49:08 pve4 corosync[4146982]: [QB ] server name: votequorum
  937. Oct 13 18:49:08 pve4 corosync[4146982]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
  938. Oct 13 18:49:08 pve4 corosync[4146982]: [QB ] server name: quorum
  939. Oct 13 18:49:08 pve4 corosync[4146982]: [TOTEM ] Configuring link 0
  940. Oct 13 18:49:08 pve4 corosync[4146982]: [TOTEM ] Configured link number 0: local addr: 10.133.0.4, port=5405
  941. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 0)
  942. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 has no active links
  943. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  944. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 has no active links
  945. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  946. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 4 has no active links
  947. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 0)
  948. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 has no active links
  949. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  950. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 has no active links
  951. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  952. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 2 has no active links
  953. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  954. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 has no active links
  955. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  956. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 has no active links
  957. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  958. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] host: host: 1 has no active links
  959. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] link: Resetting MTU for link 0 because host 3 joined
  960. Oct 13 18:49:08 pve4 corosync[4146982]: [QUORUM] Sync members[1]: 3
  961. Oct 13 18:49:08 pve4 corosync[4146982]: [QUORUM] Sync joined[1]: 3
  962. Oct 13 18:49:08 pve4 corosync[4146982]: [TOTEM ] A new membership (3.19f2e) was formed. Members joined: 3
  963. Oct 13 18:49:08 pve4 corosync[4146982]: [QUORUM] Members[1]: 3
  964. Oct 13 18:49:08 pve4 corosync[4146982]: [MAIN ] Completed service synchronization, ready to provide service.
  965. Oct 13 18:49:08 pve4 systemd[1]: Started corosync.service - Corosync Cluster Engine.
  966. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  967. Oct 13 18:49:08 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  968. Oct 13 18:49:09 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  969. Oct 13 18:49:09 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  970. Oct 13 18:49:10 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  971. Oct 13 18:49:10 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  972. Oct 13 18:49:10 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  973. Oct 13 18:49:10 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  974. Oct 13 18:49:11 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  975. Oct 13 18:49:11 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  976. Oct 13 18:49:11 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  977. Oct 13 18:49:11 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  978. Oct 13 18:49:12 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  979. Oct 13 18:49:12 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  980. Oct 13 18:49:12 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  981. Oct 13 18:49:13 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  982. Oct 13 18:49:13 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  983. Oct 13 18:49:13 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  984. Oct 13 18:49:13 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  985. Oct 13 18:49:14 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  986. Oct 13 18:49:14 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  987. Oct 13 18:49:14 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  988. Oct 13 18:49:15 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  989. Oct 13 18:49:15 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  990. Oct 13 18:49:16 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  991. Oct 13 18:49:16 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  992. Oct 13 18:49:16 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  993. Oct 13 18:49:16 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  994. Oct 13 18:49:17 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  995. Oct 13 18:49:17 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  996. Oct 13 18:49:17 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  997. Oct 13 18:49:17 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  998. Oct 13 18:49:18 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  999. Oct 13 18:49:18 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1000. Oct 13 18:49:18 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1001. Oct 13 18:49:19 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1002. Oct 13 18:49:19 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1003. Oct 13 18:49:19 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1004. Oct 13 18:49:19 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1005. Oct 13 18:49:20 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1006. Oct 13 18:49:20 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1007. Oct 13 18:49:20 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1008. Oct 13 18:49:21 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1009. Oct 13 18:49:21 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1010. Oct 13 18:49:21 pve4 corosync[4146982]: [KNET ] link: Resetting MTU for link 0 because host 4 joined
  1011. Oct 13 18:49:21 pve4 corosync[4146982]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
  1012.  
  1013.  
  1014. [...]
  1015.  
  1016.  
  1017. Oct 13 19:10:24 pve4 corosync[4146982]: [QUORUM] Sync members[1]: 3
  1018. Oct 13 19:10:24 pve4 corosync[4146982]: [TOTEM ] A new membership (3.1a2e2) was formed. Members
  1019. Oct 13 19:10:24 pve4 corosync[4146982]: [QUORUM] Members[1]: 3
  1020. Oct 13 19:10:24 pve4 corosync[4146982]: [MAIN ] Completed service synchronization, ready to provide service.
  1021. Oct 13 19:10:25 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1022. Oct 13 19:10:25 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1023. Oct 13 19:10:25 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1024. Oct 13 19:10:25 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1025. Oct 13 19:10:26 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1026. Oct 13 19:10:26 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1027. Oct 13 19:10:26 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1028. Oct 13 19:10:26 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1029. Oct 13 19:10:27 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1030. Oct 13 19:10:27 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1031. Oct 13 19:10:27 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1032. Oct 13 19:10:28 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1033. Oct 13 19:10:29 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1034. Oct 13 19:10:29 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1035. Oct 13 19:10:29 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1036. Oct 13 19:10:29 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1037. Oct 13 19:10:29 pve4 corosync[4146982]: [QUORUM] Sync members[1]: 3
  1038. Oct 13 19:10:29 pve4 corosync[4146982]: [TOTEM ] A new membership (3.1a2e6) was formed. Members
  1039. Oct 13 19:10:29 pve4 corosync[4146982]: [QUORUM] Members[1]: 3
  1040. Oct 13 19:10:29 pve4 corosync[4146982]: [MAIN ] Completed service synchronization, ready to provide service.
  1041. Oct 13 19:10:30 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1042. Oct 13 19:10:30 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:34295
  1043. Oct 13 19:10:30 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1044. Oct 13 19:10:30 pve4 corosync[4146982]: [KNET ] rx: Packet rejected from PUBLIC_IP_PVE1:5405
  1045.  
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!