F fischeranalytics Renowned Member Oct 11, 2015 4 0 66 Oct 11, 2015 #1 Hi there! After I've upgraded to Prox 4 there is something I'm interpreting as an error. Look at the screenshot. The Corosync service is marked as dead and is not starable (but it shows "TASK OK") We have a community subscription!
Hi there! After I've upgraded to Prox 4 there is something I'm interpreting as an error. Look at the screenshot. The Corosync service is marked as dead and is not starable (but it shows "TASK OK") We have a community subscription!
dietmar Proxmox Staff Member Staff member Apr 28, 2005 17,298 723 253 Austria www.proxmox.com Oct 11, 2015 #2 What is the output of # systemctl status corosync -l and what do you get if you try to start: # systemctl start corosync
What is the output of # systemctl status corosync -l and what do you get if you try to start: # systemctl start corosync
tom Proxmox Staff Member Staff member Aug 29, 2006 15,948 1,244 273 Oct 11, 2015 #3 In you do not run a cluster, its dead by design. Reactions: tontonpolak
F fischeranalytics Renowned Member Oct 11, 2015 4 0 66 Oct 11, 2015 #4 Thanks for the answers! Is this a correct output? We don't run a cluster
dietmar Proxmox Staff Member Staff member Apr 28, 2005 17,298 723 253 Austria www.proxmox.com Oct 12, 2015 #5 fischeranalytics said: Is this a correct output? We don't run a cluster Click to expand... Yes, this is correct if you do not run a cluster.
fischeranalytics said: Is this a correct output? We don't run a cluster Click to expand... Yes, this is correct if you do not run a cluster.