Looks like if I disable my security plugin, then the error does not occur,
but I still get the 500 error. Looks like my initial issue is related to the
import plugin.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255477,255488#msg-255488
___
*New Development*
The core php error logs are below, but the site specific error logs show
this. The memory on my php.ini file is :
memory_size 1024;
so it's not php's memory limit. I've also disabled all my plugin's, so it's
not the memory limit that is on my security plugin.
2014/12/13 16:12:
so, the forking command is not a bug. The PHP process stopping 100% due to
the child being killed is the fundamental problem.
Why or how I am still unsure. Any ideas anyone?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255477,255478#msg-255478
___
I am having troubles with a wordpress plugin running a full batch of
imports. I get this error when I enable the nginx debug. The result is I get
an immediate 404 error afterwards and I am unable to fully import my data.
I am pretty sure this is a bug, but I can't find the right answer to fix
it.
I am having troubles with a wordpress plugin running a full batch of
imports. I get this error when I enable the nginx debug. The result is I get
an immediate 404 error afterwards and I am unable to fully import my data.
I am pretty sure this is a bug, but I can't find the right answer to fix
it.
