On Sat, Oct 26, 2013 at 09:06:23AM -0600, Dan Ferris wrote:
Unfortunatly, I was not correct. Not fixed. :(
It's most probably a libvirt issue, tracked by
Bug 1034312 - vdsm-tool segfaults during vdsmd start
solved upstream and hopefully to be backported to Fedora 19.
Unfortunatly, I was not correct. Not fixed. :(
VDSM died randomly yesterday. This was the message from systemctl:
vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
Active: failed (Result: exit-code) since Fri 2013-10-25
So, just an update...
I upgraded to Ovirt 3.3.0.1 today and I have the latest libvirt.
I *THINK* the issue may be gone, but I will have to do a little more
testing.
Dan
On 10/18/2013 11:15 AM, Dan Ferris wrote:
That did work. vdsmd decided it would start again.
Dan
On 10/17/2013 3:15
On Thu, Oct 17, 2013 at 05:15:48PM -0400, Jason Brooks wrote:
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To: users@ovirt.org users@ovirt.org
Sent: Tuesday, October 15, 2013 9:24:44 AM
Subject: [Users] vdsmd seg fault
I updated to the latest
That did work. vdsmd decided it would start again.
Dan
On 10/17/2013 3:15 PM, Jason Brooks wrote:
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To: users@ovirt.org users@ovirt.org
Sent: Tuesday, October 15, 2013 9:24:44 AM
Subject: [Users] vdsmd seg fault
I
On Fri, 2013-10-18 at 14:16 +0300, Dan Kenigsberg wrote:
On Thu, Oct 17, 2013 at 05:15:48PM -0400, Jason Brooks wrote:
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To: users@ovirt.org users@ovirt.org
Sent: Tuesday, October 15, 2013 9:24:44 AM
On Fri, Oct 18, 2013 at 11:32:51AM -0700, Jason Brooks wrote:
On Fri, 2013-10-18 at 14:16 +0300, Dan Kenigsberg wrote:
On Thu, Oct 17, 2013 at 05:15:48PM -0400, Jason Brooks wrote:
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To:
On Wed, Oct 16, 2013 at 09:43:57AM -0600, Dan Ferris wrote:
On 10/16/2013 8:55 AM, Dan Kenigsberg wrote:
On Wed, Oct 16, 2013 at 08:33:10AM -0600, Dan Ferris wrote:
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to
- Original Message -
From: Dan Ferris dfer...@prometheusresearch.com
To: users@ovirt.org users@ovirt.org
Sent: Tuesday, October 15, 2013 9:24:44 AM
Subject: [Users] vdsmd seg fault
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
On 10/16/2013 02:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service - Virtual Desktop Server Manager
Loaded: loaded
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service - Virtual Desktop Server Manager
Loaded: loaded
On Wed, Oct 16, 2013 at 08:33:10AM -0600, Dan Ferris wrote:
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service
On 10/16/2013 8:55 AM, Dan Kenigsberg wrote:
On Wed, Oct 16, 2013 at 08:33:10AM -0600, Dan Ferris wrote:
On 10/16/2013 12:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not
On 10/16/2013 7:27 AM, Douglas Schilling Landgraf wrote:
On 10/16/2013 02:27 AM, Dan Kenigsberg wrote:
On Tue, Oct 15, 2013 at 10:24:44AM -0600, Dan Ferris wrote:
I updated to the latest Fedora 19 on two test servers, and now vdsmd
will not start.
Systedctl says this:
dsmd.service -
15 matches
Mail list logo