API tools faq
paste
bduijve

Untitled

bduijve
Jan 15th, 2024
40
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 75.49 KB | None | 0 0
raw download clone embed print report
  1. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(vethb7e5015) entered disabled state
  2. Jan 15 13:09:43 pve-ryzen kernel: vetha082881: renamed from eth0
  3. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(vethb7e5015) entered disabled state
  4. Jan 15 13:09:43 pve-ryzen kernel: vethb7e5015 (unregistering): left allmulticast mode
  5. Jan 15 13:09:43 pve-ryzen kernel: vethb7e5015 (unregistering): left promiscuous mode
  6. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(vethb7e5015) entered disabled state
  7. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(veth11c603c) entered blocking state
  8. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(veth11c603c) entered disabled state
  9. Jan 15 13:09:43 pve-ryzen kernel: veth11c603c: entered allmulticast mode
  10. Jan 15 13:09:43 pve-ryzen kernel: veth11c603c: entered promiscuous mode
  11. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(veth11c603c) entered blocking state
  12. Jan 15 13:09:43 pve-ryzen kernel: docker0: port 1(veth11c603c) entered forwarding state
  13. Jan 15 13:09:43 pve-ryzen kernel: eth0: renamed from veth75bd5e0
  14. Jan 15 13:13:44 pve-ryzen pveproxy[1074998]: worker exit
  15. Jan 15 13:13:44 pve-ryzen pveproxy[1585]: worker 1074998 finished
  16. Jan 15 13:13:44 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  17. Jan 15 13:13:44 pve-ryzen pveproxy[1585]: worker 1144936 started
  18. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth11c603c) entered disabled state
  19. Jan 15 13:14:44 pve-ryzen kernel: veth75bd5e0: renamed from eth0
  20. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth11c603c) entered disabled state
  21. Jan 15 13:14:44 pve-ryzen kernel: veth11c603c (unregistering): left allmulticast mode
  22. Jan 15 13:14:44 pve-ryzen kernel: veth11c603c (unregistering): left promiscuous mode
  23. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth11c603c) entered disabled state
  24. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered blocking state
  25. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered disabled state
  26. Jan 15 13:14:44 pve-ryzen kernel: veth57ac6bb: entered allmulticast mode
  27. Jan 15 13:14:44 pve-ryzen kernel: veth57ac6bb: entered promiscuous mode
  28. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered blocking state
  29. Jan 15 13:14:44 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered forwarding state
  30. Jan 15 13:14:44 pve-ryzen kernel: eth0: renamed from veth2880e87
  31. Jan 15 13:15:05 pve-ryzen pvedaemon[1090869]: <root@pam> successful auth for user 'root@pam'
  32. Jan 15 13:17:01 pve-ryzen CRON[1156811]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
  33. Jan 15 13:17:01 pve-ryzen CRON[1156812]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
  34. Jan 15 13:17:01 pve-ryzen CRON[1156811]: pam_unix(cron:session): session closed for user root
  35. Jan 15 13:19:16 pve-ryzen pveproxy[1099102]: worker exit
  36. Jan 15 13:19:16 pve-ryzen pveproxy[1585]: worker 1099102 finished
  37. Jan 15 13:19:16 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  38. Jan 15 13:19:16 pve-ryzen pveproxy[1585]: worker 1164840 started
  39. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered disabled state
  40. Jan 15 13:19:45 pve-ryzen kernel: veth2880e87: renamed from eth0
  41. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered disabled state
  42. Jan 15 13:19:45 pve-ryzen kernel: veth57ac6bb (unregistering): left allmulticast mode
  43. Jan 15 13:19:45 pve-ryzen kernel: veth57ac6bb (unregistering): left promiscuous mode
  44. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(veth57ac6bb) entered disabled state
  45. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered blocking state
  46. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered disabled state
  47. Jan 15 13:19:45 pve-ryzen kernel: vetha3c518f: entered allmulticast mode
  48. Jan 15 13:19:45 pve-ryzen kernel: vetha3c518f: entered promiscuous mode
  49. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered blocking state
  50. Jan 15 13:19:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered forwarding state
  51. Jan 15 13:19:45 pve-ryzen kernel: eth0: renamed from veth65e1dd7
  52. Jan 15 13:22:11 pve-ryzen pvedaemon[1058904]: worker exit
  53. Jan 15 13:22:11 pve-ryzen pvedaemon[1577]: worker 1058904 finished
  54. Jan 15 13:22:11 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  55. Jan 15 13:22:11 pve-ryzen pvedaemon[1577]: worker 1175276 started
  56. Jan 15 13:24:25 pve-ryzen pvedaemon[1122003]: <root@pam> successful auth for user 'root@pam'
  57. Jan 15 13:24:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered disabled state
  58. Jan 15 13:24:45 pve-ryzen kernel: veth65e1dd7: renamed from eth0
  59. Jan 15 13:24:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered disabled state
  60. Jan 15 13:24:45 pve-ryzen kernel: vetha3c518f (unregistering): left allmulticast mode
  61. Jan 15 13:24:45 pve-ryzen kernel: vetha3c518f (unregistering): left promiscuous mode
  62. Jan 15 13:24:45 pve-ryzen kernel: docker0: port 1(vetha3c518f) entered disabled state
  63. Jan 15 13:24:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered blocking state
  64. Jan 15 13:24:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered disabled state
  65. Jan 15 13:24:46 pve-ryzen kernel: vethc4f6665: entered allmulticast mode
  66. Jan 15 13:24:46 pve-ryzen kernel: vethc4f6665: entered promiscuous mode
  67. Jan 15 13:24:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered blocking state
  68. Jan 15 13:24:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered forwarding state
  69. Jan 15 13:24:46 pve-ryzen kernel: eth0: renamed from veth1ddd080
  70. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered disabled state
  71. Jan 15 13:29:46 pve-ryzen kernel: veth1ddd080: renamed from eth0
  72. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered disabled state
  73. Jan 15 13:29:46 pve-ryzen kernel: vethc4f6665 (unregistering): left allmulticast mode
  74. Jan 15 13:29:46 pve-ryzen kernel: vethc4f6665 (unregistering): left promiscuous mode
  75. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(vethc4f6665) entered disabled state
  76. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered blocking state
  77. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered disabled state
  78. Jan 15 13:29:46 pve-ryzen kernel: veth6db1f6e: entered allmulticast mode
  79. Jan 15 13:29:46 pve-ryzen kernel: veth6db1f6e: entered promiscuous mode
  80. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered blocking state
  81. Jan 15 13:29:46 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered forwarding state
  82. Jan 15 13:29:47 pve-ryzen kernel: eth0: renamed from veth0aa417e
  83. Jan 15 13:30:06 pve-ryzen pveproxy[1127450]: worker exit
  84. Jan 15 13:30:06 pve-ryzen pveproxy[1585]: worker 1127450 finished
  85. Jan 15 13:30:06 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  86. Jan 15 13:30:06 pve-ryzen pveproxy[1585]: worker 1203632 started
  87. Jan 15 13:31:05 pve-ryzen pvedaemon[1090869]: <root@pam> successful auth for user 'root@pam'
  88. Jan 15 13:33:13 pve-ryzen pveproxy[1144936]: worker exit
  89. Jan 15 13:33:13 pve-ryzen pveproxy[1585]: worker 1144936 finished
  90. Jan 15 13:33:13 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  91. Jan 15 13:33:13 pve-ryzen pveproxy[1585]: worker 1214578 started
  92. Jan 15 13:34:30 pve-ryzen pvedaemon[1090869]: worker exit
  93. Jan 15 13:34:30 pve-ryzen pvedaemon[1577]: worker 1090869 finished
  94. Jan 15 13:34:30 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  95. Jan 15 13:34:30 pve-ryzen pvedaemon[1577]: worker 1219300 started
  96. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered disabled state
  97. Jan 15 13:34:47 pve-ryzen kernel: veth0aa417e: renamed from eth0
  98. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered disabled state
  99. Jan 15 13:34:47 pve-ryzen kernel: veth6db1f6e (unregistering): left allmulticast mode
  100. Jan 15 13:34:47 pve-ryzen kernel: veth6db1f6e (unregistering): left promiscuous mode
  101. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth6db1f6e) entered disabled state
  102. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth8af6153) entered blocking state
  103. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth8af6153) entered disabled state
  104. Jan 15 13:34:47 pve-ryzen kernel: veth8af6153: entered allmulticast mode
  105. Jan 15 13:34:47 pve-ryzen kernel: veth8af6153: entered promiscuous mode
  106. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth8af6153) entered blocking state
  107. Jan 15 13:34:47 pve-ryzen kernel: docker0: port 1(veth8af6153) entered forwarding state
  108. Jan 15 13:34:48 pve-ryzen kernel: eth0: renamed from veth290935e
  109. Jan 15 13:39:17 pve-ryzen pveproxy[1164840]: worker exit
  110. Jan 15 13:39:17 pve-ryzen pveproxy[1585]: worker 1164840 finished
  111. Jan 15 13:39:17 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  112. Jan 15 13:39:17 pve-ryzen pveproxy[1585]: worker 1236318 started
  113. Jan 15 13:39:25 pve-ryzen pvedaemon[1175276]: <root@pam> successful auth for user 'root@pam'
  114. Jan 15 13:39:35 pve-ryzen smartd[1232]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 67
  115. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth8af6153) entered disabled state
  116. Jan 15 13:39:48 pve-ryzen kernel: veth290935e: renamed from eth0
  117. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth8af6153) entered disabled state
  118. Jan 15 13:39:48 pve-ryzen kernel: veth8af6153 (unregistering): left allmulticast mode
  119. Jan 15 13:39:48 pve-ryzen kernel: veth8af6153 (unregistering): left promiscuous mode
  120. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth8af6153) entered disabled state
  121. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered blocking state
  122. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered disabled state
  123. Jan 15 13:39:48 pve-ryzen kernel: veth6b5dac1: entered allmulticast mode
  124. Jan 15 13:39:48 pve-ryzen kernel: veth6b5dac1: entered promiscuous mode
  125. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered blocking state
  126. Jan 15 13:39:48 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered forwarding state
  127. Jan 15 13:39:48 pve-ryzen kernel: eth0: renamed from veth74a8daf
  128. Jan 15 13:42:26 pve-ryzen pvedaemon[1122003]: worker exit
  129. Jan 15 13:42:27 pve-ryzen pvedaemon[1577]: worker 1122003 finished
  130. Jan 15 13:42:27 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  131. Jan 15 13:42:27 pve-ryzen pvedaemon[1577]: worker 1247687 started
  132. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered disabled state
  133. Jan 15 13:44:49 pve-ryzen kernel: veth74a8daf: renamed from eth0
  134. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered disabled state
  135. Jan 15 13:44:49 pve-ryzen kernel: veth6b5dac1 (unregistering): left allmulticast mode
  136. Jan 15 13:44:49 pve-ryzen kernel: veth6b5dac1 (unregistering): left promiscuous mode
  137. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth6b5dac1) entered disabled state
  138. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth059f27a) entered blocking state
  139. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth059f27a) entered disabled state
  140. Jan 15 13:44:49 pve-ryzen kernel: veth059f27a: entered allmulticast mode
  141. Jan 15 13:44:49 pve-ryzen kernel: veth059f27a: entered promiscuous mode
  142. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth059f27a) entered blocking state
  143. Jan 15 13:44:49 pve-ryzen kernel: docker0: port 1(veth059f27a) entered forwarding state
  144. Jan 15 13:44:49 pve-ryzen kernel: eth0: renamed from veth961ac9d
  145. Jan 15 13:47:05 pve-ryzen pvedaemon[1247687]: <root@pam> successful auth for user 'root@pam'
  146. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth059f27a) entered disabled state
  147. Jan 15 13:49:50 pve-ryzen kernel: veth961ac9d: renamed from eth0
  148. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth059f27a) entered disabled state
  149. Jan 15 13:49:50 pve-ryzen kernel: veth059f27a (unregistering): left allmulticast mode
  150. Jan 15 13:49:50 pve-ryzen kernel: veth059f27a (unregistering): left promiscuous mode
  151. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth059f27a) entered disabled state
  152. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth5c29339) entered blocking state
  153. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth5c29339) entered disabled state
  154. Jan 15 13:49:50 pve-ryzen kernel: veth5c29339: entered allmulticast mode
  155. Jan 15 13:49:50 pve-ryzen kernel: veth5c29339: entered promiscuous mode
  156. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth5c29339) entered blocking state
  157. Jan 15 13:49:50 pve-ryzen kernel: docker0: port 1(veth5c29339) entered forwarding state
  158. Jan 15 13:49:50 pve-ryzen kernel: eth0: renamed from vethe46e17c
  159. Jan 15 13:50:03 pve-ryzen pveproxy[1203632]: worker exit
  160. Jan 15 13:50:04 pve-ryzen pveproxy[1585]: worker 1203632 finished
  161. Jan 15 13:50:04 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  162. Jan 15 13:50:04 pve-ryzen pveproxy[1585]: worker 1275417 started
  163. Jan 15 13:51:39 pve-ryzen pvedaemon[1175276]: worker exit
  164. Jan 15 13:51:40 pve-ryzen pvedaemon[1577]: worker 1175276 finished
  165. Jan 15 13:51:40 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  166. Jan 15 13:51:40 pve-ryzen pvedaemon[1577]: worker 1281297 started
  167. Jan 15 13:52:14 pve-ryzen pveproxy[1214578]: worker exit
  168. Jan 15 13:52:15 pve-ryzen pveproxy[1585]: worker 1214578 finished
  169. Jan 15 13:52:15 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  170. Jan 15 13:52:15 pve-ryzen pveproxy[1585]: worker 1283337 started
  171. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(veth5c29339) entered disabled state
  172. Jan 15 13:54:51 pve-ryzen kernel: vethe46e17c: renamed from eth0
  173. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(veth5c29339) entered disabled state
  174. Jan 15 13:54:51 pve-ryzen kernel: veth5c29339 (unregistering): left allmulticast mode
  175. Jan 15 13:54:51 pve-ryzen kernel: veth5c29339 (unregistering): left promiscuous mode
  176. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(veth5c29339) entered disabled state
  177. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered blocking state
  178. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered disabled state
  179. Jan 15 13:54:51 pve-ryzen kernel: vethc2a1063: entered allmulticast mode
  180. Jan 15 13:54:51 pve-ryzen kernel: vethc2a1063: entered promiscuous mode
  181. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered blocking state
  182. Jan 15 13:54:51 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered forwarding state
  183. Jan 15 13:54:51 pve-ryzen kernel: eth0: renamed from veth5d49f4c
  184. Jan 15 13:55:26 pve-ryzen pvedaemon[1219300]: <root@pam> successful auth for user 'root@pam'
  185. Jan 15 13:59:36 pve-ryzen pveproxy[1236318]: worker exit
  186. Jan 15 13:59:37 pve-ryzen pveproxy[1585]: worker 1236318 finished
  187. Jan 15 13:59:37 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  188. Jan 15 13:59:37 pve-ryzen pveproxy[1585]: worker 1310143 started
  189. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered disabled state
  190. Jan 15 13:59:52 pve-ryzen kernel: veth5d49f4c: renamed from eth0
  191. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered disabled state
  192. Jan 15 13:59:52 pve-ryzen kernel: vethc2a1063 (unregistering): left allmulticast mode
  193. Jan 15 13:59:52 pve-ryzen kernel: vethc2a1063 (unregistering): left promiscuous mode
  194. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethc2a1063) entered disabled state
  195. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered blocking state
  196. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered disabled state
  197. Jan 15 13:59:52 pve-ryzen kernel: vethe4da875: entered allmulticast mode
  198. Jan 15 13:59:52 pve-ryzen kernel: vethe4da875: entered promiscuous mode
  199. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered blocking state
  200. Jan 15 13:59:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered forwarding state
  201. Jan 15 13:59:52 pve-ryzen kernel: eth0: renamed from veth516701f
  202. Jan 15 14:03:05 pve-ryzen pvedaemon[1219300]: <root@pam> successful auth for user 'root@pam'
  203. Jan 15 14:04:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered disabled state
  204. Jan 15 14:04:52 pve-ryzen kernel: veth516701f: renamed from eth0
  205. Jan 15 14:04:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered disabled state
  206. Jan 15 14:04:52 pve-ryzen kernel: vethe4da875 (unregistering): left allmulticast mode
  207. Jan 15 14:04:52 pve-ryzen kernel: vethe4da875 (unregistering): left promiscuous mode
  208. Jan 15 14:04:52 pve-ryzen kernel: docker0: port 1(vethe4da875) entered disabled state
  209. Jan 15 14:04:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered blocking state
  210. Jan 15 14:04:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered disabled state
  211. Jan 15 14:04:53 pve-ryzen kernel: veth83b50d9: entered allmulticast mode
  212. Jan 15 14:04:53 pve-ryzen kernel: veth83b50d9: entered promiscuous mode
  213. Jan 15 14:04:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered blocking state
  214. Jan 15 14:04:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered forwarding state
  215. Jan 15 14:04:53 pve-ryzen kernel: eth0: renamed from veth7874fbf
  216. Jan 15 14:08:03 pve-ryzen pvedaemon[1219300]: worker exit
  217. Jan 15 14:08:04 pve-ryzen pvedaemon[1577]: worker 1219300 finished
  218. Jan 15 14:08:04 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  219. Jan 15 14:08:04 pve-ryzen pvedaemon[1577]: worker 1340356 started
  220. Jan 15 14:08:45 pve-ryzen pveproxy[1275417]: worker exit
  221. Jan 15 14:08:45 pve-ryzen pveproxy[1585]: worker 1275417 finished
  222. Jan 15 14:08:45 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  223. Jan 15 14:08:45 pve-ryzen pveproxy[1585]: worker 1342733 started
  224. Jan 15 14:09:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered disabled state
  225. Jan 15 14:09:53 pve-ryzen kernel: veth7874fbf: renamed from eth0
  226. Jan 15 14:09:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered disabled state
  227. Jan 15 14:09:53 pve-ryzen kernel: veth83b50d9 (unregistering): left allmulticast mode
  228. Jan 15 14:09:53 pve-ryzen kernel: veth83b50d9 (unregistering): left promiscuous mode
  229. Jan 15 14:09:53 pve-ryzen kernel: docker0: port 1(veth83b50d9) entered disabled state
  230. Jan 15 14:09:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered blocking state
  231. Jan 15 14:09:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered disabled state
  232. Jan 15 14:09:54 pve-ryzen kernel: veth12795f0: entered allmulticast mode
  233. Jan 15 14:09:54 pve-ryzen kernel: veth12795f0: entered promiscuous mode
  234. Jan 15 14:09:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered blocking state
  235. Jan 15 14:09:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered forwarding state
  236. Jan 15 14:09:54 pve-ryzen kernel: eth0: renamed from veth7689e80
  237. Jan 15 14:11:26 pve-ryzen pvedaemon[1281297]: <root@pam> successful auth for user 'root@pam'
  238. Jan 15 14:13:19 pve-ryzen pveproxy[1283337]: worker exit
  239. Jan 15 14:13:19 pve-ryzen pveproxy[1585]: worker 1283337 finished
  240. Jan 15 14:13:19 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  241. Jan 15 14:13:19 pve-ryzen pveproxy[1585]: worker 1359087 started
  242. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered disabled state
  243. Jan 15 14:14:54 pve-ryzen kernel: veth7689e80: renamed from eth0
  244. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered disabled state
  245. Jan 15 14:14:54 pve-ryzen kernel: veth12795f0 (unregistering): left allmulticast mode
  246. Jan 15 14:14:54 pve-ryzen kernel: veth12795f0 (unregistering): left promiscuous mode
  247. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth12795f0) entered disabled state
  248. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered blocking state
  249. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered disabled state
  250. Jan 15 14:14:54 pve-ryzen kernel: veth40cbfb2: entered allmulticast mode
  251. Jan 15 14:14:54 pve-ryzen kernel: veth40cbfb2: entered promiscuous mode
  252. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered blocking state
  253. Jan 15 14:14:54 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered forwarding state
  254. Jan 15 14:14:55 pve-ryzen kernel: eth0: renamed from vethece688c
  255. Jan 15 14:17:01 pve-ryzen CRON[1372424]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
  256. Jan 15 14:17:01 pve-ryzen CRON[1372425]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
  257. Jan 15 14:17:01 pve-ryzen CRON[1372424]: pam_unix(cron:session): session closed for user root
  258. Jan 15 14:18:05 pve-ryzen pvedaemon[1247687]: <root@pam> successful auth for user 'root@pam'
  259. Jan 15 14:18:11 pve-ryzen pvedaemon[1247687]: worker exit
  260. Jan 15 14:18:11 pve-ryzen pvedaemon[1577]: worker 1247687 finished
  261. Jan 15 14:18:11 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  262. Jan 15 14:18:11 pve-ryzen pvedaemon[1577]: worker 1376440 started
  263. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered disabled state
  264. Jan 15 14:19:55 pve-ryzen kernel: vethece688c: renamed from eth0
  265. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered disabled state
  266. Jan 15 14:19:55 pve-ryzen kernel: veth40cbfb2 (unregistering): left allmulticast mode
  267. Jan 15 14:19:55 pve-ryzen kernel: veth40cbfb2 (unregistering): left promiscuous mode
  268. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40cbfb2) entered disabled state
  269. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered blocking state
  270. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered disabled state
  271. Jan 15 14:19:55 pve-ryzen kernel: veth40f4f31: entered allmulticast mode
  272. Jan 15 14:19:55 pve-ryzen kernel: veth40f4f31: entered promiscuous mode
  273. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered blocking state
  274. Jan 15 14:19:55 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered forwarding state
  275. Jan 15 14:19:56 pve-ryzen kernel: eth0: renamed from vethe6fc71b
  276. Jan 15 14:20:26 pve-ryzen pveproxy[1310143]: worker exit
  277. Jan 15 14:20:26 pve-ryzen pveproxy[1585]: worker 1310143 finished
  278. Jan 15 14:20:26 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  279. Jan 15 14:20:26 pve-ryzen pveproxy[1585]: worker 1384520 started
  280. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered disabled state
  281. Jan 15 14:24:56 pve-ryzen kernel: vethe6fc71b: renamed from eth0
  282. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered disabled state
  283. Jan 15 14:24:56 pve-ryzen kernel: veth40f4f31 (unregistering): left allmulticast mode
  284. Jan 15 14:24:56 pve-ryzen kernel: veth40f4f31 (unregistering): left promiscuous mode
  285. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth40f4f31) entered disabled state
  286. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered blocking state
  287. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered disabled state
  288. Jan 15 14:24:56 pve-ryzen kernel: veth9c87cbb: entered allmulticast mode
  289. Jan 15 14:24:56 pve-ryzen kernel: veth9c87cbb: entered promiscuous mode
  290. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered blocking state
  291. Jan 15 14:24:56 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered forwarding state
  292. Jan 15 14:24:56 pve-ryzen kernel: eth0: renamed from veth0cd3d9c
  293. Jan 15 14:25:11 pve-ryzen pvedaemon[1281297]: worker exit
  294. Jan 15 14:25:11 pve-ryzen pvedaemon[1577]: worker 1281297 finished
  295. Jan 15 14:25:11 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  296. Jan 15 14:25:11 pve-ryzen pvedaemon[1577]: worker 1401550 started
  297. Jan 15 14:26:26 pve-ryzen pvedaemon[1340356]: <root@pam> successful auth for user 'root@pam'
  298. Jan 15 14:28:21 pve-ryzen pveproxy[1342733]: worker exit
  299. Jan 15 14:28:21 pve-ryzen pveproxy[1585]: worker 1342733 finished
  300. Jan 15 14:28:21 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  301. Jan 15 14:28:21 pve-ryzen pveproxy[1585]: worker 1412781 started
  302. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered disabled state
  303. Jan 15 14:29:57 pve-ryzen kernel: veth0cd3d9c: renamed from eth0
  304. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered disabled state
  305. Jan 15 14:29:57 pve-ryzen kernel: veth9c87cbb (unregistering): left allmulticast mode
  306. Jan 15 14:29:57 pve-ryzen kernel: veth9c87cbb (unregistering): left promiscuous mode
  307. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth9c87cbb) entered disabled state
  308. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered blocking state
  309. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered disabled state
  310. Jan 15 14:29:57 pve-ryzen kernel: veth8f7bd20: entered allmulticast mode
  311. Jan 15 14:29:57 pve-ryzen kernel: veth8f7bd20: entered promiscuous mode
  312. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered blocking state
  313. Jan 15 14:29:57 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered forwarding state
  314. Jan 15 14:29:57 pve-ryzen kernel: eth0: renamed from veth2bcb066
  315. Jan 15 14:33:07 pve-ryzen pveproxy[1359087]: worker exit
  316. Jan 15 14:33:07 pve-ryzen pveproxy[1585]: worker 1359087 finished
  317. Jan 15 14:33:07 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  318. Jan 15 14:33:07 pve-ryzen pveproxy[1585]: worker 1429899 started
  319. Jan 15 14:34:05 pve-ryzen pvedaemon[1376440]: <root@pam> successful auth for user 'root@pam'
  320. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered disabled state
  321. Jan 15 14:34:58 pve-ryzen kernel: veth2bcb066: renamed from eth0
  322. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered disabled state
  323. Jan 15 14:34:58 pve-ryzen kernel: veth8f7bd20 (unregistering): left allmulticast mode
  324. Jan 15 14:34:58 pve-ryzen kernel: veth8f7bd20 (unregistering): left promiscuous mode
  325. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth8f7bd20) entered disabled state
  326. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered blocking state
  327. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered disabled state
  328. Jan 15 14:34:58 pve-ryzen kernel: veth7fc2c51: entered allmulticast mode
  329. Jan 15 14:34:58 pve-ryzen kernel: veth7fc2c51: entered promiscuous mode
  330. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered blocking state
  331. Jan 15 14:34:58 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered forwarding state
  332. Jan 15 14:34:58 pve-ryzen kernel: eth0: renamed from veth4c7469c
  333. Jan 15 14:39:35 pve-ryzen smartd[1232]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66
  334. Jan 15 14:39:53 pve-ryzen pvedaemon[1340356]: worker exit
  335. Jan 15 14:39:53 pve-ryzen pvedaemon[1577]: worker 1340356 finished
  336. Jan 15 14:39:53 pve-ryzen pvedaemon[1577]: starting 1 worker(s)
  337. Jan 15 14:39:53 pve-ryzen pvedaemon[1577]: worker 1454298 started
  338. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered disabled state
  339. Jan 15 14:39:59 pve-ryzen kernel: veth4c7469c: renamed from eth0
  340. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered disabled state
  341. Jan 15 14:39:59 pve-ryzen kernel: veth7fc2c51 (unregistering): left allmulticast mode
  342. Jan 15 14:39:59 pve-ryzen kernel: veth7fc2c51 (unregistering): left promiscuous mode
  343. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth7fc2c51) entered disabled state
  344. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth186112a) entered blocking state
  345. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth186112a) entered disabled state
  346. Jan 15 14:39:59 pve-ryzen kernel: veth186112a: entered allmulticast mode
  347. Jan 15 14:39:59 pve-ryzen kernel: veth186112a: entered promiscuous mode
  348. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth186112a) entered blocking state
  349. Jan 15 14:39:59 pve-ryzen kernel: docker0: port 1(veth186112a) entered forwarding state
  350. Jan 15 14:39:59 pve-ryzen kernel: eth0: renamed from vethee2a3f8
  351. Jan 15 14:40:33 pve-ryzen pveproxy[1384520]: worker exit
  352. Jan 15 14:40:33 pve-ryzen pveproxy[1585]: worker 1384520 finished
  353. Jan 15 14:40:33 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  354. Jan 15 14:40:33 pve-ryzen pveproxy[1585]: worker 1456833 started
  355. Jan 15 14:41:44 pve-ryzen pvedaemon[1401550]: <root@pam> successful auth for user 'root@pam'
  356. Jan 15 14:42:19 pve-ryzen pvedaemon[1401550]: <root@pam> starting task UPID:pve-ryzen:00165302:02B46733:65A5363B:vzdump::root@pam:
  357. Jan 15 14:42:19 pve-ryzen pvedaemon[1463042]: INFO: starting new backup job: vzdump 101 103 100 105 --mailnotification failure --mode snapshot --node pve-ryzen --mailto [email protected] --storage truenas --compress zstd --all 0 --notes-template '{{guestname}}'
  358. Jan 15 14:42:19 pve-ryzen pvedaemon[1463042]: INFO: Starting Backup of VM 100 (lxc)
  359. Jan 15 14:42:19 pve-ryzen dmeventd[663]: No longer monitoring thin pool pve-data-tpool.
  360. Jan 15 14:42:19 pve-ryzen dmeventd[663]: Monitoring thin pool pve-data-tpool.
  361. Jan 15 14:42:20 pve-ryzen kernel: EXT4-fs (dm-32): write access unavailable, skipping orphan cleanup
  362. Jan 15 14:42:20 pve-ryzen kernel: EXT4-fs (dm-32): mounted filesystem db8a37a6-4cca-4ea1-98b9-4add6b612ccb ro without journal. Quota mode: none.
  363. Jan 15 14:42:48 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  364. Jan 15 14:42:48 pve-ryzen pvestatd[1549]: status update time (10.465 seconds)
  365. Jan 15 14:42:58 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  366. Jan 15 14:42:58 pve-ryzen pvestatd[1549]: status update time (10.468 seconds)
  367. Jan 15 14:43:09 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  368. Jan 15 14:43:09 pve-ryzen pvestatd[1549]: status update time (10.466 seconds)
  369. Jan 15 14:43:19 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  370. Jan 15 14:43:19 pve-ryzen pvestatd[1549]: status update time (10.480 seconds)
  371. Jan 15 14:43:30 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  372. Jan 15 14:43:30 pve-ryzen pvestatd[1549]: status update time (10.453 seconds)
  373. Jan 15 14:43:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  374. Jan 15 14:43:36 pve-ryzen pvestatd[1549]: status update time (5.950 seconds)
  375. Jan 15 14:43:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  376. Jan 15 14:43:46 pve-ryzen pvestatd[1549]: status update time (6.595 seconds)
  377. Jan 15 14:43:57 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  378. Jan 15 14:43:57 pve-ryzen pvestatd[1549]: status update time (6.600 seconds)
  379. Jan 15 14:44:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  380. Jan 15 14:44:07 pve-ryzen pvestatd[1549]: status update time (6.597 seconds)
  381. Jan 15 14:44:16 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  382. Jan 15 14:44:16 pve-ryzen pvestatd[1549]: status update time (6.586 seconds)
  383. Jan 15 14:44:26 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  384. Jan 15 14:44:27 pve-ryzen pvestatd[1549]: status update time (6.596 seconds)
  385. Jan 15 14:44:36 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  386. Jan 15 14:44:36 pve-ryzen pvestatd[1549]: status update time (6.035 seconds)
  387. Jan 15 14:44:45 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  388. Jan 15 14:44:45 pve-ryzen pvestatd[1549]: status update time (5.217 seconds)
  389. Jan 15 14:44:54 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  390. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth186112a) entered disabled state
  391. Jan 15 14:45:00 pve-ryzen kernel: vethee2a3f8: renamed from eth0
  392. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth186112a) entered disabled state
  393. Jan 15 14:45:00 pve-ryzen kernel: veth186112a (unregistering): left allmulticast mode
  394. Jan 15 14:45:00 pve-ryzen kernel: veth186112a (unregistering): left promiscuous mode
  395. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth186112a) entered disabled state
  396. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth260b902) entered blocking state
  397. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth260b902) entered disabled state
  398. Jan 15 14:45:00 pve-ryzen kernel: veth260b902: entered allmulticast mode
  399. Jan 15 14:45:00 pve-ryzen kernel: veth260b902: entered promiscuous mode
  400. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth260b902) entered blocking state
  401. Jan 15 14:45:00 pve-ryzen kernel: docker0: port 1(veth260b902) entered forwarding state
  402. Jan 15 14:45:00 pve-ryzen kernel: eth0: renamed from veth573dd1e
  403. Jan 15 14:45:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  404. Jan 15 14:45:07 pve-ryzen pvestatd[1549]: status update time (6.104 seconds)
  405. Jan 15 14:45:16 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  406. Jan 15 14:45:16 pve-ryzen pvestatd[1549]: status update time (5.383 seconds)
  407. Jan 15 14:45:25 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  408. Jan 15 14:45:25 pve-ryzen pvestatd[1549]: status update time (5.262 seconds)
  409. Jan 15 14:45:32 pve-ryzen kernel: INFO: task zstd:1463251 blocked for more than 120 seconds.
  410. Jan 15 14:45:32 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  411. Jan 15 14:45:32 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  412. Jan 15 14:45:32 pve-ryzen kernel: task:zstd state:D stack:0 pid:1463251 ppid:1463249 flags:0x00004002
  413. Jan 15 14:45:32 pve-ryzen kernel: Call Trace:
  414. Jan 15 14:45:32 pve-ryzen kernel: <TASK>
  415. Jan 15 14:45:32 pve-ryzen kernel: __schedule+0x3fd/0x1450
  416. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  417. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  418. Jan 15 14:45:32 pve-ryzen kernel: ? nfs_pageio_complete+0xee/0x140 [nfs]
  419. Jan 15 14:45:32 pve-ryzen kernel: schedule+0x63/0x110
  420. Jan 15 14:45:32 pve-ryzen kernel: io_schedule+0x46/0x80
  421. Jan 15 14:45:32 pve-ryzen kernel: folio_wait_bit_common+0x136/0x330
  422. Jan 15 14:45:32 pve-ryzen kernel: ? __pfx_wake_page_function+0x10/0x10
  423. Jan 15 14:45:32 pve-ryzen kernel: folio_wait_bit+0x18/0x30
  424. Jan 15 14:45:32 pve-ryzen kernel: folio_wait_writeback+0x2c/0xa0
  425. Jan 15 14:45:32 pve-ryzen kernel: __filemap_fdatawait_range+0x90/0x100
  426. Jan 15 14:45:32 pve-ryzen kernel: filemap_write_and_wait_range+0x94/0xc0
  427. Jan 15 14:45:32 pve-ryzen kernel: nfs_wb_all+0x27/0x130 [nfs]
  428. Jan 15 14:45:32 pve-ryzen kernel: nfs4_file_flush+0x7e/0xe0 [nfsv4]
  429. Jan 15 14:45:32 pve-ryzen kernel: filp_close+0x38/0xa0
  430. Jan 15 14:45:32 pve-ryzen kernel: close_fd+0x55/0x70
  431. Jan 15 14:45:32 pve-ryzen kernel: __x64_sys_close+0x11/0x50
  432. Jan 15 14:45:32 pve-ryzen kernel: do_syscall_64+0x5b/0x90
  433. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  434. Jan 15 14:45:32 pve-ryzen kernel: ? __f_unlock_pos+0x12/0x20
  435. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  436. Jan 15 14:45:32 pve-ryzen kernel: ? ksys_write+0xe6/0x100
  437. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  438. Jan 15 14:45:32 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  439. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  440. Jan 15 14:45:32 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  441. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  442. Jan 15 14:45:32 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  443. Jan 15 14:45:32 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  444. Jan 15 14:45:32 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  445. Jan 15 14:45:32 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  446. Jan 15 14:45:32 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  447. Jan 15 14:45:32 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  448. Jan 15 14:45:32 pve-ryzen kernel: RIP: 0033:0x7efce44ffc57
  449. Jan 15 14:45:32 pve-ryzen kernel: RSP: 002b:00007fffa6317f68 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
  450. Jan 15 14:45:32 pve-ryzen kernel: RAX: ffffffffffffffda RBX: 00007efce45d6760 RCX: 00007efce44ffc57
  451. Jan 15 14:45:32 pve-ryzen kernel: RDX: 00007efce45d19e0 RSI: 00007efcd0000b70 RDI: 0000000000000001
  452. Jan 15 14:45:32 pve-ryzen kernel: RBP: 00007efce45d25e0 R08: 0000000000000000 R09: 0000000000000000
  453. Jan 15 14:45:32 pve-ryzen kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
  454. Jan 15 14:45:32 pve-ryzen kernel: R13: 0000000000000002 R14: 000055aa32f3c018 R15: 00000000db256800
  455. Jan 15 14:45:32 pve-ryzen kernel: </TASK>
  456. Jan 15 14:45:34 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  457. Jan 15 14:45:36 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  458. Jan 15 14:45:36 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  459. Jan 15 14:45:37 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  460. Jan 15 14:45:37 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  461. Jan 15 14:45:40 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  462. Jan 15 14:45:40 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  463. Jan 15 14:45:42 pve-ryzen kernel: nfs: server not responding, timed out
  464. Jan 15 14:45:43 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  465. Jan 15 14:45:43 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  466. Jan 15 14:45:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  467. Jan 15 14:45:46 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  468. Jan 15 14:45:46 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  469. Jan 15 14:45:46 pve-ryzen pvestatd[1549]: status update time (6.271 seconds)
  470. Jan 15 14:45:49 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  471. Jan 15 14:45:49 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  472. Jan 15 14:45:52 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  473. Jan 15 14:45:52 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  474. Jan 15 14:45:56 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  475. Jan 15 14:45:56 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  476. Jan 15 14:45:56 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  477. Jan 15 14:45:56 pve-ryzen pvestatd[1549]: status update time (5.408 seconds)
  478. Jan 15 14:45:59 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  479. Jan 15 14:45:59 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  480. Jan 15 14:46:02 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  481. Jan 15 14:46:02 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  482. Jan 15 14:46:03 pve-ryzen kernel: nfs: server not responding, timed out
  483. Jan 15 14:46:04 pve-ryzen kernel: nfs: server not responding, timed out
  484. Jan 15 14:46:05 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  485. Jan 15 14:46:05 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  486. Jan 15 14:46:05 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  487. Jan 15 14:46:05 pve-ryzen pvestatd[1549]: status update time (5.029 seconds)
  488. Jan 15 14:46:08 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  489. Jan 15 14:46:08 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  490. Jan 15 14:46:09 pve-ryzen kernel: nfs: server not responding, timed out
  491. Jan 15 14:46:11 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  492. Jan 15 14:46:11 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  493. Jan 15 14:46:14 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  494. Jan 15 14:46:14 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  495. Jan 15 14:46:14 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  496. Jan 15 14:46:17 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  497. Jan 15 14:46:20 pve-ryzen kernel: nfs: server 192.168.1.39 not responding, still trying
  498. Jan 15 14:46:26 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  499. Jan 15 14:46:26 pve-ryzen pvestatd[1549]: status update time (6.275 seconds)
  500. Jan 15 14:46:34 pve-ryzen kernel: nfs: server not responding, timed out
  501. Jan 15 14:46:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  502. Jan 15 14:46:36 pve-ryzen pvestatd[1549]: status update time (5.401 seconds)
  503. Jan 15 14:46:45 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  504. Jan 15 14:46:45 pve-ryzen pvestatd[1549]: status update time (5.031 seconds)
  505. Jan 15 14:46:46 pve-ryzen kernel: nfs: server not responding, timed out
  506. Jan 15 14:46:54 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  507. Jan 15 14:47:06 pve-ryzen kernel: nfs: server not responding, timed out
  508. Jan 15 14:47:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  509. Jan 15 14:47:06 pve-ryzen pvestatd[1549]: status update time (6.100 seconds)
  510. Jan 15 14:47:06 pve-ryzen kernel: nfs: server not responding, timed out
  511. Jan 15 14:47:07 pve-ryzen kernel: traps: mariadbd[1470235] general protection fault ip:7f1f7184d898 sp:7f1f5c0db730 error:0 in libc.so.6[7f1f7184d000+195000]
  512. Jan 15 14:47:15 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  513. Jan 15 14:47:16 pve-ryzen pvestatd[1549]: status update time (5.208 seconds)
  514. Jan 15 14:47:25 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  515. Jan 15 14:47:25 pve-ryzen pvestatd[1549]: status update time (5.393 seconds)
  516. Jan 15 14:47:33 pve-ryzen kernel: INFO: task zstd:1463251 blocked for more than 241 seconds.
  517. Jan 15 14:47:33 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  518. Jan 15 14:47:33 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  519. Jan 15 14:47:33 pve-ryzen kernel: task:zstd state:D stack:0 pid:1463251 ppid:1463249 flags:0x00004002
  520. Jan 15 14:47:33 pve-ryzen kernel: Call Trace:
  521. Jan 15 14:47:33 pve-ryzen kernel: <TASK>
  522. Jan 15 14:47:33 pve-ryzen kernel: __schedule+0x3fd/0x1450
  523. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  524. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  525. Jan 15 14:47:33 pve-ryzen kernel: ? nfs_pageio_complete+0xee/0x140 [nfs]
  526. Jan 15 14:47:33 pve-ryzen kernel: schedule+0x63/0x110
  527. Jan 15 14:47:33 pve-ryzen kernel: io_schedule+0x46/0x80
  528. Jan 15 14:47:33 pve-ryzen kernel: folio_wait_bit_common+0x136/0x330
  529. Jan 15 14:47:33 pve-ryzen kernel: ? __pfx_wake_page_function+0x10/0x10
  530. Jan 15 14:47:33 pve-ryzen kernel: folio_wait_bit+0x18/0x30
  531. Jan 15 14:47:33 pve-ryzen kernel: folio_wait_writeback+0x2c/0xa0
  532. Jan 15 14:47:33 pve-ryzen kernel: __filemap_fdatawait_range+0x90/0x100
  533. Jan 15 14:47:33 pve-ryzen kernel: filemap_write_and_wait_range+0x94/0xc0
  534. Jan 15 14:47:33 pve-ryzen kernel: nfs_wb_all+0x27/0x130 [nfs]
  535. Jan 15 14:47:33 pve-ryzen kernel: nfs4_file_flush+0x7e/0xe0 [nfsv4]
  536. Jan 15 14:47:33 pve-ryzen kernel: filp_close+0x38/0xa0
  537. Jan 15 14:47:33 pve-ryzen kernel: close_fd+0x55/0x70
  538. Jan 15 14:47:33 pve-ryzen kernel: __x64_sys_close+0x11/0x50
  539. Jan 15 14:47:33 pve-ryzen kernel: do_syscall_64+0x5b/0x90
  540. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  541. Jan 15 14:47:33 pve-ryzen kernel: ? __f_unlock_pos+0x12/0x20
  542. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  543. Jan 15 14:47:33 pve-ryzen kernel: ? ksys_write+0xe6/0x100
  544. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  545. Jan 15 14:47:33 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  546. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  547. Jan 15 14:47:33 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  548. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  549. Jan 15 14:47:33 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  550. Jan 15 14:47:33 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  551. Jan 15 14:47:33 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  552. Jan 15 14:47:33 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  553. Jan 15 14:47:33 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  554. Jan 15 14:47:33 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  555. Jan 15 14:47:33 pve-ryzen kernel: RIP: 0033:0x7efce44ffc57
  556. Jan 15 14:47:33 pve-ryzen kernel: RSP: 002b:00007fffa6317f68 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
  557. Jan 15 14:47:33 pve-ryzen kernel: RAX: ffffffffffffffda RBX: 00007efce45d6760 RCX: 00007efce44ffc57
  558. Jan 15 14:47:33 pve-ryzen kernel: RDX: 00007efce45d19e0 RSI: 00007efcd0000b70 RDI: 0000000000000001
  559. Jan 15 14:47:33 pve-ryzen kernel: RBP: 00007efce45d25e0 R08: 0000000000000000 R09: 0000000000000000
  560. Jan 15 14:47:33 pve-ryzen kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
  561. Jan 15 14:47:33 pve-ryzen kernel: R13: 0000000000000002 R14: 000055aa32f3c018 R15: 00000000db256800
  562. Jan 15 14:47:33 pve-ryzen kernel: </TASK>
  563. Jan 15 14:47:34 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  564. Jan 15 14:47:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  565. Jan 15 14:47:46 pve-ryzen pvestatd[1549]: status update time (6.479 seconds)
  566. Jan 15 14:47:55 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  567. Jan 15 14:47:56 pve-ryzen pvestatd[1549]: status update time (5.207 seconds)
  568. Jan 15 14:48:02 pve-ryzen kernel: nfs: server not responding, timed out
  569. Jan 15 14:48:05 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  570. Jan 15 14:48:05 pve-ryzen pvestatd[1549]: status update time (5.045 seconds)
  571. Jan 15 14:48:14 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  572. Jan 15 14:48:26 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  573. Jan 15 14:48:26 pve-ryzen pvestatd[1549]: status update time (6.484 seconds)
  574. Jan 15 14:48:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  575. Jan 15 14:48:35 pve-ryzen pvestatd[1549]: status update time (5.048 seconds)
  576. Jan 15 14:48:43 pve-ryzen kernel: nfs: server not responding, timed out
  577. Jan 15 14:48:44 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  578. Jan 15 14:48:54 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  579. Jan 15 14:49:03 pve-ryzen kernel: nfs: server not responding, timed out
  580. Jan 15 14:49:05 pve-ryzen kernel: nfs: server not responding, timed out
  581. Jan 15 14:49:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  582. Jan 15 14:49:06 pve-ryzen pvestatd[1549]: status update time (6.285 seconds)
  583. Jan 15 14:49:09 pve-ryzen kernel: nfs: server not responding, timed out
  584. Jan 15 14:49:15 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  585. Jan 15 14:49:16 pve-ryzen pvestatd[1549]: status update time (5.232 seconds)
  586. Jan 15 14:49:24 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  587. Jan 15 14:49:25 pve-ryzen pvestatd[1549]: status update time (5.200 seconds)
  588. Jan 15 14:49:34 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  589. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:15486 blocked for more than 120 seconds.
  590. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  591. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  592. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:15486 ppid:15438 flags:0x00004002
  593. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  594. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  595. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  596. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  597. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  598. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  599. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  600. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  601. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  602. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  603. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  604. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  605. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  606. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  607. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  608. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  609. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  610. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  611. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  612. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  613. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f7193ddbf
  614. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007ffd600324f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000007
  615. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffdfc RBX: 0000000000000000 RCX: 00007f1f7193ddbf
  616. Jan 15 14:49:34 pve-ryzen kernel: RDX: 00000000ffffffff RSI: 0000000000000003 RDI: 0000564c2629da88
  617. Jan 15 14:49:34 pve-ryzen kernel: RBP: 00007ffd600326b0 R08: 0000000000000000 R09: 00007ffd6003216f
  618. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000080000 R11: 0000000000000293 R12: 00007f1f714ee700
  619. Jan 15 14:49:34 pve-ryzen kernel: R13: 00007ffd600325f0 R14: 0000000000000027 R15: 0000000000000000
  620. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  621. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:16368 blocked for more than 120 seconds.
  622. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  623. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  624. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:16368 ppid:15438 flags:0x00004002
  625. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  626. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  627. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  628. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  629. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  630. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  631. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  632. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  633. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  634. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  635. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  636. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  637. Jan 15 14:49:34 pve-ryzen kernel: ? __x64_sys_futex+0x95/0x200
  638. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  639. Jan 15 14:49:34 pve-ryzen kernel: ? __secure_computing+0x89/0xf0
  640. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  641. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  642. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  643. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  644. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  645. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  646. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  647. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  648. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  649. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  650. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  651. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  652. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  653. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  654. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  655. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f718b6117
  656. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f7128db50 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
  657. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffdfc RBX: 0000000000000000 RCX: 00007f1f718b6117
  658. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 0000564c254d0c0c
  659. Jan 15 14:49:34 pve-ryzen kernel: RBP: 0000564c254d0be0 R08: 0000000000000000 R09: 00000000ffffffff
  660. Jan 15 14:49:34 pve-ryzen kernel: R10: 00007f1f7128dc90 R11: 0000000000000246 R12: 0000000000000000
  661. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000000000000000 R14: 0000564c254d0c0c R15: 0000000000315faf
  662. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  663. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:16377 blocked for more than 120 seconds.
  664. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  665. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  666. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:16377 ppid:15438 flags:0x00004002
  667. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  668. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  669. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  670. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  671. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  672. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  673. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  674. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  675. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  676. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  677. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  678. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  679. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  680. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  681. Jan 15 14:49:34 pve-ryzen kernel: ? sysvec_apic_timer_interrupt+0x4b/0xd0
  682. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  683. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f718b6117
  684. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f70a54b00 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
  685. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffdfc RBX: 0000000000000000 RCX: 00007f1f718b6117
  686. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 0000564c254431c8
  687. Jan 15 14:49:34 pve-ryzen kernel: RBP: 0000564c254431a0 R08: 0000000000000000 R09: 00000000ffffffff
  688. Jan 15 14:49:34 pve-ryzen kernel: R10: 00007f1f70a54c20 R11: 0000000000000246 R12: 0000000000000000
  689. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000000000000000 R14: 0000564c254431c8 R15: 0000000000007636
  690. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  691. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:16381 blocked for more than 120 seconds.
  692. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  693. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  694. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:16381 ppid:15438 flags:0x00004002
  695. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  696. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  697. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  698. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  699. Jan 15 14:49:34 pve-ryzen kernel: ? update_cfs_group+0x99/0xd0
  700. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  701. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  702. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  703. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  704. Jan 15 14:49:34 pve-ryzen kernel: ? raw_spin_rq_unlock+0x10/0x40
  705. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  706. Jan 15 14:49:34 pve-ryzen kernel: ? finish_task_switch.isra.0+0x85/0x2c0
  707. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  708. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  709. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  710. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  711. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  712. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  713. Jan 15 14:49:34 pve-ryzen kernel: ? do_futex+0x10f/0x200
  714. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  715. Jan 15 14:49:34 pve-ryzen kernel: ? __x64_sys_futex+0x95/0x200
  716. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  717. Jan 15 14:49:34 pve-ryzen kernel: ? __secure_computing+0x89/0xf0
  718. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  719. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  720. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  721. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  722. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  723. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  724. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  725. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  726. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  727. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  728. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  729. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  730. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f71943a7d
  731. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f57ffebe8 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
  732. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffffc RBX: 0000000000000000 RCX: 00007f1f71943a7d
  733. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000009
  734. Jan 15 14:49:34 pve-ryzen kernel: RBP: 0000564c25dca6a8 R08: 0000000000000000 R09: 0000000000000008
  735. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 00007f1f57ffec30
  736. Jan 15 14:49:34 pve-ryzen kernel: R13: 00007f1f57ffec78 R14: 00007f1f57ffec78 R15: 0000564c25dca780
  737. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  738. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:16386 blocked for more than 120 seconds.
  739. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  740. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  741. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:16386 ppid:15438 flags:0x00004002
  742. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  743. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  744. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  745. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  746. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  747. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  748. Jan 15 14:49:34 pve-ryzen kernel: ? __futex_unqueue+0x29/0x60
  749. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  750. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  751. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  752. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  753. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  754. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  755. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  756. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  757. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  758. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  759. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  760. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  761. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  762. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0xa5/0x190
  763. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  764. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  765. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  766. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  767. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  768. Jan 15 14:49:34 pve-ryzen kernel: ? sysvec_reschedule_ipi+0x7a/0x120
  769. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  770. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f718b6117
  771. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f16f4bb00 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
  772. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 00007f1f718b6117
  773. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 0000564c24b6012c
  774. Jan 15 14:49:34 pve-ryzen kernel: RBP: 0000564c24b60100 R08: 0000000000000000 R09: 00000000ffffffff
  775. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
  776. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000000000000000 R14: 0000000000000023 R15: 0000564c24b6012c
  777. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  778. Jan 15 14:49:34 pve-ryzen kernel: INFO: task iou-wrk-15486:16435 blocked for more than 120 seconds.
  779. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  780. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  781. Jan 15 14:49:34 pve-ryzen kernel: task:iou-wrk-15486 state:D stack:0 pid:16435 ppid:15438 flags:0x00004000
  782. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  783. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  784. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  785. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  786. Jan 15 14:49:34 pve-ryzen kernel: ? try_to_wake_up+0x28d/0x5d0
  787. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  788. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  789. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  790. Jan 15 14:49:34 pve-ryzen kernel: ? kvfree_call_rcu+0x114/0x360
  791. Jan 15 14:49:34 pve-ryzen kernel: io_wq_worker+0x33a/0x3c0
  792. Jan 15 14:49:34 pve-ryzen kernel: ? __pfx_io_wq_worker+0x10/0x10
  793. Jan 15 14:49:34 pve-ryzen kernel: ret_from_fork+0x47/0x70
  794. Jan 15 14:49:34 pve-ryzen kernel: ? __pfx_io_wq_worker+0x10/0x10
  795. Jan 15 14:49:34 pve-ryzen kernel: ret_from_fork_asm+0x1b/0x30
  796. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x0
  797. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:0000000000000000 EFLAGS: 00000246 ORIG_RAX: 00000000000001aa
  798. Jan 15 14:49:34 pve-ryzen kernel: RAX: 0000000000000000 RBX: 0000564c25ddf4e0 RCX: 00007f1f71943a7d
  799. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000009
  800. Jan 15 14:49:34 pve-ryzen kernel: RBP: 00007ffd6002dcd0 R08: 0000000000000000 R09: 0000000000000008
  801. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000564c25dca6a8
  802. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000564c25dca780 R14: 0000000000004000 R15: 0000564c25ddf4e0
  803. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  804. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:17347 blocked for more than 120 seconds.
  805. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  806. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  807. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:17347 ppid:15438 flags:0x00004002
  808. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  809. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  810. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  811. Jan 15 14:49:34 pve-ryzen kernel: ? path_lookupat+0x97/0x1a0
  812. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  813. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  814. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  815. Jan 15 14:49:34 pve-ryzen kernel: ? __futex_unqueue+0x29/0x60
  816. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  817. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  818. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  819. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  820. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  821. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  822. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  823. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  824. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  825. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  826. Jan 15 14:49:34 pve-ryzen kernel: ? irqentry_exit_to_user_mode+0x17/0x20
  827. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  828. Jan 15 14:49:34 pve-ryzen kernel: ? irqentry_exit+0x43/0x50
  829. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  830. Jan 15 14:49:34 pve-ryzen kernel: ? exc_page_fault+0x94/0x1b0
  831. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  832. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f718b6117
  833. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f5c1beb20 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
  834. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 00007f1f718b6117
  835. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 0000564c24c10d0c
  836. Jan 15 14:49:34 pve-ryzen kernel: RBP: 0000564c24c10ce0 R08: 0000000000000000 R09: 00000000ffffffff
  837. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
  838. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000000000000000 R14: 0000000000000003 R15: 0000564c24c10d0c
  839. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  840. Jan 15 14:49:34 pve-ryzen kernel: INFO: task mariadbd:17411 blocked for more than 120 seconds.
  841. Jan 15 14:49:34 pve-ryzen kernel: Tainted: P O 6.5.11-7-pve #1
  842. Jan 15 14:49:34 pve-ryzen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  843. Jan 15 14:49:34 pve-ryzen kernel: task:mariadbd state:D stack:0 pid:17411 ppid:15438 flags:0x00004002
  844. Jan 15 14:49:34 pve-ryzen kernel: Call Trace:
  845. Jan 15 14:49:34 pve-ryzen kernel: <TASK>
  846. Jan 15 14:49:34 pve-ryzen kernel: __schedule+0x3fd/0x1450
  847. Jan 15 14:49:34 pve-ryzen kernel: ? psi_task_switch+0xd3/0x240
  848. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  849. Jan 15 14:49:34 pve-ryzen kernel: ? raw_spin_rq_unlock+0x10/0x40
  850. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  851. Jan 15 14:49:34 pve-ryzen kernel: schedule+0x63/0x110
  852. Jan 15 14:49:34 pve-ryzen kernel: do_exit+0x119/0xae0
  853. Jan 15 14:49:34 pve-ryzen kernel: do_group_exit+0x35/0x90
  854. Jan 15 14:49:34 pve-ryzen kernel: get_signal+0xa3b/0xa40
  855. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  856. Jan 15 14:49:34 pve-ryzen kernel: arch_do_signal_or_restart+0x42/0x280
  857. Jan 15 14:49:34 pve-ryzen kernel: exit_to_user_mode_prepare+0x11b/0x190
  858. Jan 15 14:49:34 pve-ryzen kernel: syscall_exit_to_user_mode+0x29/0x60
  859. Jan 15 14:49:34 pve-ryzen kernel: do_syscall_64+0x67/0x90
  860. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  861. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  862. Jan 15 14:49:34 pve-ryzen kernel: ? exit_to_user_mode_prepare+0x39/0x190
  863. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  864. Jan 15 14:49:34 pve-ryzen kernel: ? syscall_exit_to_user_mode+0x37/0x60
  865. Jan 15 14:49:34 pve-ryzen kernel: ? srso_alias_return_thunk+0x5/0x7f
  866. Jan 15 14:49:34 pve-ryzen kernel: ? do_syscall_64+0x67/0x90
  867. Jan 15 14:49:34 pve-ryzen kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  868. Jan 15 14:49:34 pve-ryzen kernel: RIP: 0033:0x7f1f7186821a
  869. Jan 15 14:49:34 pve-ryzen kernel: RSP: 002b:00007f1f5c173af0 EFLAGS: 00000293 ORIG_RAX: 0000000000000080
  870. Jan 15 14:49:34 pve-ryzen kernel: RAX: fffffffffffffffc RBX: 00007f1f5c173bd0 RCX: 00007f1f7186821a
  871. Jan 15 14:49:34 pve-ryzen kernel: RDX: 0000000000000000 RSI: 00007f1f5c173bd0 RDI: 00007f1f5c173b50
  872. Jan 15 14:49:34 pve-ryzen kernel: RBP: 00007f1f5c173ca0 R08: 0000000000000000 R09: 0000564c24c0b240
  873. Jan 15 14:49:34 pve-ryzen kernel: R10: 0000000000000008 R11: 0000000000000293 R12: 00007f1f5c173bd0
  874. Jan 15 14:49:34 pve-ryzen kernel: R13: 0000564c242e5bb0 R14: 0000564c24c0c6a0 R15: 000000008000002f
  875. Jan 15 14:49:34 pve-ryzen kernel: </TASK>
  876. Jan 15 14:49:34 pve-ryzen kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
  877. Jan 15 14:49:36 pve-ryzen kernel: nfs: server not responding, timed out
  878. Jan 15 14:49:46 pve-ryzen kernel: nfs: server not responding, timed out
  879. Jan 15 14:49:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  880. Jan 15 14:49:46 pve-ryzen pvestatd[1549]: status update time (6.470 seconds)
  881. Jan 15 14:49:55 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  882. Jan 15 14:49:55 pve-ryzen pvestatd[1549]: status update time (5.040 seconds)
  883. Jan 15 14:50:00 pve-ryzen kernel: docker0: port 1(veth260b902) entered disabled state
  884. Jan 15 14:50:00 pve-ryzen kernel: veth573dd1e: renamed from eth0
  885. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth260b902) entered disabled state
  886. Jan 15 14:50:01 pve-ryzen kernel: veth260b902 (unregistering): left allmulticast mode
  887. Jan 15 14:50:01 pve-ryzen kernel: veth260b902 (unregistering): left promiscuous mode
  888. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth260b902) entered disabled state
  889. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth836dde5) entered blocking state
  890. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth836dde5) entered disabled state
  891. Jan 15 14:50:01 pve-ryzen kernel: veth836dde5: entered allmulticast mode
  892. Jan 15 14:50:01 pve-ryzen kernel: veth836dde5: entered promiscuous mode
  893. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth836dde5) entered blocking state
  894. Jan 15 14:50:01 pve-ryzen kernel: docker0: port 1(veth836dde5) entered forwarding state
  895. Jan 15 14:50:01 pve-ryzen kernel: eth0: renamed from veth0ceb0aa
  896. Jan 15 14:50:04 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  897. Jan 15 14:50:05 pve-ryzen pvedaemon[1401550]: <root@pam> successful auth for user 'root@pam'
  898. Jan 15 14:50:06 pve-ryzen kernel: nfs: server not responding, timed out
  899. Jan 15 14:50:07 pve-ryzen kernel: nfs: server not responding, timed out
  900. Jan 15 14:50:14 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  901. Jan 15 14:50:26 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  902. Jan 15 14:50:26 pve-ryzen pvestatd[1549]: status update time (6.492 seconds)
  903. Jan 15 14:50:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  904. Jan 15 14:50:35 pve-ryzen pvestatd[1549]: status update time (5.213 seconds)
  905. Jan 15 14:50:44 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  906. Jan 15 14:50:53 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  907. Jan 15 14:51:02 pve-ryzen kernel: nfs: server not responding, timed out
  908. Jan 15 14:51:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  909. Jan 15 14:51:06 pve-ryzen pvestatd[1549]: status update time (6.103 seconds)
  910. Jan 15 14:51:15 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  911. Jan 15 14:51:15 pve-ryzen pvestatd[1549]: status update time (5.398 seconds)
  912. Jan 15 14:51:24 pve-ryzen pveproxy[1412781]: worker exit
  913. Jan 15 14:51:24 pve-ryzen pveproxy[1585]: worker 1412781 finished
  914. Jan 15 14:51:24 pve-ryzen pveproxy[1585]: starting 1 worker(s)
  915. Jan 15 14:51:24 pve-ryzen pveproxy[1585]: worker 1496898 started
  916. Jan 15 14:51:24 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  917. Jan 15 14:51:33 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  918. Jan 15 14:51:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  919. Jan 15 14:51:46 pve-ryzen pvestatd[1549]: status update time (6.458 seconds)
  920. Jan 15 14:51:48 pve-ryzen kernel: nfs: server not responding, timed out
  921. Jan 15 14:51:55 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  922. Jan 15 14:51:55 pve-ryzen pvestatd[1549]: status update time (5.040 seconds)
  923. Jan 15 14:52:03 pve-ryzen kernel: nfs: server not responding, timed out
  924. Jan 15 14:52:04 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  925. Jan 15 14:52:05 pve-ryzen kernel: nfs: server not responding, timed out
  926. Jan 15 14:52:09 pve-ryzen kernel: nfs: server not responding, timed out
  927. Jan 15 14:52:16 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  928. Jan 15 14:52:17 pve-ryzen pvestatd[1549]: status update time (6.470 seconds)
  929. Jan 15 14:52:26 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  930. Jan 15 14:52:26 pve-ryzen pvestatd[1549]: status update time (6.039 seconds)
  931. Jan 15 14:52:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  932. Jan 15 14:52:35 pve-ryzen pvestatd[1549]: status update time (5.212 seconds)
  933. Jan 15 14:52:36 pve-ryzen kernel: nfs: server not responding, timed out
  934. Jan 15 14:52:44 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  935. Jan 15 14:52:46 pve-ryzen kernel: nfs: server not responding, timed out
  936. Jan 15 14:52:56 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  937. Jan 15 14:52:57 pve-ryzen pvestatd[1549]: status update time (6.290 seconds)
  938. Jan 15 14:53:00 pve-ryzen kernel: nfs: server not responding, timed out
  939. Jan 15 14:53:06 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  940. Jan 15 14:53:06 pve-ryzen pvestatd[1549]: status update time (6.429 seconds)
  941. Jan 15 14:53:07 pve-ryzen kernel: nfs: server not responding, timed out
  942. Jan 15 14:53:09 pve-ryzen kernel: nfs: server not responding, timed out
  943. Jan 15 14:53:15 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  944. Jan 15 14:53:15 pve-ryzen pvestatd[1549]: status update time (5.194 seconds)
  945. Jan 15 14:53:24 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  946. Jan 15 14:53:36 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  947. Jan 15 14:53:37 pve-ryzen pvestatd[1549]: status update time (6.290 seconds)
  948. Jan 15 14:53:46 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  949. Jan 15 14:53:46 pve-ryzen pvestatd[1549]: status update time (6.031 seconds)
  950. Jan 15 14:53:55 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  951. Jan 15 14:53:55 pve-ryzen pvestatd[1549]: status update time (5.219 seconds)
  952. Jan 15 14:54:02 pve-ryzen kernel: nfs: server not responding, timed out
  953. Jan 15 14:54:04 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  954. Jan 15 14:54:16 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  955. Jan 15 14:54:16 pve-ryzen pvestatd[1549]: status update time (6.102 seconds)
  956. Jan 15 14:54:25 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  957. Jan 15 14:54:26 pve-ryzen pvestatd[1549]: status update time (5.394 seconds)
  958. Jan 15 14:54:35 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  959. Jan 15 14:54:35 pve-ryzen pvestatd[1549]: status update time (5.034 seconds)
  960. Jan 15 14:54:44 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  961. Jan 15 14:54:50 pve-ryzen kernel: nfs: server not responding, timed out
  962. Jan 15 14:54:56 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  963. Jan 15 14:54:56 pve-ryzen pvestatd[1549]: status update time (6.282 seconds)
  964. Jan 15 14:55:01 pve-ryzen kernel: docker0: port 1(veth836dde5) entered disabled state
  965. Jan 15 14:55:01 pve-ryzen kernel: veth0ceb0aa: renamed from eth0
  966. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(veth836dde5) entered disabled state
  967. Jan 15 14:55:02 pve-ryzen kernel: veth836dde5 (unregistering): left allmulticast mode
  968. Jan 15 14:55:02 pve-ryzen kernel: veth836dde5 (unregistering): left promiscuous mode
  969. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(veth836dde5) entered disabled state
  970. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(vethdf5f3e6) entered blocking state
  971. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(vethdf5f3e6) entered disabled state
  972. Jan 15 14:55:02 pve-ryzen kernel: vethdf5f3e6: entered allmulticast mode
  973. Jan 15 14:55:02 pve-ryzen kernel: vethdf5f3e6: entered promiscuous mode
  974. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(vethdf5f3e6) entered blocking state
  975. Jan 15 14:55:02 pve-ryzen kernel: docker0: port 1(vethdf5f3e6) entered forwarding state
  976. Jan 15 14:55:02 pve-ryzen kernel: eth0: renamed from veth966d627
  977. Jan 15 14:55:03 pve-ryzen kernel: nfs: server not responding, timed out
  978. Jan 15 14:55:05 pve-ryzen kernel: nfs: server not responding, timed out
  979. Jan 15 14:55:05 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  980. Jan 15 14:55:06 pve-ryzen pvestatd[1549]: status update time (5.399 seconds)
  981. Jan 15 14:55:09 pve-ryzen kernel: nfs: server not responding, timed out
  982. Jan 15 14:55:15 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  983. Jan 15 14:55:15 pve-ryzen pvestatd[1549]: status update time (5.029 seconds)
  984. Jan 15 14:55:24 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  985. Jan 15 14:55:36 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  986. Jan 15 14:55:36 pve-ryzen pvestatd[1549]: status update time (6.474 seconds)
  987. Jan 15 14:55:38 pve-ryzen kernel: nfs: server not responding, timed out
  988. Jan 15 14:55:45 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  989. Jan 15 14:55:45 pve-ryzen pvestatd[1549]: status update time (5.031 seconds)
  990. Jan 15 14:55:46 pve-ryzen kernel: nfs: server not responding, timed out
  991. Jan 15 14:55:49 pve-ryzen pvedaemon[1376440]: <root@pam> successful auth for user 'root@pam'
  992. Jan 15 14:55:55 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  993. Jan 15 14:56:00 pve-ryzen kernel: nfs: server not responding, timed out
  994. Jan 15 14:56:04 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  995. Jan 15 14:56:09 pve-ryzen kernel: nfs: server not responding, timed out
  996. Jan 15 14:56:10 pve-ryzen kernel: nfs: server not responding, timed out
  997. Jan 15 14:56:16 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  998. Jan 15 14:56:16 pve-ryzen pvestatd[1549]: status update time (6.296 seconds)
  999. Jan 15 14:56:25 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  1000. Jan 15 14:56:25 pve-ryzen pvestatd[1549]: status update time (5.212 seconds)
  1001. Jan 15 14:56:34 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
  1002. Jan 15 14:56:44 pve-ryzen pvestatd[1549]: storage 'truenas' is not online
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
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!