Advertisement
Guest User

Untitled

a guest
Jun 2nd, 2025
44
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.15 KB | None | 0 0
  1. 2025-06-02T12:24:10.000Z prox-01 pvestatd[1780]: got timeout
  2. 2025-06-02T12:24:16.000Z prox-01 pvestatd[1780]: got timeout
  3. 2025-06-02T12:24:16.000Z prox-01 pvestatd[1780]: status update time (7.248 seconds)
  4. 2025-06-02T12:24:20.000Z prox-01 pvestatd[1780]: got timeout
  5. 2025-06-02T12:24:25.000Z prox-01 pvestatd[1780]: got timeout
  6. 2025-06-02T12:24:25.000Z prox-01 pvestatd[1780]: status update time (7.256 seconds)
  7. 2025-06-02T12:24:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  8. 2025-06-02T12:25:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  9. 2025-06-02T12:26:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  10. 2025-06-02T12:27:23.000Z prox-01 pvestatd[1780]: got timeout
  11. 2025-06-02T12:27:25.000Z prox-01 pvestatd[1780]: got timeout
  12. 2025-06-02T12:27:25.000Z prox-01 pvestatd[1780]: status update time (7.254 seconds)
  13. 2025-06-02T12:27:34.000Z prox-01 pvestatd[1780]: got timeout
  14. 2025-06-02T12:27:35.000Z prox-01 pvestatd[1780]: status update time (6.701 seconds)
  15. 2025-06-02T12:27:43.000Z prox-01 pvestatd[1780]: got timeout
  16. 2025-06-02T12:27:45.000Z prox-01 pvestatd[1780]: got timeout
  17. 2025-06-02T12:27:45.000Z prox-01 pvestatd[1780]: status update time (7.266 seconds)
  18. 2025-06-02T12:27:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  19. 2025-06-02T12:27:53.000Z prox-01 pvestatd[1780]: got timeout
  20. 2025-06-02T12:27:55.000Z prox-01 pvestatd[1780]: got timeout
  21. 2025-06-02T12:27:55.000Z prox-01 pvestatd[1780]: status update time (7.254 seconds)
  22. 2025-06-02T12:28:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  23. 2025-06-02T12:29:20.000Z prox-01 pvestatd[1780]: got timeout
  24. 2025-06-02T12:29:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  25. 2025-06-02T12:30:23.000Z prox-01 pvestatd[1780]: got timeout
  26. 2025-06-02T12:30:25.000Z prox-01 pvestatd[1780]: got timeout
  27. 2025-06-02T12:30:25.000Z prox-01 pvestatd[1780]: status update time (7.260 seconds)
  28. 2025-06-02T12:30:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  29. 2025-06-02T12:30:50.000Z prox-01 pvestatd[1780]: got timeout
  30. 2025-06-02T12:31:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  31. 2025-06-02T12:32:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  32. 2025-06-02T12:33:35.000Z prox-01 postfix/qmgr[1507]: 8E701350D3: from=<>, size=28350, nrcpt=1 (queue active)
  33. 2025-06-02T12:33:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  34. 2025-06-02T12:34:00.000Z prox-01 pvestatd[1780]: got timeout
  35. 2025-06-02T12:34:05.000Z prox-01 pvestatd[1780]: got timeout
  36. 2025-06-02T12:34:05.000Z prox-01 pvestatd[1780]: status update time (7.292 seconds)
  37. 2025-06-02T12:34:06.000Z prox-01 postfix/smtp[901035]: connect to gmail-smtp-in.l.google.com[74.125.195.26]:25: Connection timed out
  38. 2025-06-02T12:34:06.000Z prox-01 postfix/smtp[901034]: connect to gmail-smtp-in.l.google.com[74.125.195.26]:25: Connection timed out
  39. 2025-06-02T12:34:10.000Z prox-01 pvestatd[1780]: got timeout
  40. 2025-06-02T12:34:36.000Z prox-01 postfix/smtp[901035]: connect to gmail-smtp-in.l.google.com[2607:f8b0:400e:c09::1a]:25: Connection timed out
  41. 2025-06-02T12:34:36.000Z prox-01 postfix/smtp[901034]: connect to gmail-smtp-in.l.google.com[2607:f8b0:400e:c09::1a]:25: Connection timed out
  42. 2025-06-02T12:34:45.000Z prox-01 snmpd[1311]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  43. 2025-06-02T12:34:57.000Z prox-01 kernel: [135713.708768] ceph: [a97ccc4a-2fa3-4cc3-a252-8e1eb0b79ab5 35415983]: mds0 caps stale
  44. 2025-06-02T12:35:06.000Z prox-01 postfix/smtp[901034]: connect to alt1.gmail-smtp-in.l.google.com[173.194.208.27]:25: Connection timed out
  45. 2025-06-02T12:35:06.000Z prox-01 postfix/smtp[901035]: connect to alt1.gmail-smtp-in.l.google.com[173.194.208.27]:25: Connection timed out
  46. 2025-06-02T12:35:08.000Z prox-01 ceph-mon[1514]: 2025-06-02T12:35:08.124+0000 71019e91f6c0 -1 mon.prox-01@0(leader) e3 get_health_metrics reporting 9 slow ops, oldest is log(1 entries from seq 11563 at 2025-06-02T12:33:37.735562+0000)
  47. 2025-06-02T12:35:08.000Z prox-01 watchdog-mux[890]: client watchdog expired - disable watchdog updates
  48. 2025-06-02T12:35:12.000Z prox-01 pvestatd[1780]: got timeout
  49. 2025-06-02T12:35:15.000Z prox-01 watchdog-mux[890]: exit watchdog-mux with active connections
  50. 2025-06-02T12:35:15.000Z prox-01 pve-ha-crm[1852]: loop take too long (66 seconds)
  51. 2025-06-02T12:35:15.000Z prox-01 kernel: [135732.399569] watchdog: watchdog0: watchdog did not stop!
  52. 2025-06-02T12:35:23.000Z prox-01 pve-firewall[1751]: firewall update time (57.518 seconds)
  53.  
  54. ## Reboot looks to have happened here.
  55.  
  56. 2025-06-02T12:39:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  57. 2025-06-02T12:39:12.000Z prox-01 pvestatd[1747]: VM 105 qmp command failed - VM 105 qmp command 'query-proxmox-support' failed - got timeout
  58. 2025-06-02T12:39:12.000Z prox-01 pvestatd[1747]: status update time (8.296 seconds)
  59. 2025-06-02T12:39:22.000Z prox-01 pvestatd[1747]: VM 105 qmp command failed - VM 105 qmp command 'query-proxmox-support' failed - unable to connect to VM 105 qmp socket - timeout after 51 retries
  60. 2025-06-02T12:39:23.000Z prox-01 pvestatd[1747]: status update time (8.315 seconds)
  61. 2025-06-02T12:39:46.000Z prox-01 pvestatd[1747]: got timeout
  62. 2025-06-02T12:39:51.000Z prox-01 pvestatd[1747]: got timeout
  63. 2025-06-02T12:39:51.000Z prox-01 pvestatd[1747]: status update time (7.246 seconds)
  64. 2025-06-02T12:39:56.000Z prox-01 pvestatd[1747]: got timeout
  65. 2025-06-02T12:40:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  66. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [KNET ] link: Resetting MTU for link 0 because host 5 joined
  67. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  68. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [QUORUM] Sync members[5]: 1 2 3 4 5
  69. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [QUORUM] Sync joined[1]: 5
  70. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [TOTEM ] A new membership (1.173b) was formed. Members joined: 5
  71. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: members: 1/1423, 2/1418, 3/1391, 4/1780, 5/780
  72. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: starting data syncronisation
  73. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [QUORUM] Members[5]: 1 2 3 4 5
  74. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [MAIN ] Completed service synchronization, ready to provide service.
  75. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [KNET ] pmtud: PMTUD link change for host: 5 link: 0 from 469 to 8885
  76. 2025-06-02T12:40:24.000Z prox-01 corosync[1520]: [KNET ] pmtud: Global data MTU changed to: 8869
  77. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: cpg_send_message retried 1 times
  78. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [status] notice: members: 1/1423, 2/1418, 3/1391, 4/1780, 5/780
  79. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [status] notice: starting data syncronisation
  80. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: received sync request (epoch 1/1423/00000003)
  81. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [status] notice: received sync request (epoch 1/1423/00000003)
  82. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: received all states
  83. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: leader is 1/1423
  84. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: synced members: 1/1423, 2/1418, 3/1391, 4/1780
  85. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: start sending inode updates
  86. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: sent all (12) updates
  87. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [dcdb] notice: all data is up to date
  88. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [status] notice: received all states
  89. 2025-06-02T12:40:24.000Z prox-01 pmxcfs[1423]: [status] notice: all data is up to date
  90. 2025-06-02T12:40:45.000Z prox-01 chronyd[1324]: Selected source 99.28.14.242 (2.debian.pool.ntp.org)
  91. 2025-06-02T12:40:45.000Z prox-01 chronyd[1324]: System clock TAI offset set to 37 seconds
  92. 2025-06-02T12:40:47.000Z prox-01 pvestatd[1747]: got timeout
  93. 2025-06-02T12:40:56.000Z prox-01 pvestatd[1747]: got timeout
  94. 2025-06-02T12:41:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  95. 2025-06-02T12:41:06.000Z prox-01 postfix/qmgr[1497]: EF1453222D: from=<>, size=21851, nrcpt=1 (queue active)
  96. 2025-06-02T12:41:37.000Z prox-01 postfix/smtp[5546]: connect to gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out
  97. 2025-06-02T12:41:51.000Z prox-01 chronyd[1324]: Selected source 5.78.62.36 (2.debian.pool.ntp.org)
  98. 2025-06-02T12:41:56.000Z prox-01 pvestatd[1747]: got timeout
  99. 2025-06-02T12:42:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  100. 2025-06-02T12:42:07.000Z prox-01 postfix/smtp[5546]: connect to gmail-smtp-in.l.google.com[2607:f8b0:400e:c09::1a]:25: Connection timed out
  101. 2025-06-02T12:42:37.000Z prox-01 postfix/smtp[5546]: connect to alt1.gmail-smtp-in.l.google.com[2607:f8b0:4023:100d::1a]:25: Connection timed out
  102. 2025-06-02T12:43:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  103. 2025-06-02T12:43:07.000Z prox-01 postfix/smtp[5546]: connect to alt1.gmail-smtp-in.l.google.com[173.194.208.26]:25: Connection timed out
  104. 2025-06-02T12:43:26.000Z prox-01 pvestatd[1747]: got timeout
  105. 2025-06-02T12:43:37.000Z prox-01 postfix/smtp[5546]: connect to alt2.gmail-smtp-in.l.google.com[142.251.190.27]:25: Connection timed out
  106. 2025-06-02T12:44:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  107. 2025-06-02T12:45:06.000Z prox-01 pvestatd[1747]: got timeout
  108. 2025-06-02T12:45:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  109. 2025-06-02T12:45:11.000Z prox-01 kernel: [ 558.939971] ceph: [a97ccc4a-2fa3-4cc3-a252-8e1eb0b79ab5 36424098]: mds0 reconnect start
  110. 2025-06-02T12:45:11.000Z prox-01 kernel: [ 558.940887] ceph: [a97ccc4a-2fa3-4cc3-a252-8e1eb0b79ab5 36424098]: mds0 reconnect success
  111. 2025-06-02T12:45:13.000Z prox-01 kernel: [ 560.965183] ceph: [a97ccc4a-2fa3-4cc3-a252-8e1eb0b79ab5 36424098]: mds0 recovery completed
  112. 2025-06-02T12:45:14.000Z prox-01 ceph-mds[1505]: 2025-06-02T12:45:14.690+0000 70037140c6c0 -1 mds.pinger is_rank_lagging: rank=0 was never sent ping request.
  113. 2025-06-02T12:46:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  114. 2025-06-02T12:47:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  115. 2025-06-02T12:48:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  116. 2025-06-02T12:49:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  117. 2025-06-02T12:50:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  118. 2025-06-02T12:51:05.000Z prox-01 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
  119. 2025-06-02T12:51:05.000Z prox-01 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
  120. 2025-06-02T12:51:05.000Z prox-01 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
  121. 2025-06-02T12:51:05.000Z prox-01 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
  122. 2025-06-02T12:51:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  123. 2025-06-02T12:51:36.000Z prox-01 postfix/smtp[9567]: connect to gmail-smtp-in.l.google.com[74.125.142.26]:25: Connection timed out
  124. 2025-06-02T12:51:46.000Z prox-01 pvestatd[1747]: got timeout
  125. 2025-06-02T12:52:06.000Z prox-01 postfix/smtp[9567]: connect to gmail-smtp-in.l.google.com[2607:f8b0:400e:c09::1a]:25: Connection timed out
  126. 2025-06-02T12:52:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  127. 2025-06-02T12:52:36.000Z prox-01 postfix/smtp[9567]: connect to alt1.gmail-smtp-in.l.google.com[2607:f8b0:4023:100d::1b]:25: Connection timed out
  128. 2025-06-02T12:52:39.000Z prox-01 pvestatd[1747]: got timeout
  129. 2025-06-02T12:52:41.000Z prox-01 pvestatd[1747]: got timeout
  130. 2025-06-02T12:52:41.000Z prox-01 pvestatd[1747]: status update time (7.265 seconds)
  131. 2025-06-02T12:53:06.000Z prox-01 postfix/smtp[9567]: connect to alt1.gmail-smtp-in.l.google.com[173.194.208.27]:25: Connection timed out
  132. 2025-06-02T12:53:06.000Z prox-01 snmpd[1302]: systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
  133. 2025-06-02T12:53:16.000Z prox-01 pvestatd[1747]: got timeout
  134. 2025-06-02T12:53:36.000Z prox-01 postfix/smtp[9567]: connect to alt2.gmail-smtp-in.l.google.com[142.251.190.26]:25: Connection timed out
  135.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement