server code: 504 error and similar – solution
-
Hello,
(thank you for the great plugin!).
After I’ve seen this error for the first time today trying to use it on a different server than usual type, it was impossible to run the installer (step 2 were it unzips the archive and import the database).
It was stopping after the unzipping (but this may vary).
I’ve seen that many others have the same problem with some hosting providers, while it is not present with others.
As we have full control over the server we had a chance to discover what is the problem, so this may be of help to you to fix it (if possible at all) – but you can reproduce it easily.
The difference was LVE and it’s default limits. The kandidates IMO are:
EP (which was 20) (Max number of processes)
NPROC (100) (Max number of processes within LVE)
IO (1024KB/sec) (IO throughput – combines both read & write operations)Most probably it is the last one. An archive of just 100MB would make the script to work 200 seconds and it times out at some point because of some other web server watching module.
I hadn’t have time to try which one exactly is the reason for timeout, but when set all to unlimited the problem was solved. Bad news is that regular hosting users can’t force providers to change those settings for their accounts..
Good luck.
- The topic ‘server code: 504 error and similar – solution’ is closed to new replies.
