I put all of the engine logs up there now… Try engine.log-20160103.gz
On Jan 4, 2016, at 7:48 AM, Eliraz Levi <elevi@redhat.com> wrote:
ok thanks :) It looks like you didn't press refresh capabilities. I can't learn a lot from this log. can you refresh the host's capabilities and then send the log? thanks :) Eliraz.
----- Original Message ----- From: "Will Dennis" <wdennis@nec-labs.com> To: "Eliraz Levi" <elevi@redhat.com> Sent: Monday, 4 January, 2016 2:22:03 PM Subject: RE: [ovirt-users] host status "Non Operational" - how to diagnose & fix?
If you try it again, should work now... Damn hackers...
Sent with Good (www.good.com)
-----Original Message----- From: Eliraz Levi [elevi@redhat.com<mailto:elevi@redhat.com>] Sent: Monday, January 04, 2016 07:17 AM Eastern Standard Time To: Will Dennis Subject: Re: [ovirt-users] host status "Non Operational" - how to diagnose & fix?
Hi Will :) The link is broken. Can you please send a valid one to the list? thanks :) Eliraz.
----- Original Message ----- From: "Will Dennis" <wdennis@nec-labs.com> To: "Eliraz Levi" <elevi@redhat.com> Sent: Sunday, 3 January, 2016 8:23:59 PM Subject: Re: [ovirt-users] host status "Non Operational" - how to diagnose & fix?
Digital Ocean droplet and Python SimpleHTTPServer FTW ;) http://c7-01.thiscant.fail
On Jan 3, 2016, at 9:33 AM, Eliraz Levi <elevi@redhat.com<mailto:elevi@redhat.com>> wrote:
vdsClient output: http://fpaste.org/306666/82858714/
The engine.log is very large (4496 lines) so cannot fpaste… Is there a file upload service that can be used to share these sorts of things with you?
Hi Will how are you? Perhaps you can upload the log to some sort of a cloud? say google and share the URL? I think it will be the fastest way around. Thanks :) please send the URL in the mailing list so everybody will be able to follow. Cheers! Eliraz :)