Closed asos-francesca closed 5 years ago
You can turn logging on from the admin console(localhost:8881/admin) for the DifferenceProxy package to see if there are any networking or payload parsing failures happening. Please share the logs once you have them for further troubleshooting if necessary.
if you are running diffy
from the docker container, make sure that the master
, secondary
& candidate
is available for your network (localhost)
helped me docker run -ti --net=host \ ...
without port forwarding
Closing old issues. Please comment if needs to be re-opened.
Hello, I have the same issue. In fact, the docker image starts ok and when I do the curl, it gives me back the api result correctly, but when I go to the front-end o diffy on localhost:8888, nothing had happen :/...I mean, is empty, there is nothing logged
If I check de docker logs, when doing the curl, this line gets logged:
15:39:46.970 [finagle/netty4-2-16] INFO com.twitter.finagle - FailureAccrualFactory marking connection to "candidate" as dead. Remote Address: Inet(localhost/127.0.0.1:9290,Map())
But, my candidate is alive...Is started and i can access with a curl to it (localhost:9290)
Using docker, wanting to compare my local dev instance with production, running:
Then:
curl localhost:8880/my/path/to/page
I get nothing. No results in the diffy comparison window. No errors. No logging. No network problems.