You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
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:
[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
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 onmesos-consul
side, even with debug mode.here is tcpdump of session:
healtcheck of mesos-consul shows OK
here
Is it possible to log such cases? we want to be sure that synchronization between
mesos
andconsul
works properly, how we can do it?Thanks in advance
The text was updated successfully, but these errors were encountered: