6:05 a.m.
Ran `make clean install-dev` and the process freezes at:
[INFO] weaveinfo Join point 'constructor-execution(void
com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised by after advice from
'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
My computer freezes at that point and I have to power it off. I tried
doing it in the terminal without the Desktop Environment and I get the
same result. The component being built is the UI Common Web. Advice on
what to do next is appreciated.
--
- Warm regards
Leni Kadali Mutungi
8:58 a.m.
On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised by after advice from
'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
My computer freezes at that point and I have to power it off. I tried
doing it in the terminal without the Desktop Environment and I get the
same result. The component being built is the UI Common Web. Advice on
what to do next is appreciated.
How long did you wait?
Perhaps you run out of memory? How much do you have?
Was the kernel not responding either?
You can search the net for general debugging techniques for such
occasions. E.g. you can (beforehand):
echo 1 > /proc/sys/kernel/sysrq
Then you can press Alt-SysRq-m to see (in text console) memory status
and Alt-SysRq-t to see some information about each running task.
Did you increase number of max open file descriptors?
Building the gwt ui is a very heavy process.
You can build for firefox only by passing BUILD_ALL_USER_AGENTS=0,
or not build it at all by passing BUILD_GWT=0.
See also README.adoc .
Good luck,
--
- Warm regards
Leni Kadali Mutungi
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Didi
5:13 a.m.
On 5/25/17, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Thu, May 25, 2017 at 6:05 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
> in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
> (ControlFlowAnalyzer.java:905) advised by after advice from
> 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
>
> My computer freezes at that point and I have to power it off. I tried
> doing it in the terminal without the Desktop Environment and I get the
> same result. The component being built is the UI Common Web. Advice on
> what to do next is appreciated.
How long did you wait?
10-15 minutes. I tried 30 minutes at one point.
Perhaps you run out of memory? How much do you have?
8GB of
RAM, 16GB of swap
Was the kernel not responding either?
I have no idea; have
never been in a situation where the kernel
doesn't respond. When I was running the build in a virtual terminal, I
would become unable to access the other terminals using Ctrl-Alt-F1 to
F6 after I attempted to access the GUI on F7.
You can search the net for general debugging techniques for such
occasions. E.g. you can (beforehand):
echo 1 > /proc/sys/kernel/sysrq
Then you can press Alt-SysRq-m to see (in text console) memory status
and Alt-SysRq-t to see some information about each running task.
I'll try this,
thanks.
Did you increase number of max open file descriptors?
No I
didn't. Will also do.
Building the gwt ui is a very heavy process.
You can build for firefox only by passing BUILD_ALL_USER_AGENTS=0,
or not build it at all by passing BUILD_GWT=0.
Will try this as a last resort.
--
- Warm regards
Leni Kadali Mutungi
6:52 a.m.
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 file
'/usr/local/etc/logrotate.d/ovirt-engine-setup': Permission denied
install: cannot create regular file
'/usr/local/etc/logrotate.d/ovirt-engine-notifier': Permission denied
install: cannot create regular file
'/usr/local/etc/logrotate.d/ovirt-engine': Permission denied
Makefile:301: recipe for target 'copy-recursive' failed
make[2]: *** [copy-recursive] Error 1
make[2]: Leaving directory '/home/user/ovirt-engine'
Makefile:420: recipe for target 'install-packaging-files' failed
make[1]: *** [install-packaging-files] Error 2
make[1]: Leaving directory '/home/user/ovirt-engine'
Makefile:521: recipe for target 'install-dev' failed
make: *** [install-dev] Error 2
So usually I'd solve this by running as root, but since you've advised
against it, what should I do to give the normal user permission to run
this operation since the folder is owned by root and the group is
staff? My looking through other responses to similar situations
indicates to me that giving the non-root user access to this folder
isn't recommended. What would be the best solution in my case?
--
- Warm regards
Leni Kadali Mutungi
9:32 a.m.
On Mon, May 29, 2017 at 6:52 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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 too important :P.
It is, eventually, but if you do manage to build without it, then it's
a good step forward, and it most likely means you do need more memory.
I suggest opening a new thread about this specifically, perhaps even
one here (ask what developers are using) and one on infra (ask what CI
uses when building release builds).
If it turns out that at least some people use similar hardware without
problems, it might indeed be an issue specific to your environment -
kernel, swap etc configuration, jdk/jvm, etc.
If possible it might make sense to try an identical build on a centos7
VM just to see it's not a hardware problem (although I can't think of
anything that will trigger such a problem).
Build went on fine. Ran into this issue:
install: cannot create regular file
'/usr/local/etc/logrotate.d/ovirt-engine-setup': Permission denied
install: cannot create regular file
'/usr/local/etc/logrotate.d/ovirt-engine-notifier': Permission denied
install: cannot create regular file
'/usr/local/etc/logrotate.d/ovirt-engine': Permission denied
Makefile:301: recipe for target 'copy-recursive' failed
make[2]: *** [copy-recursive] Error 1
make[2]: Leaving directory '/home/user/ovirt-engine'
Makefile:420: recipe for target 'install-packaging-files' failed
make[1]: *** [install-packaging-files] Error 2
make[1]: Leaving directory '/home/user/ovirt-engine'
Makefile:521: recipe for target 'install-dev' failed
make: *** [install-dev] Error 2
So usually I'd solve this by running as root, but since you've advised
against it, what should I do to give the normal user permission to run
this operation since the folder is owned by root and the group is
staff? My looking through other responses to similar situations
indicates to me that giving the non-root user access to this folder
isn't recommended. What would be the best solution in my case?
I guess most if not all developers simply use PREFIX that points at a
writable place - ~/my-ovirt-engine or something like that. That's
mentioned in the readme, and also in:
http://www.ovirt.org/develop/developer-guide/engine/engine-development-en...
Best,
--
- Warm regards
Leni Kadali Mutungi
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Didi
9:33 a.m.
On Mon, May 29, 2017 at 9:32 AM, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Mon, May 29, 2017 at 6:52 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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 too important :P.
It is, eventually, but if you do manage to build without it, then it's
a good step forward, and it most likely means you do need more memory.
I suggest opening a new thread about this specifically, perhaps even
one here
Or perhaps on devel(a)ovirt.org.
(ask what developers are using) and one on infra (ask what CI
uses when building release builds).
If it turns out that at least some people use similar hardware without
problems, it might indeed be an issue specific to your environment -
kernel, swap etc configuration, jdk/jvm, etc.
If possible it might make sense to try an identical build on a centos7
VM just to see it's not a hardware problem (although I can't think of
anything that will trigger such a problem).
>
> Build went on fine. Ran into this issue:
>
> install: cannot create regular file
> '/usr/local/etc/logrotate.d/ovirt-engine-setup': Permission denied
> install: cannot create regular file
> '/usr/local/etc/logrotate.d/ovirt-engine-notifier': Permission denied
> install: cannot create regular file
> '/usr/local/etc/logrotate.d/ovirt-engine': Permission denied
> Makefile:301: recipe for target 'copy-recursive' failed
> make[2]: *** [copy-recursive] Error 1
> make[2]: Leaving directory '/home/user/ovirt-engine'
> Makefile:420: recipe for target 'install-packaging-files' failed
> make[1]: *** [install-packaging-files] Error 2
> make[1]: Leaving directory '/home/user/ovirt-engine'
> Makefile:521: recipe for target 'install-dev' failed
> make: *** [install-dev] Error 2
>
> So usually I'd solve this by running as root, but since you've advised
> against it, what should I do to give the normal user permission to run
> this operation since the folder is owned by root and the group is
> staff? My looking through other responses to similar situations
> indicates to me that giving the non-root user access to this folder
> isn't recommended. What would be the best solution in my case?
I guess most if not all developers simply use PREFIX that points at a
writable place - ~/my-ovirt-engine or something like that. That's
mentioned in the readme, and also in:
http://www.ovirt.org/develop/developer-guide/engine/engine-development-en...
Best,
>
> --
> - Warm regards
> Leni Kadali Mutungi
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
--
Didi
--
Didi
7:40 p.m.
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 to work. I then killed the process
using Ctrl-C but I'm unable to re-run it again. The error I get is:
No handlers could be found for logger "ovirt.engine.ovirt_engine.configfile"
I tried running `locate` to find the code related to this but I was
unable to find it.
I have also run engine-cleanup but it didn't seem to work.
engine-config didn't seem to give me the option of correcting my
mistake.
Advice on what to do next would be appreciated.
--
- Warm regards
Leni Kadali Mutungi
6:17 a.m.
On 5/30/17, Leni Kadali Mutungi <lenikmutungi(a)gmail.com> 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 I could think of (hostname.example.com,
127.0.0.1) but they didn't seem to work.
For this I searched the archives and the problem seems to be with what
I've defined in my /etc/hosts file. So this one I know how to solve.
So how do I get the engine-setup to run again?
--
- Warm regards
Leni Kadali Mutungi
10:27 a.m.
On Wed, May 31, 2017 at 6:17 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> wrote:
On 5/30/17, Leni Kadali Mutungi <lenikmutungi(a)gmail.com>
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 I could think of (hostname.example.com,
> 127.0.0.1) but they didn't seem to work.
For this I searched the archives and the problem seems to be with what
I've defined in my /etc/hosts file. So this one I know how to solve.
So how do I get the engine-setup to run again?
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 the problem with engine-setup.
Can you please provide the full output?
Does it create a log file? Can you check/share that one too?
Can you please try this:
OTOPI_DEBUG=1 engine-setup
Best,
--
- Warm regards
Leni Kadali Mutungi
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Didi
7:58 p.m.
On 6/1/17, Yedidyah Bar David <didi(a)redhat.com> 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 the problem with engine-setup.
Can you please provide the full output?
Does it create a log file? Can you check/share that one too?
Apologies I was unable to re-run the engine-setup. So here is the full output:
herabus@trojan:~$ ovirt_engine/bin/engine-setup
[ INFO ] Stage: Initializing
Setup was run under unprivileged user this will produce
development installation do you wish to proceed? (Yes, No) [No]: Yes
[ INFO ] Stage: Environment setup
Configuration files: []
Log file:
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
Version: otopi-1.7.0_master ()
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
Configure Engine on this host (Yes, No) [Yes]: Yes
Configure WebSocket Proxy on this host (Yes, No) [Yes]: Yes
Configure VM Console Proxy on this host (Yes, No) [Yes]: Yes
Install ovirt-provider-ovn(Yes, No) [Yes]?:Yes
--== NETWORK CONFIGURATION ==--
Host fully qualified DNS name of this server
[trojan.dragon.org]: 127.0.1.1
[ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
FQDN. A FQDN is needed to be able to generate certificates correctly.
Host fully qualified DNS name of this server
[trojan.dragon.org]: trojan.dragon.org
[ ERROR ] Host name is not valid: Command 'dig' is required but missing
Host fully qualified DNS name of this server
[trojan.dragon.org]: 127.0.1.1
[ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
FQDN. A FQDN is needed to be able to generate certificates correctly.
Host fully qualified DNS name of this server
[trojan.dragon.org]: ^C[ ERROR ] Failed to execute stage 'Environment
customization': SIG2
[ INFO ] Stage: Clean up
Log file is located at
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
[ INFO ] Generating answer file
'/home/user/ovirt_engine/var/lib/ovirt-engine/setup/answers/20170601195425-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
Attached is the log file. I hope that's alright.
--
- Warm regards
Leni Kadali Mutungi
7:07 a.m.
On 6/1/17, Leni Kadali Mutungi <lenikmutungi(a)gmail.com> wrote:
On 6/1/17, Yedidyah Bar David <didi(a)redhat.com> 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 the problem with engine-setup.
>
> Can you please provide the full output?
>
> Does it create a log file? Can you check/share that one too?
>
Apologies I was unable to re-run the engine-setup. So here is the full
output:
herabus@trojan:~$ ovirt_engine/bin/engine-setup
[ INFO ] Stage: Initializing
Setup was run under unprivileged user this will produce
development installation do you wish to proceed? (Yes, No) [No]: Yes
[ INFO ] Stage: Environment setup
Configuration files: []
Log file:
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
Version: otopi-1.7.0_master ()
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PRODUCT OPTIONS ==--
Configure Engine on this host (Yes, No) [Yes]: Yes
Configure WebSocket Proxy on this host (Yes, No) [Yes]: Yes
Configure VM Console Proxy on this host (Yes, No) [Yes]: Yes
Install ovirt-provider-ovn(Yes, No) [Yes]?:Yes
--== NETWORK CONFIGURATION ==--
Host fully qualified DNS name of this server
[trojan.dragon.org]: 127.0.1.1
[ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
FQDN. A FQDN is needed to be able to generate certificates correctly.
Host fully qualified DNS name of this server
[trojan.dragon.org]: trojan.dragon.org
[ ERROR ] Host name is not valid: Command 'dig' is required but missing
Host fully qualified DNS name of this server
[trojan.dragon.org]: 127.0.1.1
[ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
FQDN. A FQDN is needed to be able to generate certificates correctly.
Host fully qualified DNS name of this server
[trojan.dragon.org]: ^C[ ERROR ] Failed to execute stage 'Environment
customization': SIG2
[ INFO ] Stage: Clean up
Log file is located at
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
[ INFO ] Generating answer file
'/home/user/ovirt_engine/var/lib/ovirt-engine/setup/answers/20170601195425-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
Attached is the log file. I hope that's alright.
Apologies again. I attached
the conf file. Attached is the log file.
--
- Warm regards
Leni Kadali Mutungi
8:32 a.m.
On Fri, Jun 2, 2017 at 7:07 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> wrote:
On 6/1/17, Leni Kadali Mutungi <lenikmutungi(a)gmail.com> wrote:
> On 6/1/17, Yedidyah Bar David <didi(a)redhat.com> 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 the problem with engine-setup.
>>
>> Can you please provide the full output?
>>
>> Does it create a log file? Can you check/share that one too?
>>
> Apologies I was unable to re-run the engine-setup. So here is the full
> output:
> herabus@trojan:~$ ovirt_engine/bin/engine-setup
> [ INFO ] Stage: Initializing
> Setup was run under unprivileged user this will produce
> development installation do you wish to proceed? (Yes, No) [No]: Yes
> [ INFO ] Stage: Environment setup
> Configuration files: []
> Log file:
>
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
> Version: otopi-1.7.0_master ()
> [ INFO ] Stage: Environment packages setup
> [ INFO ] Stage: Programs detection
> [ INFO ] Stage: Environment setup
> [ INFO ] Stage: Environment customization
>
> --== PRODUCT OPTIONS ==--
>
> Configure Engine on this host (Yes, No) [Yes]: Yes
> Configure WebSocket Proxy on this host (Yes, No) [Yes]: Yes
> Configure VM Console Proxy on this host (Yes, No) [Yes]: Yes
> Install ovirt-provider-ovn(Yes, No) [Yes]?:Yes
>
> --== NETWORK CONFIGURATION ==--
>
> Host fully qualified DNS name of this server
> [trojan.dragon.org]: 127.0.1.1
> [ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
> FQDN. A FQDN is needed to be able to generate certificates correctly.
> Host fully qualified DNS name of this server
> [trojan.dragon.org]: trojan.dragon.org
> [ ERROR ] Host name is not valid: Command 'dig' is required but missing
Indeed - please install dig. I think this should work:
apt-get install -y dnsutils
> Host fully qualified DNS name of this server
> [trojan.dragon.org]: 127.0.1.1
> [ ERROR ] Host name is not valid: 127.0.1.1 is an IP address and not a
> FQDN. A FQDN is needed to be able to generate certificates correctly.
> Host fully qualified DNS name of this server
> [trojan.dragon.org]: ^C[ ERROR ] Failed to execute stage 'Environment
> customization': SIG2
> [ INFO ] Stage: Clean up
> Log file is located at
>
/home/user/ovirt_engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20170601195203-2d7fr3.log
> [ INFO ] Generating answer file
>
'/home/user/ovirt_engine/var/lib/ovirt-engine/setup/answers/20170601195425-setup.conf'
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Execution of setup failed
>
> Attached is the log file. I hope that's alright.
Apologies again. I attached the conf file. Attached is the log file.
--
- Warm regards
Leni Kadali Mutungi
--
Didi
6:55 a.m.
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 `sed` and `keytool` commands worked. However I
don't have OpenSwitch installed so I'll add that if it's necessary.
--
- Warm regards
Leni Kadali Mutungi
9:14 a.m.
On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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,
thinking that they could be in the ovirt_engine folder or something
along those lines. The `sed` and `keytool` commands worked. However I
don't have OpenSwitch installed so I'll add that if it's necessary.
You can also ignore ovn for now - just reply 'No' when asked, and even
if you replied Yes I do not think you'll have many problems if you do
not actually use it.
So, did the engine also start successfully?
Best,
--
- Warm regards
Leni Kadali Mutungi
--
Didi
3:29 a.m.
On 6/6/17, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> wrote:
So, did the engine also start successfully?
Successfully ran
`/home/user/ovirt_engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
start`
Unfortunately all I get is the home page. Trying to access the user
portal and administration portal leaves me with a blank page. I guess
this is the consequence of not building the GWT bits?
--
- Warm regards
Leni Kadali Mutungi
9:09 a.m.
On Wed, Jun 7, 2017 at 3:29 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> wrote:
On 6/6/17, Yedidyah Bar David <didi(a)redhat.com> wrote:
> On Tue, Jun 6, 2017 at 6:55 AM, Leni Kadali Mutungi
> <lenikmutungi(a)gmail.com> wrote:
> So, did the engine also start successfully?
Successfully ran
`/home/user/ovirt_engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
start`
Unfortunately all I get is the home page. Trying to access the user
portal and administration portal leaves me with a blank page. I guess
this is the consequence of not building the GWT bits?
I guess so :-)
But check also the logs, var/log/ovirt-engine/* .
--
Didi
6:28 a.m.
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.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised by after advice from
'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
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.
I installed oVirt normally (from repos) on another CentOS VM and I
noticed during engine-setup that the minimum amount of RAM is 4GB and
the preferred amount is 16GB.
I'm guessing 8GB is probably not enough to build oVirt, though I think
it would do for a user install.
--
- Warm regards
Leni Kadali Mutungi
9:49 a.m.
On Thu, Jun 8, 2017 at 6:28 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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
com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised by after advice from
'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
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.
See end of README.adoc and ovirt_build_minimal - you can check the spec
file to see what it causes rpmbuild to actually pass to make.
I installed oVirt normally (from repos) on another CentOS VM and I
noticed during engine-setup that the minimum amount of RAM is 4GB and
the preferred amount is 16GB.
This is unrelated to building.
I'm guessing 8GB is probably not enough to build oVirt, though I
think
it would do for a user install.
For merely starting an engine and see that it works and you can login,
1-2GB are enough too.
For building, I do not know - IIRC last time I built an engine myself,
not in jenkins, I used a 16GB machine. Memory usage depends a lot on
what you choose to build and how - already discussed this in the past.
Best,
--
- Warm regards
Leni Kadali Mutungi
--
Didi
6:42 a.m.
On Thu, Jun 8, 2017 at 6:28 AM, Leni Kadali Mutungi
<lenikmutungi(a)gmail.com> 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 managed to move on
from the point where it freezed.
Here's the output:
[INFO] weaveinfo Join point 'constructor-execution(void
com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.<init>(com.google.gwt.dev.jjs.ast.JProgram))'
in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer'
(ControlFlowAnalyzer.java:905) advised by after advice from
'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java)
[INFO] Compile of permutations succeeded
[INFO] Compilation succeeded -- 357.776s
[INFO] Linking into
/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/generated-gwt/userportal
[INFO] Link succeeded
[INFO] Linking succeeded -- 1.889s
[INFO]
[INFO] --- maven-war-plugin:2.2:war (default-war) @ userportal ---
[INFO] Packaging webapp
[INFO] Assembling webapp [userportal] in
[/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources
[/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/generated-gwt/userportal]
to
[/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT]
[INFO] Copying webapp resources
[/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/src/main/webapp]
[INFO] Webapp assembled in [213 msecs]
[INFO] Building war:
/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT.war
[INFO] WEB-INF/web.xml already added, skipping
[INFO]
[INFO] --- ovirt-jboss-modules-maven-plugin:2.0.1:attach-modules
(default) @ userportal ---
[INFO] The modules source directory
"/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/src/main/modules"
doesn't exist, no modules artifacts will be attached.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ userportal ---
[INFO] Installing
/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/target/userportal-4.2.0-SNAPSHOT.war
to
/home/centos/.m2/repository/org/ovirt/engine/ui/userportal/4.2.0-SNAPSHOT/userportal-4.2.0-SNAPSHOT.war
[INFO] Installing
/home/centos/git/ovirt-engine/frontend/webadmin/modules/userportal-gwtp/pom.xml
to
/home/centos/.m2/repository/org/ovirt/engine/ui/userportal/4.2.0-SNAPSHOT/userportal-4.2.0-SNAPSHOT.pom
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building frontend-symbols 4.2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
frontend-symbols ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
frontend-symbols ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-checkstyle-plugin:2.17:check (checkstyle) @
frontend-symbols ---
[INFO] Starting audit...
Audit done.
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources
(default-testResources) @ frontend-symbols ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) @ frontend-symbols ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @
frontend-symbols ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ frontend-symbols ---
[INFO] Building jar:
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT.jar
[INFO]
[INFO] --- ovirt-jboss-modules-maven-plugin:2.0.1:attach-modules
(default) @ frontend-symbols ---
[INFO] The modules source directory
"/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/src/main/modules"
doesn't exist, no modules artifacts will be attached.
[INFO]
[INFO] --- maven-jar-plugin:2.2:test-jar (test-jar) @ frontend-symbols ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar:
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @
frontend-symbols ---
[INFO] Installing
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT.jar
to
/home/centos/.m2/repository/org/ovirt/engine/ui/frontend-symbols/4.2.0-SNAPSHOT/frontend-symbols-4.2.0-SNAPSHOT.jar
[INFO] Installing
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/pom.xml
to
/home/centos/.m2/repository/org/ovirt/engine/ui/frontend-symbols/4.2.0-SNAPSHOT/frontend-symbols-4.2.0-SNAPSHOT.pom
[INFO] Installing
/home/centos/git/ovirt-engine/frontend/webadmin/modules/frontend-symbols/target/frontend-symbols-4.2.0-SNAPSHOT-tests.jar
to
/home/centos/.m2/repository/org/ovirt/engine/ui/frontend-symbols/4.2.0-SNAPSHOT/frontend-symbols-4.2.0-SNAPSHOT-tests.jar
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building oVirt Server EAR 4.2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
8ef14cb24ef43b892570486a0baa46aa96a51bd5 for
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
8ef14cb24ef43b892570486a0baa46aa96a51bd5 for
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
Downloaded:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
(38 KB at 5.0 KB/sec)
[WARNING] The POM for
org.apache.maven.plugins:maven-ear-plugin:jar:2.8 is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
8ef14cb24ef43b892570486a0baa46aa96a51bd5 for
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
8ef14cb24ef43b892570486a0baa46aa96a51bd5 for
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
Downloaded:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2...
(38 KB at 15.4 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] oVirt Findbugs Filters ............................ SUCCESS [4.256s]
[INFO] ovirt-root ........................................ SUCCESS [1.354s]
[INFO] oVirt Build Tools root ............................ SUCCESS [0.062s]
[INFO] oVirt checkstyle .................................. SUCCESS [1.993s]
[INFO] oVirt Checkstyle Checks ........................... SUCCESS [3.378s]
[INFO] oVirt Modules - backend ........................... SUCCESS [0.067s]
[INFO] oVirt Manager ..................................... SUCCESS [0.055s]
[INFO] oVirt Engine dependencies ......................... SUCCESS [0.044s]
[INFO] oVirt Engine common dependencies .................. SUCCESS [5.191s]
[INFO] oVirt Engine tools dependencies ................... SUCCESS [0.423s]
[INFO] Utilities to extend java.logging framework ........ SUCCESS [1.274s]
[INFO] Extensions API root ............................... SUCCESS [1.044s]
[INFO] ovirt-engine-extensions-api ....................... SUCCESS [14.624s]
[INFO] oVirt Modules - manager ........................... SUCCESS [4.195s]
[INFO] Universal utilities ............................... SUCCESS [1:20.844s]
[INFO] Extensions manager ................................ SUCCESS [6.709s]
[INFO] GWT UI Compatibility .............................. SUCCESS [8.765s]
[INFO] Common Code ....................................... SUCCESS [1:00.944s]
[INFO] Common utilities .................................. SUCCESS [59.432s]
[INFO] Branding package .................................. SUCCESS [10.362s]
[INFO] ovirt-engine sso .................................. SUCCESS [7.634s]
[INFO] Data Access Layer ................................. SUCCESS [47.011s]
[INFO] engine scheduler bean ............................. SUCCESS [5.164s]
[INFO] Vds broker ........................................ SUCCESS [51.158s]
[INFO] builtin-extensions ................................ SUCCESS [2.207s]
[INFO] Search Backend .................................... SUCCESS [13.510s]
[INFO] Backend Authentication, Authorization and Accounting SUCCESS [9.961s]
[INFO] Custom Application Server Authentication Plugin ... SUCCESS [2.843s]
[INFO] Backend Logic @Service bean ....................... SUCCESS [3:50.730s]
[INFO] oVirt RESTful API Backend Integration ............. SUCCESS [0.224s]
[INFO] oVirt RESTful API interface ....................... SUCCESS [0.254s]
[INFO] oVirt Engine API Definition ....................... SUCCESS [1:13.459s]
[INFO] oVirt Engine API Commom Parent POM ................ SUCCESS [0.244s]
[INFO] oVirt Engine API Common JAX-RS .................... SUCCESS [8.020s]
[INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS [28.030s]
[INFO] oVirt RESTful API Backend Integration JAX-RS Resources SUCCESS
[2:35.597s]
[INFO] oVirt RESTful API Backend Integration Webapp ...... SUCCESS [0.579s]
[INFO] oVirt RESTful API Documentation ................... SUCCESS [1.504s]
[INFO] Custom Logger Using Extensions .................... SUCCESS [2.218s]
[INFO] oVirt Engine Web Root ............................. SUCCESS [0.366s]
[INFO] ovirt-engine services ............................. SUCCESS [3.434s]
[INFO] oVirt Engine Web Docs ............................. SUCCESS [2.098s]
[INFO] ovirt-engine welcome .............................. SUCCESS [8.770s]
[INFO] oVirt Engine Microbenchmarks ...................... SUCCESS [11.746s]
[INFO] oVirt Engine Tools ................................ SUCCESS [15.699s]
[INFO] oVirt Engine extensions tool ...................... SUCCESS [3.813s]
[INFO] oVirt Engine sso client registration tool ......... SUCCESS [2.084s]
[INFO] oVirt Modules :: Frontend ......................... SUCCESS [0.163s]
[INFO] oVirt Modules :: Webadmin ......................... SUCCESS [0.156s]
[INFO] oVirt UI Modules .................................. SUCCESS [0.260s]
[INFO] AOP tweaks for GWT compiler ....................... SUCCESS [3.970s]
[INFO] Extensions for GWT ................................ SUCCESS [4.643s]
[INFO] UI Utils Compatibility (for UICommon) ............. SUCCESS [10.358s]
[INFO] Frontend for GWT UI Projects ...................... SUCCESS [40.496s]
[INFO] UICommonWeb ....................................... SUCCESS [1:25.399s]
[INFO] oVirt GWT UI common infrastructure ................ SUCCESS [53.490s]
[INFO] WebAdmin .......................................... SUCCESS [17:35.183s]
[INFO] UserPortal ........................................ SUCCESS [8:15.850s]
[INFO] frontend-symbols .................................. SUCCESS [2.933s]
[INFO] oVirt Server EAR .................................. FAILURE [13.150s]
[INFO] ovirt-engine maven make ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 45:21.487s
[INFO] Finished at: Sat Jun 10 06:15:12 EAT 2017
[INFO] Final Memory: 430M/957M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to parse plugin descriptor for
org.apache.maven.plugins:maven-ear-plugin:2.8
(/home/centos/.m2/repository/org/apache/maven/plugins/maven-ear-plugin/2.8/maven-ear-plugin-2.8.jar):
error in opening zip file -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginDescriptorParsingE...
make[2]: *** [maven] Error 1
make[2]: Leaving directory `/home/centos/git/ovirt-engine'
make[1]: *** [tmp.built] Error 2
make[1]: Leaving directory `/home/centos/git/ovirt-engine'
make: *** [all-dev] Error 2
--
- Warm regards
Leni Kadali Mutungi
2722
days inactive
2738
days old
18 comments
2 participants
participants (2)
-
Leni Kadali Mutungi -
Yedidyah Bar David