Error 503
-
I’m getting this error:
“Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.”
PRECEDENTS: Redis service terminated yesterday due to:
“Out of memory: The process “redis-server” was terminated because the system is low on memory.Memory Information: Process Total Virtual Memory: 10042792kB. Used: 6.55 GB, Available: 8.96 GB, Installed: 15.51 GB. Uptime: 19 days, 7 hours, 30 minutes, and 42 seconds. “
As site was down. I tried next, in this order:
– Deleted wp-content/object-cache.php, (this resolves the 503 error and get things back to normal, despite object cache is disabled).
– Restarted redis service from terminal
– Issue redis FLUSHALL on terminal. It returns “OK”. Still 503 when enabling redis on the plugin.
– Deinstalled the WP Redis plugin and reinstalled again. Still 503 when enabling it. As it is a production site, I delete object-cache after each 503.
– Deinstalled the redis service on the server and re-installed from the repo (last version). Still 503 when enabling object cache on the plugin.
– Graceful Server reboot. Still 503.
– Checked wp-config, all values seem correct, as suggested on readme.doc. Tried several settings, as add a prefix, change database number, etc.
– Tested the staging site and Redis works perfectly there on staging when enabled. It is the same server, different directory on public_html.
– Deleted all wp transients on production site. Still 503.
– Redis flushall again from terminal. -> returns “OK”.
– Read this forum, everything I’ve tried doesn’t works, still a 503. (I’m aware I can delete object-cache.php to get things back to normal, without oject cache. While staging site works well all time with redis object cacheWhile error.log shows nothing, var/log/redis shows:
12911:M 14 Oct 2024 12:14:29.065 * 1 changes in 3600 seconds. Saving…
12911:M 14 Oct 2024 12:14:29.066 * Background saving started by pid 28339
28339:C 14 Oct 2024 12:14:29.181 * DB saved on disk
28339:C 14 Oct 2024 12:14:29.184 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
12911:M 14 Oct 2024 12:14:29.268 * Background saving terminated with success
Not sure if this is related to the staging site. However production still shows 503 when enabling redis, both on admin and front end.
Do I’m missing something?
- You must be logged in to reply to this topic.