Good evening, I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17. Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info? Regards, Jose Garcia
----- Original Message -----
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running.
Regards, Jose Garcia _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------090204030208040103090906 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
----- Original Message -----
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running.
Good morning, Yes, there are a bunch of errors recorded in server.log, regarding jboss-as modules: 2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.engine.ear.userportal.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.engine.ear.userportal.war".main: Failed to load module: deployment.engine.ear.userportal.war:main //at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea] Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242) at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.Module.addExportedPaths(Module.java:977) at org.jboss.modules.Module.addPaths(Module.java:883) at org.jboss.modules.Module.link(Module.java:1196) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,55] Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at path 'jboss-jaxr-1.0-api.jar' at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898) at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854) at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676) at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287) 2012-07-25 09:03:59,864 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main: Failed to load module: deployment.engine.ear.engine-bll.jar:main","jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: Failed to load module: deployment.engine.ear.webadmin.war:main","jboss.module.service.\"deployment.engine.ear.userportal.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.userportal.war\".main: Failed to load module: deployment.engine.ear.userportal.war:main","jboss.module.service.\"deployment.engine.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear\".main: Failed to load module: deployment.engine.ear:main","jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main","jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main","jboss.module.service.\"deployment.engine.ear.restapi.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.restapi.war\".main: Failed to load module: deployment.engine.ear.restapi.war:main","jboss.module.service.\"deployment.engine.ear.root.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.root.war\".main: Failed to load module: deployment.engine.ear.root.war:main","jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main"}}}} The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update. I have excluded java from the update. /# java -version/ shows: java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
Regards, Jose Garcia _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--------------090204030208040103090906 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 07/25/2012 09:05 AM, Ofer Schreiber wrote:<br> </div> <blockquote cite="mid:856303445.3112501.1343203547075.JavaMail.root@redhat.com" type="cite"> <pre wrap=""> ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">Good evening, I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17. Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info? </pre> </blockquote> <pre wrap=""> I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running. </pre> </blockquote> <br> Good morning,<br> <br> Yes, there are a bunch of errors recorded in server.log, regarding jboss-as modules:<br> <blockquote>2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.engine.ear.userportal.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.engine.ear.userportal.war".main: Failed to load module: deployment.engine.ear.userportal.war:main<br> <br> </blockquote> <blockquote><i> </i>at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]<br> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA]<br> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA]<br> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03-icedtea]<br> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03-icedtea]<br> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea]<br> <br> Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml<br> at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292)<br> at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242)<br> at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138)<br> at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122)<br> at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)<br> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)<br> at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)<br> at org.jboss.modules.Module.addExportedPaths(Module.java:977)<br> at org.jboss.modules.Module.addPaths(Module.java:883)<br> at org.jboss.modules.Module.link(Module.java:1196)<br> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225)<br> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)<br> at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]<br> ... 5 more<br> <br> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,55]<br> Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at path 'jboss-jaxr-1.0-api.jar'<br> at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898)<br> at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854)<br> at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676)<br> at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548)<br> at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287)<br> <br> 2012-07-25 09:03:59,864 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main: Failed to load module: deployment.engine.ear.engine-bll.jar:main","jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: Failed to load module: deployment.engine.ear.webadmin.war:main","jboss.module.service.\"deployment.engine.ear.userportal.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.userportal.war\".main: Failed to load module: deployment.engine.ear.userportal.war:main","jboss.module.service.\"deployment.engine.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear\".main: Failed to load module: deployment.engine.ear:main","jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main","jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main","jboss.module.service.\"deployment.engine.ear.restapi.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.restapi.war\".main: Failed to load module: deployment.engine.ear.restapi.war:main","jboss.module.service.\"deployment.engine.ear.root.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.root.war\".main: Failed to load module: deployment.engine.ear.root.war:main","jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main"}}}}<br> </blockquote> <br> The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update.<br> <br> I have excluded java from the update. <i># java -version</i> shows:<br> <br> java version "1.7.0_03-icedtea"<br> OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64)<br> OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)<br> <blockquote cite="mid:856303445.3112501.1343203547075.JavaMail.root@redhat.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap=""> Regards, Jose Garcia _______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> </blockquote> <br> </body> </html> --------------090204030208040103090906--
On 07/25/2012 10:22 AM, jose garcia wrote:
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
----- Original Message -----
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running.
Good morning,
Yes, there are a bunch of errors recorded in server.log, regarding jboss-as modules:
2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.engine.ear.userportal.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.engine.ear.userportal.war".main: Failed to load module: deployment.engine.ear.userportal.war:main
//at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea]
Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242) at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.Module.addExportedPaths(Module.java:977) at org.jboss.modules.Module.addPaths(Module.java:883) at org.jboss.modules.Module.link(Module.java:1196) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,55] Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at path 'jboss-jaxr-1.0-api.jar' at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898) at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854) at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676) at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287)
2012-07-25 09:03:59,864 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main: Failed to load module: deployment.engine.ear.engine-bll.jar:main","jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: Failed to load module: deployment.engine.ear.webadmin.war:main","jboss.module.service.\"deployment.engine.ear.userportal.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.userportal.war\".main: Failed to load module: deployment.engine.ear.userportal.war:main","jboss.module.service.\"deployment.engine.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear\".main: Failed to load module: deployment.engine.ear:main","jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main","jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main","jboss.module.service.\"deployment.engine.ear.restapi.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.restapi.war\".main: Failed to load module: deployment.engine.ear.restapi.war:main","jboss.module.service.\"deployment.engine.ear.root.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.root.war\".main: Failed to load module: deployment.engine.ear.root.war:main","jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main"}}}}
The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update.
I have excluded java from the update. /# java -version/ shows:
java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
Regards, Jose Garcia
The file /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml is not part of the installation of the jboss-as package. That probably means that you have leftovers from a previous installation, maybe of the old ovirt-engine-jbossas package. I suggest the following: 1. Stop the engine service: systemctl stop ovirt-engine.service 2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps 3. Make sure that the /usr/share/jboss-as directory is empty. If it is not clean it manually. 4. Re-install the jboss-as package: yum install jboss-as 5. Start the engine again: systemctl start ovirt-engine.service That or any other idea that you have to make sure that you don't have files that don't belong to the jboss-as package in the /usr/share/jboss-as directory. -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
On 07/25/2012 10:37 AM, Juan Hernandez wrote:
On 07/25/2012 10:22 AM, jose garcia wrote:
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
----- Original Message -----
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info?
I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running.
Good morning,
Yes, there are a bunch of errors recorded in server.log, regarding jboss-as modules:
2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.engine.ear.userportal.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.engine.ear.userportal.war".main: Failed to load module: deployment.engine.ear.userportal.war:main
//at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea]
Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242) at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.Module.addExportedPaths(Module.java:977) at org.jboss.modules.Module.addPaths(Module.java:883) at org.jboss.modules.Module.link(Module.java:1196) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,55] Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at path 'jboss-jaxr-1.0-api.jar' at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898) at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854) at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676) at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287)
2012-07-25 09:03:59,864 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main: Failed to load module: deployment.engine.ear.engine-bll.jar:main","jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: Failed to load module: deployment.engine.ear.webadmin.war:main","jboss.module.service.\"deployment.engine.ear.userportal.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.userportal.war\".main: Failed to load module: deployment.engine.ear.userportal.war:main","jboss.module.service.\"deployment.engine.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear\".main: Failed to load module: deployment.engine.ear:main","jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main","jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main","jboss.module.service.\"deployment.engine.ear.restapi.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.restapi.war\".main: Failed to load module: deployment.engine.ear.restapi.war:main","jboss.module.service.\"deployment.engine.ear.root.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.root.war\".main: Failed to load module: deployment.engine.ear.root.war:main","jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main"}}}}
The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update.
I have excluded java from the update. /# java -version/ shows:
java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
Regards, Jose Garcia
The file /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml is not part of the installation of the jboss-as package. That probably means that you have leftovers from a previous installation, maybe of the old ovirt-engine-jbossas package. I suggest the following:
1. Stop the engine service: systemctl stop ovirt-engine.service
2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
3. Make sure that the /usr/share/jboss-as directory is empty. If it is not clean it manually.
4. Re-install the jboss-as package: yum install jboss-as
5. Start the engine again: systemctl start ovirt-engine.service
That or any other idea that you have to make sure that you don't have files that don't belong to the jboss-as package in the /usr/share/jboss-as directory.
What version of jboss-as are you using? 7.1.1-4? If that is the case this can be a bug in that version. -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
On 07/25/2012 09:45 AM, Juan Hernandez wrote:
On 07/25/2012 09:05 AM, Ofer Schreiber wrote:
----- Original Message -----
Good evening,
I had installed the 3.1 beta version. After an update of Fedora 17, the portal does not show any links. I reckon that ovirt-engine version has been upgraded to 3.1.0-1.fc17.
Have I lost all the information in the database? Is there a way to bring back the datacenters and the nodes info? I'm pretty sure the DB is still there. you should take a look into the log files under /var/log/ovirt-engine (server.log and engine.log) and look for exceptions. also, you might want to make sure that postgrsql, httpd and ovirt-engine services are up and running. Good morning,
Yes, there are a bunch of errors recorded in server.log, regarding jboss-as modules:
2012-07-25 09:03:59,386 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.engine.ear.userportal.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.engine.ear.userportal.war".main: Failed to load module: deployment.engine.ear.userportal.war:main
//at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03-icedtea]
Caused by: org.jboss.modules.ModuleLoadException: Error loading module from /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:292) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:242) at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:138) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:122) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) at org.jboss.modules.Module.addExportedPaths(Module.java:977) at org.jboss.modules.Module.addPaths(Module.java:883) at org.jboss.modules.Module.link(Module.java:1196) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1225) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,55] Message: Failed to add resource root 'jboss-jaxr-1.0-api.jar' at path 'jboss-jaxr-1.0-api.jar' at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:898) at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:854) at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:676) at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:548) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:287)
2012-07-25 09:03:59,864 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-bll.jar\".main: Failed to load module: deployment.engine.ear.engine-bll.jar:main","jboss.module.service.\"deployment.engine.ear.webadmin.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.webadmin.war\".main: Failed to load module: deployment.engine.ear.webadmin.war:main","jboss.module.service.\"deployment.engine.ear.userportal.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.userportal.war\".main: Failed to load module: deployment.engine.ear.userportal.war:main","jboss.module.service.\"deployment.engine.ear\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear\".main: Failed to load module: deployment.engine.ear:main","jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-genericapi.jar\".main: Failed to load module: deployment.engine.ear.engine-genericapi.jar:main","jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.ovirtengineweb.war\".main: Failed to load module: deployment.engine.ear.ovirtengineweb.war:main","jboss.module.service.\"deployment.engine.ear.restapi.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.restapi.war\".main: Failed to load module: deployment.engine.ear.restapi.war:main","jboss.module.service.\"deployment.engine.ear.root.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.root.war\".main: Failed to load module: deployment.engine.ear.root.war:main","jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.engine.ear.engine-scheduler.jar\".main: Failed to load module: deployment.engine.ear.engine-scheduler.jar:main"}}}}
The ovirt-engine and jboss-as services are up and running. The last information logged in engine.log, however, is from before the update.
I have excluded java from the update. /# java -version/ shows:
java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
Regards, Jose Garcia The file /usr/share/jboss-as/modules/javax/xml/registry/api/main/module.xml is not part of the installation of the jboss-as package. That probably means that you have leftovers from a previous installation, maybe of the
On 07/25/2012 10:22 AM, jose garcia wrote: old ovirt-engine-jbossas package. I suggest the following:
1. Stop the engine service: systemctl stop ovirt-engine.service
2. Remove jboss-as, but not its dependencies: rpm -e jboss-as --nodeps
3. Make sure that the /usr/share/jboss-as directory is empty. If it is not clean it manually.
4. Re-install the jboss-as package: yum install jboss-as
5. Start the engine again: systemctl start ovirt-engine.service
That or any other idea that you have to make sure that you don't have files that don't belong to the jboss-as package in the /usr/share/jboss-as directory. What version of jboss-as are you using? 7.1.1-4? If that is the case
On 07/25/2012 10:37 AM, Juan Hernandez wrote: this can be a bug in that version.
That is the version: jboss-as.noarch 7.1.1-4.fc17 @updates This is the message I've got from yum after reinstalling jboss-as: Warning: RPMDB altered outside of yum. ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: ovirt-engine-3.1.0-1.fc17.noarch has missing requires of jboss-as >= ('0', '7.1.1', None)
participants (3)
-
jose garcia -
Juan Hernandez -
Ofer Schreiber