Open jnweiger opened 3 years ago
After an upgrade from 10.8.0 RC1 to 10.8.0 the service responds with 503
curl -i -k https://10.90.4.178/owncloud
HTTP/1.1 503 Service Unavailable
Date: Tue, 27 Jul 2021 14:25:47 GMT
Server:
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: script-src 'self' 'unsafe-inline' 'unsafe-eval' ; object-src 'self' ; worker-src 'self' blob:
Content-Length: 299
Connection: close
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body></html>
A stop and restart from the appcenter does not help. Reboot fixes the situation.
We've observed this only on the smaller ARM machine. The bigger x86 mchine seems more stable.
While testing, the ARM machine briefly (but multipe times) showed
This was never seen with the x86 machine. We should give a recommendation against using this specific model with ownCloud. I am afraid, it is too small.
Seen with ownCloud for QNAP 10.8.0 RC1 from
ownCloud_10.8.0_arm-x41.qpkg
No clear steps to reproduce. Happens ca. once per day. Today, after not using the server for several hours, it now only responds with HTTP 599.
Same on https://10.90.4.178/owncloud
Nothing is logged in /mnt/data/files/owncloud.log Also nothing in QNAP Notificaiton Center -> View the System logs
Workaround: A reboot of the qnap host brings back owncloud.