mantl / mesos-consul

Mesos to Consul bridge for service discovery
Apache License 2.0
338 stars 95 forks source link

logging 401 response from mesos #126

Open Vladikamira opened 6 years ago

Vladikamira commented 6 years ago

Hi, we faced a problem with synchronization when we enabled authenticate_http_readonly option on mesos-master. After enabling this option on mesos side, synchronization stoped working, but there were no errors on mesos-consul side, even with debug mode. here is tcpdump of session:

17:34:37.026188 IP mesos6-virt.dev.itim.vn.57966 > mesos5-virt.dev.itim.vn.mmcc: Flags [P.], seq 145:290, ack 141, win 1444, options [nop,nop,TS val 603983446 ecr 946918156], length 145
E...,'@.?...
...
..y.n.......{.............
$..V8p..GET /master/state.json HTTP/1.1
Host: 10.3.4.121:5050
User-Agent: Go-http-client/1.1
Content-Type: application/json
Accept-Encoding: gzip

17:34:37.027808 IP mesos5-virt.dev.itim.vn.mmcc > mesos6-virt.dev.itim.vn.57966: Flags [P.], seq 141:281, ack 290, win 1452, options [nop,nop,TS val 946918406 ecr 603983446], length 140
E...7d@.@...
..y
......n.{..........GM.....
8p..$..VHTTP/1.1 401 Unauthorized
Date: Mon, 09 Apr 2018 10:34:37 GMT
WWW-Authenticate: Basic realm="mesos-master-readonly"
Content-Length: 0

healtcheck of mesos-consul shows OK

[root@mesos:~]# docker ps
CONTAINER ID        IMAGE                                     COMMAND                  CREATED             STATUS              PORTS                      NAMES
d9e18722a47d        docker.itim.vn/mesos/mesos-consul:0.4.0   "/bin/mesos-consul..."   About an hour ago   Up About an hour    0.0.0.0:31033->24476/tcp   mesos-1c1d751c-2cd5-47b8-8bd1-859f546cebc3
...

here

[root@mesos:~]# curl http://127.0.0.1:31033/health
OK

Is it possible to log such cases? we want to be sure that synchronization between mesos and consul works properly, how we can do it? Thanks in advance