Hi Ilya,

Thanks for getting back.
My problem was actually caused by myself playing around with MySQL bind address 
setting in my.cnf.
Apologies for all the noise.

Florin


-----Original Message-----
From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
Sent: Wednesday, March 19, 2014 3:46 PM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)

Florin,

I had a similar issue earlier today.

My solution was to cleanup everything from previous builds - i did not figure 
what exactly got corrupted where, but i did have layered installs of ACS4.2.1 
on top of multiple versions of 4.3 .

My fix was something along the lines of
rm -rf `locate cloudstack`

But i would ask that you be careful when you run the command above.

I also dropped my databases in order for everything to be recreated - probably 
was not necessary, but i had nothing to loose and it worked.

Regards
ilya

On 3/18/14, 1:45 PM, Florin Dumitrascu wrote:
> Hi Alena,
>
> Actually I just had a quick look at the management server logs and I see this 
> error. MySQL server is running, so not sure what is causing it:
>
> 2014-03-18 17:37:12,453 ERROR [c.c.u.d.Merovingian2] (main:null)
> Unable to get a new db connection
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could 
> not create connection to database server. Attempted reconnect 3 times. Giving 
> up.
>
>
>
> -----Original Message-----
> From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
> Sent: Tuesday, March 18, 2014 5:40 PM
> To: dev@cloudstack.apache.org; Florin Dumitrascu
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
> Florin, can you check the output of the following DB query:
>
> Select * from configuration where name="hypervisor.list"
>
>
>
> On 3/18/14, 10:17 AM, "Florin Dumitrascu"
> <florin.dumitra...@intunenetworks.com> wrote:
>
>> Apologies for the missing link. Screenshot of the GUI bug is here:
>>
>> http://imgur.com/FL9OnY0
>>
>> Thanks,
>> Florin
>>
>>
>> -----Original Message-----
>> From: Florin Dumitrascu [mailto:florin.dumitra...@intunenetworks.com]
>> Sent: Tuesday, March 18, 2014 5:11 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>>
>> Hi,
>>
>> I am trying to create an advanced zone using RC8, but I am blocked
>> even
> >from the first steps.
>> As seen in the attached image, I cannot select the Hypervisor type
>> from the drop down box.
>> Has anyone else seen this behaviour ?
>>
>> Thanks,
>> Florin
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: Thursday, March 13, 2014 12:27 AM
>> To: dev@cloudstack.apache.org
>> Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>>
>> Hi All,
>>
>>
>>
>> I've created a 4.3.0 release, with the following artifacts up for a
>>
>> vote:
>>
>>
>>
>>
>>
>> Git Branch and Commit SH:
>>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h
>> =r
>> efs
>> /heads/4.3
>> Commit: 6a6ec648099553a42f830dcd566eab2452428908
>>
>>
>>
>> List of changes:
>>
>> New Features in 4.3:
>> https://issues.apache.org/jira/issues/?filter=12325248
>>
>> Improvement in 4.3:
>> https://issues.apache.org/jira/issues/?filter=12325249
>>
>> Issues fixed in 4.3
>> https://issues.apache.org/jira/issues/?filter=12326161
>>
>> Known Issues in 4.3:
>> https://issues.apache.org/jira/issues/?filter=12326162
>>
>>
>>
>>
>>
>>
>>
>> Source release (checksums and signatures are available at the same
>>
>> location):
>>
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.3.0/
>>
>>
>>
>> PGP release keys (signed using 94BE0D7C):
>>
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>>
>>
>> Testing instructions are here:
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+p
>> ro
>> ced
>> ure
>>
>>
>>
>> Vote will be open for 72 hours (Monday evening PST 5:30 PM)
>>
>>
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>> indicate "(binding)" with their vote?
>>
>>
>>
>> [ ] +1  approve
>>
>> [ ] +0  no opinion
>>
>> [ ] -1  disapprove (and reason why)
>>
>>
>>
>> Thanks
>>
>> Animesh
>>
>>
>>
>> IMPORTANT NOTE: The information in this e-mail (and any attachments)
>> is confidential. The contents may not be disclosed or used by anyone
>> other than the addressee. If you are not the intended recipient,
>> please notify the sender immediately or telephone: +353 (0)1 6204700.
>> We cannot accept any responsibility for the accuracy or completeness
>> of this message as it has been transmitted over a public network. If
>> you suspect that the message may have been intercepted or amended, please 
>> call the sender.
>>
>>
>> IMPORTANT NOTE: The information in this e-mail (and any attachments)
>> is confidential. The contents may not be disclosed or used by anyone
>> other than the addressee. If you are not the intended recipient,
>> please notify the sender immediately or telephone: +353 (0)1 6204700.
>> We cannot accept any responsibility for the accuracy or completeness
>> of this message as it has been transmitted over a public network. If
>> you suspect that the message may have been intercepted or amended, please 
>> call the sender.
>
> IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
> confidential. The contents may not be disclosed or used by anyone other than 
> the addressee. If you are not the intended recipient, please notify the 
> sender immediately or telephone: +353 (0)1 6204700. We cannot accept any 
> responsibility for the accuracy or completeness of this message as it has 
> been transmitted over a public network. If you suspect that the message may 
> have been intercepted or amended, please call the sender.


IMPORTANT NOTE: The information in this e-mail (and any attachments) is 
confidential. The contents may not be disclosed or used by anyone other than 
the addressee. If you are not the intended recipient, please notify the sender 
immediately or telephone: +353 (0)1 6204700. We cannot accept any 
responsibility for the accuracy or completeness of this message as it has been 
transmitted over a public network. If you suspect that the message may have 
been intercepted or amended, please call the sender.

Reply via email to