Project

General

Profile

tickets #105518

Since today https://progress.opensuse.org/projects/qa/wiki/Tools fails to load (or takes very long), unlike https://progress.opensuse.org/projects/qa/wiki

Added by okurz 5 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Redmine
Target version:
-
Start date:
2022-01-26
Due date:
% Done:

100%

Estimated time:

Description

Hi, since today https://progress.opensuse.org/projects/qa/wiki/Tools fails to load (or takes very long), unlike https://progress.opensuse.org/projects/qa/wiki . I am not aware of anything special that we included on the page except for changing simple text that could explain such behaviour.

In contrast curl https://progress.opensuse.org/projects/qa/wiki/Tools.json works very snappy, 0.3s for me.

History

#1 Updated by okurz 5 months ago

  • Private changed from Yes to No

#2 Updated by okurz 5 months ago

  • Description updated (diff)

#3 Updated by bmwiedemann 5 months ago

I found these related log entries:

==> /var/log/nginx/redmine.error.log <==
2022/01/26 13:26:40 [error] 1366#1366: *2671483 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 2a02:...:7812, server: progress.opensuse.org, request: "GET /projects/qa/wiki/Tools HTTP/1.1", upstream: "http://127.0.0.1:3000/projects/qa/wiki/Tools", host: "progress.opensuse.org", referrer: "https://progress.opensuse.org/issues/105518"

==> /var/log/nginx/redmine.access.log <==
2a02:...:7812 - - [26/Jan/2022:13:29:45 +0000] "GET /projects/qa/wiki/Tools HTTP/1.1" 504 494 "https://progress.opensuse.org/issues/105518" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"

#4 Updated by okurz 5 months ago

So nginx says that redmine timed out, right. I logged in to progress.i.o.o myself and checked /opt/redmine/log/production.log . I would have expected many messages and also something related to that but there is not much traffic in this

#5 Updated by bmwiedemann 5 months ago

  • Status changed from New to Resolved
  • Assignee set to bmwiedemann
  • % Done changed from 0 to 100

Seems to be back working after a power-cycle of the progress VM.

Maybe it did not like the hot-add + hot-remove of yesterday.

Also available in: Atom PDF