- Users - oVirt List Archives

Re: [ovirt-users] fail to shutdown ubuntu guest
by Dan Kenigsberg 16 Jun '14

16 Jun '14

Adding Vinzenz and the list, since they should know of a possible agent bug. On Mon, Jun 16, 2014 at 05:40:59PM +0800, John Xue wrote: > On Fri, Jun 13, 2014 at 6:19 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Fri, Jun 13, 2014 at 09:22:37AM +0800, John Xue wrote: > >> I went through the xfce GUI options "Settings Manager" - "Power > >> Manager" to the field "When power button is pressed", set to power > >> off, but only successful one time, after reboot it was already set to > >> "Ask". If no one login to guest(just power on from console, and power > >> off), it always fail. > >> > >> I try to modify acpi configuration: > >> #cat /etc/acpi/events/powerbtn > >> event=button[ /]power > >> #action=/etc/acpi/powerbtn.sh > >> action=/sbin/poweroff > >> > >> It work, but I think this isn't a good solution. Any idea? Thanks! > >> > >> On Thu, Jun 12, 2014 at 11:50 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > >> > On Thu, Jun 12, 2014 at 01:37:19PM +0000, Sven Kieske wrote: > >> >> are you sure acpid is running inside the guest? > >> > > >> > ... or a guest agent? > >> > >> yes, both of them are running in guest. > >> > >> > > >> > Can you find the shutdown request on /var/log/vdsm/vdsm.log on the host > >> > that runs your guest? > >> > >> yes, this is the log: > >> > >> Thread-158109::DEBUG::2014-06-12 > >> 16:08:26,589::BindingXMLRPC::965::vds::(wrapper) client > >> [10.10.10.75]::call vmShutdown with > >> ('b552d1aa-bc35-4788-a448-1726d4b984d5', '30', 'System Administrator > >> has initiated shutdown of this Virtual Machine. Virtual Machine is > >> shutting down.') {} flowID [5939b847] > >> Thread-158109::DEBUG::2014-06-12 > >> 16:08:26,590::vm::2532::vm.Vm::(shutdown) > >> vmId=`b552d1aa-bc35-4788-a448-1726d4b984d5`::guestAgent shutdown > >> called > >> Thread-158109::DEBUG::2014-06-12 > >> 16:08:26,590::guestIF::304::vm.Vm::(desktopShutdown) > >> vmId=`b552d1aa-bc35-4788-a448-1726d4b984d5`::desktopShutdown called > >> Thread-158109::DEBUG::2014-06-12 > >> 16:08:26,591::BindingXMLRPC::972::vds::(wrapper) return vmShutdown > >> with {'status': {'message': 'Machine shut down', 'code': 0}} > > > > I there no attempt to use ACPI lower in the logs? > > > > Anyway, it seems that an ACPI even is received by the guest. Could you > > now share the log of your guest agent, in order to see if it received > > the shutdown request and handled it somehow? > > This is the log: > Dummy-2::INFO::2014-06-16 > 17:01:06,001::OVirtAgentLogic::266::root::Received an external > command: shutdown... > Dummy-2::INFO::2014-06-16 > 17:01:06,001::OVirtAgentLogic::291::root::Shutting down (timeout = 30, > message = 'System Administrator has initiated shutdown of this Virtual > Machine. Virtual Machine is shutting down.') > Dummy-2::DEBUG::2014-06-16 > 17:01:06,002::GuestAgentLinux2::178::root::Executing shutdown command: > ['/usr/share/ovirt-guest-agent/ovirt-shutdown', '-h', '+1', u'"System > Administrator has initiated shutdown of this Virtual Machine. Virtual > Machine is shutting down."'] > > After check this log, I think I find the problem, the ovirthguest user > haven't permission to sudo, so I add ovirtagent to sudoers. > %ovirtagent ALL NOPASSWD: /usr/share/ovirt-guest-agent/ovirt-shutdown-wrapper.sh > > It work. But I find another problem. I just modify a guest of pool, > after reboot, I miss sodoers config, it is back to orignal. How to > keep this config without change template? > > Thank you! > > -- > Regards, > John Xue

1 0

Call for Papers Deadline in One Week
by Brian Proffitt 15 Jun '14

15 Jun '14

Conference: Open World Forum 2014 Information: This year's program will show you how to take back control of your digital world, including IT/IS and (personal) data, whether you are a professional or not. Stop losing control and discover how Free and Open Source software may help you be more and more independent, whether technologically, legally or financially. Date: October 30-November 1, 2014 Location: Paris, France Website: http://openworldforum.org/ Call for Papers Deadline: June 22, 2014 Call for Papers URL: http://openworldforum.org/en/cfp/ -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

After Upgrade to 3.4.2 no conole icon activation
by Markus Stockhausen 15 Jun '14

15 Jun '14

------=_NextPartTM-000-6db8488a-f18e-4c62-ab27-e5e97c254097 Content-Type: multipart/alternative; boundary="_000_12EF8D94C6F8734FB2FF37B9FBEDD1735862B0A8EXCHANGEcollogi_" --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735862B0A8EXCHANGEcollogi_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, after starting a VM in webadmin on ovirt engine 3.4.2 we have to manually switch to another VM and back to get the console icon active. Is this behaviour desired? Markus --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735862B0A8EXCHANGEcollogi_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html dir=3D"ltr"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" id=3D"owaParaStyle"></style> </head> <body fpstyle=3D"1" ocsi=3D"0"> <div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: = 10pt;">Hello, <div><br> </div> <div>after starting a VM in webadmin on ovirt engine 3.4.2 we have</div> <div>to manually switch to another VM and back to get the console</div> <div>icon active.</div> <div><br> </div> <div>Is this behaviour desired?</div> <div><br> </div> <div>Markus</div> </div> </body> </html> --_000_12EF8D94C6F8734FB2FF37B9FBEDD1735862B0A8EXCHANGEcollogi_-- ------=_NextPartTM-000-6db8488a-f18e-4c62-ab27-e5e97c254097 Content-Type: text/plain; name="InterScan_Disclaimer.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="InterScan_Disclaimer.txt" **************************************************************************** Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Über das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 **************************************************************************** ------=_NextPartTM-000-6db8488a-f18e-4c62-ab27-e5e97c254097--

2 2

Resource Pools in oVirt
by s k 14 Jun '14

14 Jun '14

--_fd17b1d6-c06b-4854-bb53-dd62b57eb9ae_ Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Hello all=2C As far as I understand=2C CPU Shares can be set on each VM individually and= cannot be changed while it's powered on. It would be great if we could create resource pools (similar to what VMware= does) for CPU shares so that we could assign priorities on multiple VMs an= d be able to move them between Resource Pools of different priorities. I k= now that we can configure quotas but it's not the same as CPU shares. Is that something planned for a future release? Shall I open an RFE for tha= t ? Regards=2C Sokratis = --_fd17b1d6-c06b-4854-bb53-dd62b57eb9ae_ Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable <html> <head> <style></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>Hello all=2C<div><br></div><div>= As far as I understand=2C CPU Shares can be set on each VM individually and= cannot be changed while it's powered on.</div><div><br></div><div><br></di= v><div>It would be great if we could create resource pools (similar to what= VMware does) for CPU shares so that we could assign priorities on multiple= VMs and be able to move them between Resource Pools of different prioritie= s. &nbsp=3BI know that we can configure quotas but it's not the same as CPU= shares.</div><div><br></div><div>Is that something planned for a future re= lease? Shall I open an RFE for that ?</div><div><br></div><div>Regards=2C</= div><div><br></div><div>Sokratis</div> </div></body> </html>= --_fd17b1d6-c06b-4854-bb53-dd62b57eb9ae_--

3 4

Gluster VMs Paused State then not resumable
by Andrew Lau 14 Jun '14

14 Jun '14

Hi all, I'm wondering if anyone's had any luck with running VMs on top of a gluster VM? I have a bug open here, https://bugzilla.redhat.com/show_bug.cgi?id=1058300 about VMs going into a paused state and not being able to resume. It's gone a little quiet, so I was wondering has anyone else had any luck with this style of setup? I have my gluster and virt on the same boxes, and currently 5 in the cluster (replica 2) A few cases this can be reproduced: - switch dies - cable unplug - gluster volume stop - gluster brick dies I recently tried a suggested volume option: gluster volume set vm-data network.ping-timeout 10 The qemu logs now report on virsh resume vmname: block I/O error in device 'drive-virtio-disk0': Transport endpoint is not connected (107) Thanks, Andrew

1 0

Live Snapshot issue (once more) with the new QEMU Packages (V10) from CENTOS Updates
by Christian Rebel 13 Jun '14

13 Jun '14

Hi all, after today's CentOS "yum update", I had once more the Problem with LIVE Snapshots due to the new "qemu packages". Can anyone explain me why there is such a huge difference between the "CENTOS QEMU Packages" and the "Jenkins RHEV qemu Packages". CENTOS QEMU = LIVE Snapshot failed (tested with qemu versions V8 and V10) * VDSErrorException: VDSGenericException: VDSErrorException: Failed to SnapshotVDS, error = Snapshot failed, code = 48 JENKINS QEMU = LIVE Snapshots ok (tested with qemu versions V8 and V10) * Command CreateAllSnapshotsFromVm, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) returned status finished, result 'success'. Thanks! Christian

3 2

Live Snapshot issue (once more) with the new QEMU Packages (V5.10) from CENTOS Updates
by Christian Rebel 13 Jun '14

13 Jun '14

Hi all, after today's CentOS "yum update", I had once more the Problem with LIVE Snapshots due to the new "qemu packages". Can anyone explain me why there is such a huge difference between the "CENTOS QEMU Packages" and the "Jenkins RHEV qemu Packages". CENTOS QEMU = LIVE Snapshot failed (tested with qemu versions V5.8 and 5.10) * VDSErrorException: VDSGenericException: VDSErrorException: Failed to SnapshotVDS, error = Snapshot failed, code = 48 JENKINS QEMU = LIVE Snapshots ok (tested with qemu versions V5.8 and 5.10) * Command CreateAllSnapshotsFromVm, Parameters Type org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters) returned status finished, result 'success'. Thanks! Christian

1 0

Network traffic being mirrored
by Jim Rippon 13 Jun '14

13 Jun '14

--=_4ab7acf68b2ea1ad39d80d5183539e8e Content-Transfer-Encoding: 7bit Content-Type: text/plain Hi guys, I am seeing network traffic being sent to all my VMs on one of my oVirt hosts, but not the other two in that same datacentre. The VMs are running CentOS, and I've been monitoring the sessions with iptraf, and can see traffic from all other VMs on that network being received by all other VMs running on this host which have an interface on that same network. Is this something anyone has seen, or could anyone suggest anything I should be looking at to further diagnose? Many thanks, Jim Rippon --=_4ab7acf68b2ea1ad39d80d5183539e8e Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html><body style=3D'font-size: 10pt; font-family: Verdana,Geneva,sans-seri= f'> <p>Hi guys,</p> <p>I am seeing network traffic being sent to all my VMs on one of my oVirt = hosts, but not the other two in that same datacentre.  The VMs are run= ning CentOS, and I've been monitoring the sessions with iptraf, and can see= traffic from all other VMs on that network being received by all other VMs= running on this host which have an interface on that same network.</p> <p>Is this something anyone has seen, or could anyone suggest anything I sh= ould be looking at to further diagnose?</p> <p>Many thanks,</p> <p>Jim Rippon</p> <div> </div> </body></html> --=_4ab7acf68b2ea1ad39d80d5183539e8e--

2 2

Re: [ovirt-users] [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute
by Gianluca Cecchi 13 Jun '14

13 Jun '14

Il 13/giu/2014 19:14 "Todd" <tdsan(a)yahoo.com> ha scritto: > > This is what I found, thank you for sharing: > > [root@ovirt ~]# journalctl -r -a -u ovirt-engine > > -- Logs begin at Wed 2014-06-04 10:56:26 EDT, end at Fri 2014-06-13 13:04:02 EDT > > Jun 12 17:02:18 ovirt.od.itots.local ovirt-engine.py[6127]: 2014-06-12 17:02:18, > > Jun 12 17:02:17 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... > > Jun 12 17:01:28 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. > > -- Reboot -- > > Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter > > Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. > > Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc > > Jun 11 00:11:07 ovirt.od.itots.local ovirt-engine.py[6504]: 2014-06-11 00:11:07, > > Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... > > Jun 11 00:10:39 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. > > Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter > > Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. > > Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc > > Jun 11 00:02:02 ovirt.od.itots.local ovirt-engine.py[3623]: 2014-06-11 00:02:02, > > Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... > > Jun 11 00:01:34 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. > > Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter > > Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. > > Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc > > Jun 10 20:31:22 ovirt.od.itots.local ovirt-engine.py[31568]: 2014-06-10 20:31:22 > > Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... > > Jun 10 20:30:53 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. > > Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter > > Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. > > Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc > > Jun 10 20:29:11 ovirt.od.itots.local ovirt-engine.py[28721]: 2014-06-10 20:29:11 > > Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... > > Jun 10 20:28:12 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. > > > > [root@ovirt ~]# systemctl status ovirt-engine > > ovirt-engine.service - oVirt Engine > > Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; disabled) > > Active: failed (Result: exit-code) since Thu 2014-06-12 17:02:18 EDT; 20h ago > > Main PID: 6127 (code=exited, status=1/FAILURE) > > CGroup: /system.slice/ovirt-engine.service > > > > Jun 12 17:02:18 ovirt.od.itots.local ovirt-engine.py[6127]: 2014-06-12 17:02:... > > Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main ...E > > Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. > > Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service e.... > > Hint: Some lines were ellipsized, use -l to show in full. > > > > Todd > > > > From: Gianluca Cecchi [mailto:gianluca.cecchi@gmail.com] > Sent: Thursday, June 12, 2014 6:35 PM > To: Todd; users > > Subject: Re: [ovirt-users] [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute > > > > On Fri, Jun 13, 2014 at 12:23 AM, Todd <tdsan(a)yahoo.com> wrote: > > One thing I did, I added an additional 4 to make it 8GB to the machine. > > > > And it still does the same thing, but it is saying there is a problem with the systemctl “Closing up” error. > > > > How is that related to the amount of memory, at present, I just want to bring up the web interface and get it installed. > > > > Todd > > > > > > Keep replies on list, so that other can help too if necessary. > I think the init service should have been installed anyway. > What you get from the command > > # systemctl status ovirt-engine > > for example on my system I get this > > > [g.cecchi@tekkaman ~]$ sudo systemctl status ovirt-engine > ovirt-engine.service - oVirt Engine > Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled) > Active: active (running) since Fri 2014-06-13 00:24:55 CEST; 2min 49s ago > Main PID: 1899 (ovirt-engine.py) > CGroup: name=systemd:/system/ovirt-engine.service > ├─1899 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --system... > └─2370 ovirt-engine -server -XX:+TieredCompilation -Xms1g -Xmx1g -XX:PermSize=256m -XX:MaxPermSize=256m -Djava.... > > Jun 13 00:24:54 tekkaman.localdomain.local systemd[1]: Starting oVirt Engine... > Jun 13 00:24:55 tekkaman.localdomain.local systemd[1]: Started oVirt Engine. > > And also the command > > # journalctl -r -a -u ovirt-engine > > for example I had a failure on November and the comamnd at a certain point gives: > > Nov 24 20:27:29 tekkaman.localdomain.local systemd[1]: Unit ovirt-engine.service entered failed state. > Nov 24 20:27:29 tekkaman.localdomain.local systemd[1]: Failed to start oVirt Engine. > Nov 24 20:27:29 tekkaman.localdomain.local systemd[1]: ovirt-engine.service: control process exited, code=exited status=1 > Nov 24 20:27:29 tekkaman.localdomain.local engine-service[2598]: Starting engine-service: [FAILED] > Nov 24 20:27:29 tekkaman.localdomain.local engine-service[2598]: The directory "/usr/lib/jvm/jre-1.7.0-openjdk.x86_64" doesn' > Nov 24 20:27:29 tekkaman.localdomain.local systemd[1]: Starting oVirt Engine... > > so your output should contain something useful. > > Also, id you run > > engine-cleanup > > before running engine-setup again after adding memory? It should help too. > > Gianluca > > ________________________________ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2014.0.4142 / Virus Database: 3604/6715 - Release Date: 10/01/13 > Internal Virus Database is out of date. What about engine-cleanup? Did you run it? Also, engine-setup generates a log file (you should find its reference in output). share it with the list so that one of the developers could help you....

1 0

[ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute
by Todd 13 Jun '14

13 Jun '14

This is a multipart message in MIME format. ------=_NextPart_000_03B4_01CF870A.56908BD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I have increased the amount of Ram from 4GB to 8GB This is what I found: [root@ovirt ~]# journalctl -r -a -u ovirt-engine -- Logs begin at Wed 2014-06-04 10:56:26 EDT, end at Fri 2014-06-13 13:04:02 EDT Jun 12 17:02:18 ovirt.od.itots.local ovirt-engine.py[6127]: 2014-06-12 17:02:18, Jun 12 17:02:17 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... Jun 12 17:01:28 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. -- Reboot -- Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc Jun 11 00:11:07 ovirt.od.itots.local ovirt-engine.py[6504]: 2014-06-11 00:11:07, Jun 11 00:11:07 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... Jun 11 00:10:39 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc Jun 11 00:02:02 ovirt.od.itots.local ovirt-engine.py[3623]: 2014-06-11 00:02:02, Jun 11 00:02:02 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... Jun 11 00:01:34 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc Jun 10 20:31:22 ovirt.od.itots.local ovirt-engine.py[31568]: 2014-06-10 20:31:22 Jun 10 20:31:22 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... Jun 10 20:30:53 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service enter Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main proc Jun 10 20:29:11 ovirt.od.itots.local ovirt-engine.py[28721]: 2014-06-10 20:29:11 Jun 10 20:29:11 ovirt.od.itots.local systemd[1]: Starting oVirt Engine... Jun 10 20:28:12 ovirt.od.itots.local systemd[1]: Stopped oVirt Engine. [root@ovirt ~]# systemctl status ovirt-engine ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; disabled) Active: failed (Result: exit-code) since Thu 2014-06-12 17:02:18 EDT; 20h ago Main PID: 6127 (code=exited, status=1/FAILURE) CGroup: /system.slice/ovirt-engine.service Jun 12 17:02:18 ovirt.od.itots.local ovirt-engine.py[6127]: 2014-06-12 17:02:... Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: ovirt-engine.service: main ...E Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: Failed to start oVirt Engine. Jun 12 17:02:18 ovirt.od.itots.local systemd[1]: Unit ovirt-engine.service e.... Hint: Some lines were ellipsized, use -l to show in full. Todd ---------------------------------------------------------------------------- ------------------------------------------- Message: 3 Date: Thu, 12 Jun 2014 21:51:20 +0200 From: Gianluca Cecchi < <mailto:gianluca.cecchi@gmail.com> gianluca.cecchi(a)gmail.com> To: Todd < <mailto:tdsan@yahoo.com> tdsan(a)yahoo.com> Cc: users < <mailto:users@ovirt.org> users(a)ovirt.org> Subject: Re: [ovirt-users] [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute Message-ID: < <mailto:CAG2kNCw5wLniTXsz2BJGmJZr1o_dMHPzzucoqOwAOA4mFRHVDg@mail.gmail.com> CAG2kNCw5wLniTXsz2BJGmJZr1o_dMHPzzucoqOwAOA4mFRHVDg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" How much ram do you have on this system?

1 0