Production really slow no display of the articles / no display guidelines: upstream timed out (110: Operation timed out) / (101: Network unreachable)

[eliselavy]

Problem to dispaly guidelines:

2023/11/08 09:11:07 [error] 39#39: *261330 connect() to [2606:50c0:8000::154]:443 failed (101: Network unreachable) while connecting to upstream, client: 10.244.9.63, server: , request: "GET /proxy-githubusercontent/C2DH/jdh-notebook/master/examples/hermeneutic-layer.ipynb HTTP/1.1", upstream: "https://[2606:50c0:8000::154]:443/C2DH/jdh-notebook/master/examples/hermeneutic-layer.ipynb", host: "journalofdigitalhistory.org", referrer: "https://journalofdigitalhistory.org/en/fingerprint-explained"

Problem to display articles:

2023/11/08 09:12:23 [error] 39#39: *261330 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.244.9.63, server: , request: "GET /api/articles?limit=100 HTTP/1.1", upstream: "http://172.19.0.4:8000/api/articles?limit=100", host: "journalofdigitalhistory.org", referrer: "https://journalofdigitalhistory.org/en/articles"

[eliselavy]

I restart the production Many:

110: Operation timed out Timeout when page call the api 101: Network unreachable when page linked to GitHub ( guidelines / preview notebook)

See log here log_nginx_0811.log

[c2dhfma]

The call to /api/articles/?limit=100 is now monitored with Uptime Kuma http://dev.c2dh.uni.lux:3001/dashboard/22

But this does not mean you can leave it like that:

• Your sysadmin must monitor the server in order to find possible bottlenecks;
• Your dev team must investigate the call. It actually takes around 1s to get the response which is quite high. HTH.