HI... Igor and thomas..

scalr.instances_connection_policy is auto..

It looks like the value is not any affect on the major issue..

change this value???


On Wednesday, February 18, 2015 at 2:47:11 AM UTC+9, Thomas Orozco wrote:
>
> Just in case: this file is found in 
> /opt/scalr-server/embedded/scalr/app/etc/config.yml
>
> Cheers,
>
> -- Thomas | Product Manager @ Scalr | [email protected] <javascript:> | 
> www.scalr.com | blog.scalr.com
>
> On Tue, Feb 17, 2015 at 9:43 AM, Igor Savchenko <[email protected] 
> <javascript:>> wrote:
>
>> Hi Hee-Sung Kim,
>>
>> What is the value of scalr.instances_connection_policy configuration
>> in your config.yml?
>>
>> Regards,
>> Igor
>>
>> On 16 February 2015 at 18:46, Hee-Sung Kim <[email protected] 
>> <javascript:>> wrote:
>> >
>> > My host ips
>> >   - client(scalarizr) : 172.19.130.118
>> >   - proxy server     : 172.19.130.119
>> >   - app web server : 172.19.130.120
>> >   - mysql DB server : 172.19.130.121
>> >
>> > it is right server..
>> >
>> > scalarizr (172.19.130.118) -> proxy (172.19.130.119) (mod_proxy 
>> Loadbalancer
>> > by scalr-package-installation, only proxy[:enable] = true) -> app web 
>> server
>> > (172.19.130.120) (all web[:enable] = true, cron[:enable] = true,
>> > service[:enable] = true and memcached[:enable] = true)
>> >
>> > the app-web-server (SCALR) does not know the client ip except for 
>> proxy-ip.
>> >
>> >
>> > On Tuesday, February 17, 2015 at 9:23:11 AM UTC+9, Thomas Orozco wrote:
>> >>
>> >> You seem to not be importing the right server.
>> >>
>> >> According to your screenshot, the server you're trying to import has IP
>> >> 172.19.130.118.
>> >>
>> >> However, the server you are trying to import (i.e. the one you 
>> selected in
>> >> the Server dropdown has IP 172.19.130.119, which is your load 
>> balancer's
>> >> IP).
>> >>
>> >> Are you sure d8ab80a4-... is the right server? Can you provide a
>> >> screenshot of your Horizon OpenStack dashboard (or a screenshot of a 
>> nova
>> >> list CLI call) showing your 3 Scalr Servers and the one you are trying 
>> to
>> >> import?
>> >>
>> >> As for DSR: no, Scalr does not use DSR, and you're not supposed to 
>> somehow
>> >> enable DSR to use Scalr.
>> >>
>> >> Cheers,
>> >>
>> >> On Monday, February 16, 2015 at 4:05:41 PM UTC-8, Hee-Sung Kim wrote:
>> >>>
>> >>>
>> >>>
>> >>> 2015년 2월 17일 화요일 오전 9시 2분 15초 UTC+9, Hee-Sung Kim 님의 말:
>> >>>>
>> >>>> Hi.. thomas..
>> >>>>
>> >>>> it seems like not to pass the client ip to app-server....
>> >>>> i think... proxy-server needs like DSR function..
>> >>>> or possible to use and configure DSR (Direct Server Return) on
>> >>>> proxy-server??
>> >>>>
>> >>>> 2015년 2월 17일 화요일 오전 1시 23분 30초 UTC+9, Thomas Orozco 님의 말:
>> >>>>>
>> >>>>> Hi there,
>> >>>>>
>> >>>>> 8013 is the port Scalr uses to connect to the agent on the instance
>> >>>>> you're importing.
>> >>>>>
>> >>>>> But here, it looks like Scalr is trying to connect to the agent on 
>> your
>> >>>>> proxy server.
>> >>>>>
>> >>>>> Can you double check you selected the right server in the import 
>> step
>> >>>>> (that you didn't unintentionally select the proxy server)
>> >>>>>
>> >>>>> If that doesn't seem work, can you send a screenshot of your sever
>> >>>>> import screen?
>> >>>>>
>> >>>>> ---
>> >>>>>
>> >>>>> To answer your second question: Scalr -> Instances communication 
>> does
>> >>>>> *not* go through the proxy.
>> >>>>>
>> >>>>> Cheers,
>> >>>>>
>> >>>>> On Feb 16, 2015 4:35 AM, "Hee-Sung Kim" <[email protected]> wrote:
>> >>>>>>
>> >>>>>> HI. there...
>> >>>>>>
>> >>>>>> after using the Scalr packages installation, i can not create role
>> >>>>>> from a non-scalr-server.
>> >>>>>>
>> >>>>>>     * one proxy server + one server (all the service for scalr) + 
>> one
>> >>>>>> db server
>> >>>>>>       - proxy server ip : 192.168.56.10
>> >>>>>>       - service for scalr server ip : 192.168.56.20
>> >>>>>>       - db server ip : 192.168.56.30
>> >>>>>>       - non-scalr-server ip : 192.168.56.40
>> >>>>>>
>> >>>>>> when the non-scalr-server(192.168.56.40) was imported, outbound 
>> (scalr
>> >>>>>> -> non-scalr-server) communication couldn't be established.
>> >>>>>>
>> >>>>>> - error message
>> >>>>>>
>> >>>>>>          Could not establish communication with 192.168.56.10:8013
>> >>>>>>
>> >>>>>> is there some function like DSR(Direct Server Return) on
>> >>>>>> scalr-proxy-server so that the server could send return traffic 
>> directly to
>> >>>>>> the client..??
>> >>>>>> that ip is proxy-server-ip, not non-scalr-server ip..
>> >>>>>>
>> >>>>>> --
>> >>>>>> You received this message because you are subscribed to the Google
>> >>>>>> Groups "scalr-discuss" group.
>> >>>>>> To unsubscribe from this group and stop receiving emails from it, 
>> send
>> >>>>>> an email to [email protected].
>> >>>>>> For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > You received this message because you are subscribed to the Google 
>> Groups
>> > "scalr-discuss" group.
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an
>> > email to [email protected] <javascript:>.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "scalr-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to