Re: [ovirt-users] problem after rebooting the node

2017-02-09 Thread Yaniv Kaul
On Thu, Feb 9, 2017 at 9:51 AM, Shalabh Goel wrote: > Sorry for the late reply. Actually the problem is with only one of my > three nodes. So I think that it is an issue with the upgrade. I am using > Ovirt-ng node OS. I will just re-install ovirt-ng OS on this node and

Re: [ovirt-users] problem after rebooting the node

2017-02-08 Thread Shalabh Goel
Sorry for the late reply. Actually the problem is with only one of my three nodes. So I think that it is an issue with the upgrade. I am using Ovirt-ng node OS. I will just re-install ovirt-ng OS on this node and upgrade it the way I did others. Actually, I upgraded my storage node (NFS) and lost

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Edward Haas
The ones you mentioned before, we just need the whole files and not snippets of them. vdsm.log, supervdsm.log, messages.log and the ovs ones you previously mentioned. On Mon, Feb 6, 2017 at 1:14 PM, Shalabh Goel wrote: > which all log files? Actually I am new to Ovirt,

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Shalabh Goel
which all log files? Actually I am new to Ovirt, so it would be really helpful if you can tell me which ones?? Thanks On Mon, Feb 6, 2017 at 4:39 PM, Edward Haas wrote: > Please package the logs (tar or zip) and send them. > > On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Edward Haas
Please package the logs (tar or zip) and send them. On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel wrote: > Yes, I am using OVS as the switch type and I did not know that it was not > supported officially. > > The output of ovs-vsctl show is as follows: > >

Re: [ovirt-users] problem after rebooting the node

2017-02-06 Thread Shalabh Goel
Yes, I am using OVS as the switch type and I did not know that it was not supported officially. The output of ovs-vsctl show is as follows: f634d53e-4849-488b-8454-6b1fafa7c6ac ovs_version: "2.6.90" I am attaching OVS switch logs below: /var/log/openvswitch/ovsdb-server.log

Re: [ovirt-users] problem after rebooting the node

2017-02-04 Thread Edward Haas
Based on what I can see, you used OVS as the switch type and it seems ovs (openvswitch) is not properly installed on your host. Make sure that you have ovs operational by issuing "ovs-vsctl show". You should note that OVS network support is not an official release feature, and you should use it

Re: [ovirt-users] problem after rebooting the node

2017-02-02 Thread Edward Haas
Hello Shalabh, Please provide the logs from your node: - messages - vdsm/vdsm.log, vdsm/supervdsm.log It may be that you are missing openvswitch installed, although VDSM should not require it for its operation. Thanks, Edy. On Thu, Feb 2, 2017 at 2:10 PM, Shalabh Goel

[ovirt-users] problem after rebooting the node

2017-02-02 Thread Shalabh Goel
HI, I am getting the following error on my node after rebooting it. VDSM ovirtnode2 command HostSetupNetworksVDS failed: Executing commands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) To solve this, I am trying to restart