API tools faq
paste
Guest User

journal

a guest
Mar 5th, 2022
143
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.81 KB | None | 0 0
raw download clone embed print report
  1. Mar 05 11:37:38 pve8 pvedaemon[1195]: <root@pam> starting task UPID:pve8:00001222:0000D19F:62234B82:clusterjoin::root@pam:
  2.  
  3. Mar 05 11:37:38 pve8 systemd[1]: Stopping The Proxmox VE cluster filesystem...
  4.  
  5. Mar 05 11:37:38 pve8 pmxcfs[1083]: [main] notice: teardown filesystem
  6.  
  7. Mar 05 11:37:39 pve8 systemd[4219]: etc-pve.mount: Succeeded.
  8.  
  9. Mar 05 11:37:39 pve8 systemd[1]: etc-pve.mount: Succeeded.
  10.  
  11. Mar 05 11:37:40 pve8 pmxcfs[1083]: [main] notice: exit proxmox configuration filesystem (0)
  12.  
  13. Mar 05 11:37:40 pve8 systemd[1]: pve-cluster.service: Succeeded.
  14.  
  15. Mar 05 11:37:40 pve8 systemd[1]: Stopped The Proxmox VE cluster filesystem.
  16.  
  17. Mar 05 11:37:40 pve8 systemd[1]: Starting Corosync Cluster Engine...
  18.  
  19. Mar 05 11:37:40 pve8 systemd[1]: Starting The Proxmox VE cluster filesystem...
  20.  
  21. Mar 05 11:37:40 pve8 corosync[4672]: [MAIN ] Corosync Cluster Engine 3.1.5 starting up
  22.  
  23. Mar 05 11:37:40 pve8 corosync[4672]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vqsim nozzle sn>
  24.  
  25. Mar 05 11:37:40 pve8 pmxcfs[4674]: [quorum] crit: quorum_initialize failed: 2
  26.  
  27. Mar 05 11:37:40 pve8 pmxcfs[4674]: [quorum] crit: can't initialize service
  28.  
  29. Mar 05 11:37:40 pve8 pmxcfs[4674]: [confdb] crit: cmap_initialize failed: 2
  30.  
  31. Mar 05 11:37:40 pve8 pmxcfs[4674]: [confdb] crit: can't initialize service
  32.  
  33. Mar 05 11:37:40 pve8 pmxcfs[4674]: [dcdb] crit: cpg_initialize failed: 2
  34.  
  35. Mar 05 11:37:40 pve8 pmxcfs[4674]: [dcdb] crit: can't initialize service
  36.  
  37. Mar 05 11:37:40 pve8 pmxcfs[4674]: [status] crit: cpg_initialize failed: 2
  38.  
  39. Mar 05 11:37:40 pve8 pmxcfs[4674]: [status] crit: can't initialize service
  40.  
  41. Mar 05 11:37:40 pve8 corosync[4672]: [TOTEM ] Initializing transport (Kronosnet).
  42.  
  43. Mar 05 11:37:40 pve8 kernel: sctp: Hash tables configured (bind 256/256)
  44.  
  45. Mar 05 11:37:40 pve8 corosync[4672]: [TOTEM ] totemknet initialized
  46.  
  47. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypt>
  48.  
  49. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync configuration map access [0]
  50.  
  51. Mar 05 11:37:40 pve8 corosync[4672]: [QB ] server name: cmap
  52.  
  53. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync configuration service [1]
  54.  
  55. Mar 05 11:37:40 pve8 corosync[4672]: [QB ] server name: cfg
  56.  
  57. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
  58.  
  59. Mar 05 11:37:40 pve8 corosync[4672]: [QB ] server name: cpg
  60.  
  61. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync profile loading service [4]
  62.  
  63. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
  64.  
  65. Mar 05 11:37:40 pve8 corosync[4672]: [WD ] Watchdog not enabled by configuration
  66.  
  67. Mar 05 11:37:40 pve8 corosync[4672]: [WD ] resource load_15min missing a recovery key.
  68.  
  69. Mar 05 11:37:40 pve8 corosync[4672]: [WD ] resource memory_used missing a recovery key.
  70.  
  71. Mar 05 11:37:40 pve8 corosync[4672]: [WD ] no resources configured.
  72.  
  73. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync watchdog service [7]
  74.  
  75. Mar 05 11:37:40 pve8 corosync[4672]: [QUORUM] Using quorum provider corosync_votequorum
  76.  
  77. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
  78.  
  79. Mar 05 11:37:40 pve8 corosync[4672]: [QB ] server name: votequorum
  80.  
  81. Mar 05 11:37:40 pve8 corosync[4672]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
  82.  
  83. Mar 05 11:37:40 pve8 corosync[4672]: [QB ] server name: quorum
  84.  
  85. Mar 05 11:37:40 pve8 corosync[4672]: [TOTEM ] Configuring link 0
  86.  
  87. Mar 05 11:37:40 pve8 corosync[4672]: [TOTEM ] Configured link number 0: local addr: 172.29.12.9, port=5405
  88.  
  89. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  90.  
  91. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 has no active links
  92.  
  93. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  94.  
  95. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 has no active links
  96.  
  97. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  98.  
  99. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 1 has no active links
  100.  
  101. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  102.  
  103. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 has no active links
  104.  
  105. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  106.  
  107. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 has no active links
  108.  
  109. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  110.  
  111. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 2 has no active links
  112.  
  113. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  114.  
  115. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  116.  
  117. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  118.  
  119. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  120.  
  121. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  122.  
  123. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  124.  
  125. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 0)
  126.  
  127. Mar 05 11:37:40 pve8 corosync[4672]: [KNET ] host: host: 3 has no active links
  128.  
  129. Mar 05 11:37:40 pve8 corosync[4672]: [QUORUM] Sync members[1]: 3
  130.  
  131. Mar 05 11:37:40 pve8 corosync[4672]: [QUORUM] Sync joined[1]: 3
  132.  
  133. Mar 05 11:37:40 pve8 corosync[4672]: [TOTEM ] A new membership (3.5) was formed. Members joined: 3
  134.  
  135. Mar 05 11:37:40 pve8 corosync[4672]: [QUORUM] Members[1]: 3
  136.  
  137. Mar 05 11:37:40 pve8 systemd[1]: Started Corosync Cluster Engine.
  138.  
  139. Mar 05 11:37:40 pve8 corosync[4672]: [MAIN ] Completed service synchronization, ready to provide service.
  140.  
  141. Mar 05 11:37:41 pve8 systemd[1]: Started The Proxmox VE cluster filesystem.
  142.  
  143. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] rx: host: 2 link: 0 is up
  144.  
  145. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  146.  
  147. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
  148.  
  149. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  150.  
  151. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] rx: host: 1 link: 0 is up
  152.  
  153. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
  154.  
  155. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] pmtud: PMTUD link change for host: 5 link: 0 from 469 to 1397
  156.  
  157. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] pmtud: PMTUD link change for host: 2 link: 0 from 469 to 1397
  158.  
  159. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] pmtud: PMTUD link change for host: 1 link: 0 from 469 to 1397
  160.  
  161. Mar 05 11:37:43 pve8 corosync[4672]: [KNET ] pmtud: Global data MTU changed to: 1397
  162.  
  163. Mar 05 11:37:43 pve8 corosync[4672]: [QUORUM] Sync members[4]: 1 2 3 5
  164.  
  165. Mar 05 11:37:43 pve8 corosync[4672]: [QUORUM] Sync joined[3]: 1 2 5
  166.  
  167. Mar 05 11:37:43 pve8 corosync[4672]: [TOTEM ] A new membership (1.11ac) was formed. Members joined: 1 2 5
  168.  
  169. Mar 05 11:37:43 pve8 corosync[4672]: [QUORUM] This node is within the primary component and will provide service.
  170.  
  171. Mar 05 11:37:43 pve8 corosync[4672]: [QUORUM] Members[4]: 1 2 3 5
  172.  
  173. Mar 05 11:37:43 pve8 corosync[4672]: [MAIN ] Completed service synchronization, ready to provide service.
  174.  
  175. Mar 05 11:37:46 pve8 pmxcfs[4674]: [status] notice: update cluster info (cluster name 19C, version = 13)
  176.  
  177. Mar 05 11:37:46 pve8 pmxcfs[4674]: [status] notice: node has quorum
  178.  
  179. Mar 05 11:37:46 pve8 pmxcfs[4674]: [dcdb] notice: members: 1/2479487, 2/3410342, 3/4674, 5/60467
  180.  
  181. Mar 05 11:37:46 pve8 pmxcfs[4674]: [dcdb] notice: starting data syncronisation
  182.  
  183. Mar 05 11:37:46 pve8 pmxcfs[4674]: [status] notice: members: 1/2479487, 2/3410342, 3/4674, 5/60467
  184.  
  185. Mar 05 11:37:46 pve8 pmxcfs[4674]: [status] notice: starting data syncronisation
  186.  
  187. Mar 05 11:37:46 pve8 pmxcfs[4674]: [dcdb] notice: received sync request (epoch 1/2479487/0000003B)
  188.  
  189. Mar 05 11:37:46 pve8 pmxcfs[4674]: [status] notice: received sync request (epoch 1/2479487/00000029)
  190.  
  191. Mar 05 11:37:46 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  192.  
  193. Mar 05 11:37:53 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  194.  
  195. Mar 05 11:37:53 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  196.  
  197. Mar 05 11:37:53 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  198.  
  199. Mar 05 11:37:56 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  200.  
  201. Mar 05 11:37:56 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  202.  
  203. Mar 05 11:38:52 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  204.  
  205. Mar 05 11:38:52 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  206.  
  207. Mar 05 11:38:52 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  208.  
  209. Mar 05 11:38:54 pve8 corosync[4672]: [TOTEM ] Token has not been received in 3225 ms
  210.  
  211. Mar 05 11:38:55 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  212.  
  213. Mar 05 11:38:55 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  214.  
  215. Mar 05 11:39:03 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  216.  
  217. Mar 05 11:39:03 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  218.  
  219. Mar 05 11:39:03 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  220.  
  221. Mar 05 11:39:06 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  222.  
  223. Mar 05 11:39:06 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  224.  
  225. Mar 05 11:39:16 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  226.  
  227. Mar 05 11:39:16 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  228.  
  229. Mar 05 11:39:16 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  230.  
  231. Mar 05 11:39:19 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  232.  
  233. Mar 05 11:39:19 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  234.  
  235. Mar 05 11:39:55 pve8 corosync[4672]: [TOTEM ] FAILED TO RECEIVE
  236.  
  237. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Sync members[1]: 3
  238.  
  239. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Sync left[3]: 1 2 5
  240.  
  241. Mar 05 11:39:55 pve8 corosync[4672]: [TOTEM ] A new membership (3.11b0) was formed. Members left: 1 2 5
  242.  
  243. Mar 05 11:39:55 pve8 corosync[4672]: [TOTEM ] Failed to receive the leave message. failed: 1 2 5
  244.  
  245. Mar 05 11:39:55 pve8 pmxcfs[4674]: [dcdb] notice: members: 3/4674
  246.  
  247. Mar 05 11:39:55 pve8 pmxcfs[4674]: [dcdb] notice: all data is up to date
  248.  
  249. Mar 05 11:39:55 pve8 pmxcfs[4674]: [dcdb] notice: dfsm_deliver_queue: queue length 1
  250.  
  251. Mar 05 11:39:55 pve8 corosync[4672]: [VOTEQ ] Unable to determine origin of the qdevice register call!
  252.  
  253. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] This node is within the non-primary component and will NOT provide any services.
  254.  
  255. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Members[1]: 3
  256.  
  257. Mar 05 11:39:55 pve8 corosync[4672]: [MAIN ] Completed service synchronization, ready to provide service.
  258.  
  259. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: node lost quorum
  260.  
  261. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: members: 3/4674
  262.  
  263. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: all data is up to date
  264.  
  265. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: dfsm_deliver_queue: queue length 3
  266.  
  267. Mar 05 11:39:55 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  268.  
  269. Mar 05 11:39:55 pve8 pvedaemon[4642]: can't create shared ssh key database '/etc/pve/priv/authorized_keys'
  270.  
  271. Mar 05 11:39:55 pve8 pvestatd[1163]: authkey rotation error: cfs-lock 'authkey' error: no quorum!
  272.  
  273. Mar 05 11:39:55 pve8 pvestatd[1163]: status update time (127.538 seconds)
  274.  
  275. Mar 05 11:39:55 pve8 cron[1149]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
  276.  
  277. Mar 05 11:39:55 pve8 pvescheduler[4830]: replication: cfs-lock 'file-replication_cfg' error: no quorum!
  278.  
  279. Mar 05 11:39:55 pve8 pvescheduler[4832]: jobs: cfs-lock 'file-jobs_cfg' error: no quorum!
  280.  
  281. Mar 05 11:39:55 pve8 cron[1149]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
  282.  
  283. Mar 05 11:39:55 pve8 pvedaemon[4642]: unable to create directory '/etc/pve/nodes' - Permission denied
  284.  
  285. Mar 05 11:39:55 pve8 pvedaemon[1195]: <root@pam> end task UPID:pve8:00001222:0000D19F:62234B82:clusterjoin::root@pam: unable to crea>
  286.  
  287. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Sync members[4]: 1 2 3 5
  288.  
  289. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Sync joined[3]: 1 2 5
  290.  
  291. Mar 05 11:39:55 pve8 corosync[4672]: [TOTEM ] A new membership (1.11b4) was formed. Members joined: 1 2 5
  292.  
  293. Mar 05 11:39:55 pve8 pmxcfs[4674]: [dcdb] notice: members: 1/2479487, 2/3410342, 3/4674, 5/60467
  294.  
  295. Mar 05 11:39:55 pve8 pmxcfs[4674]: [dcdb] notice: starting data syncronisation
  296.  
  297. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: members: 1/2479487, 2/3410342, 3/4674, 5/60467
  298.  
  299. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: starting data syncronisation
  300.  
  301. Mar 05 11:39:55 pve8 corosync[4672]: [VOTEQ ] Unable to determine origin of the qdevice register call!
  302.  
  303. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] This node is within the primary component and will provide service.
  304.  
  305. Mar 05 11:39:55 pve8 corosync[4672]: [QUORUM] Members[4]: 1 2 3 5
  306.  
  307. Mar 05 11:39:55 pve8 corosync[4672]: [MAIN ] Completed service synchronization, ready to provide service.
  308.  
  309. Mar 05 11:39:55 pve8 pmxcfs[4674]: [status] notice: node has quorum
  310.  
  311. Mar 05 11:39:56 pve8 pmxcfs[4674]: [dcdb] notice: received sync request (epoch 1/2479487/0000003C)
  312.  
  313. Mar 05 11:39:56 pve8 pmxcfs[4674]: [dcdb] notice: received sync request (epoch 1/2479487/0000003D)
  314.  
  315. Mar 05 11:39:56 pve8 pmxcfs[4674]: [status] notice: received sync request (epoch 1/2479487/0000002A)
  316.  
  317. Mar 05 11:39:56 pve8 pmxcfs[4674]: [status] notice: received sync request (epoch 1/2479487/0000002B)
  318.  
  319. Mar 05 11:39:58 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  320.  
  321. Mar 05 11:39:58 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  322.  
  323. Mar 05 11:39:58 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  324.  
  325. Mar 05 11:40:00 pve8 pve-ha-lrm[1226]: loop take too long (129 seconds)
  326.  
  327. Mar 05 11:40:00 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  328.  
  329. Mar 05 11:40:01 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  330.  
  331. Mar 05 11:40:01 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  332.  
  333. Mar 05 11:40:01 pve8 cron[1149]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
  334.  
  335. Mar 05 11:40:05 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  336.  
  337. Mar 05 11:40:10 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  338.  
  339. Mar 05 11:40:13 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  340.  
  341. Mar 05 11:40:13 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  342.  
  343. Mar 05 11:40:13 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  344.  
  345. Mar 05 11:40:15 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  346.  
  347. Mar 05 11:40:15 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  348.  
  349. Mar 05 11:40:15 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  350.  
  351. Mar 05 11:40:20 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  352.  
  353. Mar 05 11:40:25 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  354.  
  355. Mar 05 11:40:30 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  356.  
  357. Mar 05 11:40:35 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  358.  
  359. Mar 05 11:40:40 pve8 pve-ha-lrm[1226]: unable to write lrm status file - unable to open file '/etc/pve/nodes/pve8/lrm_status.tmp.122>
  360.  
  361. Mar 05 11:40:41 pve8 corosync[4672]: [KNET ] link: host: 5 link: 0 is down
  362.  
  363. Mar 05 11:40:41 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
  364.  
  365. Mar 05 11:40:41 pve8 corosync[4672]: [KNET ] host: host: 5 has no active links
  366.  
  367. Mar 05 11:40:44 pve8 corosync[4672]: [KNET ] rx: host: 5 link: 0 is up
  368.  
  369. Mar 05 11:40:44 pve8 corosync[4672]: [KNET ] host: host: 5 (passive) best link: 0 (pri: 1)
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!