One thing you could try would be to just setup Apache on the management server with mod_rewrite, sending your site request down one path, and CS down the other. This way you could keep similar URLs and not require your users to remember port numbers (yuck). Hope that helps..
-Ian On 12/16/14, 1:23 PM, "Tilak Raj Singh" <tila...@gmail.com> wrote: >Hi Kevin, > >Thanks for your help...that got it up and running perfectly...I changed my >system tomcat6 port to 8090 and now everything is working fine. >I wanted to same port as that of cloudstack i.e. 8080 because the website >I >created is using VMs of cloudstack to provide various ondemand >services...Hence I wanted to keep the url same for both the features > >On Wed, Dec 17, 2014 at 2:36 AM, Kevin McCormick < >kevin.mccorm...@intrinium.com> wrote: >> >> You need to first stop the system tomcat, which will take down your >> /portal/ site and free up port 80. `service tomcat6 stop` or something >> similar will probably get you there. Then restart the Cloudstack >>management >> service. >> >> Don't know about putting your site into Cloudstack's, but it doesn't >>sound >> like a good idea. >> >> >> >> Kevin McCormick >> Director of Cloud Services >> >> >> Intrinium >> Tel: (509) 465-1234 x7080 >> Fax: (866) 565-4578 >> Lync / Skype: kevin.mccorm...@intrinium.com >> Web: www.intrinium.com >> -----Original Message----- >> From: Tilak Raj Singh [mailto:tila...@gmail.com] >> Sent: Tuesday, December 16, 2014 12:37 >> To: users@cloudstack.apache.org >> Subject: Re: client not opening on browser >> >> Thanks Kevin... >> >> So what should I do to restart my cloudstack servlet and use port 8080. >> Right now the website is working fine but cloudstack client does not >>show >> up on the webbrowser...I even ran the command *service >> cloudstack-management restart *but sill the website is running and >> cludstack cannot capture port 8080. >> So what steps should I take..ould you please guide me. >> >> Also I wanted to know is there anyway through which I can put my website >> into the cloudstack servlet so that both of them use the same port 8080 >> >> Regards >> >> On Wed, Dec 17, 2014 at 1:45 AM, Kevin McCormick < >> kevin.mccorm...@intrinium.com> wrote: >> > >> > I believe Cloudstack uses its own servlet container, not the system >> > tomcat. Both Cloudstack & the system tomcat default to port 8080, but >> only >> > one of them can use that. So, whichever starts up first wins. >> > >> > The recommended option here is probably to not run anything but ACS on >> the >> > management server, but you could also change the system tomcat to use >>a >> > different port. >> > >> > >> > >> > Kevin McCormick >> > Director of Cloud Services >> > >> > >> > Intrinium >> > Tel: (509) 465-1234 x7080 >> > Fax: (866) 565-4578 >> > Lync / Skype: kevin.mccorm...@intrinium.com >> > Web: www.intrinium.com >> > -----Original Message----- >> > From: Tilak Raj Singh [mailto:tila...@gmail.com] >> > Sent: Tuesday, December 16, 2014 11:36 >> > To: users@cloudstack.apache.org >> > Subject: client not opening on browser >> > >> > Hello everyone, >> > >> > I ran into a problem and would really appreciate if someone could >>help in >> > urgently. >> > I am having a cloudstack management server on ip 172.31.101.202 >> > >> > Earlier when I used to access 172.31.101.202:8080/client I could >>easily >> do >> > that >> > But today I hosted a website on my tomcat server on the same machine >> > I put the website name *portal* in */var/libs/tomcat6/webaps/* >>directory >> > and then ran the command >> > >> > *service tomcat6 restart* >> > >> > As result *I can access my website i.e. 172.31.101.202:8080/portal >> > <http://172.31.101.202:8080/portal>* from the browser >> > but *accessing cloudstack i.e. 172.31.101.202:8080/client >> > <http://172.31.101.202:8080/client> shows a blank page*. >> > >> > Could anyone please help me as quickly as possible >> > >> > Regards >> > >> > >> > This email and any files transmitted with it are confidential and >> intended >> > solely for the use of the individual or entity to whom they are >> addressed. >> > If you have received this email in error please notify the system >> manager. >> > This message contains confidential information and is intended only >>for >> the >> > individual named. If you are not the named addressee you should not >> > disseminate, distribute or copy this e-mail. Please notify the sender >> > immediately by e-mail if you have received this e-mail by mistake and >> > delete this e-mail from your system. If you are not the intended >> recipient >> > you are notified that disclosing, copying, distributing or taking any >> > action in reliance on the contents of this information is strictly >> > prohibited. >> > >> > >>
