On Mon, Jul 29, 2013 at 11:38 AM, Evanthika Amarasiri <[email protected]>wrote:
> Hi Sameera, > > As per the offline discussion we had with you all, set the IP as > the localMemberHost instead of the *HostName *and we were able to access > the Management console successfully. Also removed all entries from > /etc/hosts file of both ELB & manager nodes. > > However, with the previous clustering implementation, we were able to use > the host name as well (The documentation mentions that we should set the > /etc/hosts entries and that we can use the Host name for localMemberHost > parmater). So, I suppose this should be fixed? > Oh.. yes.. this is a bug IMO and should be fixed. Hard coding IPs is hard when it comes to a real deployment. > > Regards, > Evanthika > > > On Mon, Jul 29, 2013 at 2:05 PM, Nirodha Pramod <[email protected]> wrote: > >> Hi, >> >> When the WRK/MGR separated cluster is created fronted with the latest ELB >> we noticed the $subject. Even though it logs that the the member joined to >> the ELB but it really does not. >> >> Issue reported at [1] >> [1] https://wso2.org/jira/browse/CARBON-14238 >> >> -Nirodha >> >> >> -- >> * >> * >> *Nirodha Gallage* >> Senior Software Engineer, QA. >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94716429078 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
