cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jessica Tomechak (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-405) management server startup missing from install documents
Date Tue, 23 Oct 2012 23:32:11 GMT


Jessica Tomechak updated CLOUDSTACK-405:

    Status: Ready To Review  (was: In Progress)
> management server startup missing from install documents
> --------------------------------------------------------
>                 Key: CLOUDSTACK-405
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Doc
>            Reporter: Noa Resare
>            Assignee: Jessica Tomechak
> For the simplest possible test case (that I can come up with) the Installation Guide
instructions fail, with status 404 when attempting to connect to http://MANAGEMENT_SERVER:8080/client

> Expected outcome:
> The cloudstack web UI in the web browser when accessing http://MANAGEMENT_SERVER:8080/client
> Actual outcome:
> The default tomcat 404 page
> Steps to reproduce:
> - I created a fully updated vmware vm running a 64 bit Ubuntu 12.04.1
> - installed mysql-server, with root password abc123
> - ran mysql_secure_installation, default options
> - pulled the latest built ubuntu packages from jenkins:
> - ran the install script installing the management server (which translates install 'apt-get
install cloud-client')
> - ran "cloud-setup-databases cloud:foobar --deploy-as=root:abc123" with the output "CloudStack
has successfully initialized database"
> - attempted to connect with my web browser at http://MANAGEMENT_SERVER:8080/client
> Additional notes:
> Looking at the output from the installer, it seems the tomcat6 starts on install, listening
on port 8080. If I run
> "/etc/init.d/tomcat6 stop" followed by "/etc/init.d/cloud-management start" I get a cloudstack
login prompt at http://MANAGEMENT_SERVER:8080/client/

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:

View raw message