Re: [ovirt-users] Building oVirt engine on Debian

> On Thu, Jun 8, 2017 at 6:28 AM, Leni Kadali Mutungi > wrote: >> I assigned the CentOS VM 3GB of RAM, so that could very well be the >> problem. So the next step will be to increase the RAM of the VM to 4GB >> and report back with my findings. Results of the build. It

Re: [ovirt-users] Building oVirt engine on Debian

On Thu, Jun 8, 2017 at 6:28 AM, Leni Kadali Mutungi wrote: > Results on trying a separate build on a CentOS VM are again a freeze > at the same point as stated below: > > [INFO] weaveinfo Join point 'constructor-execution(void >

Re: [ovirt-users] Building oVirt engine on Debian

Results on trying a separate build on a CentOS VM are again a freeze at the same point as stated below: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' in Type

Re: [ovirt-users] Building oVirt engine on Debian

On Wed, Jun 7, 2017 at 3:29 AM, Leni Kadali Mutungi wrote: > On 6/6/17, Yedidyah Bar David wrote: >> On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi >> wrote: >> So, did the engine also start successfully? > Successfully ran >

Re: [ovirt-users] Building oVirt engine on Debian

On 6/6/17, Yedidyah Bar David wrote: > On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi > wrote: > So, did the engine also start successfully? Successfully ran `/home/user/ovirt_engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py start`

Re: [ovirt-users] Building oVirt engine on Debian

On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi wrote: > Setup was successful. Attached is the message I received. I didn't > mind the firewalld bits since I don't have that installed. However all > the ovn-* commands didn't work. I tried locating their equivalents, >

Re: [ovirt-users] Building oVirt engine on Debian

Setup was successful. Attached is the message I received. I didn't mind the firewalld bits since I don't have that installed. However all the ovn-* commands didn't work. I tried locating their equivalents, thinking that they could be in the ovirt_engine folder or something along those lines. The

Re: [ovirt-users] Building oVirt engine on Debian

On Fri, Jun 2, 2017 at 7:07 AM, Leni Kadali Mutungi wrote: > On 6/1/17, Leni Kadali Mutungi wrote: >> On 6/1/17, Yedidyah Bar David wrote: >>> The message: >>> >>> No handlers could be found for logger >>>

Re: [ovirt-users] Building oVirt engine on Debian

On 6/1/17, Yedidyah Bar David wrote: > The message: > > No handlers could be found for logger > "ovirt.engine.ovirt_engine.configfile" > > is ugly, but harmless. It almost always appears in the setup log file. > You are welcome to open a bug about it, though. > > Not sure what's

Re: [ovirt-users] Building oVirt engine on Debian

On Wed, May 31, 2017 at 6:17 AM, Leni Kadali Mutungi wrote: > On 5/30/17, Leni Kadali Mutungi wrote: >> Managed to build successfully using a directory in home that the >> non-root user can write to. However I when I ran the engine-setup, I >> ran

Re: [ovirt-users] Building oVirt engine on Debian

On 5/30/17, Leni Kadali Mutungi wrote: > Managed to build successfully using a directory in home that the > non-root user can write to. However I when I ran the engine-setup, I > ran into the issue of specifying a fully qualified domain name. I > tried the possible answers

Re: [ovirt-users] Building oVirt engine on Debian

Managed to build successfully using a directory in home that the non-root user can write to. However I when I ran the engine-setup, I ran into the issue of specifying a fully qualified domain name. I tried the possible answers I could think of (hostname.example.com, 127.0.0.1) but they didn't seem

Re: [ovirt-users] Building oVirt engine on Debian

On Mon, May 29, 2017 at 9:32 AM, Yedidyah Bar David wrote: > On Mon, May 29, 2017 at 6:52 AM, Leni Kadali Mutungi > wrote: >> I have read what is in the README.adoc and done all of it. >> Unfortunately, even with BUILD_ALL_USER_AGENTS=0, my computer would

Re: [ovirt-users] Building oVirt engine on Debian

On Mon, May 29, 2017 at 6:52 AM, Leni Kadali Mutungi wrote: > I have read what is in the README.adoc and done all of it. > Unfortunately, even with BUILD_ALL_USER_AGENTS=0, my computer would > still freeze. I had to opt to not build the gwt ui instead. I hope > it's not

Re: [ovirt-users] Building oVirt engine on Debian

I have read what is in the README.adoc and done all of it. Unfortunately, even with BUILD_ALL_USER_AGENTS=0, my computer would still freeze. I had to opt to not build the gwt ui instead. I hope it's not too important :P. Build went on fine. Ran into this issue: install: cannot create regular

Re: [ovirt-users] Building oVirt engine on Debian

I have forgotten that you are doing it in debian. Maybe in case of debian the error can there for some other reason so I leave it for others to answer. But one more thing you can try is to decrease your swappiness value to 10. If you have enough ram then this will at least make your system freeze

Re: [ovirt-users] Building oVirt engine on Debian

On 5/25/17, shubham dubey wrote: > Hi, > I got the same problem once and it seems to be related to memory. > So first thing is make sure you have at least 4 gb of ram because thats the > minimum requirement for ovirt-engine to run. > If with 4gb+ ram you still getting error

Re: [ovirt-users] Building oVirt engine on Debian

On 5/25/17, Yedidyah Bar David wrote: > On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi > wrote: >> Ran `make clean install-dev` and the process freezes at: >> [INFO] weaveinfo Join point 'constructor-execution(void >>

Re: [ovirt-users] Building oVirt engine on Debian

On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi wrote: > Ran `make clean install-dev` and the process freezes at: > [INFO] weaveinfo Join point 'constructor-execution(void > com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' > in

[ovirt-users] Building oVirt engine on Debian

Ran `make clean install-dev` and the process freezes at: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised