Simon, I appreciate your assistance with this. As it turns out, I deployed this last night (half asleep) and I did not run YUM UPDATE on my management host. In doing so, several packages updated and rebooted the host. Once rebooted, everything connected up just fine. Now, I just need to work on the networking portion which I am deathly afraid of.
Again, thank you. On Sat, Apr 30, 2016 at 1:59 PM, Simon Weller <swel...@ena.com> wrote: > I'm mobile currently...but it looks like libvirtd isn't running. Can you > start it with systemctl start libvirtd? > > - Si > > Simon Weller/ENA > (615) 312-6068 > > -----Original Message----- > From: Brian Smith [bmsmit...@gmail.com] > Received: Saturday, 30 Apr 2016, 12:19PM > To: users@cloudstack.apache.org [users@cloudstack.apache.org] > Subject: Re: Issue Joining host to Cluster > > Pardon me: I should have also added the rest of the log. Here is where it > failed to start: http://pastebin.com/U1bjQd10 > > On Sat, Apr 30, 2016 at 1:10 PM, Brian Smith <bmsmit...@gmail.com> wrote: > > > Thank you Simon. > > > > I corrected the typo from the guest network interface. > > > > On the hypervisor: > > [root@node01 ~]# service cloudstack-agent status > > cloudstack-agent dead but subsys locked > > > > I have run the command for place the agent in debug mode. When I try to > > manually start the agent this appears - > http://prntscr.com/ayqts0 > > > > Logs from the agent on a "cloudstack-agent restart" command on the KVM > > host - > http://pastebin.com/EeLqP0Vw > > > > > > >
