Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Cam Mac
To update the thread here after some offline discussion with Piotr, the problem was that vdsmd had stopped running and wasn't able to start. It wasn't reported in the logs that I could see, but I noticed it after trying to restart it at Piotr's suggestion, after running a 'systemctl'. A

Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Campbell McLeay
No problem Piotr, I will send you the full logs shortly. Thanks, Campbell On 5 May 2016 at 11:37, Piotr Kliczewski wrote: > Cam, > > It is really hard to understand partial logs. Please send me directly > full logs and I will analyze. > > Thanks, > Piotr > > On Mon,

Re: [ovirt-users] node unresponsive after reboot

2016-05-05 Thread Piotr Kliczewski
Cam, It is really hard to understand partial logs. Please send me directly full logs and I will analyze. Thanks, Piotr On Mon, May 2, 2016 at 4:35 PM, Cam Mac wrote: > Hi Piotr, > > Attached are the vdsm log, the engine log and the supervdsm log. I've > attached them as a

Re: [ovirt-users] node unresponsive after reboot

2016-05-02 Thread Cam Mac
Hi Piotr, Attached are the vdsm log, the engine log and the supervdsm log. I've attached them as a .tgz. I noticed it is complaining about configuring an interface in one of the node logs. It shows as up in the engine web GUI though (and on the command line). Thanks for the help. -Cam On Mon,

Re: [ovirt-users] node unresponsive after reboot

2016-05-02 Thread Piotr Kliczewski
Cam, Please provide engine and failing vdsm logs. Thanks, Piotr On Sun, May 1, 2016 at 4:05 PM, Cam Mac wrote: > Hi, > > I have a two node + engine ovirt setup, and I was having problems > doing a live migration between nodes. I looked in the vdsm logs and > noticed selinux