+us...@dcos.io
On Wed, May 18, 2016 at 11:27 AM, QiangChen <chenqi...@qiyi.com> wrote:
> I think I should get the root cause that the ip-detect provided in
> official may want to get the source ip (agent ip), but the script found
> wrong source ip but gateway ip. so bound to <slave>:5051 is our aim not
> <gw>:5051
>
> I fixed the script to adapt to my network env to the the source ip. and
> now the DC/OS works successfully now.
>
> The ip-detect script is updated as follows:
>
> ```
> #!/usr/bin/env bash
> set -o nounset -o errexit
>
> MASTER_IP=10.221.82.185
>
> #echo $(/usr/sbin/ip route show to match 10.221.82.185 | grep -Eo
> '[0-9]{1,3}. [0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}' | tail -1)
> echo $(/usr/sbin/ip -d route get 10.221.82.185 | egrep -o 'src ([0-9.]*)'
> | grep -o '[0- 9.]*')
>
> ```
>
> Thanks all for your help.
>
>
> On 2016年05月17日 23:18, Chengwei Yang wrote:
>
>> ABRT generally means that something crittical happened and you may not
>> found
>> that from stdout/stderr, so as journalctl.
>>
>> You may try to run ExecXXX in its ervice file from console manually to
>> see what
>> will happen and get some hints.
>>
>>
>
--
Best Regards,
Haosdent Huang
