Ta yaya ake binciken kurakuran 502 da 504 a Nginx?

Question

IT Interview Practice · Accepted Answer

Gano inda buƙatar ta gaza kafin ƙara timeouts. 502 yakan nuna sadarwar upstream ta gaza; 504 yakan nuna lokacin jiran upstream ya ƙare. Logs suna bambance ainihin matsalar.

## Misali: manhajar ba ta sauraro

Ka ɗauka cewa wani ɓangaren error log ya ce:

```text
connect() failed (111: Connection refused) while connecting to upstream
upstream: "http://127.0.0.1:3000/products"
```

Nginx ya yi ƙoƙarin haɗuwa da port 3000 amma an ƙi shi. Duba ko manhajar tana aiki kuma tana sauraro a adireshin. Daga na'ura ko container na Nginx kansa, gwada `curl -i http://127.0.0.1:3000/products`. Cikin container, wannan adireshin yana nufin container ɗin kansa, ba container na wata manhaja kai tsaye ba.

## Misali: an haɗu amma headers na amsa ba su iso a kan lokaci ba

```text
upstream timed out while reading response header from upstream
```

Wannan yana nuna jiran response headers. Haɗa buƙatar da logs na manhaja da tambayoyin database masu jinkiri. Duba lokacin haɗuwa da na amsar upstream don ware aikin kafa network daga aikin manhaja.

## Tabbatar da gyaran

Gyara adireshin ko dawo da manhajar da ta gaza a yanayin farko; binciki aikin da yake jinkiri a na biyu. Maimaita route ɗin da ya shafa kuma ka lura da error rate da latency. Tsawon `proxy_read_timeout` yana ba da tazara mafi tsawo tsakanin karatu; ba ya ƙirƙirar ƙarfin backend. Duba logs na CDN da na manhaja ma idan ɗayansu ya samar da kuskuren.

[Takardun hukuma](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout).

Misali: manhajar ba ta sauraro

Misali: an haɗu amma headers na amsa ba su iso a kan lokaci ba

Tabbatar da gyaran

Tambayoyi masu alaƙa