Re: ACS in a VMware environment

2014-09-01 Thread Damoder Reddy
Or simply disable the db ha in "/etc/cloudstack/management/db.properties” if you really not required, till you upgrade to the next version. On 02-Sep-2014, at 9:33 am, Rajani Karuturi wrote: > I think you are hitting this defect > https://issues.apache.org/jira/browse/CLOUDSTACK-6892 > The fix

Re: ACS in a VMware environment

2014-09-01 Thread Rajani Karuturi
I think you are hitting this defect https://issues.apache.org/jira/browse/CLOUDSTACK-6892 The fix is in 4.3.1 and 4.4.1 branches. As workaround, you can manually update catalina.properties as per the changes in the fix [1] [1] https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=

RE: ACS in a VMware environment

2014-08-28 Thread Geoff Higginbottom
] Sent: 28 August 2014 14:17 To: users@cloudstack.apache.org Subject: Re: ACS in a VMware environment I must be missing something. So I am installing this on a CentOS 6.5 fully patched server that is configured as a basic server. Here are the steps I take when installing ACS. 1. Extract the RPMs

Re: ACS in a VMware environment

2014-08-28 Thread Xerex Bueno
So I have found the cause of the problem, can someone explain why? The issue is happens when I enable DB HA. Below is the log output 2014-08-28 08:17:03,792 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : true 2014-08-28 08:17:03,824 INFO [c.c.u.d.T.Tran

Re: ACS in a VMware environment

2014-08-28 Thread Xerex Bueno
I must be missing something. So I am installing this on a CentOS 6.5 fully patched server that is configured as a basic server. Here are the steps I take when installing ACS. 1. Extract the RPMs and run ‘createrepo’ 2. Create the .repo, and run yum install cloudstack-management 3. Run setenforce

Re: ACS in a VMware environment

2014-08-28 Thread ilya musayev
Xerex I've just rebuild cloudstack. I had no issues with this build. no 404s. http://download.cloudsand.com/cloudsand/rhel/6/x86_64/cloudstack-4.3.0.1-08282014.rpm.tgz Regards ilya On 8/27/14, 2:31 PM, Xerex Bueno wrote: > Ilya, > > I have installed from the packages you provided. However I am

Re: ACS in a VMware environment

2014-08-27 Thread Xerex Bueno
Ilya, I have installed from the packages you provided. However I am running into a 404 error when I try and access the Web UI. Have you experienced this issue? On 8/20/14, 10:23 AM, "Xerex Bueno" wrote: >Thanks for the info and the link. I will give it a shot. > > > > > >On 8/19/14, 3:46

Re: ACS in a VMware environment

2014-08-20 Thread Xerex Bueno
Thanks for the info and the link. I will give it a shot. On 8/19/14, 3:46 PM, "ilya musayev" wrote: >Xerex, > >Dont use forward branch, you need to use 4.3 under "heads". > >example: git checkout remotes/origin/4.3 > >16 servers is rather small. I've just completed a rebuild of 4.3.0.1 >fro

Re: ACS in a VMware environment

2014-08-19 Thread ilya musayev
Xerex, Dont use forward branch, you need to use 4.3 under "heads". example: git checkout remotes/origin/4.3 16 servers is rather small. I've just completed a rebuild of 4.3.0.1 from source (includes noredist packages). http://download.cloudsand.com/cloudsand/rhel/6/x86_64/cloudstack-4.3.0.1-

Re: ACS in a VMware environment

2014-08-18 Thread Erik Weber
It should be the 4.3 branch, and yes you still have to download jars and pass noredist. Erik 19. aug. 2014 04:37 skrev "Xerex Bueno" følgende: > It is going to start with a max of 16 servers and I don¹t see it utilizing > more then four servers to start with. As for the 4.3.1 source code, is >

Re: ACS in a VMware environment

2014-08-18 Thread Xerex Bueno
It is going to start with a max of 16 servers and I don¹t see it utilizing more then four servers to start with. As for the 4.3.1 source code, is that under Github 4.3.0 forward? Also do I still need to compile it with -NoRedist and the vmware .jar files? On 8/18/14, 3:27 PM, "ilya musayev"

Re: ACS in a VMware environment

2014-08-18 Thread ilya musayev
Xerex You want the latest 4.3.0.1 (aka 4.3.1), build it from source. There are few patches that haven't been committed upstream yet, but they address a specific issue witnessed only on large vmware envs. Depending on how large is your environment, you may want to tweak the java heap size and