Hi all, new to this awesome community, and would greatly appreciate some
help. I love Nginx but for months I've been trying to tackle a very strange
issue where fastcgi is caching a blank page when monitoring tools like
Monitis or Uptime Robot run keyword-based uptime monitors for the root URL
only
> 2017/04/26 20:18:22 [error] 7#7: *34966 open() "/etc/nginx/html/v1/_ping"
> failed (2: No such file or directory), client: 10.40.210.70, server:
> 10.39.228.151, request: "GET /v1/_ping HTTP/1.1", host: "10.39.228.151:9000"
I'm not familiar with the software stack you're using but just looking
Michael Salmon Wrote:
---
> I started testing using a Unix domain socket so that I could a way to
> send a message when my site was down for maintenance but I ran into a
> problem. When I restarted nginx it complained that the sockets already
> ex
HI All,
Below is my issue, I have contacted artifactory support already and no much
help from them, if someone can help me with this, will be of great help.
Described my issue here.
https://github.com/docker/distribution/issues/2266
I have already tried to increase the nginx proxy timeout from d
Test mail,
On Sun, May 7, 2017 at 3:46 PM, Michael Salmon
wrote:
> I started testing using a Unix domain socket so that I could a way to send
> a message when my site was down for maintenance but I ran into a problem.
> When I restarted nginx it complained that the sockets already existed and
>
I started testing using a Unix domain socket so that I could a way to send a
message when my site was down for maintenance but I ran into a problem. When I
restarted nginx it complained that the sockets already existed and wouldn't
start. Is this the expected behaviour?
/Michael Salmon
SE KI34
In limit_req_zone with rate set to 100/s and burst=50, we have below
observation
.
Scenario1
==
no. of request made by jmeter = 170
# of request expected to be failing = 20
# of request actually failed = 23
Question: why 3 more request are failing and is this much of failure
expected
Scen
