RE: Upgrade from 2.2.14 to 4.2 fails
Hi Sanjeev, I have tried to file a bug but could not find cloudstack in the list of software that i can file a bug, the following what i have found, would you please advise where to file it?Ant: Ant is a Java based build tool.Apache httpd‑2: Apache HTTP Server Version 2Apache httpd‑test: Test framework and utilities for the Apache HTTP ServerAPR: Apache Portable Runtime.JMeter: Pure Java desktop application designed to load test functional behavior and measure performanceLenya: Lenya is a Content Management System based on XML and XSLT. One of its core components is Apache Cocoon.Log4j: A reliable, fast and extensible logging library for Java.POI: The POI project consists of complete ports of popular productivity office suite file formats.Rivet: Apache Rivet is a system for creating dynamic web content via the Tcl programming language integrated with the Apache Web Server.Steve: Apache SteveTaglibs: A collection of JavaServer Pages (JSP) custom tag libraries useful in building web applicationsTomcat 6: A Servlet container implementing the Servlet Specification v2.5 and the Java Server Pages (JSP) Specification v2.1.Tomcat 7: A Servlet container implementing the Servlet Specification v3.0 and the Java Server Pages (JSP) Specification v2.2.Tomcat 8: A Servlet container implementing the Servlet Specification v3.1 and the Java Server Pages (JSP) Specification TBD, EL specification 3.0 and WebSocket specification 1.0Tomcat Connectors: Provides integration between Apache Tomcat and a range of web serversTomcat Modules: Additional modules for Apache Tomcat. Modules may be for a specific Tomcat version or may work with several. See each module's documentation for details.Tomcat Native: Provides an APR based native HTTP and AJP connectors for TomcatWebSH: Thanks in advanceAmin From: sanjeev.neelar...@citrix.com To: users@cloudstack.apache.org Subject: RE: Upgrade from 2.2.14 to 4.2 fails Date: Fri, 8 Nov 2013 08:53:38 + This looks like a bug . Please report the issue in issues.apache.org with DB schema before upgrade and management server logs. -Original Message- From: Amin Samir [mailto:aminsamira...@hotmail.com] Sent: Friday, November 08, 2013 12:56 PM To: users@cloudstack.apache.org Subject: Upgrade from 2.2.14 to 4.2 fails Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
RE: Upgrade from 2.2.14 to 4.2 fails
This looks like a bug . Please report the issue in issues.apache.org with DB schema before upgrade and management server logs. -Original Message- From: Amin Samir [mailto:aminsamira...@hotmail.com] Sent: Friday, November 08, 2013 12:56 PM To: users@cloudstack.apache.org Subject: Upgrade from 2.2.14 to 4.2 fails Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
RE: Upgrade from 2.2.14 to 4.2 fails
Hi, I have observed Duplicate column name 'hypervisor_version' only when I tried to restart the Management server second time which was failed to start for the first time soon after upgrade . Analysis : The first script that gets executed during 2.2.14 to 4.2 is /usr/share/cloudstack-management/setup/db/schema-2214to30.sql . In this sql script , the first sql stmt is : ALTER TABLE `cloud`.`host` ADD COLUMN `hypervisor_version` varchar(32) COMMENT 'hypervisor version' AFTER hypervisor_type; == There is a possibility that the schema-2214to30.sql got executed already during the first attempt of upgrade. This would have created hypervisor_version column which resulted duplicate entry failure during second attempt. Can you please check for Exceptions which were logged during first attempt of upgrade. Thanks , Sailaja.M -Original Message- From: Amin Samir [mailto:aminsamira...@hotmail.com] Sent: 08 November 2013 12:56 To: users@cloudstack.apache.org Subject: Upgrade from 2.2.14 to 4.2 fails Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
Re: Upgrade from 2.2.14 to 4.2 fails
Hi Sailaja, Thanks for your response, How can I check for the exception which were logged during the upgrade? Amin Sent from my iPad On Nov 8, 2013, at 5:41 PM, Sailaja Mada sailaja.m...@citrix.com wrote: Hi, I have observed Duplicate column name 'hypervisor_version' only when I tried to restart the Management server second time which was failed to start for the first time soon after upgrade . Analysis : The first script that gets executed during 2.2.14 to 4.2 is /usr/share/cloudstack-management/setup/db/schema-2214to30.sql . In this sql script , the first sql stmt is : ALTER TABLE `cloud`.`host` ADD COLUMN `hypervisor_version` varchar(32) COMMENT 'hypervisor version' AFTER hypervisor_type; == There is a possibility that the schema-2214to30.sql got executed already during the first attempt of upgrade. This would have created hypervisor_version column which resulted duplicate entry failure during second attempt. Can you please check for Exceptions which were logged during first attempt of upgrade. Thanks , Sailaja.M -Original Message- From: Amin Samir [mailto:aminsamira...@hotmail.com] Sent: 08 November 2013 12:56 To: users@cloudstack.apache.org Subject: Upgrade from 2.2.14 to 4.2 fails Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
Re: Upgrade from 2.2.14 to 4.2 fails
Hello, Forgot to mention my environment is as follows: 1) One Ubuntu 10.04 as Management server 2) One Ubuntu 10.4 as NFS server. 3) two Xen servers 5.6 sp2. If that's help. Amin Samir Thanks in advance. Sent from my iPad On Nov 8, 2013, at 5:41 PM, Sailaja Mada sailaja.m...@citrix.com wrote: Hi, I have observed Duplicate column name 'hypervisor_version' only when I tried to restart the Management server second time which was failed to start for the first time soon after upgrade . Analysis : The first script that gets executed during 2.2.14 to 4.2 is /usr/share/cloudstack-management/setup/db/schema-2214to30.sql . In this sql script , the first sql stmt is : ALTER TABLE `cloud`.`host` ADD COLUMN `hypervisor_version` varchar(32) COMMENT 'hypervisor version' AFTER hypervisor_type; == There is a possibility that the schema-2214to30.sql got executed already during the first attempt of upgrade. This would have created hypervisor_version column which resulted duplicate entry failure during second attempt. Can you please check for Exceptions which were logged during first attempt of upgrade. Thanks , Sailaja.M -Original Message- From: Amin Samir [mailto:aminsamira...@hotmail.com] Sent: 08 November 2013 12:56 To: users@cloudstack.apache.org Subject: Upgrade from 2.2.14 to 4.2 fails Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
Upgrade from 2.2.14 to 4.2 fails
Hello, I am new to cloudstack and I have an assignment to upgrade a current production environment from 2.2.14 to 4.2, I follow the exact 4.2 release documentation and then the upgrade fails the output of the log file states the following: Duplicate column name 'hypervisor_version' Unable to execute upgrade script: /usr/share/cloudstack-management/setup/db/schema-2214to30.sql System integrity check failed. Refuse to startup Could anyone help please with the aforementioned issue? I am also not sure how to collaborate with the team is it the right way to send an inquiry mail to users@cloudstack.apache.org? or there are other ways to ask questions? Amin SamirSystems Administrator
