Re: [ovirt-users] jboss deployments timeout (was: getting 404 after fresh install of oVirt 3.4 on CentOS 6.5 (+ solution))

2014-05-14 Thread Yedidyah Bar David
I am the reporter of the below bz, and the author of the fix [1]. However, I
don't know jboss at all - just searched around, found somewhere the option
'deployment-timeout' (not sure where, probably a quick search can find this)
and verified that the fix works. It seems like neither any of the reviewers
of the change know enough about jboss to do some more analysis. Can anyone
else, that knows jboss, please look at this issue? Specifically:
1. Was anything related to the maximum time for deployments changed in relevant
jboss versions?
2. What is affected? What isn't?
- fedora 19/20(/21?), el6
- ovirt repos (3.3, 3.4, master) and minimum requirements

John: If this is reproducible for you, you might want to try the fix [1]
(linked to from the bug). If you do, please report - what exact versions
(OS, jboss, ovirt, etc) you used, and (according to the logs) how long did
the deployment take. Thanks!

[1] http://gerrit.ovirt.org/25895

Best Regards,
-- 
Didi

- Original Message -
 From: John Taylor jtt77...@gmail.com
 To: R P Herrold herr...@owlriver.com
 Cc: users@ovirt.org
 Sent: Tuesday, May 13, 2014 11:36:57 PM
 Subject: Re: [ovirt-users] getting 404 after fresh install of oVirt 3.4 on 
 CentOS 6.5 (+ solution)
 
 I've seen a similar problem (404 on webadmin) on my 4GB physical ovirt
 engine box, but it turned out to be the jboss timeout in deployment
 Relevant bz
 https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1078291
 
 so it might have been that it wasn't a memory limit in the OP that
 caused failure, but the time it took jboss to deploy
 
 -John
 
 On Tue, May 13, 2014 at 12:31 PM, R P Herrold herr...@owlriver.com wrote:
  On Tue, 13 May 2014, Sven Kieske wrote:
 
  Doesn't this make you wonder where the minimum requirements come from?
 
  If it runs with less than 1 GB RAM, why do the docs say you need 4 GB
  and recommend even 16 GB ?
 
  certainly a fair question ... There is also a statement in
  that setup script as to needed filesystem space which seems to
  have been simply 'pulled out of the air', rather than
  documented / explained
 
  Is it just a matter of scale(number of vms/hosts/DCs) ?
  What would make engine consume more RAM?
 
  Can you maybe lower the minimum requirements?
 
  Or isolate the recommendations to a flat file which is
  commented, and sourced by the script, so a person can discern
  the difference between 'hard' requirements, and simple
  'recommendations' for a stated use case
 
  -- Russ herrold
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] jboss deployments timeout (was: getting 404 after fresh install of oVirt 3.4 on CentOS 6.5 (+ solution))

2014-05-14 Thread John Taylor
Didi,

Some background is that I first ran into this when I added dwh+reports
to my 3.4 setup, and I found your bz then and did the fix (with
changes below) and it worked for me. The fixed ovirt-engine.xml.in got
overwritten when I upgraded to 3.4.1 and I reapplied .

But I did change
deployment-scanner scan-interval=5000 path=$tempdir/deployments/
deployment-timeout=1200
to
deployment-scanner scan-interval=5000 path=$tempdir/deployments
deployment-timeout=1200/

i.e. the / looks to be misplaced and should be used to close the
deployment-scanner tag.

If you do, please report - what exact versions (OS, jboss, ovirt, etc) you use
fedora 19 w/ latest updates
 kernel-3.13.11-100.fc19.x86_64
 ovirt-engine-3.4.1-1.fc19.noarch
 jboss-as-7.1.1-21.fc19.noarch
 ovirt-engine-reports-3.4.1-1.fc19.noarch

and (according to the logs) how long did the deployment take. Thanks!
My last startup shows that was right at the 59 second mark. So you can
see I'm right on the edge of it failing with default timeout of 60
seconds.

from server.log
2014-05-12 23:22:00,463 INFO  [org.jboss.as.server.deployment] (MSC
service thread 1-5) JBAS015876: Starting deployment of engine.ear
2014-05-12 23:22:00,464 INFO  [org.jboss.as.server.deployment] (MSC
service thread 1-6) JBAS015876: Starting deployment of
ovirt-engine-reports.war
...
2014-05-12 23:22:59,383 INFO  [org.jboss.as.server]
(DeploymentScanner-threads - 2) JBAS018559: Deployed engine.ear
2014-05-12 23:22:59,385 INFO  [org.jboss.as.server]
(DeploymentScanner-threads - 2) JBAS018559: Deployed
ovirt-engine-reports.war

Thanks,
-John
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users