API tools faq
paste
KpuCko

Proxmox cluster failing

KpuCko
Oct 25th, 2023
73
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 20.69 KB | None | 0 0
raw download clone embed print report
  1. Thanks for the fast replay, here is all the info you require
  2.  
  3.  
  4. [CODE]root@sofx1010pve3302.home.lan:~# pvecm status
  5.  
  6. Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
  7.  
  8. [email protected]:~#
  9.  
  10.  
  11. [email protected]:~# pvecm status
  12.  
  13. Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
  14.  
  15. [email protected]:~#
  16.  
  17.  
  18. root@sofx1010pve3307:~# pvecm status
  19.  
  20. Cluster information
  21.  
  22. -------------------
  23.  
  24. Name:             Proxmox
  25.  
  26. Config Version:   1
  27.  
  28. Transport:        knet
  29.  
  30. Secure auth:      on
  31.  
  32.  
  33. Quorum information
  34.  
  35. ------------------
  36.  
  37. Date:             Wed Oct 25 10:14:52 2023
  38.  
  39. Quorum provider:  corosync_votequorum
  40.  
  41. Nodes:            1
  42.  
  43. Node ID:          0x00000001
  44.  
  45. Ring ID:          1.a
  46.  
  47. Quorate:          Yes
  48.  
  49.  
  50. Votequorum information
  51.  
  52. ----------------------
  53.  
  54. Expected votes:   1
  55.  
  56. Highest expected: 1
  57.  
  58. Total votes:      1
  59.  
  60. Quorum:           1
  61.  
  62. Flags:            Quorate
  63.  
  64.  
  65. Membership information
  66.  
  67. ----------------------
  68.  
  69.     Nodeid      Votes Name
  70.  
  71. 0x00000001          1 192.168.30.7 (local)
  72.  
  73. root@sofx1010pve3307:~#
  74.  
  75. [/CODE]
  76.  
  77.  
  78. [CODE]root@sofx1010pve3302.home.lan:~# cat /etc/corosync/corosync.conf
  79.  
  80. cat: /etc/corosync/corosync.conf: No such file or directory
  81.  
  82. [email protected]:~#
  83.  
  84.  
  85. [email protected]:~# cat /etc/corosync/corosync.conf
  86.  
  87. cat: /etc/corosync/corosync.conf: No such file or directory
  88.  
  89. [email protected]:~#
  90.  
  91.  
  92. root@sofx1010pve3307:~# cat /etc/corosync/corosync.conf
  93.  
  94. logging {
  95.  
  96.   debug: off
  97.  
  98.   to_syslog: yes
  99.  
  100. }
  101.  
  102.  
  103. nodelist {
  104.  
  105.   node {
  106.  
  107.     name: sofx1010pve3307
  108.  
  109.     nodeid: 1
  110.  
  111.     quorum_votes: 1
  112.  
  113.     ring0_addr: 192.168.30.7
  114.  
  115.   }
  116.  
  117. }
  118.  
  119.  
  120. quorum {
  121.  
  122.   provider: corosync_votequorum
  123.  
  124. }
  125.  
  126.  
  127. totem {
  128.  
  129.   cluster_name: Proxmox
  130.  
  131.   config_version: 1
  132.  
  133.   interface {
  134.  
  135.     linknumber: 0
  136.  
  137.   }
  138.  
  139.   ip_version: ipv4-6
  140.  
  141.   link_mode: passive
  142.  
  143.   secauth: on
  144.  
  145.   version: 2
  146.  
  147. }
  148.  
  149.  
  150. root@sofx1010pve3307:~#
  151.  
  152. [/CODE]
  153.  
  154.  
  155. [CODE]root@sofx1010pve3302.home.lan:~# systemctl status corosync.service
  156.  
  157. ○ corosync.service - Corosync Cluster Engine
  158.  
  159.      Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)
  160.  
  161.      Active: inactive (dead)
  162.  
  163.   Condition: start condition failed at Wed 2023-10-25 10:16:31 EEST; 249ms ago
  164.  
  165.              └─ ConditionPathExists=/etc/corosync/corosync.conf was not met
  166.  
  167.        Docs: man:corosync
  168.  
  169.              man:corosync.conf
  170.  
  171.              man:corosync_overview
  172.  
  173.  
  174. Oct 25 10:14:05 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  175.  
  176. Oct 25 10:14:21 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  177.  
  178. Oct 25 10:14:37 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  179.  
  180. Oct 25 10:14:54 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  181.  
  182. Oct 25 10:15:10 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  183.  
  184. Oct 25 10:15:26 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  185.  
  186. Oct 25 10:15:42 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  187.  
  188. Oct 25 10:15:59 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  189.  
  190. Oct 25 10:16:15 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  191.  
  192. Oct 25 10:16:31 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  193.  
  194. [email protected]:~#
  195.  
  196.  
  197. [email protected]:~# systemctl status corosync.service
  198.  
  199. ○ corosync.service - Corosync Cluster Engine
  200.  
  201.      Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)
  202.  
  203.      Active: inactive (dead)
  204.  
  205.   Condition: start condition failed at Wed 2023-10-25 10:16:31 EEST; 5s ago
  206.  
  207.              └─ ConditionPathExists=/etc/corosync/corosync.conf was not met
  208.  
  209.        Docs: man:corosync
  210.  
  211.              man:corosync.conf
  212.  
  213.              man:corosync_overview
  214.  
  215.  
  216. Oct 25 10:14:05 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  217.  
  218. Oct 25 10:14:21 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  219.  
  220. Oct 25 10:14:37 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  221.  
  222. Oct 25 10:14:54 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  223.  
  224. Oct 25 10:15:10 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  225.  
  226. Oct 25 10:15:26 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  227.  
  228. Oct 25 10:15:42 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  229.  
  230. Oct 25 10:15:59 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  231.  
  232. Oct 25 10:16:15 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  233.  
  234. Oct 25 10:16:31 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  235.  
  236. [email protected]:~#
  237.  
  238.  
  239. root@sofx1010pve3307:~# systemctl status corosync.service
  240.  
  241. ● corosync.service - Corosync Cluster Engine
  242.  
  243.      Loaded: loaded (/lib/systemd/system/corosync.service; enabled; preset: enabled)
  244.  
  245.      Active: active (running) since Wed 2023-10-25 09:37:49 EEST; 38min ago
  246.  
  247.        Docs: man:corosync
  248.  
  249.              man:corosync.conf
  250.  
  251.              man:corosync_overview
  252.  
  253.    Main PID: 2445 (corosync)
  254.  
  255.       Tasks: 9 (limit: 76866)
  256.  
  257.      Memory: 157.1M
  258.  
  259.      CGroup: /system.slice/corosync.service
  260.  
  261.              └─2445 /usr/sbin/corosync -f
  262.  
  263.  
  264. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [QB    ] server name: quorum
  265.  
  266. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [TOTEM ] Configuring link 0
  267.  
  268. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [TOTEM ] Configured link number 0: local addr: 192.168.30.7, port=5405
  269.  
  270. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [KNET  ] link: Resetting MTU for link 0 because host 1 joined
  271.  
  272. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [QUORUM] Sync members[1]: 1
  273.  
  274. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [QUORUM] Sync joined[1]: 1
  275.  
  276. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [TOTEM ] A new membership (1.a) was formed. Members joined: 1
  277.  
  278. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [QUORUM] Members[1]: 1
  279.  
  280. Oct 25 09:37:49 sofx1010pve3307 corosync[2445]:   [MAIN  ] Completed service synchronization, ready to provide service.
  281.  
  282. Oct 25 09:37:49 sofx1010pve3307 systemd[1]: Started corosync.service - Corosync Cluster Engine.
  283.  
  284. root@sofx1010pve3307:~#
  285.  
  286. [/CODE]
  287.  
  288.  
  289. ​Here are the outputs only on the nodes which are failing to start the UI:
  290.  
  291.  
  292. [CODE]root@sofx1010pve3302.home.lan:~# systemctl status pveproxy.service pvedaemon.service
  293.  
  294. ● pveproxy.service - PVE API Proxy Server
  295.  
  296.      Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
  297.  
  298.      Active: active (running) since Wed 2023-10-25 10:03:50 EEST; 13min ago
  299.  
  300.     Process: 2467 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  301.  
  302.     Process: 2480 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
  303.  
  304.    Main PID: 2529 (pveproxy)
  305.  
  306.       Tasks: 4 (limit: 38288)
  307.  
  308.      Memory: 141.3M
  309.  
  310.      CGroup: /system.slice/pveproxy.service
  311.  
  312.              ├─2529 pveproxy
  313.  
  314.              ├─2530 "pveproxy worker"
  315.  
  316.              ├─2531 "pveproxy worker"
  317.  
  318.              └─2532 "pveproxy worker"
  319.  
  320.  
  321. Oct 25 10:03:49 sofx1010pve3302.home.lan systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
  322.  
  323. Oct 25 10:03:50 sofx1010pve3302.home.lan pveproxy[2529]: starting server
  324.  
  325. Oct 25 10:03:50 sofx1010pve3302.home.lan pveproxy[2529]: starting 3 worker(s)
  326.  
  327. Oct 25 10:03:50 sofx1010pve3302.home.lan pveproxy[2529]: worker 2530 started
  328.  
  329. Oct 25 10:03:50 sofx1010pve3302.home.lan pveproxy[2529]: worker 2531 started
  330.  
  331. Oct 25 10:03:50 sofx1010pve3302.home.lan pveproxy[2529]: worker 2532 started
  332.  
  333. Oct 25 10:03:50 sofx1010pve3302.home.lan systemd[1]: Started pveproxy.service - PVE API Proxy Server.
  334.  
  335.  
  336. ● pvedaemon.service - PVE API Daemon
  337.  
  338.      Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
  339.  
  340.      Active: active (running) since Wed 2023-10-25 10:03:49 EEST; 13min ago
  341.  
  342.     Process: 2313 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
  343.  
  344.    Main PID: 2462 (pvedaemon)
  345.  
  346.       Tasks: 4 (limit: 38288)
  347.  
  348.      Memory: 209.0M
  349.  
  350.      CGroup: /system.slice/pvedaemon.service
  351.  
  352.              ├─2462 pvedaemon
  353.  
  354.              ├─2463 "pvedaemon worker"
  355.  
  356.              ├─2464 "pvedaemon worker"
  357.  
  358.              └─2465 "pvedaemon worker"
  359.  
  360.  
  361. Oct 25 10:03:48 sofx1010pve3302.home.lan systemd[1]: Starting pvedaemon.service - PVE API Daemon...
  362.  
  363. Oct 25 10:03:49 sofx1010pve3302.home.lan pvedaemon[2462]: starting server
  364.  
  365. Oct 25 10:03:49 sofx1010pve3302.home.lan pvedaemon[2462]: starting 3 worker(s)
  366.  
  367. Oct 25 10:03:49 sofx1010pve3302.home.lan pvedaemon[2462]: worker 2463 started
  368.  
  369. Oct 25 10:03:49 sofx1010pve3302.home.lan pvedaemon[2462]: worker 2464 started
  370.  
  371. Oct 25 10:03:49 sofx1010pve3302.home.lan pvedaemon[2462]: worker 2465 started
  372.  
  373. Oct 25 10:03:49 sofx1010pve3302.home.lan systemd[1]: Started pvedaemon.service - PVE API Daemon.
  374.  
  375. [email protected]:~#
  376.  
  377.  
  378. [email protected]:~# systemctl status pveproxy.service pvedaemon.service
  379.  
  380. ● pveproxy.service - PVE API Proxy Server
  381.  
  382.      Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
  383.  
  384.      Active: active (running) since Wed 2023-10-25 10:03:50 EEST; 14min ago
  385.  
  386.     Process: 1402 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  387.  
  388.     Process: 1408 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
  389.  
  390.    Main PID: 1416 (pveproxy)
  391.  
  392.       Tasks: 4 (limit: 38288)
  393.  
  394.      Memory: 141.5M
  395.  
  396.      CGroup: /system.slice/pveproxy.service
  397.  
  398.              ├─1416 pveproxy
  399.  
  400.              ├─1417 "pveproxy worker"
  401.  
  402.              ├─1418 "pveproxy worker"
  403.  
  404.              └─1419 "pveproxy worker"
  405.  
  406.  
  407. Oct 25 10:03:48 sofx1010pve3303.home.lan systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
  408.  
  409. Oct 25 10:03:50 sofx1010pve3303.home.lan pveproxy[1416]: starting server
  410.  
  411. Oct 25 10:03:50 sofx1010pve3303.home.lan pveproxy[1416]: starting 3 worker(s)
  412.  
  413. Oct 25 10:03:50 sofx1010pve3303.home.lan pveproxy[1416]: worker 1417 started
  414.  
  415. Oct 25 10:03:50 sofx1010pve3303.home.lan pveproxy[1416]: worker 1418 started
  416.  
  417. Oct 25 10:03:50 sofx1010pve3303.home.lan pveproxy[1416]: worker 1419 started
  418.  
  419. Oct 25 10:03:50 sofx1010pve3303.home.lan systemd[1]: Started pveproxy.service - PVE API Proxy Server.
  420.  
  421.  
  422. ● pvedaemon.service - PVE API Daemon
  423.  
  424.      Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
  425.  
  426.      Active: active (running) since Wed 2023-10-25 10:03:48 EEST; 14min ago
  427.  
  428.     Process: 1262 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
  429.  
  430.    Main PID: 1397 (pvedaemon)
  431.  
  432.       Tasks: 4 (limit: 38288)
  433.  
  434.      Memory: 208.8M
  435.  
  436.      CGroup: /system.slice/pvedaemon.service
  437.  
  438.              ├─1397 pvedaemon
  439.  
  440.              ├─1398 "pvedaemon worker"
  441.  
  442.              ├─1399 "pvedaemon worker"
  443.  
  444.              └─1400 "pvedaemon worker"
  445.  
  446.  
  447. Oct 25 10:03:48 sofx1010pve3303.home.lan systemd[1]: Starting pvedaemon.service - PVE API Daemon...
  448.  
  449. Oct 25 10:03:48 sofx1010pve3303.home.lan pvedaemon[1397]: starting server
  450.  
  451. Oct 25 10:03:48 sofx1010pve3303.home.lan pvedaemon[1397]: starting 3 worker(s)
  452.  
  453. Oct 25 10:03:48 sofx1010pve3303.home.lan pvedaemon[1397]: worker 1398 started
  454.  
  455. Oct 25 10:03:48 sofx1010pve3303.home.lan pvedaemon[1397]: worker 1399 started
  456.  
  457. Oct 25 10:03:48 sofx1010pve3303.home.lan pvedaemon[1397]: worker 1400 started
  458.  
  459. Oct 25 10:03:48 sofx1010pve3303.home.lan systemd[1]: Started pvedaemon.service - PVE API Daemon.
  460.  
  461. [email protected]:~#
  462.  
  463. [/CODE]
  464.  
  465.  
  466. Again only on those nodes which are failing:
  467.  
  468.  
  469. [CODE]Oct 25 10:18:57 sofx1010pve3302.home.lan pacemakerd[6277]:  notice: Additional logging available in /var/log/pacemaker/pacemaker.log
  470.  
  471. Oct 25 10:18:57 sofx1010pve3302.home.lan systemd[1]: Started pacemaker.service - Pacemaker High Availability Cluster Manager.
  472.  
  473. Oct 25 10:18:57 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  474.  
  475. Oct 25 10:18:57 sofx1010pve3302.home.lan systemd[1]: Stopped pacemaker.service - Pacemaker High Availability Cluster Manager.
  476.  
  477. Oct 25 10:18:57 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Scheduled restart job, restart counter is at 56.
  478.  
  479. Oct 25 10:18:56 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  480.  
  481. Oct 25 10:18:56 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Main process exited, code=exited, status=69/UNAVAILABLE
  482.  
  483. Oct 25 10:18:56 sofx1010pve3302.home.lan pacemakerd[6229]:  crit: Could not connect to Corosync CMAP: CS_ERR_LIBRARY
  484.  
  485. Oct 25 10:18:55 sofx1010pve3302.home.lan pvestatd[2408]: status update time (10.183 seconds)
  486.  
  487. Oct 25 10:18:55 sofx1010pve3302.home.lan pvestatd[2408]: storage 'truenas-nfs' is not online
  488.  
  489. Oct 25 10:18:45 sofx1010pve3302.home.lan pvestatd[2408]: status update time (10.183 seconds)
  490.  
  491. Oct 25 10:18:45 sofx1010pve3302.home.lan pvestatd[2408]: storage 'truenas-nfs' is not online
  492.  
  493. Oct 25 10:18:41 sofx1010pve3302.home.lan pacemakerd[6229]:  notice: Additional logging available in /var/log/pacemaker/pacemaker.log
  494.  
  495. Oct 25 10:18:41 sofx1010pve3302.home.lan systemd[1]: Started pacemaker.service - Pacemaker High Availability Cluster Manager.
  496.  
  497. Oct 25 10:18:41 sofx1010pve3302.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  498.  
  499. Oct 25 10:18:41 sofx1010pve3302.home.lan systemd[1]: Stopped pacemaker.service - Pacemaker High Availability Cluster Manager.
  500.  
  501. Oct 25 10:18:41 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Scheduled restart job, restart counter is at 55.
  502.  
  503. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
  504.  
  505. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
  506.  
  507. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
  508.  
  509. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
  510.  
  511. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  512.  
  513. Oct 25 10:18:40 sofx1010pve3302.home.lan systemd[1]: pacemaker.service: Main process exited, code=exited, status=69/UNAVAILABLE
  514.  
  515. Oct 25 10:18:40 sofx1010pve3302.home.lan pacemakerd[6164]:  crit: Could not connect to Corosync CMAP: CS_ERR_LIBRARY
  516.  
  517. Oct 25 10:18:35 sofx1010pve3302.home.lan pvestatd[2408]: status update time (10.183 seconds)
  518.  
  519.  
  520. Oct 25 10:20:17 sofx1010pve3303.home.lan systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  521.  
  522. Oct 25 10:20:17 sofx1010pve3303.home.lan systemd[1]: pacemaker.service: Main process exited, code=exited, status=69/UNAVAILABLE
  523.  
  524. Oct 25 10:20:17 sofx1010pve3303.home.lan pacemakerd[5284]:  crit: Could not connect to Corosync CMAP: CS_ERR_LIBRARY
  525.  
  526. Oct 25 10:20:16 sofx1010pve3303.home.lan pvestatd[1343]: status update time (10.166 seconds)
  527.  
  528. Oct 25 10:20:16 sofx1010pve3303.home.lan pvestatd[1343]: storage 'truenas-nfs' is not online
  529.  
  530. Oct 25 10:20:06 sofx1010pve3303.home.lan pvestatd[1343]: status update time (10.166 seconds)
  531.  
  532. Oct 25 10:20:06 sofx1010pve3303.home.lan pvestatd[1343]: storage 'truenas-nfs' is not online
  533.  
  534. Oct 25 10:20:02 sofx1010pve3303.home.lan pacemakerd[5284]:  notice: Additional logging available in /var/log/pacemaker/pacemaker.log
  535.  
  536. Oct 25 10:20:02 sofx1010pve3303.home.lan systemd[1]: Started pacemaker.service - Pacemaker High Availability Cluster Manager.
  537.  
  538. Oct 25 10:20:02 sofx1010pve3303.home.lan systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.c>
  539.  
  540. Oct 25 10:20:02 sofx1010pve3303.home.lan systemd[1]: Stopped pacemaker.service - Pacemaker High Availability Cluster Manager.
  541.  
  542. Oct 25 10:20:02 sofx1010pve3303.home.lan systemd[1]: pacemaker.service: Scheduled restart job, restart counter is at 60.
  543.  
  544. Oct 25 10:20:02 sofx1010pve3303.home.lan CRON[5263]: pam_unix(cron:session): session closed for user root
  545.  
  546. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd-logind[758]: Removed session 18.
  547.  
  548. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd-logind[758]: Session 18 logged out. Waiting for processes to exit.
  549.  
  550. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd[1]: session-18.scope: Deactivated successfully.
  551.  
  552. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: pam_unix(sshd:session): session closed for user root
  553.  
  554. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: Disconnected from user root 192.168.30.2 port 36358
  555.  
  556. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: Received disconnect from 192.168.30.2 port 36358:11: disconnected by user
  557.  
  558. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: pam_env(sshd:session): deprecated reading of user environment enabled
  559.  
  560. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd[1]: Started session-18.scope - Session 18 of User root.
  561.  
  562. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd-logind[758]: New session 18 of user root.
  563.  
  564. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
  565.  
  566. Oct 25 10:20:01 sofx1010pve3303.home.lan sshd[5260]: Accepted publickey for root from 192.168.30.2 port 36358 ssh2: RSA SHA256:rbXel5Ru72ZLUZGrasjIV8XP4pn95nU/7r8Qmgx8lJ0
  567.  
  568. Oct 25 10:20:01 sofx1010pve3303.home.lan CRON[5262]: pam_unix(cron:session): session closed for user root
  569.  
  570. Oct 25 10:20:01 sofx1010pve3303.home.lan CRON[5265]: (root) CMD (/usr/local/sbin/check_interfaces_realtime.sh)
  571.  
  572. Oct 25 10:20:01 sofx1010pve3303.home.lan CRON[5264]: (root) CMD (unison profile-var-lib-vz.prf >/dev/null 2>&1)
  573.  
  574. Oct 25 10:20:01 sofx1010pve3303.home.lan CRON[5262]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
  575.  
  576. Oct 25 10:20:01 sofx1010pve3303.home.lan CRON[5263]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
  577.  
  578. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd[1]: pacemaker.service: Failed with result 'exit-code'.
  579.  
  580. Oct 25 10:20:01 sofx1010pve3303.home.lan systemd[1]: pacemaker.service: Main process exited, code=exited, status=69/UNAVAILABLE
  581.  
  582. Oct 25 10:20:01 sofx1010pve3303.home.lan pacemakerd[5189]:  crit: Could not connect to Corosync CMAP: CS_ERR_LIBRARY
  583.  
  584. Oct 25 10:19:56 sofx1010pve3303.home.lan pvestatd[1343]: status update time (10.167 seconds)
  585.  
  586.  
  587. [/CODE]
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!