504 for puma/mariadb timeouts
This commit is contained in:
parent
891aabbffe
commit
e7e5625a4f
|
@ -4,7 +4,7 @@
|
||||||
<title>Lobsters HTTP 502 status: puma timeout</title>
|
<title>Lobsters HTTP 502 status: puma timeout</title>
|
||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
<h1>Lobsters HTTP 500 status: server error</h1>
|
<h1>Lobsters HTTP 502 status: server error</h1>
|
||||||
<p>
|
<p>
|
||||||
nginx tried to pass your request to puma but failed.
|
nginx tried to pass your request to puma but failed.
|
||||||
This probably means we're in the middle of a deploy.
|
This probably means we're in the middle of a deploy.
|
||||||
|
|
|
@ -0,0 +1,20 @@
|
||||||
|
<!DOCTYPE html>
|
||||||
|
<html>
|
||||||
|
<head>
|
||||||
|
<title>Lobsters HTTP 504 status: puma timeout</title>
|
||||||
|
</head>
|
||||||
|
<body>
|
||||||
|
<h1>Lobsters HTTP 504 status: server error</h1>
|
||||||
|
<p>
|
||||||
|
The puma worker timed out responding to your request.
|
||||||
|
</p>
|
||||||
|
<p>
|
||||||
|
2023-09-01: we've been seeing this a bunch for /search and are tuning database performance to try to address it.
|
||||||
|
</p>
|
||||||
|
<p>
|
||||||
|
If this persists, please come to the
|
||||||
|
<a href="ircs://irc.libera.chat/lobsters">IRC channel</a>
|
||||||
|
(<a href="https://web.libera.chat/#lobsters">webchat</a>).
|
||||||
|
</p>
|
||||||
|
</body>
|
||||||
|
</html>
|
Loading…
Reference in New Issue