[ovirt-users] [ ERROR ] Failed to execute stage 'Closing up': Command '/bin/systemctl' failed to execute

Fri Jun 13 17:22:48 UTC 2014

Il 13/giu/2014 19:14 "Todd" <tdsan at yahoo.com> ha scritto:
>
> This is what I found, thank you for sharing:
>
> [root at 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 at 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 at 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 at 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 at 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....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140613/e8408c11/attachment-0001.html>