You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/07/26 15:35:49 UTC
[jira] [Created] (CLOUDSTACK-3858) [Upgrade from 2.2.15 to 4.2]
After upgrade from 2.2.15 to 4.2 the tomcat.conf file and server.xml file
is missing due to which the management server can't be started
Abhinav Roy created CLOUDSTACK-3858:
---------------------------------------
Summary: [Upgrade from 2.2.15 to 4.2] After upgrade from 2.2.15 to 4.2 the tomcat.conf file and server.xml file is missing due to which the management server can't be started
Key: CLOUDSTACK-3858
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3858
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Infra
Affects Versions: 4.2.0
Environment: MS : CentOS 6.1
Host : Xen 6.0.2
2.2.15 build : CloudStack-2.2.15-2-rhel6.2
4.2 : The relevant upgrade build
Reporter: Abhinav Roy
Priority: Blocker
Fix For: 4.2.0
Steps :
======================
1. Deploy a CS advanced zone setup with CentOS 6.1 and MS and Xen 6.0.2 as the Host.
2. Do some pre-upgrade configurations.
3. Upgrade to 4.2 using the following steps....... ( i am just pasting the console output i got on executing those steps)
./install.sh
Setting up the temporary repository...
Cleaning Yum cache...
Loaded plugins: fastestmirror
Cleaning repos: base cloud-temp extras updates
7 metadata files removed
Welcome to the CloudPlatform Installer. What would you like to do?
NOTE: For installing KVM agent, please setup EPEL<http://fedoraproject.org/wiki/EPEL> yum repo first;
For installing CloudPlatform on RHEL6.x, please setup distribution yum repo either from ISO or from your registeration account.
3.We detect you already have MySql server installed, you can bypass mysql install chapter in CloudPlatform installation guide.
Or you can use E) to remove current mysql then re-run install.sh selecting D) to reinstall if you think existing MySql server has some trouble.
For MySql downloaded from community, the script may not be able to detect it.
M) Install the Management Server
A) Install the Agent
B) Install BareMetal Agent
S) Install the Usage Monitor
U) Upgrade the CloudPlatform packages installed on this computer
R) Stop any running CloudPlatform services and remove the CloudPlatform packages from this computer
E) Remove the MySQL server (will not remove the MySQL databases)
Q) Quit
> u
Updating the CloudPlatform and its dependencies...
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.ispros.com.bd
* extras: mirrors.ispros.com.bd
* updates: mirrors.ispros.com.bd
base | 3.7 kB 00:00
cloud-temp | 1.3 kB 00:00 ...
cloud-temp/primary | 2.4 kB 00:00 ...
cloud-temp 6/6
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package cloud-client.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-client-ui.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-core.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-deps.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-python.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-server.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-setup.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloud-utils.x86_64 0:2.2.15-2.el6 will be obsoleted
---> Package cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
---> Package cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6 will be obsoleting
--> Processing Dependency: cloudstack-awsapi = 4.2.0 for package: cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
--> Processing Dependency: mysql-connector-java for package: cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64
--> Running transaction check
---> Package cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el6 will be installed
---> Package mysql-connector-java.noarch 1:5.1.17-6.el6 will be installed
--> Processing Dependency: jta >= 1.0 for package: 1:mysql-connector-java-5.1.17-6.el6.noarch
--> Processing Dependency: slf4j for package: 1:mysql-connector-java-5.1.17-6.el6.noarch
--> Running transaction check
---> Package geronimo-specs-compat.noarch 0:1.0-3.5.M2.el6 will be installed
--> Processing Dependency: geronimo-specs = 1.0-3.5.M2.el6 for package: geronimo-specs-compat-1.0-3.5.M2.el6.noarch
---> Package slf4j.noarch 0:1.5.8-8.el6 will be installed
--> Running transaction check
---> Package geronimo-specs.noarch 0:1.0-3.5.M2.el6 will be installed
--> Processing Dependency: apache-tomcat-apis for package: geronimo-specs-1.0-3.5.M2.el6.noarch
--> Running transaction check
---> Package apache-tomcat-apis.noarch 0:0.1-1.el6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================================================================================================================================
Package Arch Version Repository Size
=============================================================================================================================================================================================
Installing:
cloudstack-common x86_64 4.2.0-SNAPSHOT.el6 cloud-temp 86 M
replacing cloud-core.x86_64 2.2.15-2.el6
replacing cloud-deps.x86_64 2.2.15-2.el6
replacing cloud-python.x86_64 2.2.15-2.el6
replacing cloud-setup.x86_64 2.2.15-2.el6
replacing cloud-utils.x86_64 2.2.15-2.el6
cloudstack-management x86_64 4.2.0-SNAPSHOT.el6 cloud-temp 73 M
replacing cloud-client.x86_64 2.2.15-2.el6
replacing cloud-client-ui.x86_64 2.2.15-2.el6
replacing cloud-server.x86_64 2.2.15-2.el6
Installing for dependencies:
apache-tomcat-apis noarch 0.1-1.el6 base 164 k
cloudstack-awsapi x86_64 4.2.0-SNAPSHOT.el6 cloud-temp 68 M
geronimo-specs noarch 1.0-3.5.M2.el6 base 111 k
geronimo-specs-compat noarch 1.0-3.5.M2.el6 base 7.1 k
mysql-connector-java noarch 1:5.1.17-6.el6 base 1.4 M
slf4j noarch 1.5.8-8.el6 base 131 k
Transaction Summary
=============================================================================================================================================================================================
Install 8 Package(s)
Total download size: 229 M
Is this ok [y/N]: y
Downloading Packages:
(1/8): apache-tomcat-apis-0.1-1.el6.noarch.rpm | 164 kB 00:01
(5/8): geronimo-specs-1.0-3.5.M2.el6.noarch.rpm | 111 kB 00:01
(6/8): geronimo-specs-compat-1.0-3.5.M2.el6.noarch.rpm | 7.1 kB 00:00
(7/8): mysql-connector-java-5.1.17-6.el6.noarch.rpm | 1.4 MB 00:09
(8/8): slf4j-1.5.8-8.el6.noarch.rpm | 131 kB 00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 14 MB/s | 229 MB 00:16
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : apache-tomcat-apis-0.1-1.el6.noarch 1/16
Installing : geronimo-specs-1.0-3.5.M2.el6.noarch 2/16
Installing : geronimo-specs-compat-1.0-3.5.M2.el6.noarch 3/16
Installing : slf4j-1.5.8-8.el6.noarch 4/16
Installing : 1:mysql-connector-java-5.1.17-6.el6.noarch 5/16
Installing : cloudstack-common-4.2.0-SNAPSHOT.el6.x86_64 6/16
Installing : cloudstack-awsapi-4.2.0-SNAPSHOT.el6.x86_64 7/16
Installing : cloudstack-management-4.2.0-SNAPSHOT.el6.x86_64 8/16
cp: cannot stat `/etc/cloud.rpmsave/management/key': No such file or directory
Unable to determine ssl settings for server.xml, please run cloudstack-setup-management manually
Unable to determine ssl settings for tomcat.conf, please run cloudstack-setup-management manually
Erasing : cloud-client-ui-2.2.15-2.el6.x86_64 9/16
Erasing : cloud-client-2.2.15-2.el6.x86_64 10/16
Stopping cloud-management:[ OK ]
Erasing : cloud-setup-2.2.15-2.el6.x86_64 11/16
Erasing : cloud-server-2.2.15-2.el6.x86_64 12/16
Erasing : cloud-core-2.2.15-2.el6.x86_64 13/16
Erasing : cloud-deps-2.2.15-2.el6.x86_64 14/16
Erasing : cloud-utils-2.2.15-2.el6.x86_64 15/16
Erasing : cloud-python-2.2.15-2.el6.x86_64 16/16
Installed:
cloudstack-common.x86_64 0:4.2.0-SNAPSHOT.el6 cloudstack-management.x86_64 0:4.2.0-SNAPSHOT.el6
Dependency Installed:
apache-tomcat-apis.noarch 0:0.1-1.el6 cloudstack-awsapi.x86_64 0:4.2.0-SNAPSHOT.el6 geronimo-specs.noarch 0:1.0-3.5.M2.el6 geronimo-specs-compat.noarch 0:1.0-3.5.M2.el6
mysql-connector-java.noarch 1:5.1.17-6.el6 slf4j.noarch 0:1.5.8-8.el6
Replaced:
cloud-client.x86_64 0:2.2.15-2.el6 cloud-client-ui.x86_64 0:2.2.15-2.el6 cloud-core.x86_64 0:2.2.15-2.el6 cloud-deps.x86_64 0:2.2.15-2.el6 cloud-python.x86_64 0:2.2.15-2.el6
cloud-server.x86_64 0:2.2.15-2.el6 cloud-setup.x86_64 0:2.2.15-2.el6 cloud-utils.x86_64 0:2.2.15-2.el6
Complete!
Done
[root@MS-CentOS61 CloudPlatform-4.2-dbupgrade-14-rhel6.2]# cloudstack-setup-encryption
Preparing /etc/cloudstack/management/db.properties [ OK ]
Processing encryption ... [ OK ]
Finalizing setup ... [ OK ]
CloudStack has successfully setup Encryption
-----------------------------------
After this i tried to start the management service and got this error,
#service cloudstack-management start
/etc/sysconfig/cloudstack-management: line 21: /etc/cloudstack/management/tomcat6.conf: No such file or directory
Starting cloudstack-management: awk: cmd. line:1: fatal: cannot open file `/etc/cloudstack/management/tomcat6.conf' for reading (No such file or directory)
Error code 4 [FAILED]
and as we can see the files are not present in /etc/cloudstack/management
[root@MS-CentOS61 management]# ls /etc/cloudstack/management
applicationContext.xml catalina.properties commons-logging.properties ec2-service.properties log4j-cloud.xml tomcat6-nonssl.conf web.xml
Catalina classpath.conf db.properties environment.properties server-nonssl.xml tomcat6-ssl.conf
catalina.policy cloud-bridge.properties db.properties.rpmnew key server-ssl.xml tomcat-users.xml
------------------------------------------------------------------
NOTE : Both the Management server VM and the XEN host were freshly installed for this deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira