Jump to content
The Uniform Server Community

Avoid for Production Servers - US 13.3.2


Recommended Posts

Avoid using it on production!


HTTPD + PHP has a memory leak, slowing the server down in time and crashing at some point.


It's US 13.3.2 here, but I don't know how far the bug goes back. Haven't tested if it's the build of Apache coming with the stack, or this version of Apache, or PHP.


Tried some different settings with 3 of our servers in the past 3 months. It was a disaster. The first 2 were some low end VPS servers so we thought it could be the servers. The last one is set up on a monster dedicated server with lots of resources after a format. The server was running another stack before with no issues for 5-6 years and we decided to use US for all our systems, due to it's better structure.


But now it's clear that all our troubles were this version of the stack. I was going to try a different Apache build with it, but apperantly we have no time for it now.


I don't know for how long the issue exists but old posts about crashes may be the same issue.


So don't lose time asking for a solution for crashes, it's a known bug now.


I'll miss this stack anyway, it has a good design, just needs to solve this. The dev did a good job but the project needs more attention from more devs now.

Link to comment
Share on other sites

  • 2 weeks later...

Did a lot of testing recently. It's the PHP 7.1.1 coming with the stack, which is full of memory leaking bugs. Even requests for static files increase the memory allocation uncontrollably if PHP 7.1.1 is installed, to the point PHP is unable to allocate more memory and the server crashes.


So, DON'T USE PHP 7.1.1 for production.


You can install PHP 5.6. PHP 7.1 also had numerous updates (7.1.8 currently), mostly dealing with memory leakages. You can try an up to date version.


Still strange, I'd expect some replies to people asking for help on server crashes in the recent years, as it's not a rare issue. At least a warning about 13.3 and PHP 7...

Link to comment
Share on other sites

  • 4 weeks later...
  • 3 weeks later...

Lo mejor sera volver con XAMPP, que por lo menos tienen una comunidad de soporte. Aqui @Ric ( que es el unico desarrolador) se habra hartado de tanta tonteria de @olajideolaolorun, que despues de mas de dos años solo aparece para decir sandeces.


The best will be back with XAMPP, which at least have a support community. Here @Ric (who is the only developer) will have been fed up with so much nonsense of @olajideolaolorun, that after more than two years only appears to say nonsense.

Link to comment
Share on other sites

  • 1 month later...
  • 8 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...