Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
sites inaccessible
Just a heads up. Since yesterday I’ve been experiencing a number of 504 errors on the .com txp domains. I also confirmed these with downforeveryoneorjustme.com.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: sites inaccessible
You are not alone! Today while posting in another thread I had 3 or so occurrences.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
Offline
Re: sites inaccessible
Aye, me too. Gateway timeouts. Usually that’s indicative of a third party / dependent site not responding in time.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: sites inaccessible
I contacted Pete earlier and he has now upped memory limits on the server which may have been causing this issue. Please let us know if the problem persists. Ta!
Offline
Re: sites inaccessible
Right now, the forum was terribly slow to access (at first). But then accessing the login page, etc and reaching here went quite fast.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
Offline
Re: sites inaccessible
Some technicals (I’ll write more later): I’ve upped the time out window for PHP on Nginx, and also bumped the memory_limit on PHP.
I’ve also juggled the file format for the hourly forum database backup (which runs ~400MB), so that should improve responsiveness.
Apologies for the turbulence.
Offline
Re: sites inaccessible
Post mortem.
Cause of sporadic outage: PHP 7.3 memory_limit was too low. A combination of PHP-FPM (i.e. the glue that makes PHP work with Nginx, in this case) and PHPBU using the same version of PHP, along with a typo in the config file (i.e. memory_limit = 128M should have been memory_limit = 512M) meant there wasn’t enough system RAM allotted to all the stuff that was happening. And there was a lot of stuff happening.
Solution: PHP 7.3 memory_limit has been increased.
Offline