[Engine-devel] Updating ovirt engine from 3.0 to the 3.1.0 version
Shu Ming
shuming at linux.vnet.ibm.com
Wed May 2 09:04:45 UTC 2012
After "touch engine.ear.doreply" in
/usr/share/jboss-as-7.1.0.Beta1b/standalone/deployments, ovirt engine
can be accessed now. Thanks for your support.
On 2012-5-2 0:50, Ofer Schreiber wrote:
> What about creating the engine.ear.dodeploy file as suggested earlier?
>
>
>
> On 1 May 2012, at 18:15, Shu Ming <shuming at linux.vnet.ibm.com
> <mailto:shuming at linux.vnet.ibm.com>> wrote:
>
>> Oops. Actually, I deleted the engine.ear.failed and engine.ear was
>> there untouched.
>> Her is the directory hierarchy now in jboss deployment directory.
>>
>> [root at ovirt-engine-112 deployments]# pwd
>> /usr/share/jboss-as-7.1.0.Beta1b/standalone/deployments
>> [root at ovirt-engine-112 deployments]# ls -l
>> total 16
>> lrwxrwxrwx. 1 root root 34 Apr 28 01:14 engine.ear ->
>> /usr/share/ovirt-engine/engine.ear
>> -rw-r--r--. 1 jboss-as jboss-as 8868 Dec 2 05:10 README.txt
>> lrwxrwxrwx. 1 root root 48 Apr 28 01:14 ROOT.war ->
>> /usr/share/ovirt-engine/resources/jboss/ROOT.war
>> -rw-rw-r--. 1 jboss-as jboss-as 8 Apr 28 01:14 ROOT.war.deployed
>> [root at ovirt-engine-112 deployments]#
>>
>>
>>
>> On 2012-5-1 4:11, Ofer Schreiber wrote:
>>> Please re create the link to engine.ear.
>>> That's the base java code that contains webadmin.
>>>
>>> If it doesn't deploy, create also engine.ear.dodeploy
>>>
>>> Ofer.
>>>
>>>
>>>
>>> On 30 Apr 2012, at 19:23, Shu Ming <shuming at linux.vnet.ibm.com
>>> <mailto:shuming at linux.vnet.ibm.com>> wrote:
>>>
>>>> After deleting the engine.ear in
>>>> /usr/share/jboss-as-7.1.0.Beta1b/standalone/deployments, I can
>>>> access the page now. Thanks for you suggestions.
>>>>
>>>> However, when I tried to access "Administrator Portal(no SSL)".
>>>> The following errors were encountered.
>>>>
>>>>
>>>> HTTP Status 404 - /webadmin
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> *type* Status report
>>>>
>>>> *message* _/webadmin_
>>>>
>>>> *description* _The requested resource (/webadmin) is not available._
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> JBoss Web/7.0.3.Final
>>>>
>>>>
>>>>
>>>> On 2012-4-30 15:22, Ofer Schreiber wrote:
>>>>> Looks like something went wrong with the .ear deployment. (already saw such an issue inhttp://lists.ovirt.org/pipermail/engine-devel/2012-January/000483.html)
>>>>>
>>>>> Can you please:
>>>>> 1. Stop JBoss
>>>>> 2. Make sure jboss deployment directory contain a single engine.ear
>>>>> - Remove engine.ear.failed (or similar files if exists)
>>>>> 3. Start JBoss again
>>>>>
>>>>> ----- Original Message -----
>>>>>> On 2012-4-29 19:33, Ofer Schreiber wrote:
>>>>>>> I need more info about this:
>>>>>>> 1. It looks like a clean install (DB created from scratch). why do
>>>>>>> you call it an upgrade?
>>>>>> Sorry for confusion here. I used engine-cleanup and ran engine-setup
>>>>>> again after the 3.1 RPM package were installed.
>>>>>>
>>>>>>> 2. Do you see any error in JBoss/engine logs? (/var/log/jboss-as
>>>>>>> and /var/log/ovirt-engine usually)
>>>>>> [root at ovirt-engine-112 ~]# cat /var/log/jboss-as/console.log
>>>>>>
>>>>>> 01:15:16,901 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS
>>>>>> 7.1.0.Beta1b "Tesla" started in 2405ms - Started 140 of 203 services
>>>>>> (61
>>>>>> services are passive or on-demand)
>>>>>> 01:15:17,207 INFO [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed
>>>>>> deployment engine.ear
>>>>>> 01:15:17,431 INFO [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed
>>>>>> deployment ROOT.war
>>>>>> 01:15:17,432 INFO [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS015003: Found ROOT.war in
>>>>>> deployment
>>>>>> directory. To trigger deployment create a file called
>>>>>> ROOT.war.dodeploy
>>>>>> 01:15:17,432 INFO [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS015003: Found engine.ear in
>>>>>> deployment directory. To trigger deployment create a file called
>>>>>> engine.ear.dodeploy
>>>>>> 01:15:17,478 ERROR [org.jboss.as.controller]
>>>>>> (DeploymentScanner-threads
>>>>>> - 2) JBAS014612: Operation ("add") failed - address: ([("deployment"
>>>>>> =>
>>>>>> "engine.ear")]): java.lang.IllegalStateException: JBAS014666:
>>>>>> Duplicate
>>>>>> resource [("deployment" => "engine.ear")]
>>>>>> at
>>>>>> org.jboss.as.controller.OperationContextImpl.addResource(OperationContextImpl.java:503)
>>>>>> [jboss-as-controller-7.1.0.Beta1b.jar:]
>>>>>> at
>>>>>> org.jboss.as.controller.OperationContextImpl.createResource(OperationContextImpl.java:471)
>>>>>> [jboss-as-controller-7.1.0.Beta1b.jar:]
>>>>>> at
>>>>>> org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:170)
>>>>>> ....
>>>>>>
>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>>>>>> [:1.6.0_24]
>>>>>> at
>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>>>>>> [:1.6.0_24]
>>>>>> at
>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>>>>>> [:1.6.0_24]
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>>>>> [:1.6.0_24]
>>>>>> at
>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>>>>> [:1.6.0_24]
>>>>>> at java.lang.Thread.run(Thread.java:679) [:1.6.0_24]
>>>>>> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>>>>>> [jboss-threads-2.0.0.GA.jar:]
>>>>>>
>>>>>> 01:15:17,482 ERROR [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS014654: Composite operation was
>>>>>> rolled back
>>>>>> 01:15:17,483 ERROR [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) JBAS014654: Composite operation was
>>>>>> rolled back
>>>>>> 01:15:17,483 ERROR [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation
>>>>>> failed
>>>>>> and was rolled back. Steps that failed:" => {"Operation step-1" =>
>>>>>> "JBAS014749: Operation handler failed: JBAS014666: Duplicate resource
>>>>>> [(\"deployment\" => \"engine.ear\")]"}}
>>>>>> 01:15:17,483 ERROR [org.jboss.as.server.deployment.scanner]
>>>>>> (DeploymentScanner-threads - 1) undefined
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 3. Any error in the httpd log?
>>>>>> [root at ovirt-engine-112 ~]# cat /var/log/httpd/access_log
>>>>>> 9.181.193.205 - - [30/Apr/2012:00:28:27 +0800] "GET / HTTP/1.0" 404 -
>>>>>> "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28)
>>>>>> Gecko/20120306 Firefox/3.6.28 ( .NET CLR 3.5.30729)"
>>>>>> 9.181.193.205 - - [30/Apr/2012:00:28:44 +0800] "GET /favicon.ico
>>>>>> HTTP/1.0" 404 - "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>> rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 ( .NET CLR 3.5.30729)"
>>>>>> 9.181.193.205 - - [30/Apr/2012:00:28:44 +0800] "GET /favicon.ico
>>>>>> HTTP/1.0" 404 - "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>> rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 ( .NET CLR 3.5.30729)"
>>>>>> 9.181.193.205 - - [30/Apr/2012:00:28:54 +0800] "GET / HTTP/1.0" 404 -
>>>>>> "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28)
>>>>>> Gecko/20120306 Firefox/3.6.28 ( .NET CLR 3.5.30729)"
>>>>>> 9.181.193.205 - - [30/Apr/2012:00:28:55 +0800] "GET /favicon.ico
>>>>>> HTTP/1.0" 404 - "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>>>>>> rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 ( .NET CLR 3.5.30729)"
>>>>>> [root at ovirt-engine-112 ~]#
>>>>>>
>>>>>> [root at ovirt-engine-112 ~]# cat /var/log/httpd/error_log
>>>>>> [Sun Apr 29 03:36:02 2012] [notice] Digest: generating secret for
>>>>>> digest
>>>>>> authentication ...
>>>>>> [Sun Apr 29 03:36:02 2012] [notice] Digest: done
>>>>>> [Sun Apr 29 03:36:02 2012] [notice] SSL FIPS mode disabled
>>>>>> [Sun Apr 29 03:36:02 2012] [notice] Apache/2.2.22 (Unix) DAV/2
>>>>>> mod_ssl/2.2.22 OpenSSL/1.0.0h-fips configured -- resuming normal
>>>>>> operations
>>>>>> [root at ovirt-engine-112 ~]#
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 4. What happens if you stop iptables and access your server with
>>>>>>> :8080?
>>>>>> The same as before.
>>>>>>
>>>>>>> Thanks,
>>>>>>> Ofer
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>>> Hi,
>>>>>>>> I built a set of ovirt engine RPM packages from near the
>>>>>>>> latest
>>>>>>>> ovirt
>>>>>>>> engine source code. However, when I try to access the engine
>>>>>>>> server
>>>>>>>> with URL"http://ovirt-engine-112:80", the browser displayed a
>>>>>>>> blank
>>>>>>>> page without http error returned. Any clue about what is going on
>>>>>>>> here?
>>>>>>>> Why didn't the engine administrator home page be shown?
>>>>>>>>
>>>>>>>>
>>>>>>>> And the packages were also installed successfully in my target
>>>>>>>> system,
>>>>>>>> checked this by "rpm -q -a|grep engine".
>>>>>>>> I) upgraded the packages to the 3.1
>>>>>>>>
>>>>>>>> [root at ovirt-engine-112 ~]# rpm -q -a |grep engine
>>>>>>>> ovirt-engine-restapi-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-dbscripts-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64
>>>>>>>> ovirt-engine-genericapi-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-backend-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-setup-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-jbossas-1.2-2.fc16.x86_64
>>>>>>>> ovirt-engine-jboss-deps-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-config-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-webadmin-portal-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-userportal-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-tools-common-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-image-uploader-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-notification-service-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> ovirt-engine-iso-uploader-3.1.0_0001-1.8.fc16.x86_64
>>>>>>>> gtk2-engines-2.20.2-2.fc15.x86_64
>>>>>>>>
>>>>>>>> Step II)
>>>>>>>> Then I used "engine-setup" to setup the engine. It seems
>>>>>>>> that
>>>>>>>> everything is ok, see the log below.
>>>>>>>>
>>>>>>>> -------------
>>>>>>>> [root at ovirt-engine-112 ~]# engine-setup
>>>>>>>> Welcome to oVirt Engine setup utility
>>>>>>>> HTTP Port [80] :
>>>>>>>> HTTPS Port [443] :
>>>>>>>> Host fully qualified domain name, note that this name should be
>>>>>>>> fully
>>>>>>>> resolvable [ovirt-engine-112] :
>>>>>>>> ERROR: domain is not a valid domain name
>>>>>>>> User input failed validation, do you still wish to use it?
>>>>>>>> (yes|no):
>>>>>>>> yes
>>>>>>>> Password for Administrator (admin at internal) :
>>>>>>>> Warning: Weak Password.
>>>>>>>> Confirm password :
>>>>>>>> Organization Name for the Certificate: cstl
>>>>>>>> The default storage type you will be using ['NFS'| 'FC'| 'ISCSI']
>>>>>>>> [NFS] :
>>>>>>>> Enter DB type for installation ['remote'| 'local'] [local] :
>>>>>>>> Local database password :
>>>>>>>> Warning: Weak Password.
>>>>>>>> Confirm password :
>>>>>>>> Should the installer configure NFS share on this server to be used
>>>>>>>> as
>>>>>>>> an
>>>>>>>> ISO Domain? ['yes'| 'no'] [yes] :
>>>>>>>> Mount point path: /iso-dom
>>>>>>>> ERROR: mount point already exists in /etc/exports
>>>>>>>> Mount point path: /iso-dom
>>>>>>>> Display name for the ISO Domain: iso-domains
>>>>>>>> Firewall ports need to be opened.
>>>>>>>> You can let the installer configure iptables automatically
>>>>>>>> overriding
>>>>>>>> the current configuration. The old configuration will be backed
>>>>>>>> up.
>>>>>>>> Alternately you can configure the firewall later using an example
>>>>>>>> iptables file found under
>>>>>>>> /usr/share/ovirt-engine/conf/iptables.example
>>>>>>>> Configure iptables ? ['yes'| 'no']: yes
>>>>>>>>
>>>>>>>> oVirt Engine will be installed using the following configuration:
>>>>>>>> =================================================================
>>>>>>>> http-port: 80
>>>>>>>> https-port: 443
>>>>>>>> host-fqdn: ovirt-engine-112
>>>>>>>> auth-pass: ********
>>>>>>>> org-name: cstl
>>>>>>>> default-dc-type: NFS
>>>>>>>> db-remote-install: local
>>>>>>>> db-local-pass: ********
>>>>>>>> nfs-mp: /iso-dom
>>>>>>>> iso-domain-name: iso-domains
>>>>>>>> config-nfs: yes
>>>>>>>> override-iptables: yes
>>>>>>>> Proceed with the configuration listed above? (yes|no): yes
>>>>>>>>
>>>>>>>> Installing:
>>>>>>>> Configuring oVirt-engine... [ DONE ]
>>>>>>>> Creating CA... [ DONE ]
>>>>>>>> Editing JBoss Configuration... [ DONE ]
>>>>>>>> Setting Database Configuration... [ DONE ]
>>>>>>>> Setting Database Security... [ DONE ]
>>>>>>>> Creating Database... [ DONE ]
>>>>>>>> Updating the Default Data Center Storage Type... [ DONE ]
>>>>>>>> Editing oVirt Engine Configuration... [ DONE ]
>>>>>>>> Editing Postgresql Configuration... [ DONE ]
>>>>>>>> Configuring the Default ISO Domain... [ DONE ]
>>>>>>>> Configuring Firewall (iptables)... [ DONE ]
>>>>>>>> Starting JBoss Service... [ DONE ]
>>>>>>>> Handling HTTPD... [ DONE ]
>>>>>>>>
>>>>>>>> **** Installation completed successfully ******
>>>>>>>>
>>>>>>>> (Please allow oVirt Engine a few moments to start up.....)
>>>>>>>>
>>>>>>>>
>>>>>>>> Additional information:
>>>>>>>> * SSL Certificate fingerprint:
>>>>>>>> C6:01:83:93:4B:2C:2A:38:65:C8:49:C9:17:34:FE:4B:1C:10:D5:FF
>>>>>>>> * SSH Public key fingerprint:
>>>>>>>> 69:8c:bd:05:43:17:0a:43:a3:cc:62:7e:f7:be:0c:42
>>>>>>>> * A default ISO share has been created on this host.
>>>>>>>> If IP based access restrictions are required, please edit
>>>>>>>> /iso-dom
>>>>>>>> entry in /etc/exports
>>>>>>>> * The firewall has been updated, the old iptables configuration
>>>>>>>> file
>>>>>>>> was saved to
>>>>>>>> /usr/share/ovirt-engine/conf/iptables.backup.011513-04282012_2225
>>>>>>>> * The installation log file is available at:
>>>>>>>> /var/log/ovirt-engine/engine-setup_2012_04_28_01_13_01.log
>>>>>>>> * Please use the user "admin" and password specified in order
>>>>>>>> to
>>>>>>>> login
>>>>>>>> into oVirt Engine
>>>>>>>> * To configure additional users, first configure authentication
>>>>>>>> domains using the 'engine-manage-domains' utility
>>>>>>>> * To access oVirt Engine please go to the following URL:
>>>>>>>> http://ovirt-engine-112:80
>>>>>>>> [root at ovirt-engine-112 ~]#
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Shu Ming<shuming at linux.vnet.ibm.com>
>>>>>>>> IBM China Systems and Technology Laboratory
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Engine-devel mailing list
>>>>>>>> Engine-devel at ovirt.org
>>>>>>>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>>>>>>>
>>>>>> --
>>>>>> Shu Ming<shuming at linux.vnet.ibm.com>
>>>>>> IBM China Systems and Technology Laboratory
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Shu Ming<shuming at linux.vnet.ibm.com>
>>>> IBM China Systems and Technology Laboratory
>>
>>
>> --
>> Shu Ming<shuming at linux.vnet.ibm.com>
>> IBM China Systems and Technology Laboratory
--
Shu Ming<shuming at linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/engine-devel/attachments/20120502/2cec3a91/attachment.html>
More information about the Engine-devel
mailing list