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@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
participants (1)
-
Gianluca Cecchi