[ovirt-users] getting 404 after fresh install of oVirt 3.4 on CentOS 6.5 (+ solution)

[Yedidyah Bar David]

----- Original Message -----
> From: "Steven Van Acker" <Steven.VanAcker at cs.kuleuven.be>
> To: users at ovirt.org
> Sent: Tuesday, May 13, 2014 10:39:03 AM
> Subject: [ovirt-users] getting 404 after fresh install of oVirt 3.4 on	CentOS 6.5 (+ solution)
> 
> Hello all,
> 
> I was asked to post the following problem on this mailinglist.
> 
> After installing a clean CentOS 6.5 with a clean oVirt 3.4, following the
> instructions from
> http://www.ovirt.org/Download#Red_Hat_Enterprise_Linux_6.2FCentOS_Installation_Instructions
> I went to http://localhost.localdomain:80/ovirt-engine as indicated and was
> redirected to a 404 page. The same happened when using https.
> 
> During the installation, engine-setup will print out the following on my VM
> with 512MB RAM:
> 
> [WARNING] Warning: Not enough memory is available on the host. Minimum
> requirement is 4096MB, and 16384MB is recommended.
> SSH fingerprint: 4B:DE:48:26:99:AA:C0:72:E3:C8:B5:64:5F:6E:6D:00
> Internal CA FB:82:FE:14:35:3A:BE:1A:B1:E6:99:C2:DC:CD:6D:E0:44:64:0F:47
> Web access is enabled at:
> http://localhost.localdomain:80/ovirt-engine
> https://localhost.localdomain:443/ovirt-engine
> Please use the user "admin" and password specified in order to login into
> oVirt Engine
> 
> The consequence of not having enough RAM for oVirt is that it will silently
> fail to start up, without apparent errors or warnings.

You mean, in the log?

> In my view, the warning above should be rephrased as "Not enough memory is
> available on the host, oVirt will refuse to start" and colored red.

Did it 'refuse' to start, or simply failed to start?

With what conditions exactly you want this error? What if the engine does
manage to start (e.g. because you did some weird tweaking and managed to
make it run in 256MB)? What if it later fails, after you add a few tens of
hosts/VMs?

I know I regularly use a 1GB VM for testing setup, never had problems.

Generally, red stuff in setup is reserved to real errors - when something
failed.

> 
> The solution to this problem is to have at least 4GB of RAM, after which
> oVirt seems to start up fine (with only 1.2GB of RAM in use).

How did you measure that? On my current test VM, I have:

# ps aux | grep ovirt-engine
ovirt    10840  0.0  0.2 207952  2168 ?        Ss   10:08   0:00 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py --redirect-output --systemd=notify start
ovirt    10879  0.8 52.4 2247040 534892 ?      Sl   10:08   0:46 ovirt-engine -server -XX:+TieredCompilation -Xms1g -Xmx1g -XX:PermSize=256m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Djsse.enableSNIExtension=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/ovirt-engine/dump -Djava.util.logging.manager=org.jboss.logmanager -Dlogging.configuration=file:///var/tmp/ovirt-engine/config/ovirt-engine-logging.properties -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.modules.write-indexes=false -Djboss.server.default.config=ovirt-engine -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=/usr/share/ovirt-engine -Djboss.server.data.dir=/var/lib/ovirt-engine -Djboss.server.log.dir=/var/log/ovirt-engine -Djboss.server.config.dir=/var/tmp/ovirt-engine/config -Djboss.server.temp.dir=/var/tmp/ovirt-engine/tmp -Djboss.controller.temp.dir=/var/tmp/ovirt-engine/tmp -jar /usr/share/jboss-as/jboss-modules.jar -mp /var/tmp/ovirt-engine/modules/00-ovirt-engin -modules:/var/tmp/ovirt-engine/modules/01-jboss-as-modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -c ovirt-engine.xml
ovirt    10900  0.0  0.2 286084  2604 ?        Ss   10:08   0:01 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py --systemd=notify start
root     12200  0.0  0.0 112636   964 pts/10   S+   11:38   0:00 grep --color=auto ovirt-engine

# free
             total       used       free     shared    buffers     cached
Mem:       1019660     936780      82880          0       5068     259496
-/+ buffers/cache:     672216     347444
Swap:     14749692     164328   14585364

So the engine uses 2.2GB of virtual memory, but only 530MB rss, and total
system use is, without caches, 670MB. So it's likely that a 512MB VM will
not be enough.

Thanks for the report!
-- 
Didi